Don’t most YouTubers make more money with their own sponsorships than from YT ads? Can we start the mass migration to PeerTube already?

I love that the EU is cracking down on tech, but I also wish the US government could get in on that awesome rake.

Not exactly. I’m talking specifically about being able to call axum::serve with non-Send futures.

I’m not sure what tokio (or axum) can do to avoid the trait bounds. Would it makes sense to provide a “share nothing” runtime implementation that can be injected at startup? I wonder how the intermediate layers (e.g. axum) would indicate that futures are usable by a more generic runtime which may or may not need Send + 'static.

Without some way to write generic code for either runtime, the whole tokio ecosystem would end up bifurcated by this choice of runtime.

Rate-limiting could also be applied at the federation level, but I’m less sure of what the implementation would look like. Requiring filters on a per-account basis might be resource intensive.

Why resort to an expensive decentralized mechanism when we already have a client-server model? We can just implement rate-limiting on the server.

It seems irrelevant whether this person is using encrypted channels if they failed to maintain anonymity. If they distributed material and leaked any identifying info (e.g. IP address), then it would be trivial for investigators or CIs to track them down.

How exactly do you debug code when your build process is separate from your code editor? Having to compile my code, run it until I find a bug, then open it up in a debugger and start it all over sounds extremely inefficient.

There’s a lot of incorrect assumptions baked into this. While you may choose to invoke your debugger separately from your editor, many modern editors support the Debug Adapter Protocol (DAP). This is a protocol developed by Microsoft for VSCode, and the VSCode debugger is quite powerful. I’ve only used Visual Studio many years ago, but from what I recall, the VSCode DAP is essentially just as powerful. And if you’re not interested in VSCode, the Helix editor and probably NeoVim also support DAP.

how to make the transition from a Visual Studio user to a Linux programmer

You are also coming in with the constraint of programming in C++. For this specific language, I think I agree with others here that either CLion or VSCode+CodeLLDB are your best options today. Maybe after you get comfortable in the Linux environment, if you want to try something more keyboard-centric, install a Vim emulation plugin or even jump right into Helix or NeoVim.

Tidal is great but IIRC it either doesn’t support Amazon Echo or the integration is poorly implemented.

Do you think Valve is going to start deleting accounts over 100 years old?

Ah that explains it.

Are you kidding me? Clap has some of the best documentation of any crate.

Damn, the author sure knows how to ramble. No wonder they can’t make a game with Rust, they’re too busy talking about making a game.

If you’re going to actually give a useful critique, organize your thoughts into a succinct narrative instead of making a giant list of rambling bullet points.

Are you responding to my comment or just speaking stream of consciousness?

So… dev blames skill issues on language? Classic.

EDIT: For the record, I’m not saying the author is bad at Rust. I’m saying they’re bad at making games and balancing tradeoffs. They keep saying that they don’t like rust because they just want to worry about making a game, not fighting the language. And yet, they seem to continually make decisions that favor performance over ergonomics. Then they whine about how the Rust community is supposedly pressuring them to make bad decisions.

I assume this means that standard library locking primitives will not be usable in the kernel? What about atomic intrinsics?

They should compare defect rate with the Go teams. I’m curious if the advertised benefits of Rust’s type system give some practical advantage.

EDIT: Just watched the actual talk. Apparently they did this comparison, and found that Rust has fewer defects when compared to Go.

Cyclic reference-counted pointers are the most probable way to accidentally leak memory. But it’s a pretty well known anti-pattern that is not hard to avoid.

Sadly it doesn’t support reporting income from independent contracting (yet).

If the government cared at all about accessibility, then you’d be able to do your taxes in an HTML form.