7,735 karma · joined December 20, 2010
It isn't hard to see, tbh. Think about the controls in a Tesla from a few years ago. They had physical controls for drive selection, turn signals, cruise control/TACC, cruise control distances, volume, next and previous track, seat controls, and manual overrides for the automatic wipers. The things that were used a little less were on the touch screen, with automation attempting to mitigate the downsides of this. This largely consisted of climate, manual overrides for the automatic headlights, and things like suspension settings.
So, what has VW made better here? Well, they have physical controls for turn signals, drive selection, volume, next and previous track, etc. They appear to use the touch screen for much of the climate control and entertainment settings, including appearing to retain the much maligned touch settings for seat heaters.
I'm not convinced that this is better. By contrast, my Nissan has driving settings like lane centering and seat heater controls on physical buttons... right next to my left knee where they are nearly inaccessible while driving.
TBH, the whole debate around this needs to be recentered around actual ergonomics and less around touch vs physical.
Is it really that common, or do these posts just bring out those types of comments?
TBH, in this field, it seems like other problems are often more pressing:
- I've been a developer in XX language for NN years. How do I get my next job when the company is now hiring YY developers instead?
- There are lots of Level II jobs for YY, but I'm at level IV. Will eligibility rules even allow this transition?
- There are some Level V positions for YY, but my level IV in XX doesn't really qualify me in a way that would pass a tech screen.
The concerns in these types of posts are just so... different.If you are struggling with the neural network mechanics themselves, though, I'd recommend just skimming them once and then going back for a second watch later. The high level overview will make some of the early setup work make much more sense in a second viewing.
It isn't something that I've looked into in depth, but it feels like a lot of the discussion isn't hitting the mark here.
Your point about semi-truck damage vs lighter vehicles is exactly why I think moving in that direction is so useful. The most fair taxation would accurately take both that aspect and actual miles driven into account.
I'd guess that this is also an area where the perception makes a bigger difference than the reality.
Down the street from it is an aluminum plant. Just a few years after that data center, they announced that they were at risk of shutting down due to rising power costs. They appealed to city leaders, state leaders, the media, and the public to encourage the utilities to give them favorable rates in order to avoid layoffs. While support for causes like this is never universal, I'd say they had more supporters than detractors. I believe that a facility like theirs uses ~400 MW.
Now, there are plans for a 300 MW data center from companies that most people aren't familiar with. There are widespread efforts to disrupt the plans from people who insist that it is too much power usage, will lead to grid instability, and is a huge environmental problem!
This is an all too common pattern.
Elixir has also been working surprisingly well for me lately.
Claude Code loves to say that everything is production ready, even if it doesn't quite compile or pass automated tests yet.
But even without them getting better, as far as I know there were zero waymo fatalities due to this.
That's more than I can say about Helene, where there was at least one fatality due to traffic light outages.
Lets not forget that a big part of why we want Waymo is that it has already lead to a dramatic decrease in fatal accidents. They are a great company that will do a lot of good for the world. One bad night (in which noone was hurt, in part because of their cautiuosness) shouldn't negate that.
What went so wrong during the past 25 years?
If your website is hard for an AI like Claude Sonnet 4.5 to use today, then it probably is hard for a lot of your users to use too.
The exceptions would be sites that intentionally try to make the user's life harder by attempting to stifle the user's AI agent's usability.
Perhaps some filter could cut out submissions that don't really make sense?
We need far higher quality data than this to reach meaningful conclusions. Implying conclusions based upon this extrapolation is irresponsible.
1/500k miles that includes the interstate will be very different from the rate for an urban environment.
Of the Tesla accidents, five of them involved either collisions with fixed objects, animals, or a non-injured cyclist. Extremely minor versions of these with human drivers often go unreported.
Unfortunately, without the details, this comparison will end up being a comparison between two rates with very different measurement approaches.
There are real, legitimate concerns here, but they are hidden behind a lot of assumptions.
Meanwhile cheap roborocks had no arbitrary limitations and more honest marketing.
I miss the optimism that this company used to have, but I won't miss the entity that they became.
That's probably what people would have said before Swype was invented too. But lots of people use that in their default keyboards thanks to the people that _did_ pay for keyboards back then.
Who knows what innovations we are missing out on today just because we've consolidated things down to 2-3 suppliers?
I doubt those were particularly profitable, but there was a lot of innovation back then.
While I am not a big fan of Rust, the philosophy is likely useful here. Perhaps something like it, with a lot of technical validation pushed to the compiler, could actually be really useful here.
Getting rid of the garbage collector with no major increase in human cognitive load might actually be a big win.
Instead, they either blindly follow or quietly rebel.
It is one of the weirdest variations of people buying into too much hype.