4,776 karma · joined October 7, 2011
EVs also have very powerful motor braking that can get the car to a stop if the hydraulic brakes are busted.
Why would I need a chart for a single container app? Making this simple is what Kubernetes is designed for. No, I don’t want your ServiceAccounts or PVs because I anyway need to grant and understand the permissions and select the size and SKU of the underlying disk.
Deploying an app in your own infrastructure has too many knobs that need to be turned so you need to expose all of them. Just spend a few minutes extra to write your own deployment manifest. While it’s a few more lines of code vs ”helm install”, you will not regret it and you’ll get a much better understanding of what’s actually running.
Now there are of course exceptions to this, like Prometheus or Ingress operators where more complex charts are warranted. What I’m talking about is those charts that just wrap what can be translated from docker-compose to k8s in two minutes.
Now it’s not perfect either. It does have some issues with slow querying of the current state during planning, even when it has the tfstate as a cache, which is another source of errors.
Notably, YouTube these days prioritize AV1 codec even if you don’t have gpu acceleration for it, making lots of systems fall back to CPU decoding and making it completely unusable. Install the h264ify extension to force h264 during content negotiation and get your gpu decoding back.
Even if you can make a matrix of all those combinations, it’s even more complex than that to test in practice. Take my laptop for example, it starts off good and manages the cpu decoding for a while, a few minutes into a video it overheats and throttles, causing stutter.
What YouTube should do on the other hand, and I’m sure they already do, is to collect metrics from all playbacks. That should show black on white how many users struggle with each codec.
I don’t think I’m in any minority here given how many million installations the h264ify extension has. Google simply care more about their bandwidth cost than the user experience.
This opens up transparency of ffmpeg’s security posture, giving others the chance to fix it themselves, isolate where it’s run or build on entirely new foundations.
All this assuming the reports are in fact pointing to true security issues. Not talking about AI-slop reports.
JSX is amazing for stateless rendering of templates. Not so much for state management. That should really have been given a dedicated DSL. Here I think Marko did the right thing, why they then made even for-loops a dsl is more questionable.
Half of them which shouldn’t be needed if the language didn’t let you shoot yourself in the foot in the first place.
> Transparency in Behavior
Undefined behavior has entered the chat
> Loop structures are clean and readable
If you like fiddling with i-variables and sizeof like foreach never happened.
> Error handling and optional results use simple, explicit patterns.
Proceeds and ignores the return code of fread(), leaving errors unhandled.
At this point I lost it as became more and more obvious it’s both AI slop and it’s ignoring the past 20 years of progress in programming languages. C may have its uses but jeez don’t pretend it is ergonomic.
It solves all the warts of sql while still being true to its declarative execution. Trailing commas, from statement first and reads as a a composable pipeline, temporary variables for expressions, intuitive grouping.
Here is one famous example of a dude who’s managed to get PRs merged in dozens of packages, just to make them compatible with ancient versions of nodejs https://news.ycombinator.com/item?id=44831811
Since we are talking about OS support. 4th gen Intel isn’t supported by Windows 11, so you’d have to upgrade to Linux.
For LLM consumption, this might not matter, don’t use this for anything else.
I mean, it gets the job done but nothing is convenient. The UI looks like a Christmas tree and still everything you need to do is found several sub-menus down in confusing dialogs, like in Excel pre-ribbon times. And for the love of god, please don’t say that ribbon spoiled everything, that discussion was boring even 10 years ago. Since then, state of the art has evolved beyond that.
For small scale household data, the web version of excel is good enough and has an easier UI. For larger scale, duckdb and some python.