did you read it? apple throttled device performance. google is throttling charging speed and battery capacity for safety reasons. there are literally phones melting. also, battery capacity is something people assume will go down over time. also they're giving clear notifications when people are affected.
it's not really the same, and definitely not worse
but if there's a bug I'll know exactly which line to look at
I love alternative shells. my shell has been set to fish and zsh for about a year each, xonsh for a few years, and now nushell for a couple years, and I think that's probably my ranking as well.
fish and zsh are both nicer than bash, but they don't give you as much as xonsh and nu do. you get nice completion and configuration and such, but it's still a shell when it comes to the programming tasks.
I don't want just a shell, I want a programming language with a good repl that makes it easy to deal with commands. xonsh and nushell both do that.
my major problem with xonsh was that there was python syntax, and there was shell syntax. it didn't feel great to interleave sh cmds and py fns. everything had to be parsed and then everything had to be formatted to go back into sh cmds. the standard library of sh cmds doesn't really exist either. you either use the py version of libraries for paths/processes/whatever, or you call and parse the os version. the former seems like the intended one. I found myself having to find a pip package for whatever task.
nu solves all my problems with xonsh without sacrificing much. there isn't really a split between nu commands and shell ones syntactically. parsing is easy, most cli things output data as lines, ascii tables, or have a json flag, and nu has nice ways to deal with all of those. nu commands generally work given a single element or a list or a full table if they make sense to. running a command on each element in a list and dealing with the output is easy as opposed to having to break your pipeline and write a for loop. they also have plenty of builtins and plugins so the things I generally want to parse are already done. ls returns a table, ps returns a table, I can pass lists into rm, etc. there's community plugins for git so I don't have to remember their syntax for searching for commits, I just query in nu. aws cli has a json flag so I can explore logs and such as nu data. and if I just want.
now downsides to nu. it's not bash so you can't just source whatever file that a command probably gives you, and there's no source-bash like xonsh has, so you're stuck translating it to nu. if it just sets env vars it's not awful since you can just shell out to bash, but doesn't work for more complicated. for things like python you have to make sure you use the correct tool to make your venv since builtin one doesn't give you a nu file to load. not sure about support in other tools.
overall it's great and not really that much learning, especially if you just use it like a shell to begin with. it's not much commitment to try a new shell since you can still call scripts written in your previous one. I'd say try it and see how it goes
yeah. stopping support helps end it, but in russia's favor
they're not the government but they are a political party with 15 seats in the parliament.
the problem is there are a ton of varieties of tofu, and they're all generally around the same price. it seems the silken tofu have around 5g of protein, but some of the extra firm varieties have over 15g protein per 100 tofu, putting it in a much more respectable spot in the bottom middle with the grains and such
this just looks like poor moderation, enshittification very specifically refers to monetization efforts of the company destroying the platform
it felt to me like coffeescript solved problems that people had, then js got equivalent features. arguably that could happen to ts as well
this guy writes shitty code
try element x, on android it opens almost instantly. still in beta though
if it's not clear if it's ai, it's not the code this policy was targeting. this is so they don't have to waste time justifying removing the true ai slop.
if the code looks bad enough to be indistinguishable from ai slop, I don't think it matters that it was handwritten or not.