998 karma · joined August 5, 2014
You do not want extra weight on your rocket. Every bit of non-fuel weight you add means you have to add extra fuel, and the extra fuel to carry the extra fuel along with any extra tank needed for the extra fuel. It gets bad fast.
It just isn't worth it when you can just add that weight as fuel that normally doesn't get used. Ideally would dump in the ocean (which you cleared) so it didn't matter (much).
I mean, it seems like it should be but
* Hydrogen really likes to leak.
* Hydrogen breaks down the container holding it over time.
* Hydrogen is very low density. This means you need either a very large container or very high pressure. Combined with 1 and 2 this is going to be expensive.
I'm really asking the question. I would love to know the full cost difference with current tech vs other options.
9-14% seems comparable IMO and worst case roughly half he mentioned 1000 lbs.
The video of the natural form of this showed what appeared to be some very wet slime that was fully exposed to the open air. I'm guessing extra water requirements to keep this mass wet for the bacteria would be prohibitive at modern farming scales.
Most node code I see in the wild is just a simple `await loadData()` which doesn't block the main node thread but does block that code flow until the data returns. This is roughly the same as what would happen in a normal blocking multithreaded language other than the extra overhead of a thread. If you don't have enough threads (or they are efficent enough in your language of choice) for this overhead to be an issue then you are adding all this complexity for almost no benefit.
Basically it comes down to if you trust your language of choice's threads more or less than your language of choice's event scheduler. Since Node is fully single threaded there isn't really an option but with other languages, a single thread per worker is much simpler.
In python it is even more opaque which to use as the CPython itself is singled threaded so you are comparing its thread implementation to its event scheduler implementation. For this small win you get to rewrite all your code to new, none-standard apis.
They certainly didn’t care enough to make electrify America good.
This is no different then offering coupons to more ‘cost sensitive’ buyers
The time it got me was a thread just to timeout another process. Tests worked great but the timeout didn't work in production because the call it was wrapping was calling out to C code so nothing would run until the call returned. We even still got the timeout error in the logs and it looked like it was working (it even tossed the now waited for valid results), but not at the time of the timeout but after the call finally returned a few hours later.
Go and C# are not systems languages. Maybe a stretch goal at best.
At normal levels the 3x gets lost in the exponential to much light we get at night.
I have to agree with the Optional hate. I loved it in Scala but after a few months on Kotlin I don't think I can go back.