Have any keywords I could search for about the OGL mess? I remember it being stagnant for a while, but I don't remember any of the details.

This is me being naiive, but if it's a stationary, land-based installation, do you really care if you need flywheels that are 20x as massive as comparable Li batteries? A slug of iron's gotta be a lot cheaper than a mountain of lithium, right?

net energy consumption was pretty negligible

As long as you have infinite empty cars uphill :)

The docs roughly say, "POSIX is crufty and a bad API, we're not afraid to not implement those parts in order to get a cleaner interface".

Okay, but what does this new API look like instead? Will the features enabled by these not-implemented APIs be reimplemented in some other, cleaner fashion? Or will that functionality just not be provided at all?

Question from a layman: Do GPUs have a physical-virtual memory mapping? Ex: Could process A get space on the GPU, then when process B requests memory, the GPU would give process B the physical pages process A used to have (while copying the actual data over) to defragment the physical pages, leaving B with a copy of what A used to own? Or, perhaps process B requests so much memory that the texture space requested by process A gets paged out to main memory?

That's true. I wonder what the $/kg for mining lunar He3 compares with building a ton of nuclear bombardment facilities works out. Not that any of it is at all practical anyway...

1) the vast majority of earth helium is He4, which has some undesirable properties for fusion

2) even if it was all He3, there's not a lot of helium. He is light enough that it simply floats away from the earth

Isn't that the 80/20 rule? I know I'm guilty of doing the "exciting" stuff on little libraries, then when it comes to the bits like packaging/documentation/etc.., putting it off to "later". It's just not as fun to do those little maintenance stuff as it is the neat parts

Keeping up w/gimp a little bit, I know they were working on library-izing the codebase a few years ago. Did that ever get done?

If it's strictly browser-based, chromecast sticks (not the boxes) should work. Google is advertising that use, no less.

I learned Java way back in the 5 days. Obviously things have changed since then (and I was much less experienced). What examples are there of "the right way" Java applications?

For instance, is there a performant HTTP server/proxy that keeps pace with something like nginx whose source I could browse to see the state of the art?

People don't magically create software where there isn't a gap to fill (fucking about user interfaces excepted of course).

Everything systemd aside, that's not true. The NIH-syndrome is alive and well. Instead of working on and improving existing software, a LOT of people want to start from scratch just so they can have their braces in the place they like to see them. For instance, I was poking around with protobuf earlier and saw that there are five javascript bindings.

And if you install your CA on the machines, you can still use a local caching proxy.

The straight sections help focus the beams down into tighter bunches

He was saying you don't have to cast