Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTML Can Do That

chrisburnell.com

Post reply on HN
Print view View original

231–240 of 249 posts

Re: HTML Can Do That

#231

Post by yipinwong »

afavour wrote: post #90
yipinwong wrote: post #71

JS has been in front-line for these functionalty, and HTML has been dog-slow to catch up with slow standardization (not based on usage more academical) and recommendations. HTML can do that. yes. but adoption? welp, I don't really care nor will I use it unless I have to. I will use whatever was available in practice and continue to use them.

Odd to both complain about adoption and out yourself as someone unwilling to move to a better solution because it’s less familiar. What do you expect the answer to be here?

"Better" is a subjective term, and you have no way of proving that it is better using any metrics.

"Better" in my case is being able to move fast by implementing quickly, test fast, and move on with my tasks.

HTML might be "better" in terms of standards, but if nobody follows it, what good is it?

Re: HTML Can Do That

#232

Post by hollowturtle »

doodlesdev wrote: post #228
hollowturtle wrote: post #201

Earlier quoted context omitted.

You can have programmatic apis for accessibility, SEO pages can be dom based, performance of figma is better than if implemented via the dom api, developer experience? you just get the best and stop pretending you have capable people that spend a day on discussing effects in react. > My web browser is my agent It's very likely not anymore, otherwise Chrome wouldn't have pushed for manifest v3 > I wish Figma and Googl…

> stop pretending you have capable people that spend a day on discussing effects in react. Figma uses React for the UI panels. Google Docs uses the DOM extensively too. > have pushed for manifest v3 I don't use Google Chrome. > since we have decided app distribution to be web based No one has decided this, it just happened because web browsers were in the right place at the right time. It's not set in stone and devel…

> Figma uses React for the UI panels. Google Docs uses the DOM extensively too.

Tangential uses of the dom, the core app is on the canvas

> I don't use Google Chrome.

Who cares? They have an almost monopoly and they dictate what to implement on the web, it's already happening that many sites don't work on firefox because they've been only optimized for Chrome. And btw Firefox will implement manifest v3 as well. If you're not using Firefox or Safari you're still using chromium. We don't even have the capability anymore of developing alternative browser engines, the spec is a monster and the various attempts are still very far away.

> No one has decided this, it just happened because web browsers were in the right place at the right time

Exactly and since this is the current reality I don't see why we couldn't have better browser tooling for rendering near native stuff like we do on desktop frameworks. Developer tooling for the desktop already exists since ages but web folks have injected desktop apps as well with bloated stuff like electron

Re: HTML Can Do That

#233

Post by yipinwong »

bigbuppo wrote: post #140
afavour wrote: post #90

Earlier quoted context omitted.

Odd to both complain about adoption and out yourself as someone unwilling to move to a better solution because it’s less familiar. What do you expect the answer to be here?

I suspect he's still optimizing for IE5 compatibility.

A snarky comment that does not contribute jack.

Be gone, trollbot, if you ain't have anything better to say

Re: HTML Can Do That

#234

Post by HappMacDonald »

chmod775 wrote: post #226
edgyquant wrote: post #221

Earlier quoted context omitted.

Skill is the terminology the industry has adopted.

And people once called radio "the wireless", vacuum tubes "valve", and computer processors "the mill". Some terms and ideas are just shit, especially in the early stages of something new.

Time to steer my horseless carriage onto the Information Superhighway! :D

Re: HTML Can Do That

#235

Post by afavour »

yipinwong wrote: post #231
afavour wrote: post #90

Earlier quoted context omitted.

Odd to both complain about adoption and out yourself as someone unwilling to move to a better solution because it’s less familiar. What do you expect the answer to be here?

"Better" is a subjective term, and you have no way of proving that it is better using any metrics. "Better" in my case is being able to move fast by implementing quickly, test fast, and move on with my tasks. HTML might be "better" in terms of standards, but if nobody follows it, what good is it?

I think you can measure “better” if you’re specific. I’m saying better for user experience. You are fine foregoing that if your development experience is better.

Re: HTML Can Do That

#237

Post by abustamam »

As an aside, sometimes just because we _can_ do X in Y doesn't necessarily mean it's always the best solution. One example that comes to mind is people doing really cool things like Doom in CSS (https://github.com/NielsLeenheer/cssDOOM). Really cool? Yeah! Practical? Debatable.

That said, is _is_ quite nice that HTML can do so much natively. Now that I'm using LLMs more and more to build front-ends I find myself using fewer libraries and leaning more towards native HTML behavior, and it's been a nice experience.

Re: HTML Can Do That

#238

Post by bellowsgulch »

abanana wrote: post #149
bellowsgulch wrote: post #36

The older I get, the less I want to use new browser features that have already been somehow possible with existing ones that typically have been around for literal decades. Adopting them makes a future with multiple browser engines more labor intensive and unlikely as the number of standards targets one is required to support grows and it becomes a game of asking yourself what sites you want your browser to support.…

You started that off by raising an interesting point. Pity you had to ruin it by telling us you're exceptionally thoughtful and profound, and that those who disagree, suck! It's true, the amount of work that would be needed nowadays has made the idea of building a new browser engine almost impossible (I don't know how the Ladybird devs are getting on). It's a reason to encourage people to support Firefox on desktop,…

> Pity you had to ruin it by telling us you're exceptionally thoughtful and profound, and that those who disagree, suck!

It's just a comment on the Internet, you don't have to take it so seriously.

Re: HTML Can Do That

#239

Post by mdemare »

kotaKat wrote: post #21
dematz wrote: post #8

This comment by yurishimo should not be [dead], imo >Just a heads up but datalist is not really a great solution if you need a strong contract. The user can still type whatever they want into the field and there is no fuzzy filtering or typo mitigation. Once you add those requirements, a library that gives you a more fully featured combobox is likely going to make a lot of sense in your project. It is true! HTML can…

(iirc if you have [showdead] on you can click on the timestamp to the comment and will get a [vouch] option as a reverse-flag, fwiw. i see it and don't have showdead enabled, so enough people have re-vouched it!)

I did not know that and I’ve been here quite a while…

Re: HTML Can Do That

#240

Post by mdemare »

silvestrov wrote: post #28

I'd really wish I could force ISO format for the date input as the current "platform native" is confusing for some users when the OS use a different language than the web page that is shown. For some multi-country companies it makes sense to have all admin pages in English no matter the underlying OS language. Imagine sending a screenshot where the OS date format is different from what everybody else expects from an…

Also temperature, weights, distances…
Post reply on HN