At some I added logging to a thread pool, when it gave up on child-threads, it would be logging things like

"Child 123 is being aborted"

Not the best of phrasing for people that didn't know what that was about...

When I stopped, subversion was what we used. I’m trying to understand Git, but it’s a giant conceptual leap.

It's probably not 'that much of a leap' as you imagine. If you're looking at Git tutorials, they're usually covering all kinda complex scenarios of how to 'properly use Git'. But a lot of people barely care about 'properly using Git' and they just kinda use it as a substitute for SVN... You create branches, you merge them back and forth, and that's about it.

Like if you want to contribute to an open source project, all you have to do is create a fork (your own branch in SVN terms) - commit some stuff to it, and create a pull request (request to have your changes merged) back to the original branch. git pull is just svn update - getting someone elses commits

Not saying there aren't more complex features in git, or that learning git properly isn't worth it, just saying, I don't think you have to see it as a 'giant conceptual leap' that's preventing you from jumping back into programming. Easiest approach just to get started would be probably to just download a GUI like Sourcetree or Fork, and you just kinda pretend you're still using SVN - approach wise

I would assume this just relies on the Discord API being read by the bot - and not on having a local discord installed...

Just wait until she learns child processes get aborted

Rebasing is for noobs.

git reset head~42
git push -f

and, perhaps more critically, some Chinese GPU makers from utilizing CUDA code with translation layers.

Like that ever deterred China from violating copyright claims to trademarks. Maybe if they're huge companies that want to export, but if they're just making in-country chips, especially if it's useful for the Chinese government, these companies are not going to change anything based on some license warning

Well Lemmy is Rust - Plus Lemmy is already an alternative for Reddit, so all the "normies" are still on Reddit - So Lemmy itself is already a bit of a niche sample size.

Rust developers are already known (/memed) to be elitist about Rust - and "Java is Bad" is also just the general consensus among developers, especially ones using more niche languages

Semi-relevant: dotnet had an experiment a couple weeks ago to see whether green-threads (virtual, non-kernel threads) would be a better alternative to the async / await model:

https://github.com/dotnet/runtimelab/issues/2398
https://github.com/dotnet/runtimelab/blob/feature/green-threads/docs/design/features/greenthreads.md

The downside of async C# code is in that developers must decide which methods need to be async. It is not viable to simply make all methods in the program async. Async methods have lower performance, limitations on the type of operations that they can perform and async methods can only be called from other async methods . It makes the programming model complicated. What color is your function is a great description of this problem.

The key benefit of green threads is that it makes function colors disappear and simplifies the programming model. The green threads should be cheap enough to allow all code to be written as synchronous, without giving up on scalability and performance. Green threads have been proven to be a viable model in other programming environments. We wanted to see if it is viable with C# given the existence of async/await and the need to coexist with that model.

[...]

Conclusions and next steps

We have chosen to place the green threads experiment on hold and instead keep improving the existing (async/await) model for developing asynchronous code in .NET. This decision is primarily due to concerns about introducing a new programming model. We can likely provide more value to our users by improving the async model we already have. We will continue to monitor industry trends in this field.

Edit: the amount of downvotes you get for saying something unpopular without being violent or abusive is showing the lack of guts to discuss something in a civilized manner. Shame on you.

People aren't discussing this because "try to sue in this case" is just an absurd concept - but okay.

Who are you going to sue and for what? His concept of recognition is just "getting his code into the kernel"? He could have written a blog post in the context of “How I found a bug in the Kernel and helped fix it” - He did contribute, he did the QA part and the diagnosing part, thats contributing.

But his post with the sentiment of "I did it all for nothing!" makes it seem like the goal was to get "recognition" and get his code into the repo... The goal is just to fix bugs, and he did contribute to that

Yea, I was thinking the same. I have the JetBrains toolbox, and already have these installed:

• Rider
• RubyMine
• PyCharm
• GoLand
• CLion

I don't really get why they need to make 10 different IDEs for every language, instead of just consolidating everything into a single UI/IDE.

For pricing it doesn't make that much sense, anyone that wants more than 2 JetBrains products is better off buying the entire toolbox.

Suggestions for being able to recreate your own websites:

• Own local backup
• Copy from Wayback - https://web.archive.org/

YIKES... This shows the importance of keeping backups in a different cloud, or on-premise or something - and not trust one provider with your entire company / website

Personally I don't have any problems with it (if that was directed at me) - I've added 418 as "unhandled exception code" response to a bunch of applications, so I can easily differentiate whether my application is throwing an error, or whether it's some middleware gateway AWS io-thing

I was just curious what OP thought about it, since in the early days it wasn't uncommon to add goofs or easter-eggs into software, but nowadays not done so much... and apparently the "HTTP Working Group" doesn't like it either... So I was curious whether OP though in hindsight whether it should've been added or not