423 private links
There’s a reason this form of development became popular after all. But I do wonder if some of the trade-offs are being discounted. This form of decomposition has a price, in the form of readability and simplicity, and I somethings wonder if the benefit of reusability you’re paying that price for is oversold. When changes come through, I usually see people just rewrite the components.
Yes, after using Vue for 3 or 4 years, like every web frameworks, I try to use HTML and CSS as much as possible.
Now, everyone’s a prize exhibit in the FAANG zoo, because mastering this tangled mess is what opens their gates. Being just a CRUD monkey doesn’t feel fun anymore. If this is what “progress” looks like, I don’t want any part of it.
The technologies to build for 10 years ago dramatically improved!
As mentionned by LeHollandaisVolant, one thing the article doesn't mention is that:
- 1 the pages are more interactive
- 2 the data changes in real time
There are cycle in web development. For example, Server Rendering -> SPA -> MPA -> Server Rendering
Become a better frontend developer.
Take your frontend skills to the next level by recreating real websites from real companies.
Static web publishing for Front-End Developers
caused by AI? Such an AI is incompetent.
And the related project to use SQLite in memory of a frontend app.
The database file is loaded from a server or a local file... which can be convenient for offline databases!
If the database is available online, it is still ok if it is small and the SQLite file can be downloaded :)
The deficiencies of SQL to use it as frontend databases:
- Standard SQL doesn’t support nesting
- SQL syntax is verbose and non-uniform.
- SQL’s scalar expression language is weird and limited
- SQL doesn't have good tools for metaprogramming and changing the shape of a query at runtime
Good points! I have use cases where a frontend database approach will work perfectly!
About Svelte, React and WebComponents, . Somethings to remember