News for hackers. Stuff that matters.

guseyn

Re:Why Vanilla JavaScript on Saturday July 18, 2026 @12:42PM (#48959704)
All custom attributes must start with data, read the convention
Re:Ehtml on Tuesday November 18, 2025 @05:01AM (#45963258)
You serve your static files and that's it. You just create multipage app. And you can cache almost entire page by e-wrapper template.

I've been building an HTML-first tool – sharing it in case it helps someone

Hi everyone! I’ve been working on a project called EHTML, an HTML-first approach to building dynamic pages using mostly HTML. It lets you handle things like templating, loops, conditions, data loading, reusable components, and nested forms — all without a build step or heavy JavaScript setup.I originally built it to simplify my own workflow for small apps and prototypes, but I figured others...

( Read More... | 2 comments | 2 points | on HN )
Re:Ehtml on Saturday November 15, 2025 @07:13PM (#45941656)
EHTML — Extended HTML for Real Apps
Why do we need another framework for Node.js? This is my wish list:

I want to build my web application on a framework with zero dependencies.

I want to utilize native Node.js APIs without any additional layers of abstractions.

I want to hack my framework when I need to, e.i. I want to have quick access to my framework's folder and make quick changes.

I want to have zero downtime when I update my appliction's logic just by sending a signal.

I want to use Cluster in Node.js. It will allow me to scale my application with very little price. I also don't want to anything else for orchestration and other fancy things that Node.js provdes itlself.

I want to have HTTP/2 as a default.

I want to handle 500 User error properly.

I want to configure my application out of box in my primary and worker processes.

I want to have very simple secrets reader.

I want to be able to log into an output log file.

I want to have composable API provided by my framework and not use middlewares that reduces the code clarity. I want to be able to copy/paste logic to achieve clarity.

I want to have access to params and queries in each request URL.

I want to have control when I read body of my requests.

I want to have quick access to my external dependecies like db clients and other integrations without attaching them to request object. I want to have dependecy injection without any huge frameworks.

I want to easily configure my index.html, not-found.html files.

I want to focus on building my products quicky and make money.

Hopefully it can be interesting for somebody who want something similar from a framework.

Re:MIDI Editor on Friday December 08, 2023 @03:16PM (#38573696)
This is one is also good: unisonofficial.com
Re:EHTML Docs on Tuesday December 05, 2023 @03:47PM (#38536689)
thank you!
Re:EHTML Docs on Tuesday December 05, 2023 @03:46PM (#38536685)
Yes, you're right, thank you for such explanation.
Re:EHTML Docs on Tuesday December 05, 2023 @03:46PM (#38536682)
It's not just static content. It's Markdowns loaded right into HTML.
Re:EHTML Docs on Tuesday December 05, 2023 @03:44PM (#38536663)
I believe Turbo/Stimulus rely more on server rendering + their Turbo Drive is quite powerful, will try to catchup on turbolinks. I had implemented them previously, but it's quite difficult to make them smooth.
Re:EHTML Docs on Tuesday December 05, 2023 @10:26AM (#38532065)
Yeah, because I am using highligher for code fragments in markdowns, will try to optimize it.
Re:HTML, the Programming Language on Tuesday December 05, 2023 @10:22AM (#38532000)
could you please give a reference?
Re:HTML, the Programming Language on Tuesday December 05, 2023 @05:14AM (#38528991)
I think the biggest difference is that EHTML works more with JSON API rather than with HTML Server Rendering integration.
Re:EHTML: Front-end development can and should be simple on Thursday November 28, 2019 @03:28AM (#21655551)
It's based on JS, of course, but the goal is to get rid of JS as much as possible for the developers who want to build frontend for their apps
Re:EHTML: Front-end development can and should be simple on Thursday November 28, 2019 @03:21AM (#21655532)
loading pages with some information from endpoints and mapping it to html template, sending and validating forms, making navigations with turbolinks, making authorization via google and getting url parameters by specified pattern. And you don't need JS for such simple things
Re:EHTML: Front-end development can and should be simple on Thursday November 28, 2019 @03:11AM (#21655493)
Complex HTML is always better than complex JS, because HTML is declarative language, it's much easier to maintain and modify
Re:EHTML: Front-end development can and should be simple on Thursday November 28, 2019 @03:01AM (#21655437)
This lib allows you not to write js, it's just based on it.
Re:EHTML: Front-end development can and should be simple on Thursday November 28, 2019 @02:58AM (#21655418)
it evals, but only some part of it, so it prevents XSS attacks
Re:EHTML: Front-end development can and should be simple on Thursday November 28, 2019 @02:53AM (#21655403)
#box is just a selector, it means element with id box, and you can see errors like "element is not found" anyway

Older »