Live data from Hacker News

Don't Roll Your Own

susam.net

31–40 of 128 posts

Re: Don't Roll Your Own

#31
I'd like to add:

* Don't roll your own standard controls

Seriously. Don't. You want a single-select box? Use a combo box or radio button group. Want an edit box? Use an edit box. Want a list that finds things as you type? That's in the standard too. Don't roll your own.

This "roll our own controls for everything" bothers me to no end as a screen reader user, because practically nobody properly follows ARIA best practices, and that leads to a less accessible internet.

Re: Don't Roll Your Own

#32
If one really wanted to ruffle feathers they could make a script that checks out the latest source code for OpenSSL, OpenSSH maybe a few other communication daemons, makes just a few very subtle changes to a few ciphers, shim in some random nonsensical padding, static compile or containerize and distribute to a private network of systems in minecraft.

Whatever you do don't teach AI how to do this or there could be a flood of VPN's speaking new but not really new ciphers that code breaking farms won't know what to do with and ciphers that are not known to exist and yet nobody ever really rolled their own.

This concept was conceived whilst interacting with Rubix cube players.

Re: Don't Roll Your Own

#33
post #7

> Don't roll your own page scrolling, link navigation, text selection, context menu, copy and paste, password field, or date picker. Javascript in the browser was a mistake. And if we had to have it, the suitable scope of it was what we had around 2004. Google invested tens of billions in it realizing they had a way of owning the browser space simply by making it insanely complex. Just hire all of the web standards p…

I understand the frustration but don’t take it too far. People often post great games here, cool visualisations, useful utilities. Hardly any of those would work at all without JavaScript. You can do terrible things with JS but you can do great things too.

The cost of complexity is generally underestimated. (But hey, we can try out cool demos!)

Re: Don't Roll Your Own

#34

> Don't roll your own page scrolling. browser should not even let the page see this action > Don't roll your own link navigation. browser should not even let the page see this action > Don't roll your own text selection. browser should not even let the page see this action > Don't roll your own copy and paste. browser should not even let the page see this action I'm serious. WHY javascript code is even allowed to see…

It should be illegal for a website to hijack text copying, right clicking, or keyboard shortcuts like Ctrl*f.

No. There are already too many batshit insane laws trying to regulate the internet. We need less, not more.

Re: Don't Roll Your Own

#35

Earlier quoted context omitted.

It should be illegal for a website to hijack text copying, right clicking, or keyboard shortcuts like Ctrl*f.

No. There are already too many batshit insane laws trying to regulate the internet. We need less, not more.

Indeed, people talk about technical solutions to social problems but there is also such a thing as trying a legal solution for a technical problem.

Re: Don't Roll Your Own

#36

> Don't roll your own page scrolling. browser should not even let the page see this action > Don't roll your own link navigation. browser should not even let the page see this action > Don't roll your own text selection. browser should not even let the page see this action > Don't roll your own copy and paste. browser should not even let the page see this action I'm serious. WHY javascript code is even allowed to see…

> WHY javascript code is even allowed to see all these actions of the user?

Because the alternative is UI/UX Designers and Visionary Managers insisting on keeping Flash and Java Applets and Microsoft Visual Silverlight .Net++ around forever, because you can't do some things in the browser and We Need To Do Them.

Some things have minimal complexity that either lives in the language itself or in libraries. The Web has minimal bells and whistles that are either implemented in the browsers itself or in plugins.

Re: Don't Roll Your Own

#37
post #31

I'd like to add: * Don't roll your own standard controls Seriously. Don't. You want a single-select box? Use a combo box or radio button group. Want an edit box? Use an edit box. Want a list that finds things as you type? That's in the standard too. Don't roll your own. This "roll our own controls for everything" bothers me to no end as a screen reader user, because practically nobody properly follows ARIA best pract…

Don't worry, they bother everyone else as well since they are usually broken one way or the other.

Re: Don't Roll Your Own

#39

> Don't roll your own page scrolling. browser should not even let the page see this action > Don't roll your own link navigation. browser should not even let the page see this action > Don't roll your own text selection. browser should not even let the page see this action > Don't roll your own copy and paste. browser should not even let the page see this action I'm serious. WHY javascript code is even allowed to see…

I found that most internet pages are greatly enhanced by disabling JavaScript in my web browser.

Re: Don't Roll Your Own

#40
post #5

Totally agree. What do engineers or designers think they're trying to accomplish when they mess with the scroll bar? Or the password field? "We are so sophisticated, the built in behavior is simply not good enough for us!" Congratulations, now your website is a shitty experience for your users. Well done.

In my experience, it's never the engineers nor the designers who makes those decisions. Stuff like that always comes from higher up the ladder, some middle management figure who thinks he is smarter than he is, mandates such abominations and refuses to hear reason from the engineers and the designers. The engineers and designers then proceed to do as they're told because they like that nice fat paycheck at the end of…

In my experience it's always the designers.
Post reply on HN