I’m at the point where I’m wondering if choosing Svelte for NodeKit is a design error in terms of cultural fit and goals. (They want to be the “serverless” framework for Big Tech. I feel like I’m hitting my head against a wall whenever I want to adapt anything for small web use because it’s all geared towards corporate web use.)
Anyone here played with htmx and hyperscript? Any experience with the community?
https://htmx.org/
https://hyperscript.org
#htmx #hyperscript #thoughts
Anyone here played with htmx and hyperscript? Any experience with the community?
https://htmx.org/
https://hyperscript.org
#htmx #hyperscript #thoughts
Aral Balkan
in reply to Aral Balkan • • •#htmx #prototyping #NodeKit #design
Kristóf Marussy
in reply to Aral Balkan • • •Content warning: Re: javascript
1
, becauselet count = 1
is on the top of the file, and it looks like it always gets executed when the page is renderedI’d expect a clearer separation between the initialization and the rendering, like
or maybe even (goodness forbid!)
(btw, won’t the code display 1 times even on the first request, because the condition
count > 1
gets evaluated after the post-increment? granted, I’m not familiar with the order of side-effects in jsx interpolation expressions)Aral Balkan
in reply to Aral Balkan • • •But there’s one big drawback to htmx… no ES modules and thus no components. That’s a biggie.
🤔
#htmx #svelte #javaScript #js #nodeKit #smallWeb #prototyping
Aral Balkan
in reply to Aral Balkan • • •professional internet cat
in reply to Aral Balkan • • •Content warning: i have very little experience with jsx, this might be totally wrong
count++
in a dedicated statement before returning the template and initialize the variable with 0. depending on how exactly it evaluates templates, you'll probably end up withcount
not being the same value in the two placeholders, which in turn might give you the plural form even if it displays 1.Arne Babenhauserheide
in reply to Aral Balkan • • •But it’s big tech, too. Pair it with web components and you have a powerful abstraction.
Here’s a lessons learned for web components: https://blog.disy.net/developing-webcomponents/
Developing web components
Disy Tech-BlogEvan
in reply to Aral Balkan • • •Platform-native technology like Web Components and template strings feel like they align more with your work.
https://github.com/WebReflection/uhtml
GitHub - WebReflection/uhtml: A micro HTML/SVG render
GitHubmathew 🦜☕
in reply to Aral Balkan • • •1. You can make full use of ES modules.
2. Uses regular HTML, CSS and JS syntax in a single file per component, much like Svelte.
3. Fast builds using esbuild and Vite.
4. Can be adopted incrementally.
5. You can even use it without a special build step if you really want to:
https://markus.oberlehner.net/blog/goodbye-webpack-building-vue-applications-without-webpack
Performance wise it's not quite as good as Svelte (because virtual DOM), but not too far off.
https://vitejs.dev/
Building Vue.js Applications Without webpack
markus.oberlehner.netandregil
in reply to mathew 🦜☕ • • •Kerfuffle
in reply to Aral Balkan • • •