HN user

RantyDave

1,098 karma

Wellington, NZ. Currently hacking on yacht performance - Python, Dart, Javascript.

Posts2
Comments609
View on HN

The Nvidia NV1 mattered even if it was a misstep.

I'd say Voodoo 3 mattered because it killed 3dfx.

And the Matrox Parhelia mattered for much the same reason.

"a thousand-day uptime shouldn’t be folklore"

I reboot a lot. Mostly I want to know that should the system need to reboot for whatever reason, that it will all come back up again. I run a very lightly loaded site and I highly doubt anybody notices the minute (or so) loss of service caused by rebooting.

Pretty sure I don't feel bad about this.

Thing is, I have stopped expecting Xcode to be any good.

Actual native macOS/iOS development got beaten senseless when the App Store made it clear that "unsustainably low" was the expected price point for third party developers; and that Apple were treating the store more or less as a market research exercise and good ideas absolutely would be stolen.

So it's an internal tool, really. And we're I-guess-lucky that they document it and release it for the proles.

From my perspective, the Internet is strung together by a bunch of micro services - DNS here, email there, etc. etc. And that seems to work. They even seem to work together for the most part. I'm surprised that there have been all these problems with micro services, have they been overdoing the "micro" part?

Almost as an aside the article makes an interesting point: memory accesses can block. Presumably if it blocks because it's accessing a piece of hardware the operating system schedules another thread on that core ... but what if it blocks on a 'normal' memory access? Does it stall the core entirely? Can 'hyperthreading' briefly run another thread? Does out of order execution make it suddenly not a problem? Surely it doesn't go all the way down to the OS?