Dunno why you're being downvoted. It's very obviously deliberately chosen to make 12 year olds giggle.

One of the things I hate about merge-based Git workflows is git makes a default Merge 123234234 from user/dave/fsdf message which:

a) Is shit - it contains zero useful information (what's in the change??) and contains information you explicitly don't care about (the temporary branch name the author happened to use). a) Makes people think they are supposed to use that message.

It would probably be better if the default message was blank. But also squash & rebase is generally better anyway and it avoids this problem entirely.

Almost everyone uses Cargo. I think the only people that don't are Google and Facebook who will probably be using Bazel or Buck2. I think you're a bit confused about what Cargo is.

you can write perfectly safe software in it.

In the same way that you can safely walk through a minefield.

I dunno what you mean about it being an expressive language either. I would say it is relatively low on the expressiveness scale compared to something like Python or OCaml. It's basically as expensive as Go which is renowned for being unexpressive. Maybe you didn't mean "expressive".

The biggest problems with gRPC are:

1. Very complicated. Way more complexity than you want in most cases.
2. Depends on HTTP 2. I've seen people who weren't even doing web stuff reach for gRPC, and now boom you have a web server in your stack for now reason. Compare to Thrift which properly separates out encodings, transports, etc.
3. Doesn't work from the web. There are actually two modifications to gRPC to make it work on the web which means you have three different incompatible versions of gRPC with different feature sets. IIRC some of them require setting up complex proxies, some don't support streaming calls, ugh. Total mess.

Plain HTTP can be type safe. Just publish JSON schema or Typespec files or even use Protobuf.

Yeah depends on what you're using it for. CSV is terrible in many many ways but it is widely supported and much less complex.

I would guess if you're considering Parquet then your use case is probably one where you should use it.

JSON is another option, but I would only use it if you can guarantee that you'll never have more than like 100MB of data. Large JSON files are extremely painful.

Ha I once googled some question, found a great answer in some random forum and was like about to write a reply saying what a great answer it was when I realised it was me, like 10 years ago.

I'm not sure hardware-based full disk encryption counts as a "highly specialized requirement". It's enabled by default on Android, iOS, Mac and even Windows usually. It's a basic requirement for businesses.

It doesn't sound like it's difficult, just extra work that they don't want to do.

For example they might want to use native USB instead of libusb which is LGPL. I've done that in the past because libusb was lacking some features. It means you have to implement your USB code for each platform and doing that work for Linux probably isn't worth it, even if it isn't difficult.

FOSS is the only answer. Fuck capitalism. Fuck paid software.

Grow up. FOSS is great but it obviously isn't the only answer.

It was shit and GitHub is good. It's not a mystery. It's still shit compared to GitHub, you can go and look now.

There was also an incident where they started adding malware to downloads... But really it was already dead by that point.

I don't think I would call this functional. Python is decidedly not at all functional - there's no way to declare arbitrary functions inline, no chaining of map/filter etc.

But the static types are definitely welcome. I didn't know about the type keyword. Apparently it makes it support forward references.

It does. x-x == 0 is true unless x is NaN or infinity.