Readit NewsIf anyone wants to check out a half-done lang with lacking documentation, I'd be happy to read your feedback: https://lutra-lang.org
And in NodeJS, about four times the CPU usage of StatsD. We ended up doing our own aggregation to tamp this down and to reduce tag proliferation (StatsD is fine having multiple processes reporting the same tags, OTEL clobbers). At peak load we had 1 CPU running at 60-80% utilization. Until something changes we couldn’t vertically scale. Other factors on that project mean that’s now unlikely to happen but it grates.
OTEL is actively hostile to any language that uses one process per core. What a joke.
Just go with Prometheus. It’s not like there are other contenders out there.
> "GrapheneOS on Pixels" getting "extended Android support"
But it is really about
> GrapheneOS (commenting) on "Pixels getting extended Android support"
Otherwise this seems awesome! I'll certainly take a look at their other products
I'll admit, my FOSS prefering, DIY leaning use of tech is tedious, but is it worse than dealing with the churn companies force you (and your wallet) to deal with?
Don't complain about a company having a monopoly while using their products WHEN THERE ARE COMPLETELY FREE AND VIABLE ALTERNATIVES.
One reason I'm unwilling to move from Firefox right now: Recommended Extensions.
They're extensions that are checked by Mozilla employees for quality, security and privacy. Extensions have such unfettered access to my browsing, and so many have such nefarious practices that I'll only install extensions that Mozilla vets.
https://www.memorysafety.org/blog/introducing-river/
It's mentioned briefly in the Cloudflare blog post. I'd expect that if you're a current nginx or other proxy, River is what you'd want as an alternative.
One of the big things I'm excited about in the River plan is the ability to use wasm for scripting, which should make it relatively easy to extend.
I have my own Jellyfin server with pirated content for myself and mother, but I don't feel good charging money for "stolen" things.
Stealing to eat is one thing, stealing bread to sell for profit is different.
Hmm, perhaps, but I think we should be clear on the distinctions between:
1. "We didn't try to cause X."
2. "There is no X happening."
3. "We don't look to see if X happens."
4. "If X happens we don't try to stop it."
As someone involved in HR-tech-stuff, my default stance towards complex "AI" systems is that they all harbor biases, and the main difference is which ones have been discovered yet.
I’m sure there are exceptions, but one could assume that opaque systems are used as tools to encode biases that are advantageous but wrong.
These biases could have existed in code, but opaque agents give much better plausible deniability.
(Caveat here acknowledging one can often assume a lack of malice)