Angular is finally working hard be something we can continue to use. I absolutely love Angular! Some of the new features we know they are working o...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for the mention Jonathan! Some of these items are definitely already on my radar also, the two main being Automatic TransferState and Server-Only routes.
Analog already supports Netlify, Vercel, Edgio, and others by way of using Nitro as its server engine.
Good to know! I think all Angular devs appreciate your work! Excited to see the future!
@brandontroberts Most welcome of Automatic TransferState and Server-Only routes in new angular world.
Thanks for sharing this article, haven't heard of analogjs.org/ yet. Nice!
@jdgamble555 Thank you for sharing this useful things related to angular.
React is not dead. And who say it is slow if it can run super complicated UI smoothly such as this
quanla.github.io/macos-demo
Compared to Solid, Svelte, Vue, Qwik and even Preact, React is very slow. Angular and React are on a different level. My point about React being dead was that NextJS is a big reason it is as popular as it is.
Oh, you mean "not moving" when you say dead. Yeah, I agree it doesn't change much, but it doesn't bother me, since not changing means stable and mature. Who need to change when you are already good enough. Like "pencils" are dead, because they stay the same since forever... yeah.
Anyway, I don't even use Next, so I don't think Next is what keeping React alive. Have built many complicated React systems with the bare minimum (React 6) and still eager to build more with it.
Could be more convincing if you can give examples of how those "super fast" libs can build complex apps comparing to React... or if they can build at all (other than todo list).
Anyway, it's great if you can checkout the Mac OS that I built using React, it's packed with features and silky smooth. Can't complain
My article is NOT about React, although I'm glad it works for you. Not sure how to respond to your assumption that React is the only library that can build more than a todo app. Solid and Qwik are new, but many have used them for complex production. The features are insane. Svelte is mature now, and Vue is nearly as old as React and Angular. Preact can support most React packages, and Qwik and Solid can too.
People don't spend years developing Frameworks, especially meta frameworks with SSR, to build just todo apps. These frameworks have more features than Angular for SSR, and arguably simpler.
All frameworks have something great to offer, and they learn and build off each other. Angular is just slow on the SSR front. I'm hoping that changes.
Most React people assume React is the only thing in existence. It's the equivalent of iOS users who think iPhone is the only smart phone there is. A good mix of cult and ignorance
Ok, I take it as React is NOT dead.
Anyway, I just looked at both Solid and Qwik, quite nice. Basically I only care if a lib use Virtual DOM or not. I don't think Solid have a future, just like Angular
And why you bring up Preact? It's basically React. Geez
Virtual DOM? Really?
Yes. Virtual DOM. What is wrong. I think the naming is stupid but it is the defining feature of React and the like (Vue, Preact or Qwik). What is the problem here?
Virtual DOM is an abstraction to DOM. If you already know about the DOM, you know the web. Virtual DOM is another layer of DOM that is created by frontend frameworks that uses it.
Every time you make a change to state of a component, it a new Virtual DOM snapshot of that component is created, replace the old one, and only then is reflected in the DOM. This means that every time you update a state at one place, the entire component re-renders itself.
The changes made to the update the state is called reactivity, and Virtual DOM is the old-fashioned reactivity paradigm which was used by many popular frameworks that dated back in 2012 when state management is a huge overhead and updating states surgically in one place is extremely hard. The way that Virtual DOM works is simple: Re-render everything when there is a change. Therefore, there is no overhead of developing libraries using Virtual DOM and performance is acceptable, at least when the library is not large
However, in modern day frameworks, such reactivity is too expensive and inefficient as the price of performance gets higher and higher as the ecosystem grows. Many benchmarks have shown that Virtual DOM frameworks like Vue, Angular and React, in fact, are very slow, especially React. One single state update in React could last up to 100ms.
This is due to:
For these 2 reasons, modern frameworks started to move away from Virtual DOM and design their own reactivity paradigm, most well-known ones being Svelte and SolidJS as they're able to surgically update the state, while Astro and Qwik introduced new hydration strategies and significantly reduce JavaScript bundle.
Hope this help!
Yeah, except that I have almost 20 years of experience and have gone through many things before settling with React (Angular, JQuery, PrototypeJS, Java Swing, .NET, ... ). Call me ignorant, I don't care, have seen so many flashy new techs before. Build something awesome with it (like my MacOS), then we talk
Not talking about you, about generic React beginners. It is a framework that most beginners start with, and get stuck with.
For ENV variables, you could try
chihab/ngx-envon Github.Thanks, also wrote this arricle - dev.to/jdgamble555/angular-univers...
Compared to
@ngx-envyour approach seems way overcomplicated.True, but the
ngx-envpackage adds more dependencies and extra overhead. There are tradeoffs. Obviously best option would be if Angular had this built-in.Agree
Am I the only one who doesn't like file-based routing?
I find file-based router an abomination. It's leaking into the file system and coupling to it details of the implementation which I don't think should occur.
One thing is having files being named by conventions like app.component.ts or users.service.ts, but you can name them another way and they'll continue working... With file-based routing is the other way around... I'll never understand why anybody would choose to do that.
Of course, it's not a silver bullet but from my experience and observation it is a good architecture choice for 90% of projects (from small to big)
I think first of all author tries to say that we need options to choose from in our Angular world. Not that file based routing is always better than the "classic" way
The largest and oldest project I've been involved with using React. I've created the most projects using Vue. The projects for our company's biggest clients using Angular.
We've been talking about Next.js all the time but never implemented any project, We are excited about Nuxt, but only implemented two experimental side projects.
We care less about SSR, the main reason is that we found that it's a challenge for system design and we already have a solid foundation on .Net. We know there are some SEO problems related to SSR, but I don't think that is the appropriate scenario to use Angular in the first place.
And speaking of performance, I personally find that projects suitable for React and Angular usually aren't very strict about performance(or we can boost the hardware). Furthermore, projects that are strict about performance wouldn't choose them(though that's rarely the case).
Personally, my favorite frameworks are Angular and Nuxt, and they've also been used on different purposes.
So in my opinion, even though these frameworks can accomplish similar tasks, I believe they target different groups of developers, there is no "dead" or some terms like that. But I know what you want to say and I agree most of them, great article!
I could see that and tend to agree. That doesn't mean Angular couldn't become better so that it can target more groups IMHO. Angular is very solid as a framework.