True. I was lost 5 secs in. Just scrolling over endless lines, without time to get context...

Everything seems complicated until you understand.

@@merlinwarage and at some point rxjs seems to make sense .... Until you have to debug it 😅

I mean. Graphics Interchange Format is not Jraphics. It's G. Or you can spell it as G.I.F when you can use the "J"

I can't imagine being a "jiffer"

Haha it's just the same as a gin and tonic. You're right, it's graphics interchange format. How do we know? It's in the 1987 spec. Right next to the intended pronunciation! Nobody says oh 1024? Nah I think it makes more sense as a nice round 1000. It's defined. I get that people might naturally get it wrong but it's not like it's ambiguous, it's outright defined by the authors how to say it. And it's explained that it's pronounced in line with a popular peanut brand in America. It's just the same as Linux. I would naturally lean for lie-nucks. But its pronounced after his name and I would be wrong to insist my own version is correct. Or Adobe shouldnt have the eeee by just looking at it. Or telephony. They all require learning the correct version... and then using it! Not saying: I don't care fight me bro! 🤣

@@rtpHarry The actual RFC from 1987 doesn't specify the pronunciation. So "the creators liked a peanut butter brand" might not be as suitable as a proper pronunciation of the acronym.

@@the00one45 ooh we are getting into some spice now! 😃 That's interesting info, I'll have to look it up. I hope I haven't been spouting garbage for years 😅 My history with it is my first IBM pc as a kid was windows 95. The internet was still dial up back then and cost money that my parents only gave me limited access to. So I went through every folder on that system, tried out all the command line tools, clicked in every corner. And somewhere in Windows internals there was the legal document for gif. In my head this is where I learned about it being made by CompuServe and the pronunciation. I may have misspoke saying that it was the RFC. I may have misspoke about it all! I need to find an iso of windows 95 now to figure out what is lodged in my memory. This was nearly 30 years ago...

In the case of loading in the next page of data I don't want to clear out the previous data (otherwise page 2 data will replace page 1 data, but in this case I want the results appended onto the end)

Can you provide scenarios in which this is happening? as I dont seem to have this issue, (i am using ngxs as well) where to fetch or whatever you would have something like protected readonly timeZone = this.#store.selectSignal(SettingsState.timeZone);

Seems like we will be forced soon. Well, depending on your tolerance for customising things and not just going with the flow. I was updating the eslint stuff to v19 and saw some rules that check you are using signals in certain spots and flag it otherwise.

Here: github.com/joshuamorony/angularstart-giflist/blob/v19-migration/src/app/shared/data-access/reddit.service.ts

This is not that kind of channel.

@@BenjaminFavre29 what am I missing with another framework? (Serious question, I decided not to flip about learning bits of all frameworks and just focussed on this one because back when I started it was the only one that ionic supported)

Not really, you will run into the same fundamental issues once you convert it to a signal. If you have the Subject itself accessible, you can use that if necessary for events/actions. If you have some function that just returns a signal then it's the same problem where if you try to use that signal to react to events/actions then some may be missed.

@JoshuaMorony Having a function that returns both a Subject and its toSignal would be a game-changer for Angular developers. It would streamline the process of working with reactive data streams and provide a more consistent API for handling both Subjects and signals.

I think it would be worth going through as a lot of the stuff further in the course is based on those concepts, but also if you learn StateAdapt then you would probably understand what is going on conceptually anyway. But still, I think learning the same thing from different perspectives is useful.

Same here... I saw so many videos from Joshua and when i finally lernt enough to work with RxJs, signals comes out...

I can't recommend them highly enough; they're not too overwhelming to learn, and they make life so much easier and more responsive. Definitely worth the time investment to learn and start using them 👍

Rest assured that Signals are incredibly easy compared to RxJS.

@@becom1ng it's not the difficulty of signals it's the amount of time I put into rxjs! It's hard to abandon something that was so difficult for me to start to feel at home with... 😅

Learning signals is not about getting rid of rxjs. The combination of both is what you want. Signals for state and observables for events. So I encourage you to go that route. It's worth it.

This would actually work in this case, but the danger of using signal sets as a mechanism for "actions" is that they can miss actions/events due to the way effect scheduling works/signals not being designed for event handling generally. I'm not really 100% sure where I stand on this at this point, at the moment I'm leaning to using Subjects to represent all actions even though it isn't technically required in every case (I figure that's better than having surprising cases)