That's... not how hashes work. 🤦‍♂️

The UK is definitely going to try to ban VPNs. Some MPs are already talking about it.

I would add this to the Wikipedia page for .mu, so at least other people don't use it. You can site this discussion as a source.

Sure, but there are a gazillion forum websites already. I'd just use an existing one. The one D uses is the best I've ever used. I think it's actually written in D, which is a very niche language but way nicer than Ruby.

Ah makes sense, thanks.

Wow, that activated some seriously ancient neurons... I just looked up some of the models it supports and surprisingly they were made within the last decade. For some reason there's still a market for cheap dedicated MP3 players.

I guess they cost basically nothing to manufacture and some people might need them...

But don’t you loose polymorphism?

No. You'll have to be more specific about what kind of polymorphism you mean (it's an overloaded term), but you can have type unions, like int | str.

Your points 1-3 are handled by running the code and reading the error messages, if any

Not unless you have ridiculously exhaustive tests, which you definitely don't. And running tests is still slower than your editor telling you of your mistake immediately.

I probably didn't explain 4-6 well enough if you haven't actually ever used static types.

They make it easier to navigate because your IDE now understands your code and you can do things like "find all references", and "go to definition". With static types you can e.g. ctrl-click on mystruct.myfield and it will go straight to the definition of myfield.

They make the code easier to understand because knowing the types of variables tells you a lot of information about what they are and how to use them. You'll often see in untyped code people add comments saying what type things are anyway.

Refactoring is easier because your IDE understands your code, so you can do things like renaming variables and moving code and it will update all the things it needs to correctly. Refactoring is also one of those areas where it tends to catch a lot of mistakes. E.g. if you change the type of something or the parameters of a function, it's very easily to miss one place where it was used.

I don't think "you need to learn it" really counts as slowing down development. It's not that hard anyway.

I can understand the appeal for enterprise code but that kind of project seems doomed to go against the Zen of Python anyways, so it’s probably not the best language for that.

It's probably best not to use Python for anything, but here we are.

I will grant that data science is probably one of the very few areas where you may not want to bother, since I would imagine most of your code is run exactly once. So that might explain why you don't see it as worthwhile. For code that is long-lived it is very very obviously worth it.

I'm not sure I agree. I think most people can understand recipes or instruction lists and totally could program, if they wanted to and had to. They just don't want to and usually don't have to. They find it boring, tedious and it's also increasingly inaccessible (e.g. JavaScript tooling is the classic example).

But I think mainly people just don't find it interesting. To understand this, think about law. You absolutely have the intellect to be a lawyer (you clever clog), so why aren't you? For me, it's mind-numbingly boring. If I was really into law and enjoyed decoding their unnecessarily obtuse language then I totally would be a lawyer. But I don't.

After Dorsey sold Twitter to Elon Musk, selling the platform out to the far right for a crisp billion-with-a-“B” dollar payout, the FOSS community shouldered the burden – both with our labor and our wallets – of a massive exodus onto our volunteer-operated servers, especially from victims fleeing the hate speech and harassment left in the wake of the sale.

That is a very weird way of putting it. Like Mastadon et al didn't want more users? That's not at all the response I remember.

It's sooo sloooow though.

Those days never existed. Even the first iPhones were like $500 and that was over a decade ago.

These prices are very high but phones last a lot longer than they used to and are improving a lot slower. I just bought a Pixel 8 for £400 which (accounting for inflation) is about the same price as we used to pay for three old Pixels and even Nexuses.

E.g. the Nexus 4 which was considered "mega cheap" was £279 for the 16GB model, which is £390 in today's money.

They're clearly going for price differentiation based on the model year, but you really don't need the latest model to have an amazing phone any more.

Without static type annotations you can only make best effort guesses that are sometimes right. Better than nothing but not remotely the same as actual static types. The LSP you linked works best when you use static type annotations.

Also I would really recommend Pylance over that if you can - it's much better but is also closed source unfortunately.