DEV Community

Discussion on: The future is JAMstack

Collapse
romkecodesome profile image
RomkaCodeSome

Unpopular opinion: SPA'as adding unnecessary complexity to relatively simple projects. There's a lot of clients who want just a simple WordPress monolith site. I have done many SPA and PWA, but these are more dashboards or internal sites where SEO or accessibility is not the primary concern.

Collapse
jonrandy profile image
Jon Randy • Edited on

Not unpopular with me... totally agree - JAMstack is way overused. Too much following of trends going on without thinking about the appropriateness of the solutions. Some of the benefits listed above are dubious too.

Another big issue is devs building a site and forgetting it is actually a website - resulting in a very flawed experience where many things that should be taken for granted on the web simply do not work. The 'solutions' to this are often even more JS to recreate normal web behaviour that has been overlooked/ignored by inexperienced developers.

A single page portfolio site with minimal UI interactions - built in React (or whatever flavour of JAMstack you like) for no apparent reason is a surefire way to not even get an interview in some companies. By all means learn the technologies, but also learn when it is appropriate to use them

Collapse
neomonst profile image
NeoMonst

I see JAM as a pratice of separation of concern. It is no doubt that in some(or most) scenarios a Wordpress theme is more than enough.

Thread Thread
jonrandy profile image
Jon Randy • Edited on

Another fairly serious issue with putting so much processing on the client side is that it can be much easier to hack - especially when no checking is done at the backend. I've successfully subverted login/security processes on 'modern' JAMstack sites way easier than would have been possible with a 'traditional' model. This isn't a problem with JAMstack per se, more an issue - again - with inexperienced developers not realising the flaws and vulnerabilities of the paradigm.