gcau

Hate this. The Apple magic keyboard is my favourite keyboard (least amount of travel/force, for speed and to be easy on my hands/wrists), and I'm paying a yearly license for a software (magic utilities) to remap the keys properly on windows. On a Mac, forget about remapping them, it doesn't work.

>just about _any_ excuse will get you out of the fine

Hilariously wrong, and if it were true it defeats the purpose of making it mandatory.

I find it hard to believe this comment isn't sarcastic. Apple's software, atleast in particular macos, is horrendous - to the point I ditched my m2 macbook for a thinkpad because of how bad it was. It's like a toy OS.

If they're intentionally causing the customer to have an unspendable balance, knowing that it's making them $200m/yr, how is that not fraud (or some kind of crime)? I'd expect atleast CA would do something about it.

I shouldn't have to explain this, but a letter is a medium of communication, that could just as easily be written by a LLM (and transcribed by a human onto paper).

If I have a VPS, what should I be running on it to replace github actions? (eg run tests, return pass/fail to github PR)

The poster you're replying to is plain wrong, using "class" is ubiquitously common in the javascript/typescript world, it's the idiomatic way to create classes, and it has better semantics than trying to use prototypes. You might compile away the class keyword for compatibility, though.

The 'rewrite it in lua' crowd are oddly silent now.

I'm a big fan of react, but all the server stuff was a cold hard mistake, it's only a matter of time before the (entire) react team realises it, assuming their nextjs overlords permit it.

Yea, I don't want something trying to emulate emotions. I don't want it to even speak a single word, I just want code, unless I explicitly ask it to speak on something, and even in that scenario I want raw bullet points, with concise useful information and no fluff. I don't want to have a conversation with it.

However, being more humanlike, even if it results in an inferior tool, is the top priority because appearances matter more than actual function.

>Maybe a kid managing to struggle through a shitty school has to work harder

It sounds like you think admissions should be based on how hard people think they worked relative to others.

I'm not sure if they meet the requirements for being a terrorist group or if I agree with them being considered terrorists, but I just want to point out the name of the organisation isn't a valid argument in favour of them, the actions of the organisation matter a lot more than the name, for example on many occasions they've used violence to prevent people from political speech (is that antifascism or fascism?)

Humans are imperfect and anyone can make mistakes, yes. I would argue there's different categories of mistakes though, in terms of potential outcomes and how preventable they are. A maintainer with potentially millions of users falling for a simple phishing email is both preventable and has a very bad potential outcome. I think all parties involved could have done better (the maintainer/npm/the email client/etc) to prevent this.

"'such' a phishing attack" makes it sound like a sophisticated, indepth attack, when in reality it's a developer yet again falling for a phishing email that even Sally from finance wouldn't fall for, and although anyone can make mistakes, there is such a thing as negligent, amateur mistakes. It's astonishing to me.

This is a nice article. I'm trying to make a map save file format. I'm curious if most developers usually use abstractions over bitflags(safely hiding away the bitwise operators from being typod, etc). My main niggle is I want maximum type safety and compile time checking, ie the compiler preventing me from accessing a bit that isn't being used or mixing things up. My other concern is also backwards compatibility if I want to modify the flags. Saving 2 bits for the version?

I want a kind of tree structure of bitflag values, and I'm trying to think of a good way to do it. For example a Grass /Stone tile, maybe 4 bits for the tile type (0001 = Grass), and then from that point forward, the remaining flags depend on the tile type (Grass having the next 2 bits for the grass colour, stone having 1 bit for whether it's cracked or not, etc), but in a safe and efficient abstraction where I can't accidentally mix them up. I don't want a pirate software monstrosity where I can't keep track of the different combinations.