4 ms·
Isn't this a false dichotomy? Why not create more modern, declarative native APIs and libraries, or use them where they already exist?
by smitherfield 10y ago
Isn't this a false dichotomy? Why not create more modern, declarative native APIs and libraries, or use them where they already exist?
- pcwalton 10y agoBecause it's less effort and more likely to be successful to just improve Web implementations.
- smitherfield 10y agoSure, but it's also more likely to make my laptop with 16 gigs of RAM, 8 simultaneous threads and SSD feel more sluggish than the one I had 10 years ago. Edit: I'll add, I frequently see people say that Windows XP was the best OS ever made. Why the rose-tinted glasses? It was the tail end of the era when hardware was getting faster, faster than software was getting slower.
- posterboy 10y ago> the old stuff worked just fine > we don't need the new stuff > how about we throw both away to shut everyone up, would that make either side happy?
- khedoros1 10y agoHow about: Take what we learn from new development so that we can improve the older, lower-level stuff, and strip away some unnecessary levels of abstraction?
- josephg 10y agoYep. I did some swift development recently and while I absolutely loved the language I was struck with how much worse the uikit APIs are compared to react. There's nothing special about javascript the language. The nice thing about web development is that the really fast framework iteration cycles. And everyone complains about them, but as a result we have some fantastic APIs for UI development in javascript land now. (Eg, react.) What I want to see is someone port those lovely abstractions across to native languages. For example, a port of choo[1] to swift on top of uikit would be gloriously fast, efficient, small and easy to work with. [1] https://github.com/yoshuawuyts/choo https://github.com/yoshuawuyts/choo
- deleted 10y ago[deleted]