1/2 pound (225 g)

What kind of insanity is this a pound is 500g.

2 cups (390 g) rice

Your cups weigh 195g a piece? Reasonable for stoneware, I guess. But why are you telling me and what does it have to do with the mass of rice?

The German standard is to write out everything up to 12 and as English also doesn't say one-teen and two-teen that's how I always did it. (why not tenty-one btw? be consistent your numbers are all weird)

So can any TLD holder. The rules for .org might change to disallow individuals. .com might outlaw non-profits. .net might get restricted to ISPs. There is a small, but existent, chance that all the oxygen molecules in the room I'm in are going to decide that they'll huddle up in some corner, leaving me to suffocate. I refuse to worry about it.

If you want to be paranoid like that you can send the rust foundation some money and tell them to spend it on the .rust and .ferris gTLDs.

That the CPU should be called by a single aspect they can’t actually handle!!! That’s moronic.

People literally use the word "literally" to mean figuratively. It doesn't make any sense. One might even call it moronic.

But it's the way it's done. Deal with it.

1. The whole article overall lacks sources.
2. That section is completely unsourced.
3. It doesn't say what you think it says.

You were arguing the definition of "X-bit CPU". We're not talking about "X-bit ALU". It's also not up to contention that "A 64-bit integer is 64 bit wide". So, to the statement:

Also, 64-bit central processing units (CPU) and arithmetic logic units (ALU) are those that are based on processor registers, address buses, or data buses of that size.

This does not say which of "processor register, address buses, or data buses" applies to CPU and which to ALU.

Obviously 64 bits means registers are 64 bit, the addresses are therefore also 64 bit,

Having 64 bit registers doesn't necessitate that you have 64 bit addresses. It's common, incredibly common, for the integer registers to match the pointer width but there's no hard requirement in theory or practice. It's about as arbitrary a rule as "Instruction length must be wider than the register size", so that immediate constants fit into the instruction stream, makes sense doesn't it... and then along come RISC architectures and split load immediate instructions into two.

otherwise it would require type casting every time you need to make calculations on them

Processors don't typecast. Please stop talking.

As I stated it’s MORE complex today, not less, as the downvoters of my posts seem to refuse to acknowledge.

The reason you're getting downvoted is because you're saying that "64-bit CPU" means something different than is universally acknowledged that it means. It means pointer width.

Yes, other numbers are important. Yes, other numbers can be listed in places. No, it's not what people mean when they say "X-bit CPU".

claiming that new CPU architectures haven’t increased in bit width for 30 years is simply naive and false, because they have in many more significant ways than the base instruction set.

RV128 exists. It refers to pointer width. Crays existed, by your account they were gazillion-bit machines because they had quite chunky vector lengths. Your Ryzen does not have a larger "databus" than a Cray1 which had 4096 bit (you read that right) vector registers. They were never called 4096 bit machines, they Cray1 has a 64-bit architecture because that's the pointer width.

Yes, the terminology differs when it comes to 8 vs. 16-bit microcontrollers. But just because data bus is that important there (and 8-bit pointers don't make any practical sense) doesn't mean that anyone is calling a Cray a 4096 bit architecture. You might call them 4096 bit vector machines, and you're free to call anything with AVX2 a 256-bit SIMD machine (though you might actually be looking at 2x 128-bit ALUs), but neither makes them 64-bit architectures. Why? Because language is meant for communication and you don't get to have your own private definition of terms: Unless otherwise specified, the number stated is the number of bits in a pointer.

People who don't understand bees and think that the queen is ruling the hive -- if the queen can't swarm then they're going to dispose of her and raise a new one. All you're doing is weakening the hive without actually preventing it from swarming. You might even kill it off.

You let them swarm, you let them get their rocks on, and you also have a nice property ready for them to settle back into.

The Intel 80386DX did NOT have any 80 bit instructions at all, the built in math co-processor came with i486.

You're right, I misremembered.

And in that regard, the Databus is a very significant part, that directly influence the speed and number of clocks of almost everything the CPU does.

For those old processors, yes, that's why the 6502 was 8-bit, for modern processors, though? You don't even see it listed on spec sheets. Instead, for the external stuff, you see number of memory controllers and PCIe lanes, while everything internal gets mushed up in IPC. "It's wide enough to not stall the pipeline what more do you want" kind of attitude.

Go look at anything post-2000: 64 bit means that pointers take up 64 bits. 32 bits means that pointers take up 32 bits. 8-bit and 16-bit are completely relegated to microcontrollers, I think keeping the data bus terminology, and soonish they're going to be gone because everything at that scale will be RISC-V, where "RV32I" means... pointers. So does "RV64I" and "RV128I". RV16E was proposed as an April Fool's joke and it's not completely out of the question that it'll happen. In any case there won't be RV8 because CPUs with an 8-bit address bus are pointlessly small, and "the number refers to pointer width" is the terminology of <currentyear>. An RV16 CPU might have a 16 bit data bus, it might have an 8 bit data bus, heck it might have a 256bit data bus because it's actually a DSP and has vector instructions. Sounds like a rare beast but not entirely nonsensical.

Hier in .sh, im späten letzten Jahrhundert, war das durchaus ähnlich aber auch stark Lehrerabhängig, von Zeit zu Zeit gab das da mal einen gläubigen. Im großen und ganzen mehr entspannte Ethik und mal über Moral nachdenken als irgendwas Christliches damit ist die Kirche (will sagen EKD Nordelbien) auch absolut einverstanden. Dann der Schock im Konfirmationsunterricht: Da sah das nicht anders aus. Solange du die nicht direkt fragst reden die halt nicht über Theologie, es geht darum was Leute tun nicht was sie glauben, und was sie sonst so sagen könnte im großen und ganzen auch von Humanisten kommen.

Katholischen Unterricht gab's theoretisch, aber nicht praktisch (im Prinzip null Nachfrage) nach etwas rumstôbern auf den Seiten vom Erzbistum Hamburg hat man halt seine Schulen -- in HH und MV, nicht SH -- und ist offen gegenüber ökumenischem Religionsunterricht, übersetzt in's Deutsche: "Wir wissen dass ihr eure Kinder zu den Lutheranern schickt und werden euch dafür nicht exkommunizieren".

Konfessionellen Islamunterricht gibt's nicht, das Land bietet aber ueberkonfessionellen Islamunterricht an genauso wie Ethikunterricht. Meinerzeit gab's beides noch nicht da hatte man entweder Religion oder frei, was sicherlich auch dazu beigetragen hat dass das der Unterricht in der Regel entspannt war ansonsten wären doch alle gleich weg sobald sie 14 werden und selbst aussuchen können.

2+3: Try to fetch image, if you get it proxy it, if your storage gets full use LRU eviction, once evicted or some amount of time has passed delete it and don't fetch again, ever. Fall back to pure 3 if there's ever any issues with anything, including you not particularly feeling like implementing smart caching: Our referrer privacy is not your responsibility.

There's no non-reference designs of Radeon PROs, I think. Instincts, even less. If the ranges bleed into each other they might actually sell reference designs down into the gamer mid-range but I admit that I'm hand-waving. But if, as a very enthusiastic enthusiast, you're buying something above the intended high-end gaming point and well into the pro region it's probably going to be a reference design.

And as a side note finally they're selling CPUs boxed but without fan.

I wonder, what is easier: Convincing data centre operators to not worry about the power draw and airflow impact of those LEDs on the fans, or convincing gamers that LEDs don't make things faster?

Maybe a bold strategy is in order: Buy cooling assemblies exclusively from Noctua, and exclusively in beige/brown.

Kodak isn't dead they're just not dominating the imagining industry any more. They even multiplied, there's now Kodak Alaris in addition to the original Kodak.

Between them they still are dominating analogue film which still has its uses and it could even be said that if they hadn't tried to get into digital they might've averted bankruptcy.

There's also horse breeders around which survived the invention of the automobile, and probably also a couple that didn't because their investments into car manufacturing didn't pan out. Sometimes it's best to stick to what you know while accepting that the market will shrink. Last year they raised prices for ordinary photography film because they can't keep up with demand, their left-over factories are running 24/7.

And modern X86 chips are in fact NOT 64 bit anymore, but hybrids that handle tasks with 256 bits routinely, and some even with 512 bits, with instruction extensions that have become standard on both Intel and AMD

On a note of technical correctness: That's not what the bitwidth of a CPU is about.

By your account a 386DX would be an 80-bit CPU because it could handle 80-bit floats natively, and the MOS6502 (of C64 fame) a 16-bit processor because it could add two 16-bit integers. Or maybe 32 bits because it could multiply two 16-bit numbers into a 32-bit result?

In reality the MOS6502 is considered an 8-bit CPU, and the 386 a 32-bit one. The "why" gets more complicated, though: The 6502 had a 16 bit address bus and 8 bit data bus, the 368DX a 32 bit address and data bus, the 368SX a 32 bit address bus and 16 bit external data bus.

Or, differently put: Somewhere around the time of the fall of the 8 bit home computer the common understanding of "x-bit CPU" switched from data bus width to address bus width.

...as, not to make this too easy, understood by the instruction set, not the CPU itself: Modern 64 bit processors use pointers which are 64 bit wide, but their address buses usually are narrower. x86_64 only requires 48 bits to be actually usable, the left-over bits are required to be either all ones or all zeroes (enforced by hardware to keep people from bit-hacking and causing forwards compatibility issues, 1/0 IIRC distinguishes between user vs. kernel memory mappings it's been a while since I read the architecture manual). Addressable physical memory might even be lower, again IIRC. 2^48^B are 256TiB no desktop system can fit that much, and I doubt the processors in there could address it.

I wouldn’t consider a country that cannot manage its own power supply “successful.”

Like, dunno, the US? Over here we don't have a word for "brownout" and don't get me started on Texas.

I'd be eating popcorn over here in Europe if I wasn't busy facepalming. The US is enforcing secondary sanctions on Cuban gas imports for buying from Venezuela while making no such moves for Russian energy exports. The US is enforcing crippling sanctions on Cuba while being chaps with Vietnam. It's plain as day that the US' approach to Cuba has nothing to do with the stated policies but Cuba daring to declare independence, not willing to be a banana republic. They got over the domino theory (which made them intervene in Vietnam), they never got over Bacardi and United Fruit (nowadays Chiquita) losing their slaves. That's where the term "banana republic" comes from, btw: Chiquita's slave plantations.

Heck, the US is perfectly willing to shoot themselves into the foot over cigars: A couple of years ago someone in the Eurozone ordered Cuban cigars from a Danish trader, all perfectly legal. Because that involves two different currencies the banks needed to convert stuff, and standard practice between the banks involved happened to be to clear everything via USD. The Americans intercepted the payment, the whole thing made the press over here, and the EU instituted regulations to stop banks from clearing via USD, which they started to do way before the regulations came into effect because they didn't want to deal with that kind of pettiness, either. Lest you think the US cares about the status of the USD as reserve currency, evidently stopping some random European from smoking Cuban cigars is more important.

It's pathetic. The US is acting like a spoiled brat miffed that it can't light the neighbour's dog on fire so they're buying up all the shelters in the neighbourhood and setting those on fire. That's the approximate level of maturity on display, here.

I expect them to merge enthusiast into the pro segment: It doesn't make sense for them to have large RDNA cards because there's too few customers just as it doesn't make sense for them to make small CDNA cards but in the future there's only going to be UDNA and the high end of gaming and the low end of professional will overlap.

I very much doubt they're going to do compute-only cards as then you're losing sales to people wanting a (maybe overly beefy) CAD or Blender or whatever workstation, just to save on some DP connectors. Segmenting the market only makes sense when you're a (quasi-) monopolist and want to abuse that situation, that is, if you're nvidia.

I've had phones newer than the first RAZR that didn't have bluetooth but it's been a while and bluetooth is incredibly cheap -- in fact it probably comes for free with the GSM module, just needs the right software the hardware is already capable of doing it. Separate bluetooth modules (ESP32) cost what 1.30, antenna, maybe ten cents.

That's about trying to not have things flooded, and saving lives. It's not about replacing your home or restaurant.

That said there's nothing whatsoever stopping Italy from having a public-law insurance company. Stuff doesn't need to be profit-oriented to provide insurance and unlike with health insurance, it's actually reasonable to expect people to risk-manage in the sense that if you insist on building a house at the bottom of a valley, yeah flood insurance is going to cost quite a bit more than if you build it 30m up.

Unlikely, and even more unlikely to not be able to be worked around by a local rust user group.

Like, the .eu restriction to only give out domains to individuals and companies within the EEA is more about having a domestic contact than anything else, EURid doesn't care who actually uses the domain just that it has European legal representation.

Pre- and post-increment are only really useful when you're doing C-style looping and there's a good reason we don't do that in Rust.

I actually honestly can't recall ever making an off by one error in Rust, I'm sure when implementing specific data structures or when doing pointer manipulation it's still a possibility but you can write a gazillion lines of code without ever running risk of that particular annoyance. Also while C folks may have an argument regarding operator semantics, C++ folks don't they're doing unspeakable things to <<.

Also, FWIW Haskell uses ++ to append lists and therefore also strings. It's not like it's an odd-ball usage of the symbols, that'd be .. which I vaguely remember some language using. Would cause a whole new class of confusion regarding 'a'..'z' vs. "a".."z". Not to mention that "aa".."zz" actually makes sense as a range all that's missing is &str: Step. Probably not a good idea to have built-in because do we mean printable ASCII? Whole unicode range? Just the alphabet? Not an issue when you're doing it to single chars but strings get ambiguous fast. Does Rust even guarantee stuff about Char ordering C certainly doesn't really do that, short of I think 0..9 being contiguous.