I agree wholeheartedly - I've fought against refactors like this for the same reason. In the end readability is king, and jumping through 6 methods instead of one decreases readability quite a bit.

Isn't the primary benefit the lack of gravity?

You can reduce metals through vacuum pyrolysis at much lower temperatures without a reducing agent if you have a vacuum. This could make industrial scale processing of steel relatively easy on the moon.

Reducing ferric oxide to magnetite, perhaps, but I think if you tried that with ferrous oxide you'd get iron vapor coming off along with the oxygen.

An issue with any high temperature process is things start evaporating. This is part of why carbothermal reduction of aluminum oxide doesn't work: at the required temperature aluminum oxide is volatile.

(There are thermochemical water splitting technologies that exploit partially reducing transition or rare earth oxides at high temperature, then reacting them with steam at a bit lower temperature to make hydrogen. I believe cerium oxides are the current best approach there, although still not competitive.)

Remember that a large part of hiring is finding someone who fits in an existing team. A team that uses react won't appreciate someone choosing to use native DOM APIs instead of a react component.

In every React team I've been part of we've wanted to use as little react as possible and use native DOM apis when possible. React would be used purely for state management or interactivity.

I feel like teams that have used react enough learn that the less React you can use the better :) it's a great tool, but most teams use it because it's all they know and they don't know what they don't know about html.

Weird comment, I'm a web dev that has been using react for 10+ years and I prefer using native browser features whenever possible. I'd honestly avoid hiring framework specific devs because the skills required are never about just one single framework.

Also this is just all JS + HTML here, let's not act like it's impossible to learn the most popular frontend tool at the moment.

Eh. I build apps with Preact, but I prefer candidates who know the core web platform. They’ll be more apt to use the right tool for the job and not be baffled by edge cases.

I suppose just checking scroll height of the container? Once you're x pixels above the bottom, fetch more. Not the smoothest, but doable

No! Let's encrypt is easily the best thing that's happened for a secure internet the last 10 years.

If I set this up i would just run every service on the same machine sans jails. Are there any practical benefits to doing it like this? The extra complexity buys some slight measure of security in case one service is exploited, I guess?

Isolation is certainly one big reason to use jails. You also get independent management of dependencies, and can optionally share the base system.

They're somewhat similar to how you'd use Docker containers on Linux, but have different approach to security and networking.

If you use *BSD, you have to use jails, it's just law

Star gate zero point modules incoming?

There is a whole subcommunity of highly respected physics quacks like that one guy from Lockheed obsessed with propellantless propulsion. They are very much into zero-point stuff and how they do it is semi litho.

In the US, this is much the same thing

I'd frame it such that LLM advice is best when it's the type that can be quickly or easily confirmed. Like a pointer in the right (or wrong) direction. If it was false, then try again - quick iterations. Taking it at its "word" is the potentially harmful bit.

hahah nice one :D