4 ms·
Bitter over 30 year-old? (I'm 43 btw so not trying to be ageist, just asking what seems like an obvious question) It does look similar but it is night and day
by eagsalazar2 10y ago
Bitter over 30 year-old? (I'm 43 btw so not trying to be ageist, just asking what seems like an obvious question)
It does look similar but it is night and day different beyond the superficial appearance. Are you actually trying to say that the in-browser experience in web apps from 15 years ago were in the same ballpark as even simple single page javascript apps from today? That is laughable. So something must be different right?? Derisive condescending comments like yours prevent the conversation from figuring out what the positive is and ultimately keep the conversation stuck in the all too common and boring whining about javascript which has infected HN.
- flukus 10y ago> Bitter over 30 year-old? Yes I'm bitter that the same errors we made with desktop apps in the 90's (and possibly earlier) are being repeated. > Are you actually trying to say that the in-browser experience in web apps from 15 years ago were in the same ballpark as even simple single page javascript apps from today? Yes. The biggest difference is the amount of postbacks, the state handling has moved client side.
- tracker1 10y agoBut are they really the same... a common prescription for state management with react is to use something like flux or redux. State management solutions that have worked out well for gaming platforms to this day. Not the MVC patterns that bring a lot of complexities that make cross cutting concerns that much more difficult. This is emphatically NOT the same as the desktop apps in the 90's.
- deleted 10y ago[deleted]
- rimantas 10y agoThe problem is that while true web apps experience might have improved, the web as the whole degraded a lot since everyone is treating everyting as the app, whn in reality majority should be just a static content sites. Now you download 4MB of crap just to see 2KB of text.