Hacker Newsnew | past | comments | ask | show | jobs | submit | jval43's commentslogin

Counterpoint: the touchscreen in my car DOES work with gloves. Of course the knobs do too.

The screen is some different tech and not quite as responsive as an iPhone screen and does not do multitouch, but otherwise works fine.


What car do you have? Usually lower end cars have resistive touchscreens which yours sounds like an example of, but higher end ones have capacitive touchscreens and those don't generally work with gloves, but of course gloves that work with capacitive touchscreens exist and have for many years now.

Even Toyota is going touch now, with the 2026 models lacking climate control knobs.

I don't know why. Every review always praised the previous models for the physical buttons, and literally nobody asked for them. The physical buttons were perfect, yet they've taken them away.

There must be some grand anti-button conspiracy, it just doesn't make any sense.


Chasing trends and it's now cheaper to have a single touchscreen with software controls than to design and manufacture physical controls.

There’s less need for a physical button for those things now that climate control algo has become so good it has been on Auto the entire time for me.

A screen costs 75, a button is 1 each. You get a lot more that 100 buttons on a screen.

Not to mention the physical space a button takes.


We can't. It's just that everyone and their dog has an interest in selling you that lie because money.

Stochastic parrots can code yes, but that does not make them experts. Don't trust them with your life.


I did, in Java 2ME for my Nokia. That was a completely different experience and much harder to get going. I did make a color 2D game though in about a week.

The TI-200 was much more accessible and fun, creating small little programs during or after class. Only once you wanted to go assembly did it become a chore again.

To summarize: not the same.


I love the Lightning connector, and think it feels better than USB-C. My Intel MPB has terrible USB-C ports where the cables just fall out all the time.

But to be fair I've also had many issues with Lightning. A few shorted out and became unusable and burnt on one side. And those were 100% original bought in the Apple store, as were the 5W chargers and iPhone this happened with.

Knockoffs were generally terrible and might stop working. A "genuine" cable bought from big retailer turned out to be a knockoff once after a software update, resulting in annoying popups from Apple. And some knockoffs were so bad they didn't stay in.

Even certified Mfi ones from Belkin somehow felt different, like the tolerances were slightly off. Those worked though.

Overall, I think it's had a good run and was underrated as a connector physically, but on the whole I like USB-C and it's more open ecosystem more.


Bungies Marathon series (1994) had the same recording system, as other commenters mentioned due to networking multiplayer.

What's totally insane is that the modern engine rewrite Aleph One can also play back such old recordings, for M2 Durandal (1995) and Infinity (1996) at least.


More like the model knew of the previous, almost identical bug from 6 years ago. Whoever discovered that should be credited.


My parents are retired. How exactly do they come into play?

I'm actively avoiding Shorts, Reels, and whatever else with those mechanics precisely because they pull you in and snap an hour is gone with nothing of value to show for it. It's so totally different from regular long form videos.

We regulate addictive substances too, even for adults and without relying on parents. The amount of productivity and quality of life lost to these platforms must be staggering in aggregation.


>they were just the cheapest labor the company could find who could do the thing.

Thats the problem right there. The company doesn't care. No amount of personal certifications is going to fix that.

It MUST be on the companies. They should be fined out of existence for such breaches and they would quickly change tune.


> They should be fined out of existence for such breaches and they would quickly change tune.

Looks like this is a great opportunity for an object lesson. Let’s see how it goes…

As far as certification stuff…

Civil engineering has had licensing forever. That’s because Bad Things Happen, when they make mistakes.

I do think that it would be a good idea to score/certify critical infrastructure stuff. That might involve certification of the people that make it, but it should certainly involve penalties for the people responsible. That might include the authors, but it should probably also include the folks that decide to use the bad code.

I know that ISO 9000 is an attempt to address this kind of thing. In my opinion, it’s kind of a mess. I’ve worked in ISO 9000 shops, and it’s not much fun. The thing you learn, pretty quickly, is how to end-run the process, as it’s so heavy, that it basically stops all forward progress. It doesn’t have to, but often does.

Mistakes get made. If you design carefully, these mistakes won’t cause real damage.

I just figured out that an app I wrote, that’s been out for two years, has an embarrassing bug (mea culpa). I’ll get it fixed today.

Because I’m pretty careful, it doesn’t affect stuff like user privacy. It just introduces performance overhead, in one operation, so the fix will mean that the app will suddenly speed up.

I’m not sure that certification would have solved it. My security mindset is why user privacy wasn’t affected, and that comes from experience.

> Good judgment comes from experience. Experience comes from bad judgement.


Also if you are personally liable of gross negligence, you will:

1. Get paid more (as less fake "engineers" are available for the responsibility).

2. Push back harder (or at least document in detail) on malpractice during development. Manager did not listen to your warnings? Document it and when shit hits the fan, the manager gets the stick instead of you.

Hitting companies with monetary fines does not work. Hitting the employees with jail time will make sure they don't sign on dangerous or known problematic systems.

Manager not listening? Remind them they will face a trial if the issue does surface.


> Hitting companies with monetary fines does not work. Hitting the employees with jail time will make sure they don't sign on dangerous or known problematic systems.

What!? So, when you can't switch jobs because the market is bad or for any other reason, your choices are: 1) quit and lose the income (which you can't afford) or 2) sign on whatever and accept the risk of jail time?


The job market in such society would not be the same as it is now.

If you are certified, chances are you will have lots of choices to work.


Sounds like every other vocation out there.

Software devs have been insanely privileged, for the last couple of decades. That seems to be changing.


I do this on my iPad with Magic keyboard and I'm a die hard command line user otherwise.

I think the reason I started doing it on the iPad is that the keyboard focus is sometimes inconsistent, so clicking or tab-tab-tab-enter is slower and less reliable vs. just touching the screen. Definitely feel the gorilla arm though.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: