As another Tesla owner, I've had this discussion with my brother one too many times. He'll insist he needs buttons, he needs Android Auto/CarPlay and whatnot. Every time I step into one of those cars I'm overwhelmed. Half of the times it doesn't connect, when it connects I get useless notifications for everything. It's not well integrated, and it'll randomly break during the trip.
I understand it has become a standard but it's not a particularly good one, and adding it "just because it's a standard" would detract from the car experience in my opinion. It's a separate device, with a separate OS, kernel, apps etc where you can install almost anything, that's supposed to take over a piece of equipment that belongs with the car and controls all its functions. I'd really rather not have that.
If the infotainment is the basic "show 2D maps and a couple settings", then Android Auto/CarPlay can serve as a viable replacement for low-end cars. But when the car costs >30k and the screen is also the central command console, no thanks. I'd rather have proper OTA updates, give feedback, and see it evolve over time for the better.
I mostly agree with the points, but I've also managed to throw AI efficiently at the problem.
We're running a self-hosted GitLab -> hosted GitHub migration at my company (which to me feels a downgrade), and without LLMs I would have spent weeks just researching syntax for how to implement the requirements I had.
I asked Claude to simply "translate these GL templates to GH actions, I want 1 flow for this, 1 flow for that, etc" and it mostly worked. Then in the repos I link the template and ask Claude to write the workflow that uses the template with the correct inputs. I think I saved maybe 3 months worth of coding and debugging workflows. Besides maybe picking slightly outdated actions (e.g. action@v4 instead of action@v6), 95% of the work was ok, and I had to tweak a couple things afterwards.
Looks like my job is ensuring stuff builds, tests and ships correctly, not learning the 100th no-design botched homegrown language that will keep changing for the next 10y until it's a different thing altogether. And because I'm one person out of two in a ~15ppl company, where time and efficiency matter, LLMs really helped out.
> Tesla deserves credit but it’s not Tesla that accelerated the world. It’s China.
China supplied the batteries, sure.
But there's definitely a pre-Tesla and post-Tesla world regarding the vehicles themselves. Tesla changed the image of EVs available to the general public by making performant and low maintenance vehicles that looked futuristic and were capable of things basically only supercars could, for a fraction of the price. And they built the DC charging infrastructure all over the world to support long-range trips, which was non-existent before Tesla. EVs before Teslas were basically niche experiments.
> EVs before Teslas were basically niche experiments.
The Nissan Leaf (which predates any Tesla production car) was pretty much an electric version of previous Nissan cars. The VW eGolf (contemporaneous with the Tesla Model S) was _literally_ an electric version of a previous VW car. The VW ID.3 and 4, which are currently leading the European market, are also pretty much like VW electric cars. In practice, 'weird' electric cars mostly failed.
Have you ever driven more than 200km at an average of 80km/h with enough turns on the highway? Perhaps after work, just to see your family once a month?
Driver fatigue is real, no matter how much coffee you take.
Lane-keep is a game changer if the UX is well done. I'm way more rested when I arrive at destination with my Model 3 compared to when I use the regular ICE with bad lane-assist UX.
EDIT: the fact that people that look at their phones will still look at their phones with lane-keep active, only makes it a little safer for them and everyone else, really.
If you're on a road trip, pull the fuck over and sleep. Your schedule isn't worth somebody else's life. If that's your commute, get a new apartment or get a new job. Endangering everybody else with drowsy driving isn't an option you should ever find tenable.
Maybe I wasn't clear. I've always stopped to take a nap when I had the inferior car, because I knew I was risking my well being and that of others. Ever since I bought my Model 3, I never had to.
As an example, after a refreshing 8h night's sleep, you put yourself at the wheel and you know you need to drive for 8h. After 2h, you'll feel the need to stretch your legs, have a bite, go to the toilet.
But if you have something like Tesla's AP, you'll still be alert and awake. Otherwise - at least for me, but I bet for many people - the constant nagging of micro-correcting the wheel, keeping the distance to the car in front, keeping the right speed, takes a huge toll on your mental resources, so much that it puts you to sleep whether you want it or not, and many people will try and push through that regardless.
You're saying that cruise and lane assist are dangerous because they're used to do bad things.
I'm saying they're very liberating from the busywork that is driving, and even people that use them as an excuse to stay on their phones are better off for it, because something more alert and precise is driving for them and as a consequence, less harm can derive from their stupidity.
I'm not saying that people that do stupid things should not be punished, and I'm quite happy that Tesla had to implement better driver monitoring. I know how things work and that I always need to monitor the system, but many people assume it's a magic button and disconnect their brain.
> The problem is knowing which lane keeping assist systems are good and which are not. Every dealer just treats it as a 'checkbox' item and implementations vary by model and year.
Yep, I agree.
I used to travel to my parent's home 300km away once a month, and changing from a 2010 no-assist car to a Tesla Model 3 with AP (not FSD) back in 2019 was a game changer. I used to drive there on a Friday evening after work, and I basically collapsed into bed when I got there. With AP I was still tired of course, but also still functioning and way more alert. In my experience Tesla's AP UX is very good: chime when engaging, chime when disengaging, you don't need to look at the screen to know the state you're in, and if you touch controls it lets you know (via chime) and deactivates.
One of the most horrible UXes for me has been on a new Hyundai i10 with the basic lane assist (and I know it's very similar on a new VW Golf that my cousin is leasing):
- there's no chimes, you're forced to look at the screen at the center of the dashboard
- said display is 100x400 (or sth similar) 16-color pixel screen in the center of the dashboard
- out of said display, you need to look in the very corner for an icon of 10x10 pixels that can be yellow, green or white (which under low backlight/high contrast conditions can be tough to decipher)
- lane-keep is on by default at every car start, and tends to butt in on twisty roads (very common where I live), so half-way through a turn you'll feel the steering wheel literally lose force-feedback, while you're still applying force, and swearing ensues
- someone thought that constantly reminding people of the speed limits was a good idea, so the car will scream incessantly at you for being 50.1 over 50
- but will happily let you change lanes and re-engage auto-steer automatically (you need to manually enable this) while doing 120km/h on the highway without any hint that it's re-engaging automatically
- the speed warning is yet another setting that you can turn off at runtime, but you can't persist properly
- auto-steer, after is manually engaged, will stay happily engaged even after you leave they highway and are at very low speeds, and will try to correct you when doing roundabouts
I think the Tesla UX is way better there, and I think regulatory bodies should start preventing things like the i10 assist to be sold to customers, because they're actively dangerous. I've literally had minor heart attacks due to the lane-keep butting in on twisty roads - I thought the front tires were slipping for some reason.
I was driving until not long ago a VW with all those systems and, while less pleasant than the current Audi, I never met any of those inconveniences you met. Yes I know sample size, but... So, lane assist had zero visuals involved - activated or not activated, and giving your wheel a soft bump in that direction (it never tried hard turns, for better or for worse). The downside is that construction sites with colorful lines would indeed confuse it, so you'd either press the disable button, or keep your hands on the wheel (wife complained about it, but for me it was acceptable). The Audi handles construction sites perfectly, so far (soon a year). Speed limits meant on both cars only a visual some place, so you could ignore it (Audi highlights on the HUD the speed limit). So all in all, I believe Hyundai f'up it big time, or something got really wrong in that car - a perfectly good reason to give it up either way.
That's in the 50k EUR - 77k EUR range which is senior-level pay in EU. Add to that it includes pension, tax prepayments and health insurance. They also seem to offer lots of perks in the office.
If you account for the fact that Poland is generally less expensive than the average and that the average monthly living cost is ~900 EUR ( https://www.numbeo.com/cost-of-living/country_result.jsp?cou... ), even the 50k lower bracket is in the higher range. You get ~2k EUR net/month in your account after pension and tax contributions, health insurance, rent and expenses (as a single). That's not bad at all. EDIT: (excluding rent)
900 EUR might be enough for student-like living if you own the apartment you're living in, or by sharing a room when renting, but it's not even close to acceptable level in Warsaw.
Other brands force you into doing yearly/x-1000-km inspections to keep your warranty, even for EVs. If you were to skip their inspection cycle, they may decide not to cover the issue, even if it's clearly a warranty case.
You go to the garage for a Tesla only if it's broken.
In my experience with my M3 2019, I think many people don't even realize they have issues, because the cars are generally silent and decently insulated (the Highland even more so). Also, lots of people pay no attention to sounds and general driving feeling their cars make (e.g. steering wheel shaking, clicks doing certain actions, ...). The main/biggest issues with well-kept Teslas are basically suspensions, for which there is no monitoring/sensors, so the car cannot report to you that something's off.
Example #1: I asked the Tesla service center in Dec 2024 for an inspection, because I was leaving for a country with no service centers. Everything was fine after 6y and ~60'000km, they told me to just break every now and then because otherwise the brake rotors will rust. So it'd have likely failed the TUV inspection only for having a little rust on the rotors, otherwise perfectly fine and driveable.
Example #2: last year (after changing country) my rear axle nuts came a bit loose, not enough to be dangerous but enough that the axle/wheel hub interface would have some play (which could potentially become dangerous if you leave it alone for a few thousand kms). You'd hear a clunk from the back when applying torque from a standstill. My wife and mother in law kept insisting everything was fine, that they couldn't hear anything, that it was all in my head. Took it to the mechanic: rear axle nuts were loose, right more than the left one (and I heard the clunk from rear-right). Fixed with 30min labor. Different people, different reactions.
Now I have the front-right wheel clicking at times that is likely the same issue or may have something to do with suspensions, but again, if you ask my wife, everything's fine. And without mandated inspection cycles, you only learn of issues at the mandatory state inspection.
- Poliovirus can survive at room temperature for a few weeks in soil, sewage, and water
- It's highly infectious with sero-conversion rates of 90–100% among household contacts
- Factors like poor sanitation, high population density, and low vaccine coverage all fuel transmission
Yellow fever needs mosquitoes to spread and has animal reservoirs. Once you reduce/eliminate transmission in those reservoirs, the virus basically can't circulate even with low human vaccination coverage. For polio, humans are the only reservoir, and it spreads directly person-to-person. That's why you can't just rely on vaccinating travelers.
Plus, vaccine-derived polio (cVDPV) is actively circulating in Nigeria and Chad right now. In 2025 alone Nigeria reported 62 cVDPV2 cases. This happens when vaccination coverage drops low enough for the weakened vaccine virus itself to mutate and spread. So it's not just reintroduction risk, the virus is actively evolving in low-coverage areas.
If a huge cluster were to emerge, you'd need rapid mass vaccination campaigns to stop it. That's way riskier than maintaining routine childhood vaccination.
"Yes, because unvaccinated humans lack immunity. A single imported case could spread rapidly through an unvaccinated..."
That's assuming there would be an imported case. Travel restrictions can solve that. That's how we handle other US eradicated diseases, such as yellow fever.
You'd still need mass vaccination campaigns because immunity wanes over decades. If it resurges, it will rip through the elderly, especially nursing homes.
Yellow fever is spread through mosquito bites and polio is spread person-to-person. An imported case of yellow fever is nearly impossible to spread, while an imported case of polio is virtually certain to spread.
Sorry, but it's simply naive to think that in today's global world we would not import polio. It's already happening right now in the US. The only thing stopping the spread is our current high vaccination rate. You'd have to cut travel to zero in both directions to stop it.
> testing the CI/CD script on gitlab. It doesn't exist, and it's hell.
Did you try the pipeline editor? It's at <project_url>/-/ci/editor
You can see how GitLab expands the code, validate it (syntax), validate it against a branch (i.e. what happens when I get a push on main), and visualize the full YAML spec of what you have in the editor.
I have that problem with GitHub at the moment because we're switching from self-hosted GL to GH due to company policies, and for me it's much less readable (but I also know I've been playing with it ~1 month so far instead of the 7+ years I spent on GitLab, so need to learn tools etc).
> Since you've been on the ride since '04, I'm curious to hear your thoughts. How do you feel the maintenance burden compares today versus the GCC 3.x era? With the modern binhost fallback and the improvements in portage, I feel like we now spend less time fighting rebuild loops than back then? But I wonder if long time users feel the same.
I'm another one on it since the same era :)
In general stable has become _really_ stable, and unstable is still mostly usable without major hiccups. My maintenance burden is limited nowadays compared to 10y ago - pretty much running `emerge -uDN @world --quiet --keep-going` and fixing issues if any, maybe once a month I get package failures but I run a llvm+libcxx system and also package tests, so likely I get more issues than the average user on GCC.
For me these days it's not about the speed anymore of course, but really the customization options and the ability to build pretty much anything I need locally. I also really like the fact that ebuilds are basically bash scripts, and if I need to further customize or reproduce something I can literally copy-paste commands from the package manager in my local folder.
The project has successfully implemented a lot of by-default optimizations and best practices, and in general I feel the codebases for system packages have matured to the point where it's odd to run in internal compiler errors, weird dependency issues, whole-world rebuilds etc. From my point of view it also helped a lot that many compilers begun enforcing more modern and stricter C/C++ standards over time, and at the same time we got Github, CI workflows, better testing tools etc.
I run `emerge -e1 @world` maybe once a year just to shake out stuff lurking in the shadows (like stuff compiled with clang 19 vs clang 21), but it's really normally not needed anymore. The configuration stays pretty much untouched unless I want to enable a new USE for a new package I'm installing.
I am replying here as a kind of "better place to attach".
Anyway, to answer grandparent, I basically never had rebuild loops in 19 years.. just emerge -uU world every day or sometimes every week. I have been running the same base system since..let's see:
I have never once had to rebuild the whole system from scratch in those 19 years. (I've just rsync'd the rootfs from machine to machine as I upgraded HW and gradually rebuilt because as many others here have said, for me it wasn't about "perf of everything" or some kind of reproducible system - "more customization + perf of some things".) The upgrade from monolithic X11 to split X11 was "fun", though. /s
I do engage in all sorts of package.mask/per-package use/many global use. I have my own portage/local overlay for things where I disagree with upstream. I even have an automated system to "patch" my disagreements in. E.g, I control how fast I upgrade my LLVM junk so I do it on my own timeline. Mostly I use gcc. I control that, too. Any really slow individual build, basically.
If over the decades, they ever did anything that made it look like crazy amounts of rebuilds would happen, I'd tend to wait a few days/week or so and then figure something out. If some new dependency brings in a mountain of crap, I usually figure out how to block that.
I understand it has become a standard but it's not a particularly good one, and adding it "just because it's a standard" would detract from the car experience in my opinion. It's a separate device, with a separate OS, kernel, apps etc where you can install almost anything, that's supposed to take over a piece of equipment that belongs with the car and controls all its functions. I'd really rather not have that.
If the infotainment is the basic "show 2D maps and a couple settings", then Android Auto/CarPlay can serve as a viable replacement for low-end cars. But when the car costs >30k and the screen is also the central command console, no thanks. I'd rather have proper OTA updates, give feedback, and see it evolve over time for the better.
reply