barake
Joined 16 years ago
Joined 16 years ago
1: https://www.wlky.com/article/forced-busing-anniversary-50-lo...
2: https://www.louisville.com/redlining-louisville-dividing-lin...
https://www.aol.com/articles/nashville-judge-orders-release-...
https://www.aclu-co.org/press-releases/federal-judge-rules-i...
https://www.nytimes.com/2026/10/06/nyregion/ice-judge-condem...
https://alabamareflector.com/2026/09/22/federal-judge-orders...
Long term? Who knows for sure. Semaglutide has been approved for 9 years. Liraglutide was 2009 and hasn't shown thyroid issues still. Exenatide has been available since 2005.
GLP-1s aren't new and haven't shown widespread negative issues beyond gastrointestinal upset, and that is typically fixed by... drinking more water. The trials in rats have pointed towards potential thyroid cancer risks but those haven't been seen in people.
A good example is the voice assistant hardware from Amazon and Google. The speakers are everywhere, basic daily use stats are likely solid, and retail display square footage remains huge. Yet almost no one will pay for the associated subscriptions or other premium services. The hardware was sold at a loss(?) expecting downstream revenue from services that customers simply don't value enough to buy.
I used to work in this space and Lightstream was always doing interesting things, even if they never seemed to find PMF.
1: https://support.golightstream.com/hc/en-us/articles/38643168...
Doesn't bode well for the industry. PlayStation and Xbox both switched to mostly-commodity hardware this gen and are years old, yet also facing the same price pressure apparently
You end up with YAML libraries being widely available and they all implement _most_ of the spec, but the portion not implemented varies. Plus there are minor variations in how people have read the spec, and even options _within_ the specification on how to handle parsing:
https://yaml.org/spec/1.2.2/#chapter-10-recommended-schemas
This isn't really a problem for projects like Kubernetes where most of the ecosystem uses the same library. On the other hand, OpenTelemetry is rolling out "declarative configuration" across all the supported languages. I work on OTel, and have avoided contributing in that area because I lack the patience to deal with the inconsistences - I don't hate YAML, but it can be frustrating.
AFAIK, the only 100% spec compliant implementation is libfyaml.
Changes are on this branch for the curious:
https://github.com/matt-hensley/typed-ffmpeg/tree/feature/mu...
If you choose the custom build route some even can ship with Fedora or Ubuntu, so presumably Linux support is reasonable.
If you had property adjacent to a power plant they would happily lease space to setup sensors.
Apparently there are tons of businesses like this gathering data that is mostly live and selling to hedge funds etc.
Tracing is very mature, with metric and logging implementations stable for a number of popular languages [1].
the "experimental" status was renamed "development"
[0] https://opentelemetry.io/docs/specs/otel/versioning-and-stab...
[1] https://opentelemetry.io/docs/languages/#status-and-releases
bWF0dGhldy5zLmhlbnNsZXlAZ21haWwuY29t