5 ms·

I’ve used this approach - Go with templates TailwindCSS or Bootstrap, and on-page interactivity with IntercoolerJS or AlpineJS. Apps turn out to be very fast, S

by DLA 7y ago

I’ve used this approach - Go with templates TailwindCSS or Bootstrap, and on-page interactivity with IntercoolerJS or AlpineJS. Apps turn out to be very fast, SEO friendly, very easy to maintain and make great use of the optimized browser caching. My two cents. But it depends on what you are building.

retreatguru 7y ago
Does this style of development have a name? Were there trade offs or limitations with those libraries?
- vearwhershuh 7y ago
  Not that I'm aware of. The main trade-off is that you aren't going to be able to so something hyper-interactive stuff like a game. If you try to push it too hard it will end up being a mess. OTOH, the closer it is to a traditional web app, the easier it is to use. There are a bunch of examples of common web patterns here: http://intercoolerjs.org/examples/index.html http://intercoolerjs.org/examples/index.html
- DLA 7y ago
  It really depends on what you're building. A content-heavy app, search/query type apps, or a basic CRM type app with CRUD workflows can easily be done largely with server side rendering plus Intercooler for the interactive bits you need. Check out some of their examples (http://intercoolerjs.org/examples/index.html http://intercoolerjs.org/examples/index.html) and see if it meets the types of interactions you need. If you want to go more SPA-like (and you really need that) you may want to look at Mithril (https://mithril.js.org/index.html#introduction https://mithril.js.org/index.html#introduction). This is a light way to go SPA vice React (awesome but steep learning curve; all kinds of tooling needed). We've built things like this: Most pages are server rendered using whatever you like (We use Go with Echo framework) the same server also hosts JSON APIs that allow the interactive Intercooler or AlpineJS arts to get either HTML fragments or JSON data. You can grab JSON with Intercooler too (http://intercoolerjs.org/attributes/ic-transform-response.html http://intercoolerjs.org/attributes/ic-transform-response.ht...). We've done search, DB apps (CRUD workflow), content sites, etc. exactly this way with a focus on developer productivity (very few libs to learn), user experience (ultra fast and SPA-like where needed), and performance (no giant JS balls to download, parse and activate). EDIT: Just found this amazing example using MithrilJS to do very high speed updates of a bunch of data elements on a table page: https://raw.githack.com/MithrilJS/mithril.js/master/examples/dbmonster/mithril/index.html https://raw.githack.com/MithrilJS/mithril.js/master/examples... Hope this helps you.
digitaltrees 7y ago
Intercooler seems awesome, I would love to hear about your experience.

by DLA 7y ago

retreatguru 7y ago

Does this style of development have a name? Were there trade offs or limitations with those libraries?

vearwhershuh 7y ago
Not that I'm aware of. The main trade-off is that you aren't going to be able to so something hyper-interactive stuff like a game. If you try to push it too hard it will end up being a mess. OTOH, the closer it is to a traditional web app, the easier it is to use. There are a bunch of examples of common web patterns here: http://intercoolerjs.org/examples/index.html http://intercoolerjs.org/examples/index.html
DLA 7y ago
It really depends on what you're building. A content-heavy app, search/query type apps, or a basic CRM type app with CRUD workflows can easily be done largely with server side rendering plus Intercooler for the interactive bits you need. Check out some of their examples (http://intercoolerjs.org/examples/index.html http://intercoolerjs.org/examples/index.html) and see if it meets the types of interactions you need. If you want to go more SPA-like (and you really need that) you may want to look at Mithril (https://mithril.js.org/index.html#introduction https://mithril.js.org/index.html#introduction). This is a light way to go SPA vice React (awesome but steep learning curve; all kinds of tooling needed). We've built things like this: Most pages are server rendered using whatever you like (We use Go with Echo framework) the same server also hosts JSON APIs that allow the interactive Intercooler or AlpineJS arts to get either HTML fragments or JSON data. You can grab JSON with Intercooler too (http://intercoolerjs.org/attributes/ic-transform-response.html http://intercoolerjs.org/attributes/ic-transform-response.ht...). We've done search, DB apps (CRUD workflow), content sites, etc. exactly this way with a focus on developer productivity (very few libs to learn), user experience (ultra fast and SPA-like where needed), and performance (no giant JS balls to download, parse and activate). EDIT: Just found this amazing example using MithrilJS to do very high speed updates of a bunch of data elements on a table page: https://raw.githack.com/MithrilJS/mithril.js/master/examples/dbmonster/mithril/index.html https://raw.githack.com/MithrilJS/mithril.js/master/examples... Hope this helps you.

digitaltrees 7y ago

Intercooler seems awesome, I would love to hear about your experience.