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

I think it's still simpler, actually. IME the most complicated part of an ICE vehicle is the power delivery system. Transmissions are nightmares to work on. Making that all-electric and just using an engine to generate power significantly simplifies the system. I'm not a mechanic though, so take my word with a grain of salt.

My understanding is that going to hybrid actually allowed Toyota to significantly simplify their transmissions relative to ICE vehicles, even without going full EV.

The planetary gear "eCVT" systems that Toyota and Ford use in many models are mechanically a lot simpler than a traditional automatic or sequential manual transmission. Few moving parts and no clutches at all. I don't know what the long term reliability of those drivetrains is is but I wouldn't be surprised if it's measurably measurably better than a traditional transmission + engine. There's a long educational video from Weber State University that gives a good walkthrough of what's going on in those things.

https://www.youtube.com/watch?v=O61WihMRdjM


Obligatory Colin Jost Pete Hegseth warrior ethos post: https://www.youtube.com/watch?v=vZb1WO1_lGI

God I hope my bank isn't using agents to build things. "Sorry, Grok misplaced your retirement funds."

I'm new to the security side of things; I can understand that leaking any information about the backend is no bueno, but why specifically is table size an issue?

In my old company new joiners are assigned an monotonic number as id in tech. GitHub profile url reflected that.

Someone may or may not have used the pattern to get to know the attrition rate through running a simple script every month))


The author doesn't reference any tests that they themselves ran, but they did link a cybertec article [0] with some benchmarks.

[0] https://www.cybertec-postgresql.com/en/unexpected-downsides-...


I think they address this in the article when they say that this advice is specific to monolithic applications, but I may be misremembering (I skimmed).

Are you saying a monolith cannot use a distributed database?

I'm not making any claims at all, I was just adding context from my recollection of the article that appeared to be missing from the conversation.

Edit: What the article said: > The kinds of web applications I’m thinking of with this post are monolithic web apps, with Postgres as their primary OLTP database.

So you are correct that this does not disqualify distributed databases.


> It's just aggravating to see someone write "totally undeniable" when the thing is trivially denied.

You've described AI hype bros in a nutshell, I think.


I think that is it happening is an important question, but “does the consumer actually want it to happen” should be equally important. It won’t be, because the c suite will just make the decision for us all, but it ought to be.

If done properly you shouldn't be able to tell. A really good voice AI assistant is indistinguishable from front line support reading through a script, and potentially a few steps better.

You forgot the italics on Y

Also the rumor I heard from a friend at Apple (hearsay, obviously, and an anecdote to boot) was that Alan Dye was pretty unpopular among designers.

Yeah, I'd definitely classify Dye in the "failed at their jobs" category alongside 1, 8, and 9.

Bad AI is a venial sin at Apple, but bad design is mortal. Or at least, it used to be.


i wonder if Dye is the self-important personality who parked his audi r8 in handicapped parking routinely in front of IL1.

if not Dye, then apologies to Dye for looking like that person.

also, there's this.

https://9to5mac.com/2025/12/04/gruber-apple-employees-giddy-...


And users too!

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

Search: