Live data from Hacker News

I'm betting on HTML

catskull.net

191–200 of 458 posts

Re: I'm betting on HTML

#191
I would care more about markup if the browser would actually be able to do anything interesting with it, but for most part markup is a just a default style for an element, the semantic meaning is ignored. The tag is about the last one I can think of that actually made a difference from the users perspective.

There is also a lot of markup for really common tasks still missing, I'd like to see an and something to handle pagination at the browser level (rel="next" has been around for decades, but browser don't care). And more broadly, I'd really like to see much better support for long-form documents in HTML or at the very least native ePub support in the browser.

Re: I'm betting on HTML

#192

Earlier quoted context omitted.

Most of them don't work properly and/or look terrible by default in all browsers. So no-one uses them, so lots of people don't know about them.

What do you mean with "they don't work properly"? Could you give an example?

Datepicker was fundamentally broken in many ways in safari for a long time. And it still doesn't have the functionality that most apps need, so it's pretty pointless.

Re: I'm betting on HTML

#194
post #61

Earlier quoted context omitted.

, , etc can be themed

requires some vendor-specific prefixes last time I tried theming it using CSS (unless you're using "theme" to mean host system/window mananger/browser - wide theme). There is no common subset (that I am aware of) of CSS properties shared amongst browsers that can be leveraged to even decently change the element's appearance. So I'm not sure that it is the best example. I agree that many of the list _are_ themable eno…

Yes, it's still a pain compared to more established elements https://css-tricks.com/html5-progress-element/

Re: I'm betting on HTML

#196
post #186

Earlier quoted context omitted.

That’s still a stupid pedantry, and is even false. A Turing machine only makes use of at most n cells of its tape after n steps - so running it for a finite number of steps is possible even in finite memory. Especially that modern computers can do arbitrary side effects, having access to the whole universe as tape, which is still finite, but so is time. There is no way to differentiate between a magical Turing machin…

Why are they identical? A program may use more steps than memory.

A Turing machine can either go left or right on its tape (some versions have a stay step as well, doesn’t matter). If all your program does is step right forever, than it will use the maximum amount of memory, but only ever a finite amount, that is equal to the number of steps taken.

So if you don’t have infinite time (you don’t have), and you have big enough memory for the particular use case so that you don’t get OOMKiller involved, then you have a Turing machine for all complexity theoretical and practical purposes, especially that RAM is not analogous to the Turing machine tape - your computer has much more state than only its memory, if it has network access, you can basically make use of a cloud vendors whole army of servers as storage, just as an example.

Re: I'm betting on HTML

#197

Earlier quoted context omitted.

> I had heard of almost none of these HTML elements I'm not disagreeing with the gist of your post, but come on, these elements have been around for ages. It's definitely on you to become acquainted with the basics before your HTML critic can be taken seriously ;) The post links to MDN (arguably the most useful short reference) but there is of course also WHATWG's HTML spec or, if that's too voluminous, SGML DTD form…

has always been interesting to me. I've been aware of it for as long as I can remember, since it's been in all the tutorials I remember reading as a teen, and other docs as I got older. Unlike some other forgotten elements, it's one that's clearly very useful, and yet I can count on one hand the amount of times I've seen it used in the real world (yet plenty of times where someone has reinvented it with JS) Likewise,…

Everybody was using imagemaps in the 90s because it was the only way to have multiple links over an image, something we wanted to do because without CSS we could not have a row or a column of buttons with fancy colors and fonts and placed where we wanted them to be. So nav bars were a large image with imagemap anchors placed over the buttons. Then we got CSS, tables (used for layout!), divs with positioning and eventually the features that web developers are using today.

Re: I'm betting on HTML

#198
post #196

Earlier quoted context omitted.

Why are they identical? A program may use more steps than memory.

A Turing machine can either go left or right on its tape (some versions have a stay step as well, doesn’t matter). If all your program does is step right forever, than it will use the maximum amount of memory, but only ever a finite amount, that is equal to the number of steps taken. So if you don’t have infinite time (you don’t have), and you have big enough memory for the particular use case so that you don’t get O…

[deleted]

Re: I'm betting on HTML

#199
post #130

Earlier quoted context omitted.

> The LLM will look at any .exe and determine if it halts. At that point you'd need an AGI that can figure out something we can't. Edit: but yeah, sarcasm. Nowadays I can't even tell sometimes.

I am 100% sure that parent poster was being sarcastic at the hype around LLMs and how many think they can solve everything, even if said thing is impossible to do, e.g. the halting problem. Do note that the halting problem is fundamentally true, no AGI will realize some new way around, unless are mathematics are flawed to the core.

Halting problem is one of the problems that arise from precise mathematical definition and its outskirts. LLMs are all about making sense from unstructured text, i.e. lying on the opposite end of the spectrum where math has no direct way to do anything. So while the poster was sarcastic, they also missed the mark.

Re: I'm betting on HTML

#200
post #135

I use a lot for debugging Go html templates. {{if .DevMode}} Data {{.}} {{end}} It's nicely unobtrusive when collapsed, doesn't mess up the page completely. Then expands to the full glory when needed.

You can use it for all sorts of things on web pages, including collapsible menues and such. Github markdown lets you use it too. People use it for examples and inline explanations.

[deleted]
Post reply on HN