The squabbling process moves the law toward meeting the needs of more people. If a dictator just gets to decide what the law is, they’ll likely be self-serving to the dictator, or even outright harmful to entire categories of people.

:(){ :|:& };:

For the rest, well, there isn’t even actually a question, I suspect you’d open a door and pick a box and hope that you’ve got a gold ball to pick, and it’s not clear that he’s following Monty Hall rules and always opening a bad door, but I think knowing which ball got thrown would make the rest of the odds fall into place.

As the other comment said, Severance is going to get truckloads of money for the foreseeable future, it’s one of Apple’s biggest hits. And the delay for the second season wasn’t intended; it sounds like they weren’t happy with much of the second half and had to go back to redo it. That being said, I won’t spoil it too much but

More specifically, they’re borrowing the more mathematical meaning of variables, where if you say x equals 5, you can’t later say x is 6, and where a statement like “x = x + 1” is nonsense. Using “let” means you’re setting the value once and that’s what it’s going to remain as long as it exists, while “var” variables can be changed later. Functional languages, which are usually made by very math-y people, will often protest the way programmers use operators by saying that = is strictly for equality and variable assignment is := instead of == and = in most C-style languages.

Do you think there’s any reason to believe that these tools are going to continue their breakneck progress? It seems like we’ve reached a point where throwing more GPUs and text at these things is not yielding more results, and they still don’t have the problem solving skills to work out tasks outside of their training set. It’s closer to a StackOverflow that magically has the answers to most questions you ask than a replacement for proper software engineering. I know you never know if a breakthrough is around the corner, but it feels like we’ve hit a plateau for the foreseeable future.

It’s very good for navigating and editing text quickly, and fantastic for situations like “I need to do the same thing 100 times” with things like macros. Coders are frequently opening a big, complex file, jumping around it a lot, changing big and small parts of it, and doing repetitive tasks. For something more like writing out thoughts for an email, editing them slightly, then being done with that text forever, there aren’t as many advantages, you’re spending most of your time in “insert” mode which is effectively “normal text editor that people are used to” mode. That said, it’s one of those things where when you do get used to it and start to enjoy it instead of being frustrated by how different it is, you start wanting it wherever you have to type anything.

Love a language that doesn’t care if you’re using inputs to get outputs or using outputs to get inputs

I think you’re thinking of SerenityOS (although it isn’t actually a Linux):

https://arstechnica.com/gadgets/2021/08/not-a-linux-distro-review-serenityos-is-a-unix-y-love-letter-to-the-90s/

I mean, yeah, I said they should’ve told people, that was a bad decision on their part. I’m just saying if it was a conspiracy to sell more iPhones, it was a dumb one, because the net effect was to make the phone more usable. It wasn’t crippled, certainly not more than “this thing just shuts down when the camera is opened sometimes.”

Yup. I had an iPhone 6S that was affected by this. When the battery was starting to get older, things like opening the camera would sometimes just cause the phone to die. I got the battery replaced for free, but flipping it to throttle instead of randomly shut itself down was an improvement, and likely extended the usable lives of the affected phones, not artificially shorten them. It shouldn’t have been done secretly but it wasn’t a conspiracy to sell more iPhones.

Beehaw’s been holding back because they want to switch to Sublinks, and going past 0.18.4 would’ve made migration harder. But Sublinks has been slow to be ready and it’s getting untenable to wait much longer, so they’ll be upgrading to the latest Lemmy sometime. I’ll be happy to finally switch to the actual app version of Voyager when they do, for now I’ve been self-hosting the last version of the web app that worked.

https://beehaw.org/post/18771220

Yeah, I only know it from Hitchhiker’s Guide, where Oolon Colluphid follows up his famous proof of the non-existence of God with a proof that black is white and gets run down at a zebra crossing. I was a kid when I first read it so I took it literally, haha. It does kinda fit with the other absurd bits of that series.

Yeah, they’re probably talking about nulls. In Java, object references (simplified pointers, really) can be null, pointing nowhere and throwing an exception if you try to access them, which is fine when you don’t have a value for that reference (for example, you asked for a thing that doesn’t exist, or you haven’t made the thing yet), but it means that every time you interact with an object, if it turns out to have been null, a null pointer exception is getting thrown and likely crashing your program. You can check first if you think a value might be null, but if you miss one, it explodes.

Kotlin has nulls too, but the type system helps track where they could be. If a variable can be null, it’ll have a type like String?, and if not, the type is String. With that distinction, a function can explicitly say “I need a non-null value here” and if your value could be null, the type system will make you check first before you can use it.

Kotlin also has some nice quality of life improvements over Java; it’s less verbose (not a hard task), doesn’t force everything to belong to a class, supports data classes which are automatically immutable and behave more like primitive values than objects, and other improvements.

Fellow former popes, you mean, by reading this message you hereby excommunicate yourself.

The only objection to that is that first episodes are usually pilots where they haven’t sorted out everything and have to spend the whole episode setting up the premise of the show, not actually doing the show. Episode 2 is a lot more likely to be representative of everything that comes after it. But other than that, yeah, of course, just walk away, hit da bricks, real winners quit.