how about: html + css + js. The interactivity part can be done through preact + htm with JSX like syntax? Don’t need tools like webpack, vite, etc.
Ask HN: What's is your go to toolset for simple front end development?
271–280 of 295 posts
Re: Ask HN: What's is your go to toolset for simple front end development?
#272Preact [0] + htm [1] Why? Preact is small, fast, and reasonably easy to use. But the main selling point for me was that, together with htm, I don't need any build system a la webpack. No node_modules folder. I just have to load one script (preact + htm bundled), define my components in plain javascript files and import them. Bliss for me. [0] https://preactjs.com/ [1] https://github.com/developit/htm Edit: Just read…
+1. We use preact + htm and no build approach to build Moochee (https://app.moochee.us/tryout). Super simple to use yet very powerful!
Re: Ask HN: What's is your go to toolset for simple front end development?
#273Pyramid for backend. HTML+css for the front end. Often just bootstrap. Vuejs applied to very specific places that need to be interactive, but without any build/bundling/whatever - just referencing a single minified file.
i would even recommend https://deformdemo.pylonsproject.org/ ;) i used it for internal tools all the time
Re: Ask HN: What's is your go to toolset for simple front end development?
#274Re: Ask HN: What's is your go to toolset for simple front end development?
#275https://svelte.dev/tutorial/basics - easy to get started with but really powerful for complex stuff too For layout, don't use any CSS framework, but instead refer to https://css-tricks.com/snippets/css/a-guide-to-flexbox/ often - every time I use some big CSS framework I end up fighting it at some point. https://vitejs.dev/ for packaging - I got really grumpy when frontend stuff started needing build and packaging to…
Since when did frontend require building or packaging? In fact, since when did ANY web development require those things?
Our front end devs were drawing diagrams of react components with arrows everywhere. All the app is doing are some fairly basic forms with a bit of validation. NPM install to get the thing running on a development machine, and it seems to download half of the internet. What an absolute shitshow "full stack" development is these days.
Re: Ask HN: What's is your go to toolset for simple front end development?
#276Earlier quoted context omitted.
I don't consider Svelte a simple toolset because it can't be published statically
If you are in a larger scale SEO project this does blazing fast static generation with Svelte: https://github.com/Elderjs/elderjs
Can attest to this. We used it to build https://findenergy.com which has over 15k pages and a TON of data.
Re: Ask HN: What's is your go to toolset for simple front end development?
#277I reach for Vue + Vuetify (a Material Design UI component library) to get things going quickly. Vue is extremely easy to learn and can be incorporated with a script tag if you prefer. Vuetify faithfully implements almost the entire Material Web Components spec, so you have everything you need to build polished, functional web apps. It’s also got very nice documentation.
Re: Ask HN: What's is your go to toolset for simple front end development?
#278Earlier quoted context omitted.
Best recommendations. Just one thing: do a favor for your visitor's privacy and don't use a CDN, download the css/js packages and host them yourself. > An easy way to try out Mithril.js is to include it from a CDN and follow this tutorial. [1] [1] https://mithril.js.org/
> a simple front end to which I can attach some new experiments for home brew coding This thread is about engineers looking for a simple way to just create a UI. Pandering to niche neuroses about privacy by avoiding entirely mainstream technologies such as CDNs is out of scope!
> Pandering to niche neuroses about privacy
You can think of it being a neuroses for yourself, but you don't have to label it as such for others.
It can be a perfectly reasonable concern in the life of others, while not in yours.
> This thread is about engineers looking for a simple way to just create a UI
The recommendation doesn't go against this. To create a UI, you'll have to host at least one HTML file. Potentially several, also images, stylesheets, javascripts, etc. One more to ditch the CDN doesn't add work to the process. Deploying one or two files isn't much of a difference.
Re: Ask HN: What's is your go to toolset for simple front end development?
#279Elm. If there is a back-end API with a spec (GraphQL or OpenAPIv3) you can generate an Elm client for that which makes API calls type-safe and thus very robust.
Cosigned. And if the backend is yet to be written then put the whole thing on Lamdera.
I'm trying to understand Lamdera, but I dont really get it.
How does it persist data? Does it use WebSockets (and thus push from server)?
Re: Ask HN: What's is your go to toolset for simple front end development?
#280Related discussion from 2021 https://news.ycombinator.com/item?id=29311761