It could also be that the "direct blog post to video" format doesn't cut it.
This specific format is strongly associated with low-effort content-farm channels that repackage other people's posts from sites like Reddit and Medium.
I haven't had the attention span for more than short pick-up-and-play sessions lately, so I've been trying out Psycho Pinball for the Sega Genesis on my handheld emulation console. I'm not very good at it, but I'm having fun!
The real underlying issue here is that the OS interfaces these programs rely on are extremely error-prone and difficult to use correctly. A naive implementation of these system utilities in any language is basically guaranteed to stumble into bugs and vulnerabilities like the ones described in the linked message.
Ubuntu updates break shit all the time, whether or not Rust is involved. The Linux kernel, on the other hand, has a proven track record of compatibility and stability.
People don't want Firefox translation because they "want AI," though. They want it because being able to translate web pages is a useful feature. I think it's quite telling that nowhere in the linked article does the author actually defend Firefox's new "Window AI" feature as useful. Instead, the only argument he can make for it is that AI is popular.
If Henry Ford had given his users what they wanted, he would have built a faster horse.
Users want AI right now because a lot of people have spent a lot of money to convince them they want it. A few years ago, they wanted crypto and VR; a few more years from now, they'll want something else. We're already seeing evidence that the current AI boom is an unsustainable bubble. Will "hundreds of millions of users" still be using ChatGPT after OpenAI's investors get tired of losing billions of dollars every year, and decide it's time to start squeezing their customers for more cash?
This kind of trend-chasing is what happens when the people in charge have no real principles or vision underlying their actions. Firefox didn't beat Internet Explorer by following the crowd; it won by delivering a product that was better, and doing things nobody else had done before (like tabs). In order to do that, the people making it had to have a strong vision of what a "better" browser would look like.
This isn't a recent development; it's been going on for decades. Indeed, most of the reason we use the terms "FOSS" and "open source" instead of the original term—"free software"—is that "open source" was deemed more corporate-friendly.
The company said that users can opt out of having their data processed for advertising purposes by turning off a setting related to “technical and interaction data” on both desktop and mobile at any time. [Emphasis added.]
This is the real story. Having opt-out data collection is one thing, but misleading users about how they use the data they collect is just slimy.
It's not just "hardly anyone," it's "literally no one." Varlink was invented by the systemd developers out of whole cloth specifically for this purpose.
I'm not saying that anyone should flag lambdas as a problem in code review, just that when you see one, it's probably worth taking a second to ask yourself if a named function would make more sense.
I appreciate that this article highlights the value of using of named functions in functional-style code. Too often, programmers assume that "functional programming" means using lambdas everywhere, when in my experience, lambdas are actually a (very mild) code smell.
This specific format is strongly associated with low-effort content-farm channels that repackage other people's posts from sites like Reddit and Medium.
Even if all of this is true, I would rather have uBlock Origin and worse performance.
Because if it was shut down, the Epstein class couldn't abuse their insider knowledge to make money. Laws are only for the proles.
Absolutely not lol. If it were 1936 you'd be whining that FDR shouldn't go on the radio because the radio stations are all owned by robber-barons.
Communicating with the public is part of his job.
Because he has an actual job, and that isn't part of it
I haven't had the attention span for more than short pick-up-and-play sessions lately, so I've been trying out Psycho Pinball for the Sega Genesis on my handheld emulation console. I'm not very good at it, but I'm having fun!
The real underlying issue here is that the OS interfaces these programs rely on are extremely error-prone and difficult to use correctly. A naive implementation of these system utilities in any language is basically guaranteed to stumble into bugs and vulnerabilities like the ones described in the linked message.
Ubuntu updates break shit all the time, whether or not Rust is involved. The Linux kernel, on the other hand, has a proven track record of compatibility and stability.
If you can learn to read
int (*funcs[])(void*, void*), you can learn to read Rust.Works fine for me. Maybe try with a different keyboard app?
People don't want Firefox translation because they "want AI," though. They want it because being able to translate web pages is a useful feature. I think it's quite telling that nowhere in the linked article does the author actually defend Firefox's new "Window AI" feature as useful. Instead, the only argument he can make for it is that AI is popular.
If Henry Ford had given his users what they wanted, he would have built a faster horse.
Users want AI right now because a lot of people have spent a lot of money to convince them they want it. A few years ago, they wanted crypto and VR; a few more years from now, they'll want something else. We're already seeing evidence that the current AI boom is an unsustainable bubble. Will "hundreds of millions of users" still be using ChatGPT after OpenAI's investors get tired of losing billions of dollars every year, and decide it's time to start squeezing their customers for more cash?
This kind of trend-chasing is what happens when the people in charge have no real principles or vision underlying their actions. Firefox didn't beat Internet Explorer by following the crowd; it won by delivering a product that was better, and doing things nobody else had done before (like tabs). In order to do that, the people making it had to have a strong vision of what a "better" browser would look like.
This isn't a recent development; it's been going on for decades. Indeed, most of the reason we use the terms "FOSS" and "open source" instead of the original term—"free software"—is that "open source" was deemed more corporate-friendly.
This is the real story. Having opt-out data collection is one thing, but misleading users about how they use the data they collect is just slimy.
It's not just "hardly anyone," it's "literally no one." Varlink was invented by the systemd developers out of whole cloth specifically for this purpose.
If the compiler produces a program that doesn't match your description, you can debug the compiler. Can you debug an LLM?
Well, remember, a code smell isn't something that's inherently bad, it's "a hint that something might be wrong".
I'm not saying that anyone should flag lambdas as a problem in code review, just that when you see one, it's probably worth taking a second to ask yourself if a named function would make more sense.
I appreciate that this article highlights the value of using of named functions in functional-style code. Too often, programmers assume that "functional programming" means using lambdas everywhere, when in my experience, lambdas are actually a (very mild) code smell.
http://archive.today/2024.09.05-163939/https://www.thecentersquare.com/california/article_21e5a632-6b0f-11ef-990d-3314413b4c42.html