giantrobot
It's not about being dumb, I think it comes from the mental model where big electrical appliances/machines are controlled by big slow relays and switches. Changes to the state of operation involve inertia and momentum and huge power spikes and fuses that make extremely loud noises when they blow.
The first problem is e-mail fatigue. Many groups have ridiculous amounts of automated e-mails that amount to line noise. The information in them is rarely actionable and certainly never so critical it needs to be read by everyone immediately. "Everything is OK" alarms are fucking infuriating. It's very easy to miss the super highly critical e-mail from a manager that's just a lazily forwarded e-mail from the automated systems. The "Have you seen this?" with the entire contents of the line noise e-mail from the automated system.
Second is people, especially middle management, that for some reason assume e-mail is a real-time communication medium. They send an e-mail and expect the recipients to drop everything to respond to it. Simultaneously the people actually doing work are actually working and not checking their e-mail every nanosecond to see if they need to drop their actual work to explain their actual work to management. So then the middle management sends a cascade of instant messages and schedules meetings to get the people doing actual work to drop everything to explain their actual work. These meetings will inevitably contain complaints about not getting work done.
It's now even worse with AI in the middle. Instead of using LLMs to write easy to scan and digest bullet point e-mails they're used to expand bullet points into useless novellas.
My solutions to these problems are thus:
1. RSS - Automated systems should just emit RSS feeds with their normal status with separate feeds for exceptional conditions. Only in those actual "machine on fire" conditions are e-mails sent by such systems. Parties interested in constant updates just watch their feed reader and everyone has a single source of truth for event logs from the automated systems.
2. Automated systems should just file tickets automatically so everyone involved has a single source of truth and can all collaborate in one place. Even better if the ticket/bug tracker supports RSS because it becomes dead simple for anyone to follow feeds they're interested in and even set up system notifications for new issues.
3. Company/group wide e-mail policies that constantly remind everyone it's not a real-time medium and that filling everyone's inbox with noise is not effective communication. This can be enforced with automated delivery delays guaranteeing e-mail won't be immediately delivered as a safeguard against people using it instead of actual real-time channels.
4. Verbose e-mails are also rarely effective communication and shared LLM prompts that make e-mails shorter and clearer would also help.
Removing most of the noise from e-mail makes it more effective and can make it an actual communication medium. If e-mail becomes effective communication far less of everyone's limited lives needs to be spent zoning out in meetings where their only purpose is to "give a status update".
Back in the days of paper memos the literal cost and effort required to send them required the sender to really think about what they were trying to communicate and how to say it best. Because e-mail is essentially free it is widely abused since so little thought needs to go into its composition and delivery.
A minimal reproduction is great in a bug report but it's still not a complete in-situ snapshot of the machine.
As a former Apple SWE that has read innumerable sysdiagnose reports, this statement is bullshit.
External bug reports very commonly have a variation of "THIS IS BROKEN YOU SUCK FIX THIS" as the main note. Even with a crash log attached that's not at all helpful. A sysdiagnose gives a state of the system the reporter has in front of them. You can't triage a bug with "FIX NOW" as the description.
I know I know, Apple has infinity dollars and every SWE should just magically fix bugs without needing to triage them first. Every external bug reports very is also a special snowflake that deserves concierge VIP serve and a dedicated SWE team to fix.
See Meta et al complaining about Section 230 of the DMCA. Meta would be entirely able to moderate in an environment where mass scale moderation/censorship would be required to prevent a host's liability for UGC. Almost no one else would be able to do so.
That means no upstart could possible come along to dethrone Meta as they did with MySpace. It would also be impractical to run a FOSS social network (or forums). Meta could literally just have bots sign up on a FOSS social network until its DAU count ran over the statutory minimums to be subject to UGC liability.
Regulatory capture is a de facto ban on competition in a market.
The NV1 and other cards before the GF256 did accelerated drawing and geometry raster but lighting and transformations were done on the CPU in main memory then transferred to VRAM and rasterized.
Even if the GF256 had say the same texel output performance as a TNT2, the T&L running on the GPU would allow for more complex scenes at higher frame rates than a TNT2 doing T&L on the CPU. The GF256 also had better raster performance so for many games it was just a "free" performance upgrade over a TNT2.
Votes and karma. The concept of karma isn't bad but Reddit's implementation is bad. HN has a similar problem. There's only up and down votes with no context.
Why was a post upvoted or downvoted? Did people find it funny or informative? Did it correct the original link or a parent post? No fucking clue. Just scalar value that goes up and down. Then you get bad proxies for context with vote ratios (controversial etc).
Slashdot's voting system isn't perfect but much better. Instead of some scalar value a post is moderated with some sort of context (Interesting, Informative, etc). Voting is also distributed among users and limited. If you get moderator points you're limited in how many you get and you can't post to a thread you've moderated. Meta moderation also helps to correct for overzealous/reactionary moderation.
The context is useful because you get an idea of why something was moderated as it was. The limited number and random distribution of moderation points helps inspire actual moderation. You either downvote obviously trolling/bad faith posts or upvote actually constructive posts. No one wastes their mod points on memes and "me too" posts. Drive by memes and short knee jerk replies just wallow in the Score: 1 area most users quickly learn to filter out. They're not punished but also not rewarded.
Giving everyone unlimited mod points devolves a site into gaming karma. Trolls enjoy seeing how low their karma can get while karma whores will post whatever gets upvotes rather than something constructive. Karma is a bad proxy for constructive contributions to the community.
For reasons my machine with a beefy GPU is stuck on an older set of Nvidia drivers. I've got them pinned with apt. The ollama installer fucked everything up by updating stuff that apparently wasn't pinned. After I had fun cleaning up that fucking mess I found it overwrote my custom systemd service file so I had to go in and fix that.
Curl-to-shell is a bullshit antipattern. I have no interest in going back to the dark days of expanding tarballs to / and hoping for the best.
Wow. Poe's Law in full effect here. I'm not sure if you're just oblivious or trolling. If you're oblivious do yourself a huge fucking favor and read up on what Flock is doing in addition to ALPR and how even that is abused by law enforcement.
The "powers that be" chose to lose a completely optional and ill-conceived war on your dime. Instead of science or helping people they decided to spend money blowing up schoolgirls.
In space everything is an orbital change. To change orbits you need to speed up and slow down, all of that requires fuel. Even using what are known as "low energy" trajectories that use a bunch of gravitational slingshots need velocity changes to adjust trajectories to get the right angle of approach to some large body.
Most commercial launch services focus on LEO because the secondary stages don't need to carry much fuel and their engines only need to fire reliably once to get into a stable orbit.
A planetary transfer requires multiple engine firings. That's much harder than a single reliable firing. It's not impossible but the testing and engineering is expensive.
A science mission often needs to beg, borrow, and steal to get built. There's one shot to accomplish the mission objectives. That's more expensive engineering and testing. Some mission profiles require specific planetary alignments with very narrow launch windows to boot. So there's a lot of expensive work made more expensive by a tight deadline.
The actual marginal cost of the rocket, fuel, and launch is a very small part of the mission cost. Halving the launch price doesn't necessarily affect the cost of anything else.
Starlink satellites are effectively disposable. If a Falcon 9 explodes or fails to get the second stage to orbit they're out maybe a few tens of millions of dollars. If a science mission has some mission-killing failure there's no funding for a do-over.
Linux took over in all the places where a good GUI didn't matter. In ran most of the Unix server software on hardware orders of magnitude cheaper than what was needed to run a commercial Unix. Windows ran on that same cheap hardware but was much more expensive for the same capability.
Despite Sun's marketing push Linux was really the dot in most of the dotcom darlings.
Also as we have seen, the Chinese labs will just buy their kit through cut outs or do training in locations where there's no embargo.
Power density and all of the problems that are fallout from high power density. A modern LiPoly battery contains a lot of energy. It's stored in a chemical that is highly reactive with oxygen, which you happen to be surrounded by at the moment.
Watch some videos on lithium battery fires. Not only do they have extremely hot flames but they spray out molten bits of battery and can't be extinguished with water.
To make a LiPoly battery that can be safely handled by normal people it needs a strong outer casing. A sealed battery in a phone uses the phone's case itself as the battery's protective casing. A user replaceable battery would need its own strong case. The phone then needs to be larger to accommodate the extra volume or have a smaller battery which stores less power than a sealed battery of equivalent volume.
The market has rewarded thinner phones with long lifetimes but also high performance. That triple point is challenging if not impossible to hit without sealed batteries.
I can see them not releasing an M6 Ultra but no reason not to see Pro and Max versions of the M6.