Live data from Hacker News

I'm betting on HTML

catskull.net

31–40 of 458 posts

Re: I'm betting on HTML

#31

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…

Alternatively, you could set up LanguageTool[1], which runs much faster, is more reliable, is open source, and, crucially, doesn't require sending what you wrote to a server on the Internet. Plus, it already has high-quality integrations with standard software like LibreOffice, so you don't even need to write anything yourself.

[1] https://github.com/languagetool-org/languagetool

Re: I'm betting on HTML

#32
I noticed made the list but not . Is the latter a well-known tag compared to the former? In any case, semantic HTML is nice because they usually have good accessibility attributes by default.

In general, , , , , , and prove to be highly useful for quickly hacking together a personal site without having to write much JavaScript, if at all.

Re: I'm betting on HTML

#33

I've been using `dialog` and `details` of late, and couldn't be happier. At the same time, `section`, `article`, `header` and `footer` confuse me a lot. I've stopped using them.

Section and article really don't add any value, but header and footer elements are used as landmarks by adjustive technologies like screen readers

Re: I'm betting on HTML

#35

The vs. thing, how did I never realize that before? I guess I'd never thought about them having a semantic meaning.

They don't. Like, that linked document is a cool idea but it's utterly inaccurate as a description of how the tags are used by actually existing website or handled by actually existing user agents (yes, including screenreaders).

Re: I'm betting on HTML

#36

HTML is that nerd who's rich now. Give me HTML,CSS,JS combo any day over some complex js library or platform.

Used to work with that combo only – it's a mess as soon as you need to make reusable components. Svelte strikes a pretty good balance there !

Re: I'm betting on HTML

#37
post #22

I had heard of almost none of these HTML elements, and that's such a shame, because they could seriously help put the "we need JavaScript for every gosh darn thing" ecosystem to an end (or at least return JS to what it was originally meant to be: a way to add some flair, some interactivity, some whatever, but not necessarily a replacement for all of your markup and a full-DOM manager). I'm starting to think my dream…

You might like this: http://youmightnotneedjs.com/

Hahaha wow I have to say that was the least convincing demo I’ve seen.

- Fills history with massive amounts of entries, and back button doesn’t do anything

- Slider UI look like crap (ok fine, can be fixed) but use not just css but SCSS (requires a precompiler) but wait, not enough, it also needs hardcoded number of images. It’s not reusable in the most basic sense.

- Input validation has phone number on xxxx-xxx-… format and doesn’t fill dashes automatically. It’s also type=number which opens a numpad on iOS which does not have dashes available at all. I can’t proceed unless copy pasting a dash from somewhere else?

- Gave up after that but I’m sure there’s plenty more

Yeah, I’m leaning towards that JS isn’t the nemesis of accessibility. It’s simply not knowing what works and testing properly. It’s funny that frontend folks are seen as lesser beings and then counter-claims like this is passed as enlightened. Yeah on first glance maybe, but it’s proof that these regurgitated claims are made with very little insight. Like all tech, you have to know how to hold it right which takes a little time and humility to get right.

And yes, we still use too much JS. But it’s not the fault of JS or dev practices that we have newsletter popovers, cookie banners and 100 ad delivery and click tracking requests per page load. Indeed JS became extremely bloated for a while but nowadays everything is equally bloated, just look at all the backend snake oil with 1000 cloud microservices and leftpad-like APIs.

Re: I'm betting on HTML

#38
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…

Exporting to web using Flutter is a nightmare I believe. When I checked last time, rendering happens on a canvas. There is no markup at all

Re: I'm betting on HTML

#39

I had heard of almost none of these HTML elements, and that's such a shame, because they could seriously help put the "we need JavaScript for every gosh darn thing" ecosystem to an end (or at least return JS to what it was originally meant to be: a way to add some flair, some interactivity, some whatever, but not necessarily a replacement for all of your markup and a full-DOM manager). I'm starting to think my dream…

https://qutebrowser.org

Re: I'm betting on HTML

#40
post #32

I noticed made the list but not . Is the latter a well-known tag compared to the former? In any case, semantic HTML is nice because they usually have good accessibility attributes by default. In general, , , , , , and prove to be highly useful for quickly hacking together a personal site without having to write much JavaScript, if at all.

I assume was not explicitly mentioned because it generally only appears as a child of .

It's not intended to be used in the same way as say; to my knowledge

> A element may only be used as the first child of a element

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/su...

Post reply on HN