211–220 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.
Not sure if serious, but this update swaps out the internals without affecting users/developers, the API is fully backwards compatible
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?
I've been working with react for a bit more than a year, and I am trying elm. I think elm is the best thing that happened to the web in general. It's really daunting at first, but I highly encourage you to try it.
Elm really could be the future of bullet-proof web development. It has everything it needs except for runaway popularity.
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.
No thanks I'll stick with plain html and jquery for the frontend of my small projects. Plain javascript works perfectly fine as long as you namespace your functions and separate them into different files. All these frameworks end up creating much more problems than they solve.
As someone who has worked on a truly large React project, I can assure you this is not true. I cannot imagine the shitshow that project would be using jQuery to track the state. Nearly as soon as you progress from 'backend rendering html' to single-page-app, it behooves you to use React.
Worked on or maintained an existing app for a number of years? There is a very big difference.
Earlier quoted context omitted.
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.
Might be more Firefox than your macbook or the web. I've noticed (while developing an extension) that Firefox feels noticeably more sluggish than Chrome. Safari somehow feels even faster than Chrome, but I'm too tied to the extension ecosystem of Chrome to switch.
Earlier quoted context omitted.
>"At the end of the day all it would take is one of the 3 major browser vendors to offer an alternative." You mean like Dart? Besides, languages that target WebAssembly are almost certainly going to evolve to fit that space.
I have serious doubts that WebAssembly is really going to come to dominate the web the way many people here seem to believe it will. The idea that all of sudden there is going to be a rush to push compiled/closed sites after so many very successful years of using free-and-open stacks seems rather non-logical to me. Time will tell.
Earlier quoted context omitted.
The word Java and "simple development" is just absurd for any real application much less most enterprise applications.
Is it that absurd? Building Java applications using Undertow with a build setup in gradle is not _that_ different from a node.js service using Express and package.json for dependencies, or a Ruby, Sinatra and Rake stack. After having tried all three, I ended up going back to the JVM. It's not a perfect ecosystem, but it's damned good one.
Also there's definitely been some cross pollination of ideas from at least the Ruby world to the Java (Rails inspiring Grails and probably Play too), so it's getting better. Add java8 lambdas, and it's quite nice.
How does it compare with vue.js? I never worked with any modern JS framework like this but on paper I did not like writing CSS in javascript and vue.js had a normal way to write CSS and to me it looked superior in other ways as well.
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.
Not sure if serious, but this update swaps out the internals without affecting users/developers, the API is fully backwards compatible