Live data from Hacker News

I'm betting on HTML

catskull.net

11–20 of 458 posts

Re: I'm betting on HTML

#11

Tangent. > I wrote this post and then GPT-4 fixed my grammer and spelling I wrote an Autohotkey + Go script that I constantly use for fixing grammar using ChatGPT's API. You can select the text, press F8, wait a bit, and your input will be replaced by correctly grammatical text. The only catch is that it "fixes" the tone and makes it professional, which is kinda annoying. Feel free to try it out: https://github.com/a…

The misspelling of grammer instead of grammar is a little ironic in this context. Sorry:-)

Re: I'm betting on HTML

#13
> Pretty much you can highlight text. By default Safari shows a yellow highlight. I like it!

Chrome also shows a yellow highlight by default. But since I don't have Safari installed on my machine, I don't know if it's exactly the same color. Also, I'm not sure if other browsers have the same default color. Isn't it a good use case for CSS?

Re: I'm betting on HTML

#15
post #13

> Pretty much you can highlight text. By default Safari shows a yellow highlight. I like it! Chrome also shows a yellow highlight by default. But since I don't have Safari installed on my machine, I don't know if it's exactly the same color. Also, I'm not sure if other browsers have the same default color. Isn't it a good use case for CSS?

CSS will let you choose the highlight color for your readers. Semantic markup lets the reader choose the highlight rendering, including the choice of leaving it to the browser.

A blind reader can configure their client to speak highlights.

Re: I'm betting on HTML

#16
post #5

Great read and interactive demo. After a few years of dabbling with Flutter I just came back to the same conclusion: bet on HTML. Astro / Tailwind / Daisy UI / Alpine.js makes it lovely to build an HTML site with a lot of simple SSR and a little bit of client side reactivity peppered about. The result is simple sane HTML files that look and work great on desktop web browser and and mobile wrapped web view. My app is…

After trying a bunch of fancy frameworks and platforms I ended up doing exactly this - a static site with alpinejs and tailwind. It has been by far the best decision I've ever made. And the best thing is I'm confident any new dev will be able to pick up my 100 line build file and grok it in about 3min. No matter whether they're react, angular, PHP or python folks - it's dead simple and I love it.

Re: I'm betting on HTML

#17
post #4

This reminds me that I really need to re-evaluate the stuff I already know and keep it all updated.

I am lost in CSS these days since letting my skills atrophy over the past ~decade

You'll be fine. If anything CSS is the one thing that's gotten easier in web dev. It might take some time but you'll be able to grok it for sure if you've dealt with old school CSS.

Re: I'm betting on HTML

#18
post #5

Great read and interactive demo. After a few years of dabbling with Flutter I just came back to the same conclusion: bet on HTML. Astro / Tailwind / Daisy UI / Alpine.js makes it lovely to build an HTML site with a lot of simple SSR and a little bit of client side reactivity peppered about. The result is simple sane HTML files that look and work great on desktop web browser and and mobile wrapped web view. My app is…

After trying a bunch of fancy frameworks and platforms I ended up doing exactly this - a static site with alpinejs and tailwind. It has been by far the best decision I've ever made. And the best thing is I'm confident any new dev will be able to pick up my 100 line build file and grok it in about 3min. No matter whether they're react, angular, PHP or python folks - it's dead simple and I love it.

Lately I've been doing raw html and css. No build. I just write the files. It's really easy. Yeah there's some duplicate code in the header but grep is not that hard to use.

Re: I'm betting on HTML

#19
I find it interesting that many of the comments here seem to view this as an anti JS article. To me a lot of these are going to be immensely useful tools in combination with the TS heavy frameworks we use for modern Enterprise App frontends, exactly because they are HTML native tools that aren’t going to require a bunch of stuff.

Like the meter tag, which I assume will replace every loading module we currently use in React when I get to work today because that is soooooooo much better than what we currently use.

But maybe I’m just misunderstanding people, or the article in some way. But to me this is very interesting even if your entire frontend is basically all TypeScript like many larger applications are today.

Post reply on HN