Live data from Hacker News

HTML First

html-first.com

11–20 of 551 posts

Re: HTML First

#11
React was designed to solve all these problems. Now these problems are used to solve react.

Programming, like life, is a flat circle.

Re: HTML First

#12
post #3

I want to agree with this based on the title, but why would you do something like this: Click me if you're already using React? Yes the React code is a lot more verbose and has a bunch of "cruft" for lack of a better word. But you're already using it for the rest of your site, so you should (IMO) continue using it rather than mixing and matching approaches.

>But you're already using it for the rest of your site

I'm not

Re: HTML First

#13

Does anyone have a good list of vanilla approaches? I'm a fan of details/summary, but I'm sure there are more I don't know.

These vanilla JavaScript features are pretty great IMO - https://developer.mozilla.org/en-US/docs/Web/API/Document/qu... - https://developer.mozilla.org/en-US/docs/Web/API/Document/qu... - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... - https://developer.mozilla.org/en-US/docs/Web/API/Element/ins... - https://developer.mozilla.org/en-US/docs/Web/API/EventTarget... - https://developer.mozilla.org/en-…

Tbf they got better. Jquery basically existed because the js builtins were hairy

Re: HTML First

#14
Not bad, and reminded me of Simple & Useful:

> Can html be styled well enough and simply enough so that anyone can write for the web, using just a text editor, and share that work with anyone else, regardless of the platform they are using, the speed of their connection and any disabilities they may have?

https://s3.amazonaws.com/simpleuseful/index.html

From the old-school Introduction to Web Design:

https://web.archive.org/web/20210414030104/https://www.cours...

Re: HTML First

#15
post #3

I want to agree with this based on the title, but why would you do something like this: Click me if you're already using React? Yes the React code is a lot more verbose and has a bunch of "cruft" for lack of a better word. But you're already using it for the rest of your site, so you should (IMO) continue using it rather than mixing and matching approaches.

Also with "onlick" you have to lick it to trigger the event.

Re: HTML First

#16
post #8

Earlier quoted context omitted.

I don't think you'd mix in React with this approach.

Isn't it much easier to know you're going to use React (or Svelte or Vue or anything else) and just start there? Starting a build in HTML-first only to bolt on a JS framework after the fact seems like a lot of wasted effort.

The whole point of this essay is to encourage developers to avoid heavy frameworks like React, Vue, etc and use "lightweight" tools, including vanilla JS and native HTML features, instead.

Re: HTML First

#17
post #3

I want to agree with this based on the title, but why would you do something like this: Click me if you're already using React? Yes the React code is a lot more verbose and has a bunch of "cruft" for lack of a better word. But you're already using it for the rest of your site, so you should (IMO) continue using it rather than mixing and matching approaches.

Also with "onlick" you have to lick it to trigger the event.

I see you are also a fan of lickable.js

Re: HTML First

#19
post #8

Earlier quoted context omitted.

Isn't it much easier to know you're going to use React (or Svelte or Vue or anything else) and just start there? Starting a build in HTML-first only to bolt on a JS framework after the fact seems like a lot of wasted effort.

The whole point of this essay is to encourage developers to avoid heavy frameworks like React, Vue, etc and use "lightweight" tools, including vanilla JS and native HTML features, instead.

Sure, I'm just talking about that middle ground where you're trying to go with this approach and find that you now need a bunch of JS framework features.

Re: HTML First

#20
This is a blog spam post written by an author that has no credibility in the space rather than creating an agency that touts itself as "A software agency that doesn't suck.". How bizarre.

Even more, the author uses every possible library under the sun, from Tailwind to Framer, only to evangelise about raw HTML and topics he provides no credibility on.

To add to that, even the links to learn more about their agency all lead to Twitter, rather than LinkedIn, Clutch and Sortlist.

Post reply on HN