I started from a similar background in school. Learning from books in the library and coding on a sheet of paper. Opportunities to get that in a real computer was hard to come by. Some teachers helped by pitching in to get me a few hours in the school lab. Those who like it start learning well before the resources become available. You don't need to wait till UG to gain those skills.

That said, how often do you see kids these days using a real general purpose computer suitable for coding? Like a desktop or laptop? Not phones, Chromebooks or tablets. In fact, it's bewildering these days to see programming tutorials start with a statement saying that you need such a device. It was a given, back in the day. And the other stories here don't paint a good picture.

I didn't know that. That single reason alone is enough to completely exclude discord from open source projects.

I thought they were talking about Discord. Discourse should rename itself for its own sake. It's easy to get it confused with the two junk.

That is extremely annoying. Hate it when it happens.

That's not the case for open source projects. There are many projects that use Discourse as their primary support channel. There seems to be no dearth of users asking questions there.

The gold standard of threaded conversations is Zulip.

It's bloated, filled with features no one needs for straight-forward work, has a somewhat obtuse UI and is buggy as hell. I don't like Matrix much more than Discord. But even it has far fewer problems. I don't know in which universe Discord is considered as 'good'.

Using phone numbers as second factor authentication is neither secure, nor is it in good faith. Force the customer to use something more anonymous and secure - like Fido keys or even TOTPs. Sneaking in ways to force the customer to reveal their personal details, in the name of security is a sinister dark pattern.

Ooh! I'm surprised that somebody made the same conclusion, but from a different perspective.

Fish's main attraction was never its scripting language - it was its UI. You can run bash scripts from fish (using bash of course), while still enjoying its bit more modern UI. Bash was never a challenge to fish. Nushell, on the other hand, is a different case.

The impression that I got is that while there is nothing more to port in the shell itself, the performance and concurrency goals haven't been fully realized yet. The new Rust code needs a bit more tuning before it can replace the old shell.

Mailing lists aren't that hard if you have the right tools. For most people, it's just a few lines of configuration. But there are a lot of hidden tools for emails that you simply don't get with PR workflow. You'll get very attached to them once you start. That's the reason why many kernel devs are so attached to emails.