starlevel003

https://vorpus.org/blog/notes-on-structured-concurrency-or-g...

answer: use Trio (or AnyIO if you're stuck in the asyncio land) and get sane cancel mechanics built-in.

That RFC is accepted, and this is starting to happen.

Progress has been disappointingly slow,

I don't think there's ever been a more concise summary of Rust.

This is HN, so the answer to that question should be very obvious.

we lived thousands of years fine without the FDA

For those thousands of years our only medicine was "ground up unicorn toe".

Man, I didn't realise HTTP alternatives were so serious.

Python does not use semantic versioning and never has.

Hopefully all that money goes into making the GTK file picker better

Right what we need is a requirements.yaml

It already exists, it's called pyproject.toml. It already existed for years in the form of setup.py. Requirements.txt means that projects can't be automatically installed which contributes massively to the difficulty of getting packages to work.

The proliferation of requirements.txt is one of the key reasons why Python packaging sucks so much.

That was a Simpsons episode. S9E22 Trash of the Titans.

You're not missing anything. WASM's primary purpose is to push unblockable, canvas-drawn ads.

AI risk is essentially Catholicism for tech guys

It may be a convention but in practice if you want to publish your package to Maven Central you need to prove ownership of your group ID domain. (Or ownership of your SCM account, which is in essence another domain).

In practice a massive majority of people will be within Zone 6 at the furthest, where the daily cap is £14.90.

Perhaps we could optimise it further, by having sets of steel paths for the cars to drive on too.

As an occasional Yarn user, this is how I learned there is even versions beyond 1.22.

Can't wait for the Wazelle processor extensions to drop.

they sabotaged it to force you to switch, and now your conclusion is oh, they were right all along?

Sure, let's go with that!

I updated my system recently and KDE under X11 started stuttering all the time, especially when opening new windows (which made using IntelliJ unusable, for example). Switched to Wayland and it just works. That's all it really took for me to go from a "I don't care about Wayland" guy to "I am a Wayland truther" guy.

Similar story for Pipewire; Pulseaudio had crackles and Pipewire didn't. Such is the way of life.

ISO 8601 is prolific. Is RFC 3339 well used/adopted in any system?

90% of the time when a library says ISO 8601 it doesn't actually implement the more esoteric parts of ISO 8601.

Given how primitive the Go GC is, I doubt it'll work at all.

Separately, if just going for concurrency for i/o, async/await is pretty amazing:

That's not async or concurrent. You're running a synchronous function in an asynchronous task which cancels out.

It doesn't even smoothly scroll on my desktop.

but what were you gonna do anyway?

go outside, talk to friends, do something productive, etc...

nix is so clearly superior and yet nobody uses it. curious!

haswell isn't vulnerable, it only affects skylake or later

The average complexity is at all time lows.

there's more than enough breakcore out there if you measure music quality like that. theree's definitely more than in the 20th century.

I don't like icons. I like text.

I don't care how much they update it. I will not use the new UI.