6 ms·

Patterns.dev – Modern Web App Design Patterns

michaelsalim 4y ago
Just based on skimming some of it, the content is actually pretty solid. I'm quite surprised at how wide the range of the topics are. Though i think it would be nice to have a more problem-facing title. At the moment it feels like this is written for someone that wants to read it from A to Z.
jackblemming 4y ago
Beautiful formatting and presentation, but I don't agree with trying to bolt stale design patterns from the 90s into React web apps.
dimmke 4y ago
Man, ever since I started using Svelte and it became apparent to me how React has already crested the mountain and is on the downturn, I cringe so hard when I see how much work is put into React specific stuff by projects like this. I think it's going to age terribly in the next couple years.
- TDiblik 4y ago
  A lot of projects have been built with React and new ones start every day. React's here to stay for at least another 15 years (imo). Websites like these could be at least good as documentation of React features/patterns used in old React codebases you have to maintain in future. These assumptions lead me to believe that websites like these will age incrediblly well.
- harel 4y ago
  I read your comment as:. Everytime I use X I see how dead Y is, and you should stop using Y because X is better and your use case does not matter.
- tehbeard 4y ago
  You wanna give some meat to that argument or are you just proselytizing with no merit?
255kb 4y ago
Nice collection of things and well explained. But I wouldn't call all of them patterns, but rather "solutions to common problems". Like the https://www.patterns.dev/posts/virtual-lists/ https://www.patterns.dev/posts/virtual-lists/ it's a React version of the virtual scroll technique that I was coding 10 years ago.
whoomp12342 4y ago
modern patterns, but you include a singleton??? seriously, please reply to me if you actually implemented a singleton in the past 2 years
- ohthatsnotright 4y ago
  Is that not what a named export of a const declared inside a single JS file does, though? e.g. for node, the first time the file is loaded it is evaluated which would assign the const, and then the export is given to all files so unless you have a fun circular dependency you should arrive at exactly one instance.

Just based on skimming some of it, the content is actually pretty solid. I'm quite surprised at how wide the range of the topics are. Though i think it would be nice to have a more problem-facing title. At the moment it feels like this is written for someone that wants to read it from A to Z.

jackblemming 4y ago

Beautiful formatting and presentation, but I don't agree with trying to bolt stale design patterns from the 90s into React web apps.

dimmke 4y ago

Man, ever since I started using Svelte and it became apparent to me how React has already crested the mountain and is on the downturn, I cringe so hard when I see how much work is put into React specific stuff by projects like this. I think it's going to age terribly in the next couple years.

TDiblik 4y ago
A lot of projects have been built with React and new ones start every day. React's here to stay for at least another 15 years (imo). Websites like these could be at least good as documentation of React features/patterns used in old React codebases you have to maintain in future. These assumptions lead me to believe that websites like these will age incrediblly well.
harel 4y ago
I read your comment as:. Everytime I use X I see how dead Y is, and you should stop using Y because X is better and your use case does not matter.
tehbeard 4y ago
You wanna give some meat to that argument or are you just proselytizing with no merit?

255kb 4y ago

Nice collection of things and well explained. But I wouldn't call all of them patterns, but rather "solutions to common problems". Like the https://www.patterns.dev/posts/virtual-lists/ https://www.patterns.dev/posts/virtual-lists/ it's a React version of the virtual scroll technique that I was coding 10 years ago.

whoomp12342 4y ago

modern patterns, but you include a singleton??? seriously, please reply to me if you actually implemented a singleton in the past 2 years

ohthatsnotright 4y ago
Is that not what a named export of a const declared inside a single JS file does, though? e.g. for node, the first time the file is loaded it is evaluated which would assign the const, and then the export is given to all files so unless you have a fun circular dependency you should arrive at exactly one instance.