The level that they managed to fit everything inside of a simple-looking package was so high that the CEO of ULA (the Boeing/Lockheed Martin rocket company) thought they were lying when they first showed pictures [1].
The reason he was so skeptical is that for other engine manufacturers, there are generally different teams working on different parts of the engine, and because Convay's law the final artifact generally ends up looking like the organizational boundaries of the company that made it, with cleanly separated parts for every sub-organization that you can see in the final assembly. One of the things that SpaceX is good at is optimization across these kinds of boundaries, integrating hardware in ways that would be difficult for a more traditional organization.
The way it was explained to me early on was that the newest Raptor engines had simply eliminated many of the different types of test sensors, specifically because sufficient testing had been performed that they weren't getting useful data out of them any more.
That photo is thrown around a lot in the Spacex fan community. At least it was. I think the photo is at least two years old.
I suspect that many of those pipes are for testing instrumentation of the early models. And those that remain necessary, might be built into channels in the engine body now, like how a carburettor is built. That's much simpler and cheaper to manufacture and maintain, not to mention more reliable.
The TVC is clearly visible on one of the center engines in that photo, thank you. It's just about the only thing on there other than the thrust chamber, turbopumps, and bell!
It seems like running with sandbox-exec should remove pretty much all the potential for an app to cause harm… is there a reason why it’s not the default, especially for these certificate-less apps?
Just checked. Still needs it. I don't have Rosetta installed and I don't want to install Rosetta just to be able to use a game controller with DuckStation or Aethersx2. When I can also connect a PS4 controller and not need any of that.
This appears to only be in the Steam beta - the version available for download still requires Rosetta. There doesn't seem to be a direct download for the beta - you have to opt into it after installing Steam.
Mobileye still sells to a large fraction of manufacturers (I think a plurality if not majority). You will still get variation in implementation, as Mobileye only does the sensing side, and the integration is done by the OEM.
Tons of consultants are missing expertise in their clients' wheelhouses. The client and consultant each have domain knowledge, and when those domains overlap, there might be conflicts.
If you hire an architect to redo your house, it's fine to say "I see where you're going with this thing for my kids, but I know them and they will never go for it."
I think the issue comes with unknown unknowns. Before Fukushima someone might have said the same thing you just have, but a new disaster still came along and caused a lot of issues. I am still bullish on nuclear, but I think waving away concerns might do more harm than good.
Fukushima was a known risk though, they just never bothered to fix the problem. Plus just being planned in the 60s meant the initial design was born only about 15 years after nuclear power was invented. Fukishima was like driving around in a Model T, being told original brakes and tires and lack of seatbelts were unsafe, but still being regularly driven down busy roads without bothering to upgrade those features.
I may agree with your conclusion that old plants are safe enough (or at least take a deep dive study to see if their expected externality is worse than whatever would replace them). However:
> the worst disaster to ever happen without any external factors
The problem is external factors happen. You can’t just raise your hands up and say “wasn’t my fault,” when they do. A tsunami washing over a solar farm would be a lot safer than what happened at Fukushima.
The Fukushima quake was a truly extraordinary outlier though!
4th biggest quake ever recorded in history hit at the exact spot where the tsunami could overpower the protective wall at the reactor. Yet nobody died from the radiation.
Meanwhile the 20k people who died in the tsunami are forgotten. No one demands we stop building cities by the ocean.
TreeSitter is an amazing tool but is (purposefully) quite limited compared to an IDE--it doesn't even cross file boundaries, so go to definition is a non-starter. Zed uses LSPs like Rust Analyzer to fill that role.
Alacritty is already pretty performant (relative to a lot of the other terminal emulators), but my read is Ghostty has been going hard over performance/standards/protocols (like Kitty).
I did consider that. I remember nope-ing out of alacritty in the early days after seeing the developers response to people requesting a scrollback buffer. It amounted to something like "I use tmux, and if you don't, you use the terminal wrong." It left a bad taste in my mouth.
Ligatures are a renderer issue, so using alacritty as a lib wouldn't have this issue (it does demonstrate their hardline stance). Another example that would translate is how long it took them to support disambiguation of key combinations: https://github.com/alacritty/alacritty/issues/6378 (2019-2023). Of course, the maintainers are free to do whatever they want with the project - but such things do make alacritty-as-a-lib an exceptionally bad choice for situations where you want things to just work.
I suspect you may be operating in "Restricted mode," aka it doesn't know if it can trust the directory. In that mode, the main tools like Rust analyzer are quite restricted. All of your complaints should be resolved once Rust Analyzer/basedpyrite are up and running.
I do think they should have a more obvious warning that the current directory is untrusted, right now the little green warning in the corner is way too unobtrusive and will result in many people having the same issue as you.
The level that they managed to fit everything inside of a simple-looking package was so high that the CEO of ULA (the Boeing/Lockheed Martin rocket company) thought they were lying when they first showed pictures [1].
[1] https://www.benzinga.com/news/24/08/40279896/spacex-presiden...
reply