51–60 of 77 posts
The post is wrong about React changing the BSD+Patent license. It hasn't changed and is still an issue, depending on who you ask. [0] https://github.com/facebook/react/issues/10191# [1] https://code.facebook.com/posts/112130496157735/explaining-r...
It drives me crazy when I hear things like Angular4+ is better for "Large Ambitious Applications with large teams" when in reality Angular4 suffers from the same slow down/performance problems as Angular 1.x. https://github.com/angular/angular/issues/14041 https://www.airpair.com/angularjs/posts/angularjs-performanc... I mean it's like they ignored all of the lessons and knowledge the industry has learned and produce…
Ember is so good, it does not need comparisons any more :) https://medium.com/@alvincrespo/ember-your-best-bet-b5cd7275...
Earlier quoted context omitted.
As far as i understand, Polymer (and Web Components, in general) permits to define custom HTML elements. What kind of custom elements are in the (insanely unreadable) Youtube main page?
Did YouTube switch to Polymer yet? I think only the new design ( https://www.youtube.com/new ) uses it, and it's not yet switched on by default?
I've been using vue since it's conceptions (well, nearly) and it's been a joy. Initially, the templates provided the perfect path to migrate from angular 1.x. That, among other things, was the main reason I chose it over react. Now, years later and having experience with JSX in Vue, state, and building large apps, I finally checkout out React and discovered that they're pretty much the exact same thing: Define a comp…
choosing Vue.js over any of these frameworks is almost a no brainer IMO.
But, having used both Vue and React, I wouldn't say that either has a clear advantage over the other. They do the same shit in similar ways. For me, it just came down to coding preferences, and the amazing documentation the Vue has. React can fill the same roles equally well.
I've been using vue since it's conceptions (well, nearly) and it's been a joy. Initially, the templates provided the perfect path to migrate from angular 1.x. That, among other things, was the main reason I chose it over react. Now, years later and having experience with JSX in Vue, state, and building large apps, I finally checkout out React and discovered that they're pretty much the exact same thing: Define a comp…
I feel like it's 20 years ago and we're seeing the golden age of RAD again. Doesn't it feel weird to anyone else that we spent so long on the web reimplementing basic visual components with spaghetti code, as if desktop UI software never existed? I suppose hindsight is 20/20. Things are just now starting to feel maintainable and reproducible. I think it's great.
I do agree with the maintainable remark though. Things seem like they're slowly congealing in the frontend JS world into the new paradigms we've chosen. But I feel like this is only making way for developers to throw their weight at the backend. It wouldn't surprise me if suddenly a GraphQL competitor came out soon, igniting a new flamewar and churn in API design that we'll all have to start dealing with.
Earlier quoted context omitted.
Can you explain why?
The just is FB added a clause that if you sue them and use their stuff, you immediately lose the license. So they could counter sue for breach of contract.
I recently used both Angular 2 and React (the latter more recent) in some small projects. While I enjoyed working with React, I think Angular is more suited for me, a one-man startup. A lot of decisions are already made and I just follow them. In React, every time I need something not built-in (which is very often), I have to do some research, and even after deciding one, I have this "what if I'm wrong" guilt at the…
My biggest problem with Angular2 is how restrictive an obtuse the framework can be at times. I've ranted about it in other comments so I'll save space and just say that Angular makes easy things hard and difficult things nearly impossible once you step off the dotted line. Also the lack of a really solid UI library has caused many headaches. Material isn't very configurable, PrimeNg is okay but somewhat buggy and poo…
The post is wrong about React changing the BSD+Patent license. It hasn't changed and is still an issue, depending on who you ask. [0] https://github.com/facebook/react/issues/10191# [1] https://code.facebook.com/posts/112130496157735/explaining-r...
Preact https://preactjs.com/ is a good purely MIT licensed drop in replacement for React if licensing is an issue
I tried learning Angular but found it to be too monolithic, and I'm currently using React Native to develop the mobile apps. If React Native is any indicator of how React web works, I don't think it compares to RiotJS in terms of developer happiness.. i.e. React has a tougher learning curve, the code is less readable and not as concise, a lot of things feel unnecessary, whereas RiotJS is significantly more lightweight, more intuitive, and faster to get things working (from my experience)