I feel like maybe the human DNA has degraded too much in 2 or 3 generations.
Ancient Greeks notwithstanding, being non-heterosexual was considered a disease to be eliminated or cured until people finally accepted that it was a natural part of being an animal. Would you say being gay is a consequence of flawed genetics, or would you like to try phrasing that remark a bit differently?
As a developer as well, I agree that they can get fucked. Bloated crap that wastes bandwidth and ruins first-time-to-paint on mobile devices by necessitating downloading and initializing a multi-megabyte bundle of npm packages.
As a user of the internet, I need websites to work, however. I would have disabled JavaScript entirely by now if it weren’t for the fact that doing so renders what feels like half of the entire web unusable.
Might be that there’s some way of blocking that behavior if you don’t like it, though, if I’m not seeing it.
Not without either breaking most SPAs (Single-Page Applications) or writing userscripts with site-specific logic.
The classic way of doing this crap was to make a placeholder page navigate to the article page. That leaves the redirect page in the history stack so when the user presses the back button, it just opens the page that navigates them forward again.
The modern way is to use the history API with history.pushState to add a history entry while listening for the popState event to check if the user pressed the back button. Unfortunately, both of those features have a legitimate use case for enabling navigation within a SPA. Writing an extension to replace them with no-ops would, in the best case, break page history in SPA websites. In the worst case, it would break page routing entirely.
You might be able to get away with conditionally no-oping their functionality based on heuristics such as “only allow pushState if the user interacted with the page in the last 5 seconds,” but it would still end up breaking some websites.
Add another to your list. It also started happening to me recently.
Oh, please. Nobody needs cough syrup when you could instead be drinking radium as an ailment cure-all.
I’m surprised you didn’t stick with NixOS. After spending tens of hours learning how to use it, the sunk cost fallacy is strong.
I was going to make a joke that they could also replace the taskbar search bar with an AI chat bar, but after reading the article, it turns out that they’re planning on doing that for real:
Windows 11 taskbar is now being “upgraded” with AI-first features. Microsoft is working on the Ask Copilot bar, which may replace Windows Search in the taskbar.
Oh, no. I’m saying Microsoft owning your operating system and using it to push their data-harvesting software as a default browser is a monopolistic practice, whereas using Chrome by itself is just reinforcing an existing monopoly. The same goes for Mac and Safari or Android and Chrome.
Neither option is good, but it’s a step in the right direction to punish a corporation for their active attempts to subvert competition in a bid to establish their own monopoly in place of the current one.
If you have to pick between two monopolistic corporations, using both of them but giving each a little less of your data and attention is a way to mitigate the risks and damage.
If Microsoft can harvest data on how I use my computer, I can at least make it a bit harder for them to harvest my browsing habits too by not voluntarily giving them browser telemetry on top of that.
There’s plenty:
The phoronix comment section is a garden of rationality and level-headed thinking in comparison.
Any time Rust is brought up in Phoronix, half of the comments are bad-faith idiots making strawmen and whataboutism arguments amounting to “skill issue, C is 300% safe and nobody needs better” and thinly-veiled contrarian antagonism against Rust because it’s popular.
A comment section worse than that? Impressive.
Why did my son die in the rehab facility?
That was something they could actually market to the consumer as a necessary upgrade, though.
Going from HDMI 2.1 to DisplayPort 2.1a doesn’t offer anything other than higher bandwidth, and not even high-end PCs are capable of pushing resolutions at high enough framerates for that bandwidth to have been the limiting factor for games.
Because of that lack of perceptible benefit to them, the optics of replacing HDMI on consumer devices that are meant to be connected to TVs isn’t going to be good. Even if it’s an objectively better standard from a technical perspective, it will just come across to consumers as an unnecessary change meant to push their TVs towards planned obsolescence.
They’re going to complain about it, the media will pick up on the story and try to turn it into a scandal, and then legislators and regulators will step in and make decisions based on limited understanding of the technical reasons. By that point, one of the console manufacturers will have been pressured into backing down and promise to keep HDMI in their next-gen console, and the other ones will have followed suit because they don’t want to lose sales over it.
The only way console manufacturers are going to stay united in kicking HDMI to the curb is if the organization behind HDMI pulls a Unity move and starts charging royalties to the manufacturers for every time a consumer plugs the console into a TV.
As long as the manufacturers are competing against each other, that’s never going to happen.
The “gamer” consumer demographic has some of the most whiny, entitled vocal minorities. They’re going to endlessly complain about the next generation of console needing a special cable/dongle to connect to their TV, one of the manufacturers are going to fold, and then the other one is going to walk back the lack of HDMI because they don’t want to lose sales to their competitor.
Mac is very similar to Linux in that it comes with bash (these days zsh) and a lot of the command line tools you’d expect on Linux, including gcc
No it doesn’t.
The gcc command is a wrapper for clang, and the clang command is a stub that runs an executable used to install the “Xcode Command-Line Tools”
It also uses the BSD coreutils, rather than the GNU coreutils present on most Linux distros. The two are only compatible up to functionality defined by the POSIX standard, and anything beyond that is an inconsistent mess.
Windows is more difficult. The command line is very different (it inherits from DOS instead of Unix like both Mac and Linux). It doesn’t come with Python pre-installed
If you limit yourself to not using WSL, sure. WSL 2 runs an actual Linux kernel with the same Linux executables you would find on any other distro.
It’s still Windows and full of telemetry and AI garbage nobody wants, but it somehow manages to have better Linux compatibility than macOS.
Even Musk, for all his recent evil got rich trying to reduce our dependence on gas cars.
Everybody else already covered his role in Tesla, so let’s look at something else that demonstrates his concern for the environment and his fellow species:
He has a datacenter in Memphis running 35 “temporary” methane generators to power Grok, the self-described “Mecha Hitler” AI. All but a dozen of them are being used without permits for permanent generators, and none of them have air pollution filtration systems installed. Oh, and it’s near a low-income community that was already plagued by air pollution.
And native software.
Because JavaScript runs everywhere, we have companies creating “apps” and PC “programs” that are little more than glorified web views. There’s normally nothing wrong with having shared code across implementations, but when that shared code is a 4 MB bundle of crap that creates 100s of MB in dictionaries and JIT compiler caches, you’re ruining the end-user experience.
They make entire SOCs. None of them are x86 because of the duopoly that Intel and AMD have thanks to their cross-licensing agreement, but they still have functional CPUs with a common ISA.
AMD: “Our partners will fry your expensive CPU on some boards.”
INTEL: “Our software will fry your expensive CPU on all boards.”
There’s a whole lot of entitlement going on in that thread.
If the maintainers didn’t want to merge it because they had bigger issues to worry about, that’s that. Whining about it and trying to pressure them with prospects of “becoming obsolete [if you don’t merge this]” isn’t going to make a convincing argument.
They should either shut the fuck up and learn to RTFM, or maybe consider putting their money where their mouths are by actually paying to support the projects they seem to so desperately think they have a right to influence the direction of.