Yeah it was inspired by Powershell. But it also has syntax that isn't completely awful.

Me too. I think announcing this is good - otherwise he'll get no feedback.

Did they ever explain the highly suss Chinese links? I've used this a bit and it worked well but I'm still not sure I fully trust it.

I think this strategy makes perfect sense and is really working.

Most of the open source community uses Linux or Mac for development. Windows is pretty much an afterthought. You even sometimes see "cross platform" projects that don't work on Windows.

But now that you can use WSL for all that development there's much less reason to use Linux in the first place. At my company we have a couple of hundred people using Linux, and we're considering all moving to Windows with WSL because the hardware support on Linux is just too unreliable - random crashes, laptops not going to sleep when you close them, poor thermals, bad memory management, etc.

It's not a mirror. It's the primary repository. And yes unfortunately they aren't accepting PRs or using it for issue tracking, but it's a start.

So... to store encrypted data that only the user can decrypt you don't need any fancy zero knowledge algorithms. Just have the user keep the encryption key.

For authentication you could use one of these algorithms. OPAQUE seems to be popular. I'm not an expert but it seems like it has several neat zero-knowledge style properties.

But probably forget about implementing it without a strong background in cryptography.

This totally might be true, but the fact that he got as far as measuring the same latency on X and Wayland... and then just gave up and is like "well never mind what the measurements say, it's definitely Wayland"... Hmm.

You gotta do the measurements. It's probably not even that hard, all you need is a USB mouse emulator (any microcontroller with USB peripheral support can do this and there are tons of examples) and a photodiode.

You don't even need to worry about display latency if you are just comparing X with Wayland.

Have a go on your free time and see if you like it. There is an absolute ton of free learning material online. You don't need to pay anyone.

Most programming jobs (e.g. making web sites) are easy enough for the average person to do, but I think most people would find programming far too tedious and boring to learn.

It's like law - there's nothing particularly difficult about it but most people find it incredibly mind numbing to read legal documents.

So I would have a go in your free time first to make sure it is something you could do.

Ok first impressions:

1. Rotate is Shift-Right-Click?? Very weird default choice. Most programs use middle-click.
2. I created a simple sketch with a couple of slots. Surprisingly smooth! Vastly improved from when I last tried it. Still not quite as good as SolveSpace for sketch creation, but to be fair SolveSpace was originally created to demo of a state of the art sketch solver... I couldn't find the Dimension tool, but guessed the shortcut was D, which was correct.
3. Extrude is misnamed as "Pad". Why?
4. Clone icon is a sheep :-D - actually the icons are all pretty great.
5. Cut is called "Pocket"?? Actually the icon for this is not great. Minor issue though.

I only made a very simple part, but I am impressed. This is significantly better than when I last tried it, when it basically didn't work at all. I haven't tried assemblies or anything complex (e.g. extruding up to a non-flat surface, degenerate geometry etc.), but definitely for simple tasks you could use it.

... in one benchmark.

Maybe not dumb but I've definitely been forced to at least partly learn a few terrible languages so I could use some system:

• PHP so I could write custom linters for Phabricator. Pretty successful. PHP is a bad language but it's fairly easy to read and write.
• Ruby so I could understand what the hell Gitlab is doing. Total failure here, Ruby is completely incomprehensible especially in a large codebase.
• OCaml so I can work on a super niche compiler written in OCaml. It's a decent language except the syntax is pretty terrible, OPAM is super buggy, and I dunno if it's this codebase or just OCaml people in general but there are approximately zero comments and identifiers are like ityp, nsec, ef_bin... The sort of names where you already need to know what they are.

A recent notable example is xz, but there’s also event-stream npm package a few years ago that got infected with Bitcoin stealing code.

They're asking if the entire project is somehow fake, not if it's a real project that got backdoored. That's obviously impossible to tell just based on stars, language quality, and similar heuristic signals.