Видео

Great content! I have a question about handling state in this scenario. If we have a monorepo project, in which all the apps are with angular and are highly dependent on the libraries we created on the monorepo. Does it makes sense to create a library only for handling state? In my case all my apps will be close to identical only with some UI changes. Thanks again for these great videos, keep the awesome work!

Awesome!!! This is the best tutorial till date. Thank you very much

Loved this. Have been toying around with fullstack projects since the start of this year and I kept struggling on the rxjs part in the frontend. This video made it all "click". Cant thank you enough. The part Im still struggling on is clearly understanding the different use cases of simple Observables vs Subjects vs the new Angular signals.

I think that the constructor is better to inject dependencies considering testing as part of most important development phase, to inject mocks to ensuee the quality of the component

is this project stopped? no new videos are coming.

This video makes my head hurt. Which is actually a compliment as someone whose rxjs codebase is a migraine factory.

I'm curious, is there a point in using this library? Or would it make more sense to just use a more maintained react-three-fiber component, that we render in angular when we need three.js in an angular app?

@BrandonRobertsDev lol😂 @josh yes please, do it before chau releases v2

I really like neovim, but when projects begin to be bigger i found uncomfortable using it. Basically if I have to stay under the 200 lines of code, i prefer neovim, but if i have to go too over that amount, i prefer VS code.

I want to switch because its better for my hand i am suffering from the mouse

Great video Josh I definitely want to see more

I thought angular three wasnt supoorted anymore… are you using an poder versión of angular?

Are we in the Tesseract? 😅

So now we can create 3d games high on performance. Right?

Felt like the video ended as soon as it started to get interesting 😅

I've got a tip for using materialize and dematerialize for error handling in RxJS going out in the newsletter tomorrow: mobirony.ck.page/4a331b9076

What a great, great explanation Joshua! Thank you so much for this :)

What is your opinion on stuff like effects? They seem to bring declaration fragmentation into reactive code… like now you have your variable declaration with some logic, but this variable can also be changed inside effects hence bringing back jumping between variable usage places

Rxjs everywhere everywhere 😅😅😢

Nice video Joshua can you do a full tutorial on it please. A detailed tutorial for beginners I am really begging please

Great video! Just wondering if signals can impact on this?

I made another video on WHY people are obsessed with neovim (or at least why I am): ruclips.net/video/5wy2iLU5fs0/видео.html

On Windows nvim lags af

I had to charge my magic mouse and thought, "let's try neovim, would be cool to ditch the mouse!". Threw myself down the deepest rabbit hole, took like 2 weeks for me before switching from Windows to Arch, safe to say, neovim was actually kind of okay

These tutorials are genius. Thanks Josh!

animations are out of this world, can anyone tell me wt kind of tool or software was used?

Love this video as a visual learner, please make more videos like this! It really helps visual learner like me to understand and learn so much better.

Hi Joshua, you do not know how much I've been struggling to understand what are both of them, this video really resolved my confusion. I thank you with respect and love from the bottom of my heart❤

Awesome vid and explanation. It drives me nuts seeing the type of code that you describe as imperative, for exactly the reasons you describe. I think there is a lack of resources showing/teaching people alternatives.

Fighting the fight in a large enterprise app. the real pain I find is when the 2 approaches meet 🤢. For example a non serializable class going into an ngrx store, and things being mutated sometimes despite being in a store. the app was originally written in angular 2, so it's easy to see how it's happened. but now it's my job to unf**k it 😅. I could still see value in imperative to knock out an admin portal quickly for example. but once you go reactive/declarative you never go back.

Yeah, imagine doing this without RxJs.... Wouldn't even know where to start.

Although I am completely on your side in this matter, the explanation is very abstract, understandable mostly to those who already use it. I don't understand how this video will encourage a user of the imperative approach to try to apply the declarative approach without some code example.

I prefer imperative code because I can read it and understand what it does. While I theoretically agree with everything you are saying, the reality turns out to be something different (e.g. rxjs). And, the code ends up being completely unreadable unless you are 100% all-in on rxjs. And if you haven't learned the incantations, they don't make sense, and you can't really debug them to understand what is going on. const myVar = http.get(''/api/items").flipflap((j) => invert(j)).flatFlam().flibbity(). And you look at that and you're just like, 'uh, OK?'. I think the middle ground that we can agree upon is signals, where it is declarative but decipherable.

Great content

A simple code to understand it better would be great.

That's a cool representation of those concepts. People are so afraid of curry/pipe functions they just never attempt to use it, maybe your next diagrams could explain this process the functions go through.

totally on your side when it comes to declarative vs imperative code. looking back at the past I would even say that an imperative approach is much more prone to errors than a declarative one. In my current project, I have had the experience that a more declarative approach just forces the developer more to think about error states ahead of time in comparison to an imperative implementation which overall resulted in a more robust implementation

thanks again joshua for all the effort and thoughts you put in your videos it helped me so much grasping concepts and find my way through all this (sometimes complicated) stuff you are the man 🫡👍🏻

I bought your course, Its Brilliant

Makes total sense!

what would you recommand as library(ies) for declarative code outside of Angular?

Maybe people tend to do imperative code, because declarative code forces you to consider most of the links in your code upfront. Imperative at first glance makes you feel like there's less links, so while you're writing it feels easier but the reality is you will have to do the work of linking your code over and over again when you read it.

I am the only reactive programmer in my team. They have asked me to do a presentation explaining why declarative is better. I think I will start off with this vid. Thanks!

Very nice and simple explanation.

what are the difference between reactivity and declarative?

Kudos to your grate efforts for Angular community....

this is what i have to read in the actual project im working 😭 is a big codebase and the client do not want to give us the total codebase to be able to implement new modules that they pay us to do 🙃

Great explaination!

Extra content around 3D scenes and cameras for Angular apps going out in the newsletter tomorrow: mobirony.ck.page/4a331b9076

This kind of tips what the developers need. Thanks.