in my opinion classes and templates are Angular. it's one of the main reason I use Angular. Please don't make Angular syntax like React or Vue. Innovation is great, but it becomes pointless when fixing something that works. I am grateful to the Angular team for creating and maintaining Angular. Every Angular release I am always happy, for new improvements, new features and the tooling that makes it easy to upgrade, thank you.
"Templates are Angular" - bah. Templates are templates. They convey a lot of things right now, and I'm very grateful they're as powerful as they are, but there are too many mixed concerns in the language. Templates currently mix - Layout - Style - Dependency injection and configuration (via Input and #references) - User experience (drag and drop). It will probably be impossible to get rid of Templates altogether. But it would be great if we could have separate ways of expressing our intent, which are apt. Host Directive binding will go a long way; We are moving to a future that's easier to understand, not harder. We should resist unnecessary change, while embracing pragmatic decisions that help improve clarity.
I couldn't say this better. There is something really wrong with the idea of constant improvement at the point of losing what the initial objectives were
Are classes Angular? - Yes Are template Angular? - Yes (They both give a nice way to separate the concerns. Makes the code well organized. Especially when you are working with a team with mixed technical expertise) IMO .. Please dont use React Singling - They are not intuitive at all. I would rather go with the flutter approach of just simply using setState().
i partly disagree, are classes angular? it shouldn't be this way, after all javascript classes are just sugar syntax for a function declaration (*not arrow functions) are template Angular? yes, and we have already two options for declaring our templates via a file in declared on the decorator or just adding the template itself on the decorator of the angular component. It's good that the angular team start looking to alternatives for zoneless application, would be nice to see increase in the performance just out the box instead having manually having to working with .onPush and working with the ChangeDetectorRef API.
@@RajinderYadav i have been updating a project since angular 8, and it has been going good. Some versions needed more changes, but its not a nightmare, angular is very good for big projects.
@@UNDEROATHRMT Templates are just the way we express part of our application. There could be other ways of expressing it which might increase clarity, or decrease developer time to achieve the same result. We should explore those options, provided we don't unnecesarily break things. People cursed and screamed about the [] and () syntax. But I'm grateful for it. Looking forward to the new innovations
I think that the object Orientation (Class Based) of Angular is one of its Core features as it makes it less mentally challenging to build High Quality Full Stack Applications. It also seems to me that this is the primary Use Case in business as is. Using Angular as the Frontend for Enterprise Applications where the Backend often Comes in C#/Java. The Concepts and Best Practises are not Far from what they are in those Backend Enterprise Languages. I love what you have done with Angular 15 and am curious for the future. I think that this Concept in Angular should be kept in mind tho. The similarity of Design Principles and Best Practices to Design Driven Backend Technologies, is a great benefit none of the other Frameworks offer. It's Easier to start with Vue for sure, but it is not very easy to understand how to cleanly structure a Vue Project from a experienced Backend Developer's Perspective. Similar in React, even tho this technology is likely closer to home for functional Programmers, NodeJS Backend Devs and general experienced JS Devs. Angular here fills the Spot missing, here we can use Design Principles also used in Backend Languages, to improve the base Design of our Frontend Application. I truly apreciate that.
lazy routes look cool & elegant, seems interesting features are ahead. ty, nice presentation as always 👌, modest and precise, with no marketing buzzwords like "supercharged" or "developer ergonomics"
Hi, thanks for the presentation. I am working and making Angular apps since v2 and being the responsible for update Apps with it since with v5, A lot of improvements on the way of update the apps with new versions and since v9 a much better performance in dev and builds speed. Until version 13 the syntax in ts and template engine has been stable, what i dont want to see is something like react and vue has, which is two ways to write apps ( functional components and composition) where you are introducing standalone components. What it is not very clear with standalone components in your docs and videos is if we still can separate the style and template of the component in separate files ( css and html), i had not yet time to try standalone comps and at my job still using v13, but should be clear, if standalone components only means component without the need to assign to module were the rest is the same like separate css and template from the logic ( TS ). About are Classes Angular? I think a components not always need a logic / TS file, I recommend Angular to read what Aurelia did and still doing for v2 ( so called html only components) and even emberjs is thinking this way. Another thing missing is choosing linter tool setup with Angular CLI.
Did you mention that they got rid of environment files? You can still add them if you want. I think everyone is preferring to use continuos deployment settings to update api urls instead of having to do it at design time with angular buid
I'm having trouble understanding some of the diction and unfortunately, adding closed captioning doesn't seem to help. Looks like it was autogenerated and it doesn't quite understand you either. Specifically when you start the section around ng build, there are words I can't understand. You might have said ng build is using es built? There were some other acronyms that you said as well. Suggest adding a little more content to the slides for when you say something like ng which is not a standard English word but is sort of a made up Angular or Javascript centric word the auto closed captioning system will not pick up on.
We're not bringing the preact implementation of signals in Angular. What I shared is an experiment we used to see how signals will play with the rest of the framework.
I will add also a plead. Please do not change templates and classes in angular. This is the best thing in angular and I do not want to write react in angular. React and Vue just sucks.
The debugging improvement is a welcomed feature. Angular is a joke of a framework that will continue to break, these clowns keep questioning and changes the core. Is class Angular, is template Angular....Is Angualr Angualr? They created NgModule when JS module could have been used and later decided it's not needed. Why wouldn't you just make all modules lazy loaded by default? then as the page loads, it fetches the code and resources need on "demand". Nope, they needed to over-engineer and add super ugly boiler plate code, to routing. You know what is not Angualr RxJS, Streams, Observals. These things alone have resulted in over-engineer crappy, abstract hard to read and maintain code with dependences breaking. Ngrx is an over-engineer mound of dung, just to be able to have a global store to get and fetch value, only 2 simple operation are needed. Again it's over-engineed with reducers, actions, selectors, effects, component store? WTF. Angular Material should not be a part of Angular. We have CSS so leave it to someone else to create a CSS library, it's just bloat very few want to use professionally. Also bugs go unfixed, so for CSS markup this is just stupid to tightly couple it to code not under your control. You can make your own CSS components, you already got Angular + CSS. Also their reference docs are incomplete, they haven't been worked on forever, maybe fully document it first? Answering: Is Angular Angular? Nope! This is why they keep breaking the code! Zero backward compatibility, maintanance nightmare.
Tbf, rxjs can be complexe some time, but it doesn't mean that's bad. The things you can do reactively thx to it, are actually quite impressive. Even tho i agree ngrx is in many cases probably not needed and brings way too much boilerplate. Rxjs is actually helping a lot to have a strong flow and reactivity. It can be done without it, but it's more painfull to achieve. The simple fact of using changedetection.onPush + async pipe to handle dom refresh is enough to justify using rxjs. You are actually writting way more stable code while using rxjs. Especially performance wise.
I try solidjs i have no guard no active class and more so i update the routing module to my need. Even react and other are not complete you have to use some lib to get your work done but angular have everything. Only sometime i use some lib.
@@puneetsharma1437 The sad reality is - business rarely give a sh about the things that are good for developer. They tend to make a decision based on business values, and the fact that there are 2x|3x more developers on React/Vue in the market - most of the time is a key factor to start a project with React/Vue and not angular.
@@dmitriyobidin6049 You should use what project demand if project going to be bulky the angular is good option. If need light, I think there are multiple options. And tech come and go i prefer to be do what job need to do that it.
There is no battle, I use what ever tool to get the job done. I tried React but I hated jsx, but then Angular introduced me to Typescript before it was cool. for my projects I use Angular for complex and large projects, but for small projects Vue is a good option, but for landing pages, I use Astro, it replaced Vue for landing pages.
in my opinion classes and templates are Angular. it's one of the main reason I use Angular. Please don't make Angular syntax like React or Vue. Innovation is great, but it becomes pointless when fixing something that works. I am grateful to the Angular team for creating and maintaining Angular. Every Angular release I am always happy, for new improvements, new features and the tooling that makes it easy to upgrade, thank you.
"Templates are Angular" - bah. Templates are templates. They convey a lot of things right now, and I'm very grateful they're as powerful as they are, but there are too many mixed concerns in the language.
Templates currently mix
- Layout
- Style
- Dependency injection and configuration (via Input and #references)
- User experience (drag and drop).
It will probably be impossible to get rid of Templates altogether. But it would be great if we could have separate ways of expressing our intent, which are apt. Host Directive binding will go a long way; We are moving to a future that's easier to understand, not harder.
We should resist unnecessary change, while embracing pragmatic decisions that help improve clarity.
I couldn't say this better. There is something really wrong with the idea of constant improvement at the point of losing what the initial objectives were
Are classes Angular? - Yes
Are template Angular? - Yes (They both give a nice way to separate the concerns. Makes the code well organized. Especially when you are working with a team with mixed technical expertise)
IMO .. Please dont use React Singling - They are not intuitive at all. I would rather go with the flutter approach of just simply using setState().
Yeah you are right. Right now the code is well organized and when a new developer comes along, he can start pretty easily.
i partly disagree,
are classes angular? it shouldn't be this way, after all javascript classes are just sugar syntax for a function declaration (*not arrow functions)
are template Angular? yes, and we have already two options for declaring our templates via a file in declared on the decorator or just adding the template itself on the decorator of the angular component.
It's good that the angular team start looking to alternatives for zoneless application, would be nice to see increase in the performance just out the box instead having manually having to working with .onPush and working with the ChangeDetectorRef API.
Is Angular Angular, nope! this is why they keep breaking the code! Zero backward compatibility, maintanance nightmare!
@@RajinderYadav i have been updating a project since angular 8, and it has been going good. Some versions needed more changes, but its not a nightmare, angular is very good for big projects.
@@UNDEROATHRMT Templates are just the way we express part of our application. There could be other ways of expressing it which might increase clarity, or decrease developer time to achieve the same result. We should explore those options, provided we don't unnecesarily break things.
People cursed and screamed about the [] and () syntax. But I'm grateful for it. Looking forward to the new innovations
Im thrilled that Material got a update. I felt like I was always fighting with its styling.
I think that the object Orientation (Class Based) of Angular is one of its Core features as it makes it less mentally challenging to build High Quality Full Stack Applications. It also seems to me that this is the primary Use Case in business as is. Using Angular as the Frontend for Enterprise Applications where the Backend often Comes in C#/Java.
The Concepts and Best Practises are not Far from what they are in those Backend Enterprise Languages.
I love what you have done with Angular 15 and am curious for the future.
I think that this Concept in Angular should be kept in mind tho. The similarity of Design Principles and Best Practices to Design Driven Backend Technologies, is a great benefit none of the other Frameworks offer.
It's Easier to start with Vue for sure, but it is not very easy to understand how to cleanly structure a Vue Project from a experienced Backend Developer's Perspective.
Similar in React, even tho this technology is likely closer to home for functional Programmers, NodeJS Backend Devs and general experienced JS Devs.
Angular here fills the Spot missing, here we can use Design Principles also used in Backend Languages, to improve the base Design of our Frontend Application. I truly apreciate that.
lazy routes look cool & elegant, seems interesting features are ahead.
ty, nice presentation as always 👌, modest and precise, with no marketing buzzwords like "supercharged" or "developer ergonomics"
Nice to see Angular innovating again
You mean breaking, this is not innovation, it just let's change how it works again and again.
Hi, thanks for the presentation.
I am working and making Angular apps since v2 and being the responsible for update Apps with it since with v5, A lot of improvements on the way of update the apps with new versions and since v9 a much better performance in dev and builds speed.
Until version 13 the syntax in ts and template engine has been stable, what i dont want to see is something like react and vue has, which is two ways to write apps ( functional components and composition) where you are introducing standalone components.
What it is not very clear with standalone components in your docs and videos is if we still can separate the style and template of the component in separate files ( css and html), i had not yet time to try standalone comps and at my job still using v13, but should be clear,
if standalone components only means component without the need to assign to module were the rest is the same like separate css and template from the logic ( TS ).
About are Classes Angular?
I think a components not always need a logic / TS file, I recommend Angular to read what Aurelia did and still doing for v2 ( so called html only components) and even emberjs is thinking this way.
Another thing missing is choosing linter tool setup with Angular CLI.
Template only component must be a thing!
How to get the Single Component Build ?
Did you mention that they got rid of environment files? You can still add them if you want. I think everyone is preferring to use continuos deployment settings to update api urls instead of having to do it at design time with angular buid
I'm having trouble understanding some of the diction and unfortunately, adding closed captioning doesn't seem to help. Looks like it was autogenerated and it doesn't quite understand you either. Specifically when you start the section around ng build, there are words I can't understand. You might have said ng build is using es built? There were some other acronyms that you said as well. Suggest adding a little more content to the slides for when you say something like ng which is not a standard English word but is sort of a made up Angular or Javascript centric word the auto closed captioning system will not pick up on.
why painting yourself in a corner by using angular, vue or react?
or: when the framework is determining the architecture the industry isn't mature
kinda regretful if angular bring preact signal concept if there is rxangular available
We're not bringing the preact implementation of signals in Angular. What I shared is an experiment we used to see how signals will play with the rest of the framework.
Are JavaScript angular ? 😅
I will add also a plead. Please do not change templates and classes in angular. This is the best thing in angular and I do not want to write react in angular. React and Vue just sucks.
Vue is awesome... React is bad
The debugging improvement is a welcomed feature. Angular is a joke of a framework that will continue to break, these clowns keep questioning and changes the core. Is class Angular, is template Angular....Is Angualr Angualr? They created NgModule when JS module could have been used and later decided it's not needed. Why wouldn't you just make all modules lazy loaded by default? then as the page loads, it fetches the code and resources need on "demand". Nope, they needed to over-engineer and add super ugly boiler plate code, to routing. You know what is not Angualr RxJS, Streams, Observals. These things alone have resulted in over-engineer crappy, abstract hard to read and maintain code with dependences breaking. Ngrx is an over-engineer mound of dung, just to be able to have a global store to get and fetch value, only 2 simple operation are
needed. Again it's over-engineed with reducers, actions, selectors, effects, component store? WTF.
Angular Material should not be a part of Angular. We have CSS so leave it to someone else to create a CSS library, it's just bloat very few want to use professionally. Also bugs go unfixed, so for CSS markup this is just stupid to tightly couple it to code not under your control. You can make your own CSS components, you already got Angular + CSS.
Also their reference docs are incomplete, they haven't been worked on forever, maybe fully document it first?
Answering: Is Angular Angular? Nope! This is why they keep breaking the code! Zero backward compatibility, maintanance nightmare.
Tbf, rxjs can be complexe some time, but it doesn't mean that's bad. The things you can do reactively thx to it, are actually quite impressive.
Even tho i agree ngrx is in many cases probably not needed and brings way too much boilerplate. Rxjs is actually helping a lot to have a strong flow and reactivity. It can be done without it, but it's more painfull to achieve.
The simple fact of using changedetection.onPush + async pipe to handle dom refresh is enough to justify using rxjs. You are actually writting way more stable code while using rxjs. Especially performance wise.
Angular lost it's battle with React and Vue. Why would anyone choose Angular over those two?
Despite using react n vue for a long time. Choosing angular for my next project for plenty of reasons
I try solidjs i have no guard no active class and more so i update the routing module to my need.
Even react and other are not complete you have to use some lib to get your work done but angular have everything. Only sometime i use some lib.
@@puneetsharma1437 The sad reality is - business rarely give a sh about the things that are good for developer. They tend to make a decision based on business values, and the fact that there are 2x|3x more developers on React/Vue in the market - most of the time is a key factor to start a project with React/Vue and not angular.
@@dmitriyobidin6049 You should use what project demand if project going to be bulky the angular is good option.
If need light, I think there are multiple options.
And tech come and go i prefer to be do what job need to do that it.
There is no battle, I use what ever tool to get the job done. I tried React but I hated jsx, but then Angular introduced me to Typescript before it was cool. for my projects I use Angular for complex and large projects, but for small projects Vue is a good option, but for landing pages, I use Astro, it replaced Vue for landing pages.
Angular is dead