ilkkal

Thanks for the blinding insight.

Fascinating stuff, I've never really thought about what problem e.g. frameworks are solving. It's kind of too bad that in my day job my head's in the clouds and usually somewhat removed from most of these system level details.

inb4 it's just someone else's computer -- trust me I know

I guess regular religious fervor just isn’t what it used to be.

Primary cooling could be molten salt or liquid metal but unless you take the power out through the Seebeck effect like RTG’s on space probes, you still need water to make steam for turbines, I guess.

At this point, why care about Twitter?

To me this is the weirdest thing about Pantone the company, their products etc: so much trouble to try to make sure that for a fleeting moment some knick-knack produced half a world away looks like it did on the designer’s expensive monitor. Then, time happens.

Is the world better off than if we just eyeballed it?

> the end of that bell-curve

A "bell end", if you will.

I was a consultant working on two Meego projects at the time, fancy mechanics and some pretty interesting ideas about graph data storage and inference. Super talented crew of diverse hackers, kind of a tech head dream project thinking back on it now. This all was such a gut punch. I always thought they should have just rallied behind their own OS, but I don't claim to understand the business all that well.

(edit: a highlight was getting to meet Dan Ingalls once; he was cool)

Sure, but it’s incredibly naive to see gh having problems and go “they must not know what they are doing”

Got a big chuckle out of them describing server-side rendering as this new-fangled unproven technical risk of a technology :) I get the context, but it was still funny. Ah, back to editing index.php I guess.

The RUN? I thought about that but I don’t see how that would work. Or is the argument that Dockerfiles are just too hard?

(An argument I’m not unsympathetic to)

I’m sure it’s usually just a case of “thinking while typing”, but I find it surprising how often articles about Docker stuff get some basic details a bit wrong. In the very first code example there is a RUN instruction where the author probably meant to have a CMD instruction, and they talk about BuildKit and build cache optimisation even though that was always something to think about, way before BuildKit was a thing.

I’m not trying to say I know everything or that the article is wrong or bad, but it’s an observation I’ve made.

Sparrows are history these days, but even more modern weapons can be defeated. It’s a lot about knowing what your weapon’s perf envelope is, and what the other side has to throw at you, and defending appropriately.

"The Fine Comment" and "Article", respectively. Sometimes another adjective is substituted, by angry people.