221–230 of 422 posts
Great. I was waiting for React to stabilize before I learned it. I've been cleverly waiting since 2006 to learn jquery. Will start next year.
> Great. I was waiting for React to stabilize before I learned it. But once it's stable, it's outdated.
Earlier quoted context omitted.
I would love HN to provide an easy way to see where the reply thread to this first comment ends. Some js might enable that. Basic html/css - I think no.
It's that [-] button next to the username above each comment. It collapses all the cascading comments. It is enabled via JS. If you disable JS, then it disappears.
Earlier quoted context omitted.
And I would love if my 2001 Honda Accord was compatible with Tesla's autopilot, but I understand it is not a realistic expectation. I'm not sure why you'd expect the web to be a. Mostly text and b. able to render easily on obsolete devices. The web is becoming a robust application delivery platform. That is so, so awesome. Most people do not want to be stuck with shitty looking, text only websites. Moving the platfor…
They may be robust but the user experience still sucks. JS heavy web sites are unresponsive and turn my 3 year old MBP into a vacuum cleaner. Facebook is the best example. I can barely load the web site without the fans spinning. Firefox can't handle it at all. It is unusable for me.
Does it the Frontend ecosystem has yet another new framework? Do we have to retire the old one and learn the new one all over again?
Earlier quoted context omitted.
I admire your exceptional work cataloguing these resources. However, just one look at that giant horde of links is, to me, a perfect demonstration of why the front-end development ecosystem is way out of control. Its amazing to me that the autoconf/automake/libtool system for making write-once-run-everywhere *nix applications is downright simple by today's standards. Every year the hot libraries change, the build too…
That's because noone really, truly, honestly want to RTFM of a given stack, library, etc. It's more fun to roll your own or to pick up a new one. I mean, in how may ways can you organize code that manipulate a DOM tree, pull data, massage data, and update the DOM tree? Well, the more the merrier :)
React will die by the weight of the frameworks and libraries that have duplicated effort and created more confusion and divide amongst the developer community.
So they have created a kind of map/reduce system to distribute computation over a tree, except everything still runs in the same Javascript main thread.
Earlier quoted context omitted.
And I would love if my 2001 Honda Accord was compatible with Tesla's autopilot, but I understand it is not a realistic expectation. I'm not sure why you'd expect the web to be a. Mostly text and b. able to render easily on obsolete devices. The web is becoming a robust application delivery platform. That is so, so awesome. Most people do not want to be stuck with shitty looking, text only websites. Moving the platfor…
They may be robust but the user experience still sucks. JS heavy web sites are unresponsive and turn my 3 year old MBP into a vacuum cleaner. Facebook is the best example. I can barely load the web site without the fans spinning. Firefox can't handle it at all. It is unusable for me.
Does this mean something for someone starting in React Native or the changes in that regard are just under the hood?