For CHF 40 you can become a Rega patron and then they will usually pay whatever the insurance didn't cover, I think, but technically they don't have to.

Now you sound like Pl@ntNet identify: "This is not a plant! Maybe fungi?"

(Edit: It doesn't seem catch amoebae in the same way. It suggested Goldmoss instead, with 1% confidence.)

Also, you have to admit that when your first interaction on HN is posting a self-promotion it seems like bad manners at best.

It goes on to assert how everything is I/O bound, and how bad threads are for that. Fair. What follows an intro to tokio, with focus on how you span a CPU-bound task, how work stealing works, and then how you should use SIMD for your CPU-bound tasks. Huh.

I mean, if you have a mostly CPU-bound task and also the occasional I/O socket, you can keep things much simpler by using threads and std::sync. Especially if you are in the audience of that article, then you don't know yet how much more complicated things can get when you need to use async in Rust. And how much Rust's safety model actually changes the past wisdom of "threads are evil, period" in favour of threads again.

Comments URL: https://news.ycombinator.com/item?id=48423195

Points: 3

# Comments: 0

You'd think removing friction on the software side for someone who already bought their hardware would be in their interest. Especially for students and hobbyists, who will want use what they already know once they enter the industry.

Why nanoseconds though? Usually a sub-microsecond sync is good enough. I can only think of some specialized phase measurements, really, like when you need to know from which direction a radio signal is coming based on timing of two antennas.

I was able to pull the graph and collect patches and bugfixes from forks, like from a fablab somewhere using the same hardware, pushing to their fork with all their other location-specific stuff. In one case I discovered like four different forks with a different fix for the same problem.

Now you could argue the "social" part wasn't working if people fixed the same issue multiple times without knowing about each other. But at least github made it possible for me to collect everything there is, review and merge it into my own repo, and then drop a comment at the original issue tracker. (Which would have gone 404 had it been self-hosted, or with registrations closed due to spam.) In both cases I eventually got feedback from other people who found my branch and used it.

I can't write well. Let someone say it who can: (Ursula Le Guin, 5min) https://www.youtube.com/watch?v=s2v7RDyo7os&t=337

As a separate device, it should be offline always IMO, and perhaps the size of a passkey. Or one of those banking devices with a display that show an authenticated text saying what you are confirming.

Never mind the technical challenge to allow doing anything with the DOM but disallow reading the forms. Like, prevent the forms leaking its text when you do funny things like testing character width via line breaking or font changes.

The question unnerves Neo and suddenly he feels his phone vibrate as it unexpectedly reboots. The standing Agents snicker.