41–50 of 77 posts
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…
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…
Things are just now starting to feel maintainable and reproducible. I think it's great.
I'm just really glad Vue is now included in every "X vs Y" framework, or "choosing a js framework", almost every article for the past two years have only been for Angular or React.
I think Vue is great but I wish Aurelia would show up in more of these comparisons as well: http://aurelia.io
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'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.
How do you see the relevance of react and vue for RAD 2.0?
Ember is so good, it does not need comparisons any more :) https://medium.com/@alvincrespo/ember-your-best-bet-b5cd7275...
I would argue that it is by far the worst Framework one could possibly choose.
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…
Earlier quoted context omitted.
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.
Except maybe the reason the web flourished is because it wasn't stuck in the desktop paradigm?
I am saying that the paradigm for creating a UI is not so different. I have a component with a lifecycle, events, logic, and styling, and it can be instantiated arbitrarily many times and behave predictably. That's pretty new in web tech.
As a specific example: "For decades, developers were trying to separate UI templates and inline Javascript logic, but with JSX, these are intermixed again."
This is fantastic guidance for brochure sites, but did it ever really suit application development? UI components certainly have intrinsic layout and logic, and our unbundling of that, I think, came from overzealous adherence to the "rules" of a different game.
Earlier quoted context omitted.
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.
RAD is definitely back, it even has it's own gartner quadrant: low-code, with tools like Mendix, OutSystems, Betty Blocks, MS Power Apps. How do you see the relevance of react and vue for RAD 2.0?
I recently saw a company with a beautiful library and workflow for react; npm i your component, import it, and off you go with a on-brand (by default) visual component. Start binding event handlers...