News for hackers. Stuff that matters.
Re:A former Uber engineer's disaster story by pfortuny on Thursday December 10, 2020 @02:42PM (#25377630)
Not as per the long twitter thread.
Re:A former Uber engineer's disaster story by mewpmewp2 on Thursday December 10, 2020 @03:53PM (#25378484)
Well... It should be.
Re:A former Uber engineer's disaster story by ska on Thursday December 10, 2020 @05:10PM (#25379454)
That is a trade off with some pretty deep implications and some subtleties. I doubt it's such an obvious choice.
Re:A former Uber engineer's disaster story by jay_kyburz on Thursday December 10, 2020 @08:44PM (#25381285)
I've been thinking about pushing more in my client make less work for my servers.
Re:A former Uber engineer's disaster story by mcguire on Friday December 11, 2020 @02:15PM (#25389509)
Evaluating map data inaccuracy? More than just a payment UI? Driver/passenger matching? Data analytics? (Doesn't that require information from multiple clients?) On the client?

I mean, you could push some of that to the client, but I'd understand why your app is gigantic and doesn't do app-ly job very well with all the background processing. And I'd be surprised the app hasn't been hacked to get at the analytics data, if not the payments.