Doesn’t W3C already maintain the ActivityPub protocol?

Edit: nevermind I misunderstood this

Probably performance - the Java server takes up a lot of memory and CPU for what it does. The base implementation first started in 2011, so it wasn’t exactly designed to be multithreaded or parallelized because most games were still largely single-threaded at the time. Rewriting it from scratch in a different language probably helps with that

… and are keeping the hate to the appropriate boards (X, I believe it’s called nowadays). Should we contract his work and apply it where applicable?

There is no “appropriate board” for hate speech, whether it’s antisemitism, transphobia, or anything else. If you wouldn’t want someone to be a nazi in your office, why would you pay them if you know they’re a nazi somewhere else? Is it fine as long as it’s someone else’s problem?

On another level, if you had to pay a developer, and you have reason to think they might donate the money you give them to an antisemitic cause, or directly use it to fund their own antisemitism, would you still want to give them that money? Or maybe look elsewhere, even if it means getting something slightly worse?

Somehow this post has negative down votes and I’m all for it.

Pretty interesting how the number of active users per month has been fluctuating up/down but the number of comments and posts per month has been steadily going up

Isn’t servo mostly a Mozilla-led project? I thought servo would probably just replace gecko as the engine firefox used if it ends up succeeding

Someone already did that a bit ago with a bunch of fireworks and I think it worked?

But you’ll use AIs? I don’t think they are much better

I’d say it is (was? It’s been ~a year and a half since I used it consistently but I’m guessing it hasn’t changed too much since then) moderately left by US standards but definitely not progressive left - you don’t have to go very far to find thinly-veiled sexism/racism/homophobia, though that might just be because a large portion of the people there are terminally online in a bad way. That being said, there are definitely also communities ranging from conservative to hardcore conservative as well but I actively tried to avoid those so I didn’t really see them in my feeds. The same is true with progressive communities but they tended to drift away from being actually progressive once they got to a certain size.

Tears of the Kingdom storyline has entered the chat

That’s entirely fair for the usecase of a small script or plugin, or even a small website. I’d quickly get annoyed with Python if I had to use it for a larger project though.

TypeScript breaks down when you need it for a codebase that’s longer than a few thousand lines of code. I use pure JavaScript in my personal website and it’s not that bad. At work where the frontend I work on has 20,000 lines of TypeScript not including the HTML files, it’s a massive headache.

This is the case for literally all interpreted languages, and is an inherent part of them being interpreted.

It’s actually the opposite. The idea of “types” is almost entirely made up by compilers and runtime environments (including interpreters). The only thing assembly instructions actually care about is how many bits a binary value has and whether or not it should be stored as a floating point, integer, or pointer (I’m oversimplifying here but the point still stands). Assembly instructions only care about the data in the registers (or an address in memory) that they operate on.

There is no part of an interpreted language that requires it to not have any type-checking. In fact, many languages use runtime environments for better runtime type diagnostics (e.g. Java and C#) that couldn’t be enforced at runtime in a purely compiled language like C or C++. Purely compiled binaries are pretty much the only environments where automatic runtime type checking can’t be added without basically recreating a runtime environment in the binary (like what languages like go do). The only interpreter that can’t have type-checking is your physical CPU.

If you meant that it is inherent to the language in that it was intended, you could make the case that for smaller-scale languages like bash, Lua, and some cases Python, that the dynamic typing makes it better. Working with large, complex frontends is not one of those cases. Even if this was an intentional feature of JavaScript, the existence of TypeScript at all proves it was a bad one.

However, while I recognize that can happen, I’ve literally never come across it in my time working on Typescript. I’m not sure what third party libraries you’re relying on but the most popular OAuth libraries, ORMs, frontend component libraries, state management libraries, graphing libraries, etc. are all written in pure Typescript these days.

This next example doesn’t directly return any, but is more ubiquitous than the admittedly niche libraries the code I work on depends on: Many HTTP request services in TypeScript will fill fields in as undefined if they’re missing, even if the typing shouldn’t allow for that because that type requirement doesn’t actually exist at runtime. Languages like Kotlin, C#, and Rust would all error because the deserialization failed when something that shouldn’t be considered nullable had an empty value. Java might also have options for this depending on the serialization library used.

As a TypeScript dev, TypeScript is not pleasant to work with at all. I don’t love Java or C# but I’d take them any day of the week over anything JS-based. TypeScript provides the illusion of type safety without actually providing full type safety because of one random library whose functionality you depend on that returns and takes in any instead of using generic types. Unlike pretty much any other statically typed language, compiled TypeScript will do nothing to ensure typing at runtime, and won’t error at all if something else gets passed in until you try to use a method or field that it doesn’t have. It will just fail silently unless you add type checking to your functions/methods that are already annotated as taking in your desired types. Languages like Java and C# would throw an exception immediately when you try to cast the value, and languages like Rust and Go wouldn’t even compile unless you either handle the case or panic at that exact location. Pretty much the only language that handles this worse is Python (and maybe Lua? I don’t really know much about Lua though).

TLDR; TypeScript in theory is very different from TypeScript in practice and that difference makes it very annoying to use.

Bonus meme:

Rust is only huge because it doesn’t have an ABI. If you had an ABI (and didn’t have to compile every single dependency into the binary) the binary sizes would probably drop a lot to the point where they’re only slightly bigger than a C counterpart

Edit: I don’t know if Go has an ABI but they also include a runtime garbage collector in their binaries so that probably has something to do with it.

We’re already on the 6th generation of folding phones though

What priorities are there? I’m talking about emotions, not actions.

You can feel bad for both the children of this guy that will now grow up without a father and the millions of people he harmed at the same time. I’m not even saying I feel equally as bad for his children as his victims’ children (because losing a parent to a preventable death due to insurance is objectively a worse situation). All I’m saying is it’s reasonable to feel sympathy for both. It’s not like the kids had a choice in what their dad did.

It isn’t impossible to feel bad for both?

You can feel bad for his family while also not feeling bad about his death. Losing a loved one is hard regardless of how much money you have. That doesn’t mean it wasn’t ultimately a net positive (although I’m doubtful that UH will actually change any policies because of this)

There were plenty of good shows in 2023 though? Even excluding Frieren and shonens (since I’m assuming based on what you said, you aren’t interested in them) there was also Apothecary Diaries which aired during the same season. Oshi No Ko was pretty good also (the first episode is by far the best, imo the rest of the show is still pretty good tho). Those definitely stood out the most to me but I did enjoy a lot of the 2023 shows I watched.

Honestly chapter 3 was way worse to me at first. I hate those red dustbunny things and I swear they made the timing specifically so that I would constantly run into them and I hate it.