Very happy to see Angular getting some love ♥️ thank you, sir. Well done and great video
@geoili Жыл бұрын
Late to this, since just now I want to take a look at Angular. And when I saw you have a vid with him, I had to watch. Also have to add, I met Minko a couple of months ago at a conference. Despite me being a total random that somewhat now begins to understand actuall framework cogs and mechanisms. Minko decided to stay around for a bit a chat. Top bloke.
@RobertKing2 жыл бұрын
Angular, awesome 😎
@markmental66652 жыл бұрын
Great vid! started learning front-end JavaScript frameworks with Solid and React and am now working with Angular so this is helpful
@TayambaMwanza2 жыл бұрын
Thanks for your angular stream, gained a new subscriber, I like how you just explore things.
@shivrajdeopa1571 Жыл бұрын
Thank you very much
@trixchronicles2 жыл бұрын
Someone mentioned back-end solutions to use with Angular and NestJS is really great if you want to write your API with typescript and Angular syntax
@jwickerszh2 жыл бұрын
4:00:00 yes just build your monolith and find where the issues are, we built like that with a Java framework and started migrating some APIs to GoLang because it allowed getting better performance.
@aehp25582 жыл бұрын
Ryan you are awesome
@jwickerszh2 жыл бұрын
2:22:22 : new Excalidraw release? It looks almost photorealistic 😅 Good stream BTW, I'm jus dozzing on and off because of the fever.
@orilivni27302 жыл бұрын
About the transition from Angular 1 -> 2. Actually React was becoming popular before that, as I can tell that in 2014, I was one of the very few React users in Israel, and on my next job in 2016 (when Angular 2 was announced), React would be the 2nd place in the Fronend job offers (after Angular 1.x). But the biggest winner definitely was Vue. Vue wasn't really known until Angular 2 got out. Because Vue had fantastic docs and was much more similar to Angular 1.x (without $digest issues). Many start to look seriously about on Vue. By the way. At least in Israel, nowadays, there is a hiring issue with Angular ≥ 2.x. Very few want to use Angular at work.
@JLarky2 жыл бұрын
3:16:58 todomvc segment
@JLarky2 жыл бұрын
3:07:40 such a good catch! Rich changed the definition of "transitional apps" to make SvelteKit 1.0 fit it. The definition didn't make too much sense before, but this change to "it means the stuff that SvelteKit can do" makes it meaningless for any practical application outside of Svelte
@orilivni27302 жыл бұрын
I don't know how DI is built in Angular. But an interesting difference between Ember DI vs React Context, is that the DI is lazy while React Context is eager. You can hack around Context to make it "lazy", but this is not the way intended to be used or the way people use it
@larrycoleman81492 жыл бұрын
I wonder if dependency injection is a big mistake. For my current job, selectors are abused. In a form, some components are implicitly hard coupled with both children(ng-content) and parent (groupControl). It's very difficult to reason dependency relationships and I have to read UI library implementation code all the time. Explicit prop drillings/react hooks are much easier to reason.
@ShivamMishra-mn6cs2 жыл бұрын
I know react to learn solid should i learn angular with rxjs or rxjs to better understand solid pls reply
@larrycoleman81492 жыл бұрын
Probably no. Angular was designed to be imperative.
@pietervanderpol34972 жыл бұрын
having some familiarity with rxjs will give you some good perspective and in general its a very useful tool, but its not necessary.
@ryansolid2 жыл бұрын
No. RxJS might even confuse things because it is a different sort of reactivity. Learning about RxJS may be good at some point but in no way is it necessary to learn Solid.
@bigmistqke2 жыл бұрын
Surprised how different angular is
@RobertKing2 жыл бұрын
What software did you use to record this? Is it free?
@ryansolid2 жыл бұрын
Streamyard. It has a free tier but I do pay.
@sky_kryst2 жыл бұрын
Can't believe Ryan actually went through this
@cat-.- Жыл бұрын
I stared with angular and looking back this is a quite awful way to do things. My brain is trained to recognize JS scoping rules, reference rules and semantics, having 2 or 3 scoping systems (JS, selector, imports) mixed together is confusing to say at least.