|
|
-I've been considering focusing my future work more on web frameworks like Next.js. Luckily, the monolithic frameworks have all embraced Javascript front-ends ( Ruby/Ember, Laravel/Livewire ) so I've been able to blend the two. I've admin'd several headless content management systems for about 5+ years and have had headed various versions running 15+ years. I remember when Node.js first came onto the scene and the JAM and MEAN stacks were buzzwords. I've learned enough now to know the devil is in the details... efficacy is a matter of usefulness and sustainability is a matter of practice. I think the popularity of headless started in an attempt to have content available as a asynchronous data source for mobile apps and has since evolved into having other advantages and disadvantages.
|
|
|
+I've been considering focusing my future work more on entirely Javascript powered frameworks( Remix/Svelte & Supabase/Postgres ). Perhaps this is mostly because of my recent experimenting with vector functionality in Postgres. Luckily, the monolithic frameworks have all embraced Javascript front-ends ( Ruby/Ember, Laravel/Livewire ) so I've been able to blend the two. I've admin'd several headless content management systems for about 5+ years and have had headed various versions running 15+ years. I remember when Node.js first came onto the scene and the JAM and MEAN stacks were buzzwords. Although I know that the fundamentals ( JavaScript/HTML/CSS ) are key , I've learned enough now to know the devil is in the details... efficacy is a matter of usefulness and sustainability is a matter of practice. I think the popularity of headless started in an attempt to have content available as a asynchronous data source for mobile apps and has since evolved into having other advantages and disadvantages.
|
