Artwork – a simple front-end framework with no HTML (opens in new tab)

(github.com)

1 pointsunemployable3y ago4 comments

4 comments

Applications do not really benefit from markup language. Artwork uses only JavaScript and CSS, and uses web components to enable scoped CSS and so on. It avoids classes as they are too much ceremony.

Projects using Artwork can be run without any transpiling or compiling thanks to import maps and CSS imports.

I am very happy with it. Maybe it is not for you, but I like it.

ss1083y ago

> Applications do not really benefit from markup language.

The question is whether developers do.

already3y ago

I hate JS only frameworks. What’s the point of making things more complicated? HTML makes it cleaner and easier to work

unemployableOP3y ago

Why do you think it is more complicated? The logic of the UI and application itself is the complicated part. That is the difference between a document and an application. The HTML ends up being turned into small pieces and has to be dynamically manipulated in an application. There are lots of if and else statements to create the HTML.

j / k navigate · click thread line to collapse

4 comments

unemployableOP3y ago

Applications do not really benefit from markup language. Artwork uses only JavaScript and CSS, and uses web components to enable scoped CSS and so on. It avoids classes as they are too much ceremony.

Projects using Artwork can be run without any transpiling or compiling thanks to import maps and CSS imports.

I am very happy with it. Maybe it is not for you, but I like it.

ss1083y ago

> Applications do not really benefit from markup language.

The question is whether developers do.

already3y ago

I hate JS only frameworks. What’s the point of making things more complicated? HTML makes it cleaner and easier to work

unemployableOP3y ago

j / k navigate · click thread line to collapse