Similar to you, 95% of the time I do the simple use case that I've memorized. The problem is that even after a decade of using Git, when I get into those 5% where something goes wrong, I have no idea how to actually solve it. None of it makes any sense in my head, and I have to search for a bunch of magical commands to run, or nuke things to get back to a good state.
With JJ, it just makes sense. It's intuitive and clear. I have been able to recover without any help. Just the undo alone is basically a life saver. Rebasing and merge conflict resolution is so much simpler.
Yes I probably won't use it to its full potential, but still, the little I do use makes 10x more sense than Git ever did.
I don't understand why the fact that it's an Airbnb really matters here? Unless a large number of apartments are meant to be empty, why does it matter if the tenant is short term or long term? Is it that short term users leave and enter their apartment more often?
I am of course just speculating (and I had a lot of waiting time to think about this), but there are a lot of people with a lot of luggage constantly going in and out. It makes the elevators be full faster (perhaps there is a weight based sensor to determine if the elevator is full, and the luggage tricks the system into thinking the elevator is not full yet, because a piece of luggage is lighter than a person but sometimes takes up more floor space than a person). Furthermore, people with luggage take longer to get in and out.
It's a tower in Kuala Lumpur btw. Since it is rather hot here and the elevators are not airconditioned, it's extra uncomfortable.
TIL that there are countries where the building code doesn't enforce the minimum number of elevators. In Russia it's one for buildings taller than 5 floors, two for taller than 9, and I believe three for taller than 16 (every 20-something-floor building I've ever been to had at least three). But we don't have many skyscrapers so I'm not sure how it works for those.
Amusing anecdotes and musings about your stay (well, amusing to read, probably not to live).
Since you’ve got a bunch of enforced idle time, maybe see if you can find the architect firm and see if you can get the backstory? Why three elevators in a 60 floor building? Just low level sadism, or what?
Because they are short-term and many are staying just for the day + bringing family (like kids, which is why they use AirBNB instead of a hotel). The check-in/check-out already add an entry-exit if the user is staying 24 hours only.
It’s not super common to stay in one place only 24h when traveling with kids. Other than the luggage, tourists and residents move in an out of the building just the same. People who live there also need to go to work or school every morning, and come back in the afternoon creating choke points. And these people are there every day, not a handful of seasonal tourists.
The problem is probably the same as every other super tall building. It was impressive for the potential buyers but designed poorly and this only became apparent after they lived there a while (crappy elevators, probably often defective, building sway, plumbing issues, etc). So the owners started to move out and it’s possible the building is mostly short term rental now.
Isn't another issue that most successful open models are distilled from closed models, but closed models are putting more and better safeguards against distillation?
No? The only different between these robots and a washing machine is that in theory, the robot is generalist and can do many tasks, whereas a washing or laundry machine can only do one task. You can still in theory fully control what task the robot works on. Also, in theory, the robot would be the glue between all the other machines, like filling up the washing machine, then moving it to the dryer, etc. It deciding what to do isn't a "prerequisite" for the robot.
SpaceX has had 165 launches in 2025 (although admittedly 75% of those were for Starlink...) Obviously bigger isn't more economical or sensical, and most cases are served just fine with the Falcons, but there are cases we need the big boy for, and it's good that someone is working on it and has made so much progress.
Obviously a semblance of a schedule is good to have, but realistically, that's not really how research works. Look at James Webb telescope, it was originally scheduled for 2007, and ended up launching 14 years later. It's still an amazing piece of engineer/science, and it's amazing that it's up there now, even if it was very late to it. It's much better to be late and successful than early and failing.
> but there are cases we need the big boy for, and it's good that someone is working on it and has made so much progress.
I am taking issue with this claim. Are there cases where the cost/benefit actually come out favorably for Starship as it is actually turning out? Are they cases anyone should actually care about beyond sci-fi fantasies (i.e. not "colonize Mars")?
Sure, I have crappy mobile reception a lot of times on my travels, so I'll be the first when finally Starship can launch satellites with antennas big enough so that my mobile phone can directly be used for internet access.
Even better, since everything is well organized, you can add `opacity: 0.7` to `.wall` specifically, and get something that looks almost exactly like how old school wallhacks looked like.
A wall hack is any technique allowing the player to see opponents through walls. Googling for screenshots or videos should give you a good idea of how it looks.
Sometimes I'm developing an internal tool or something only for myself / handful of people. I'm perfectly fine saving time and complexity using a one liner modern CSS solution instead of having to rely on some hacky unreadable code to support 10 years of legacy browsers.
Atuvos one at 1.6mm and UGreen one at 1.7mm are great, though one time battery is annoying. There are some that have wireless charging, though thicker.
Similar to you, 95% of the time I do the simple use case that I've memorized. The problem is that even after a decade of using Git, when I get into those 5% where something goes wrong, I have no idea how to actually solve it. None of it makes any sense in my head, and I have to search for a bunch of magical commands to run, or nuke things to get back to a good state.
With JJ, it just makes sense. It's intuitive and clear. I have been able to recover without any help. Just the undo alone is basically a life saver. Rebasing and merge conflict resolution is so much simpler.
Yes I probably won't use it to its full potential, but still, the little I do use makes 10x more sense than Git ever did.
reply