Very nice talk! Regarding TS; I believe that at a high level it's bringing OOP to JS devs; so when u come from a backend world and start working with Typescript it doesn't take u that much, on the other hand, if u have never gone into an OOP world and start using typescript; some JS devs might feel that they have too many constraints when developing, but the reality is that those constraints are something good. About Angular; what can I say? I luv Angular jejeje. Congrats Juan Herrera, it's gr8 to see a Latino giving such a good and entertaining conference ;) I think u bring the color, flavor, and spiciness that we Latinos have in our continent to this JS talks ;)
que nota de explicación para las buenas practicas en Angular y mas aun me da orgullo que sea un Colombiano quien lo esté realizando, los mejores deseos y tomaré los consejos. Un saludo
In the template string binding example (around 11:49), I don't quite get the change detection thing, isn't angular going to handle the value as a string regardless on how you pass it? I mean, I totally agree that the square brackets are unnecessary and that the code is poorly written, but I don't really thing that there is any gain in performance (even slightly) with the correct version, could someone explain it a bit? am I wrong?
32:52 I believe you are not exact here, you are probably refering to forRoot/forChild pattern. Singleton Services should be provided via `@Injectable(providedIn: 'root')`. Also there is no hierarchy (no seperate injectors) for eager modules. Could someone clarify?
Hans! Thanks for writing! You are right, singleton services should be provided using (provideIn:'root'), although it is also possible to provide them by adding them to the AppModule. So my advice, is that if you are trying to create singletons and you are using the AppModule approach, you have to be careful not to provide the service more than once (for example in other modules), or it will not be a singleton anymore :)
Very nice talk!
Regarding TS; I believe that at a high level it's bringing OOP to JS devs; so when u come from a backend world and start working with Typescript it doesn't take u that much, on the other hand, if u have never gone into an OOP world and start using typescript; some JS devs might feel that they have too many constraints when developing, but the reality is that those constraints are something good.
About Angular; what can I say? I luv Angular jejeje.
Congrats Juan Herrera, it's gr8 to see a Latino giving such a good and entertaining conference ;) I think u bring the color, flavor, and spiciness that we Latinos have in our continent to this JS talks ;)
One of the best talk for good practices in Angular!
Thanks Quelito! :D
This is such a great talk. I could listen to this all day.
This is very sweet! :3
que nota de explicación para las buenas practicas en Angular y mas aun me da orgullo que sea un Colombiano quien lo esté realizando, los mejores deseos y tomaré los consejos.
Un saludo
Se me salieron las lágrimas Johnattan! Muchas gracias 🤗
In the template string binding example (around 11:49), I don't quite get the change detection thing, isn't angular going to handle the value as a string regardless on how you pass it?
I mean, I totally agree that the square brackets are unnecessary and that the code is poorly written, but I don't really thing that there is any gain in performance (even slightly) with the correct version, could someone explain it a bit? am I wrong?
Yes, completely agreed with you.
I'd say no performance gain Zeno, simply a more concise approach but that's about it :)
@@JuanHerreraMarin cool, yeah that's what I thought thanks for clarifying :)
Cool 😎
32:52 I believe you are not exact here, you are probably refering to forRoot/forChild pattern. Singleton Services should be provided via `@Injectable(providedIn: 'root')`. Also there is no hierarchy (no seperate injectors) for eager modules. Could someone clarify?
Hans! Thanks for writing! You are right, singleton services should be provided using (provideIn:'root'), although it is also possible to provide them by adding them to the AppModule. So my advice, is that if you are trying to create singletons and you are using the AppModule approach, you have to be careful not to provide the service more than once (for example in other modules), or it will not be a singleton anymore :)
@@JuanHerreraMarin Thank you for responding :-).
My wife is from Colombia and I am from austria :O
Good talk, but very low-level staff