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

Replacing JavaScript with Just HTML

htmhell.dev

Post reply on HN
Print view View original

151–160 of 296 posts

Re: Replacing JavaScript with Just HTML

#151

Post by assimpleaspossi »

nashashmi wrote: post #138
troad wrote: post #55

Plain HTML is very cozy to me - I came of age in that era. Marquee tags 4eva . But as much as I hate to admit it, it is very difficult to build something functional today with plain HTML and no/minimal JS. If you want, say, a model form that manages its children as well, you're basically going to end up with a 2003-era ASP-feeling application with way too many views and forms (as seen on your employer's current HR sy…

OT: marquee tags were a missed opportunity to implement horizontal scrolling often used on shopping websites. Now it uses JS to achieve the same. I have been trying to find other more commonly known UI patterns that could be done natively. The time has long come for tabular data to be put into HTML tables just by referencing the source. Xslt almost did that. Another one is integrating xml http requests with native ht…

There's a usability and design issue with that as you lose what you're reading as it scrolls off the screen. Also, scrolling is a styling issue and not a document description issue which is what HTML is for.

Note: has never been part of any HTML standard since the beginning except the current one which only has it for the purpose of marking it obsolete so people will quit using it.

Re: Replacing JavaScript with Just HTML

#152

Post by _heimdall »

tosti wrote: post #100
kmoser wrote: post #34

Earlier quoted context omitted.

My main beef with datalist is that there's no easy way to show and allow only text (e.g. Beverly Hills), but have the actual value selected be a number (e.g. 90210). In other words there's no analogy to Beverly Hills .

That and there's no HTML way to interactively load results. Or are you really going to serialize half a million records to HTML and transfer it all every time the relevant block is added to a page? What if it sits in the header or footer templates?

This would be possible in XSLT, if only browsers would implement the latest spec rather than abandoning it all together.

Re: Replacing JavaScript with Just HTML

#154

Post by oceansky »

bodash wrote: post #145

Just been through several frontend interviews in the last few months, where it's clear that they still judge a developer's JS skills (especially React) than being semantically correct on HTML elements. Every question/exercise is centred around how well you know React hooks, effect, memoization, modern css-in-js etc. Given I've been working with Astro recently, in one interview I talked about DOM APIs and I can see th…

Having a separate css file make small components so much cleaner. I am not against tailwind, but I wouldn't want to use it in front-end interviews.

Re: Replacing JavaScript with Just HTML

#155

Post by _heimdall »

ksec wrote: post #86
llmslave2 wrote: post #80

Earlier quoted context omitted.

Gmail with html only would not be a nice experience. Modern gmail is really bloated but it's actually one of the few web apps I have no problems with.

Hey the email services has just proved you could offer better than Gmail experience with HTML + small dose of JS. Another example being the new FE on Github. At the end of the day it isn't really the tech that is the problem. Is how people use the tech. And for thousands of different reasons keeping it simple has always provided better experience evaluated on the whole.

> Another example being the new FE on Github.

Github's old frontend was mostly HTML with a bit of JS, their new frontend is react. The old UI had its bugs, but it was much better than the react version in my experience. I still commonly find the UI out of sync with itself requiring a reload, but now I also frequently wait for the page to load and viewing large diff's is a performance nightmare.

Re: Replacing JavaScript with Just HTML

#156

Post by dekoidal »

wvenable wrote: post #101
jakelazaroff wrote: post #61

Earlier quoted context omitted.

That is no longer true! You can do it in CSS with a combination of `@starting-style` and `transition-behavior: allow-discrete`. [1] Another gotcha you'll run into is animating the height. A couple other new features (`interpolate-size: allow-keywords` and `::details-content`) will let you get around that. [2] Modern CSS is awesome. [1] https://developer.chrome.com/blog/entry-exit-animations [2] https://nerdy.dev/open…

I can't see how a bunch of esoteric incantations are better than just some straight-forward easy to understand and follow JavaScript.

Is CSS too hard to learn or something?

Re: Replacing JavaScript with Just HTML

#157

Post by rokkamokka »

bodash wrote: post #145

Just been through several frontend interviews in the last few months, where it's clear that they still judge a developer's JS skills (especially React) than being semantically correct on HTML elements. Every question/exercise is centred around how well you know React hooks, effect, memoization, modern css-in-js etc. Given I've been working with Astro recently, in one interview I talked about DOM APIs and I can see th…

Remember that a large part of hiring is finding someone who fits in an existing team. A team that uses react won't appreciate someone choosing to use native DOM APIs instead of a react component.

Re: Replacing JavaScript with Just HTML

#158

Post by halfmatthalfcat »

bodash wrote: post #145

Just been through several frontend interviews in the last few months, where it's clear that they still judge a developer's JS skills (especially React) than being semantically correct on HTML elements. Every question/exercise is centred around how well you know React hooks, effect, memoization, modern css-in-js etc. Given I've been working with Astro recently, in one interview I talked about DOM APIs and I can see th…

Because nobody outside of the HN-sphere cares about HTML purism, nor should they.

Re: Replacing JavaScript with Just HTML

#159

Post by chiefalchemist »

asdfaoeu wrote: post #144
chiefalchemist wrote: post #142

Earlier quoted context omitted.

Last I checked that without JavaScript details / summary has accessibility issues. That is, you need JS to add aria-open or similar. It’s odd and frustrating that such an essential tag is not defined to be accessible, afaik.

Why would you need aria attributes if it's summary tag?

I presume it has to do with AT and how it typically interprets the tag. TBH IDK other than I’ve seen it come up in accessibility discussions / groups.

Re: Replacing JavaScript with Just HTML

#160

Post by wiseowise »

tisc wrote: post #87
suprjami wrote: post #13

Gimme a dark/light mode switch. CSS is allowed.

Why would you build a switch instead of relying on the user’s system settings? The only reason I can imagine is that your dark/light mode is not usable/readable so it forces the user to switch

Because I don't want to toggle my whole system theme based on one special website.
Post reply on HN