throwawayish

Usually this happens when the system crashes/otherwise terminates during system upgrades. Kinda hard to boot if /sbin/init is a link to an empty file.

"win 7 and older"? There are still plenty of configuration dialogues that have only seen the slightest of changes since Windows NT 4.0; I'm not exaggregating.

Windows is easily the most visually inconsistent OS out there -- even in comparison to a Linux desktop. That has it reasons of course, many features are in there that didn't need any kind of update in the last 15+ years, therefore their UI was never updated to conform to updated guidelines and so on.

Ok, but what about having a S.H.I.E.L.D. for earth? Wouldn't that work?

These numbers match so accurately that I'd say they are throttled.

In most parts of Europe 3-phase is the standard. Neither high-leg delta nor split phase have significant deployment outside North America.

That being said, in household use the per-household balancing between the phases is usually very poor (e.g. all lightning on one phase). Overall the balancing turns out ok across the grid, but the meter doesn't see that. So this is a very relevant condition for household meters.

The hash tree (Merkle Tree) is only part of it. The proof-of-work and consensus / voting protocols are the other (main) part.

There are also the Elbrus processors which I believe are entirely designed in Russia, although some models are manufactured by TSMC (and some are manufactured in Russia).

The early models implemented a proprietary VLIW architecture with enterprise-y features (like hardware-tagged pointers, probably borrowed-ish from Itanium) with a dynamic binary translation layer for x86 compatibility on top, not sure if they still do that or perhaps the other way around now.

Some UEFI implementations even call themselves BIOS :-)

Anyone trusting a computer - any computer - is a giant fool in my book. Trust is a strong word, and computers suck balls fundamentally at keeping information safe.

> Obviously, Java has shown that you can survive without a macro pre-processor. That was even a point Gosling+Co made in a white paper I read way back in the day. But I do believe that if you are going to have a macro processor, it should be an expedient. Rust's macro processor is not expedient. It is its own impediment.

Annotation Processors (iirc Java 1.5) are clearly a form of a pre-processor. It's not macros / textual expansion, though.

Similarly C++ mostly gets along without macros since it contains a capable meta-programming system -- and I think this is the more important point here; for many tasks meta-programming is just a handy thing to have. Dynamic languages don't have that problem, since their runtime is their meta-programming system as well.

You a very much mistaken in your assessment.

System76 is neither OEM nor ODM. In fact, they are not a manufacturer at all - they assemble and ship systems designed by others.

Exactly the opposite is correct. ICC generated code whose runtime dispatch looked at "Are we running on Intel? Select fast path. Not running Intel? Select generic i386 path."

http://www.agner.org/optimize/blog/read.php?i=49#49

Actually no, enabling external cache coherency (eg. QPI) incurs a significant cost in terms of pin count, power, die space and clock speeds. The same does not transfer to ECC memory.

The IMC in almost any Intel CPU also could do ECC, but on most consumer SKUs there's that pesky little configuration flag set by the factory telling it not to. Why? Because Intel can, that's why.

I don't know why you're being downvoted, your comment is accurate. Consumer hardware traditionally does not support registered memory, which is (reg ECC) the standard for server hardware hence cheap, while unbuf, unreg ECC is rather rare. AM4/Zen is no exception, no DDR4R for consumers.

ECC is not complex to implement.

> So the board seems to accept ECC memory, hopefully that means the memory controller actually performs ECC? I found a reddit comment claiming that the boards accept ECC memory but don't perform error correction[1].

This is set up by the firmware (BIOS). Since we all already know that quite some of these still have issues (unsurprisingly, it's a new platform), it isn't far-fetched at all that current firmware doesn't quite do the right thing with certain memory sticks.

Note that this is unbuffered, unregistered ECC memory, which is usually more expensive and less available than the standard server memory (DDR3R / DDR4R), which is NOT compatible with any consumer CPUs.

> GovCloud is open to non-governmental customers

Some excellent naming there ;)

FreeBASIC is actually still around ... and used ...

... for whatever reason ...

Depending on legislation it's also not legal for lawyers to give specific advice for free. E.g. in Germany lawyering is a rather heavily regulated business - for obvious reasons - and while there's a whole bunch of exceptions (as usual) in general a lawyer cannot give legal consult for free.

> They also sell a step-up model whose main difference seems to be that it is made of stainless steel. What will the Germans think of next?

Only stainless steel tools on stainless steel work pieces and vice versa. Don't mix stainless/non-stainless tools and non-stainless/stainless work pieces. Hence stuff like screw drivers will be needed in both variants.

Not a myth: Kotlin is the better Java

Although Kotlin does have a lot of stuff that technically allows to write weird code, most of that (eg. extensions) is around for better interfacing with Java, and normally not used in pure K code.

JavaScript is typed as well.

> But the amortized O(1) lookup of hash tables is hard to beat.

On the other hand: the performance characteristics of trees are much easier to predict.

And in many cases a HT lookup isn't distinguishable from a tree lookup, at least if it's a dedicated application data structure, like some index or so.

I feel like HTs are very good for smaller structures (excellent example: dictionary/hashtable-based interpreters), but for larger data structures (e.g.: indices) ... not so much.

> Is there a good, general, incremental rehashing scheme?

Trees.

If you think regular GPU drivers are shitty, then wait until you try to install both AMD and nVidia drivers at the same time. It's not very stable, to say the least (Windows 7). Never tried it since. Not worth the hassle.

Resistive losses are only a part of the total loss on a transmission line.

The Phenom X6 had great performance both in terms of price and actual performance for developer / thread-heavy workloads. Although this is now ~seven years ago.

Oh. I'm European and I always wondered why in practically every American criminal-spy-scifi-investigative-themed TV show or movie there are people sitting at magical, proprietary computers able to find strange pieces of (personal) information in no time (but obviously always complex to use, because other characters don't know how).

I didn't know about the "Bloomberg Terminal" before, but now that makes a lot more sense where that idea comes from.

Well you have up to 16 cores fighting over one 64 bit memory bus.. so this is mostly aimed at packet-processing and filer workloads I'd say.