I have to imagine these types of features are for people who treat chatgpt like their friend/therapist/girlfriend/assistant/... instead of people who use it to answer questions
Do people have good experiences with LMDB, in terms of reliability? I've never used it in production, but I've read through the code and design documents for a database implementation class.
I remember some strange code (such as pushing return values 4k above the stack, with a comment like "this works as long as the caller doesn't use more than 4k of stack space before accessing the return value"), and the author also shared some unconventional opinions about undefined behavior (like "Compilers are deterministic, if I know what platform I'm compiling to then no behavior is undefined. And if compiler authors disagree, they are morons.")
But presumably it's thoroughly tested, so those aren't problems in practice? Would be really interested to hear from people who've actually used it. I've mainly stuck to SQLite instead.
When the lobbyist in question heard "private server" they just jumped to saying "those are illegal". Perhaps she got confused between private servers offered as part of the game and reverse-engineered community servers? Or she was caught up on thinking about ToS-breaking servers for some reason?
For what it's worth, the mentioned community servers that Microsoft is fighting are those that allow gambling or selling in-game advantages for real money. That's been against Minecraft's ToS since 2014 (pre Microsoft acquisition), but enforcement has always been difficult.
What is really bizarre is the ESA doubling down after the hearing. Maybe they just don't want to admit their vice president got something so wrong in front of the senate?
10+ gigabit serial connections (Thunderbolt, USB 3.2/4 DisplayPort 1.4, HDMI 2.1, etc) are limited to 1 or 2 meters on passive copper cables. You need optical for anything longer (or a hot, power-hungry transceiver, like for 10GBaseT ethernet)
It's a bit slice if you put it in a packed struct.
I like them, they're nicer than C's bitfields: The order isn't implementation-defined, and the types remember their range rather than being converted to a power-of-two size upon read. (Maybe that's possible with C23 _BitInt(n), I haven't tried if those work in bitfields)
Different situations call for different responses.
When someone steals a watch, we force them to give it back. Yet when someone steals a cake and eats it, we don't force them to puke it back up.
If you pirate a movie, the court might very well force you to delete all the copies you made of the movie you downloaded, destroy DVDs you burned, etc.
Using crates.io is entirely optional, you can download a library's source code and specify the path to it in your cargo config file. (Which is not uncommon in production)
For that matter, using cargo is optional, you can compile rust code using GNU make or shell scripts if you want to. (That's what the Linux kernel does)
8 billion people running a 2000 watt AC continuously for 8 hours a day = 5 trillion watts of heat. (Only the electricity consumed by the AC is turned into new heat. The heat from inside the house would have moved outside anyway, at the same rate, since it's an equilibrium)
The sun = 175 quadrillion watts of heat.
So I would say, the heat from running ACs is not significant. It's also additive with all the other existing forms of energy use we have. Unlike greenhouse gases, which are multiplicative.
Yes it is control flow, but IMO it's not hidden. It's true that you need to learn that * happens before + (which usually happens in school), but I don't see how that's any different from needing to learn that `and` short-circuits, or that `if` only evaluates its body if the condition is true.
Compare to what people usually call hidden control flow (exceptions, RAII, ...) where you don't know which parts of the code will run unless you read the definitions of the classes and bodies of the functions you use. The syntax at the call site is not enough to tell.
From what I remember, it was specifically chosen (among other reasons) because of experience with the JVM, where it was difficult to verify bytecode type-safety due to unrestricted jumps and branches.
So the choice was made to put the burden of regularizing the control flow on the compilers at compile time, rather than the browser engine at website load time. Which seems rational to me.
US still has the second amendment and the most guns per person of any country in the world (more than 10x the average), yet I don't see anybody "fight back against the benefactors"