Lazy people using tools in a shitty manner has been an age old problem.
This just lets it scale, which is the problem. There used to be a barrier to entry for those less knowledgeable or experienced, now there isn't and that's the result.
It is a productivity tool, and it's being used as one, by both people that know how and people who don't.
So you tried to defeat someone else's experience with an anecdote where you have not had that experience. What even are you trying to say here?
Lots of people's cats have behaviors like this. Feeding them a certain amount on a fixed schedule helps. We have six cats. One of them is like this. It's a pain in the ass.
Ah yes, the classic "the stupid consumers are stupid" argument.
This was sold as being an offline-capable device. It even has battery slots for power outages.
Perhaps instead of shitting on people for buying something they thought would be nice and work well, we shit on the company that can't even give a pet feeder an on-device offline schedule after selling people on a device that's supposed to work offline and even during power outages.
And figure out how we can hack it and enable folks to control the hardware they own, because they weren't stupid for buying a pet feeder. The company that runs it just does so in a moronic way.
(I don't own one of these, but I have considered it a few times, and this just pisses me off)
A lot of tokens tends to help move the needle, building in guardrails, sophisticated review of both in process work & final outputs, and consensus helps raise the bar considerably.
That and sane, universally consistent, well structured, low tech debt, organizationally elegant, systematically evolved codebases. Something the grand majority of teams don't have to begin with.
Nevermind being well documented, with excellent opinionated linting and static type enforcement configurations, with robust CI checks. More things many projects don't seem to have.
Turns out that giving AI poorly engineered and maintained codebases just amplifies the poor engineering and low rigor already present. Something that's endemic to our industry.
Did you just strawman a fact with an anecdote and then completely get your second statement backwards?
Nuclear plants have to scale down their water output for ecological regulation reasons. Which means they have to restrict their inflow, which means they have to restrict their output capacity.
Oil industry wants you to think that nuclear there doesn't work, not that it does. Oil and coal have been working against nuclear for an entire generation or more.
The nuclear capacity losses are because of environmental regulations, not because of inherent issues with nuclear.
Regulations restrict discharge of cooled water above 30°C into waterways, and they are responsible for the riverway temperature downstream of them. Since the waterways are warmer during a heat wave and the nuclear plant is responsible for the temperature of that waterway, they cannot discharge as much warm water into that waterway.
Solar doesn't work at night, and sufficiently scalable energy storage technology doesn't yet exist.
Solar loses considerable capacity as ambient temperature increases. At 40°C ambient, you're talking about a 15% or higher reduction in efficiency. Which would be HIGHER than the ~12% reduction in nuclear capacity Europe hmis seeing
They are buying up capacity from manufacturers who are stopping production of DRAM and pivot to HBM which is more profitable. Abandoning DRAM which affects a lot more than just "consumer grade RAM"
You're most definitely wrong here because the first step is to announce something like this because a project like this requires gathering a significant number of contributors.
They're trying to hard fork Firefox, which means they are trying to take on the engineering efforts of hundreds of full time engineers who are browser development experts. To keep up with bugs, web standards, security patches, and performance. Nevermind new feature development.
How are they going to maintain the hard fork when something like 95+% of all engineering efforts that support LibreWolf and similar come from the Firefox engineering team?
Mostly mundane stuff like security patches, performance fixes, and web standards features and updates make up the bulk of the engineering efforts.
Literally all knowledge and understanding requires memorization of some sort and the understanding of reality and prior information.
It is difficult to fathom the level of wrong in this comment.
Here's the thing people who lack knowledge, critical thinking and understanding about the how the world works. Still form opinions and makes decisions as if they did have that knowledge and understanding. Which negatively affects everyone else.
.... What?
Lazy people using tools in a shitty manner has been an age old problem.
This just lets it scale, which is the problem. There used to be a barrier to entry for those less knowledgeable or experienced, now there isn't and that's the result.
It is a productivity tool, and it's being used as one, by both people that know how and people who don't.