5 ms·
I like Angular and I think it's still a solid choice for new apps in an enterprise setting, and signals are a welcome addition that solve real problems, but I d
by falafel 3y ago
I like Angular and I think it's still a solid choice for new apps in an enterprise setting, and signals are a welcome addition that solve real problems, but I don't understand the hype. Signals are as old as JavaScript if not older. The diamond problem and sync propagation are not new problems. We've come full circle. Old problems become new problems but with the same solutions. What did we gain with all of these iterations if we landed back on what was essentially the Knockout model of 2010?
I'm reminded of papers such as "Deprecating the Observer Pattern (2010) [1]" which documented solutions to these problems a long time ago.
[1] https://www.semanticscholar.org/paper/Deprecating-the-Observer-Pattern-Maier-Rompf/d7341e40b11008965d60631953ad83e89aa40584 https://www.semanticscholar.org/paper/Deprecating-the-Observ...
- baq 3y agoI guess every large ecosystem has to rediscover certain facts… same thing with yaml and xml on the sysadmin excuse me devops side, nosql getting transactions and scans… everywhere you look there’s a bunch of people who like doing more than reading, and also doing gets rewarded much more than reading. The outcome is inevitable. Can’t wait for the next cycle, really curios what we’ll rediscover next.
- redonkulus 3y agoEssentially it’s because new developers cycle in every decade and do not have all the context of the previous generation of developers.