Live data from Hacker News

Don't Roll Your Own

susam.net

1–10 of 128 posts

Re: Don't Roll Your Own

#4
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.

Re: Don't Roll Your Own

#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 the month more than they like the service they're building. Which is fair enough.

Re: Don't Roll Your Own

#6

I find that most datepickers are better than the browser's default. It's a shame that they can't be styled more

I agree with a caveat: Default date pickers on mobile devices are very good. But on desktop browsers they are terrible. They break design continuity in a very ugly way and have quirks between browsers and systems. And personally, the popup calendar they provide just too small. If the system took over the date picker on desktop like it does on mobile devices instead of forcing the browser to handle it, I feel like we could get somewhere better.

Re: Don't Roll Your Own

#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 people, tell them to go crazy and then also hire thousands of C++ browser developers for decades to implement everything. Boom, a moat!

Re: Don't Roll Your Own

#10
UX standardizes as majorities begin to agree on patterns/interactions/concepts.

Unfortunately, it’s 1) difficult to reach consensus 2) difficult to broadcast and 3) difficult to enforce. For example, even when major browsers achieve 1) and (e.g. implement a standard component) 2) and 3) are still huge gaps.

Post reply on HN