1,291 karma · joined April 6, 2015
Fortunately, this is not universally true anymore.
There are now beers brewed with extremely low-alc yeasts (which have a trait that makes them unable to digest maltose) that make <0,5% alc beers with good flavours. This combined with sour malts and good hops can give you great flavours. These low-alc yeasts remove the need to maltreat the beer for removing the alc. And it is often OK to have 0,5% alc -- maybe not during pregnancy, but to avoid the annoying 5% alc. It's most probably not the industry cheap shit though.
There's also the possibility to just stop the fermentation with normal yeasts at any point, e.g., at 1% alc. I've had a couple of very good beers like this, too.
I mean, I can derive from the text that this can encode arbitrarily large integers. So what? What's the point? I also understand that this is for fun.
Just like in Iain Banks's scifi (although those AIs are actually intelligent -- I don't think you need that for a CEO).
And for APIs, you could reasonably well have turns or radians or degrees or even percentage of turns, whatever -- it depend on the context what is 'better'. What's really missing, I think, is the support of units in programming languages (in the type system) so that you cannot mess up when invoking sin()/cos(), because you would be forced to provide a unit.
This is really scary and it is progressing fast.
Some bus drivers do open the door on some such occasion, but they can really get into trouble if they are caught doing that.
To be clear, I do like 'outcounterexampled' a lot!
(Sorry, I'm a bit of a nerd. But I am sure you can cope with that.)
It is not a rumour, it is a plain public fact. Amthor's shady connection to Augustus Intelligence was revealed by a request using this law.
https://fragdenstaat.de/artikel/exklusiv/2025/03/union-will-... (In German)
It is important to understand that this is a C level problem: if you have UB in your C program, then your C program is broken, i.e., it is formally invalid and wrong, because it is against the C language spec. UB is not on the HW, it has nothing to do with crashes or faults. That cast from void* to int* most likely corresponds to no code on the HW at all -- types are in C only, not on the HW, so a cast is a reinterpretation at C level -- and no HW will crash on that cast (because there is not even code for it). You may think that an integer value in a register must be fine, right? No, because it's not about pointers actually being integers in registers on your HW, but your C program is broken by definition if the cast pointer is unaligned.
Ancient Greek spans several centuries of sound shifts and many dialects. It cannot easily be simplified into one specific pronunciation, particularly not one that is based on your specific dialect of English. Wiktionary has /kǎi̯/, /ˈkɛ/, /ˈcɛ/ and /ˈce/ for "καὶ".
internal reachability (from Germany to .de domains), too... :-)))
This is an explanation, not a justification.
(I don't want to shame Brazil, it's a global chain of problems. And other forests are decimated, too, like in Sweden and Estonia, for the demand of produce worldwide.)