21–30 of 153 posts
> And Angular is… well, it’s not React. Can someone explain what this statement means in terms of the technical benefits of React over Angular?
Probably just means that Angular (at least seems to be) losing momentum and marketshare to React. It's hard to go a day without seeing something cool or exciting about React on the front page here, but all you see about Angular is either nothing or articles about the upcoming(?) transition to 2.0.
I am amazed by how the article attempts to look forward to what the future will hold with JavaScript frameworks... and yet seems to be completely both dismiss or misunderstand (perhaps willfully) why previous frameworks have succeeded. jQuery did not succeed because it was a 'good enough' competitor to dojo or prototype or mootools or extjs... it succeeded because it went completely the opposite direction. it did not…
Interfacing with the DOM was not even something that dojo, mootools etc were doing at the time. At least that part wasn't as obvious/easy in those frameworks.
Can someone chime in as to whether React won the frontend war? As in the super majority of new project will be developed in React. I'm not that well-versed in the Node ecosystem (I got my news from ... HN). But from little I've seen, I found it hard to believe that React would be able to react the place where jQuery was (is?). Heck, we even have a post staying on the front page today lamenting the inferiority of Reac…
Then I started catching up on Angular 2 and TypeScript. It looks like the right mix between new and opinionated. I just don't have time to research a module for data, one for building, one for testing, and one for validation. That's where an opinionated framework comes in handy.
I do hope Angular 2 takes off.
Any other Angular people out there weighing in between React and Angular 2? If I were a betting man, I say it's going to come down to those two for the next few years.
This is important because development standards are a
winner-takes-all game: once jQuery became the default, it enabled an
explosion of plugins and components built on top of it,
and every JavaScript widget became a jQuery widget.
The exact same thing might very well happen with React.
And that’s a very exciting thing for Meteor.
I completely agree and I'm excited about this vision for Meteor. The dream would be to have a go-to choice with formidable standards that Just Works. Personally, what I wish existed was a full-stack framework AND dev ops built with the "best" open source libraries. I'm fine with not having my favorite X if it means having a set of well supported, highly performant with lots of documentation and training materials ser…
IMO, innovation stops when we believe we've found "the best way of doing things". I'm all excited to check out Meteor too, but I'm not getting in line at the Apple store, I mean full-stack framework store, on the day of release to be a guinea pig for the "new best thing" at my personal expense (time).
That was the magic trick that sold your client.
They proved real-time data synchronization could be simple and seamless, and everyone else had to run to catch up.
But that trick is now 4 years old, and nothing else of substance really emerged.
As Ember, Angular and React grew, you were never going to want to use their odd looking front end.
Their data sync also came with dubious claims to scalability, not the least is their tie to Mongo.
That may be fixed now, but the consequence is being tied into Meteor Galaxy.
Meteor should have thrown everything away, and become just the data layer.
Like Firebase, but open source, and backend / datastore agnostic.
They tried to standardise DDP, but it didn't catch on.
But what the world needs is a standard like GraphQL, but handling data updates, and with automatic realtime data sync.
Thatd be a wonderful legacy for Meteor.
But this won't happen, as the company needs to make money from hosting.
Earlier quoted context omitted.
Part of the reason this year has been a bit of a mess is because MDG has been focusing a lot of resources on the profit-generating component of their business: meteor hosting and support. They launched Galaxy (their hosting service) just a couple months ago so it's still too early to say how successful that will be, but it could easily be in their best interests to cannibalize some of their older features if it helps…
Not having to spend money on Blaze will make them more competitive as a hosting business. Frankly, when is the last time you saw a billion dollar unicorn hosting business? Or a hosting IPO? I doubt we will see SQL support. We will likely see something with GraphQL instead.
> Frankly, when is the last time you saw a billion dollar unicorn hosting business?
Can someone chime in as to whether React won the frontend war? As in the super majority of new project will be developed in React. I'm not that well-versed in the Node ecosystem (I got my news from ... HN). But from little I've seen, I found it hard to believe that React would be able to react the place where jQuery was (is?). Heck, we even have a post staying on the front page today lamenting the inferiority of Reac…
No, Or to rephrase, No React has not won the frontend war in the way and scale that jQuery won the front end war. At one point something like over 50% of all new (at the time of its peak) web applications big and small included it? No. I mean jQuery actually really lost its stranglehold primarily because the browsers actually started incorporating most of its core ideas into themselves to a point where it wasn't 'nec…