Don't Roll Your Own
susam.net
Don't Roll Your Own
1–10 of 128 posts
Re: Don't Roll Your Own
#2Re: Don't Roll Your Own
#3Re: Don't Roll Your Own
#4Congratulations, now your website is a shitty experience for your users. Well done.
Re: Don't Roll Your Own
#5Totally 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.
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
#6I find that most datepickers are better than the browser's default. It's a shame that they can't be styled more
Re: Don't Roll Your Own
#7Javascript 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
#8I have a personal issue with having a 500KB page load, so a button press can be animated.
Re: Don't Roll Your Own
#9I find that most datepickers are better than the browser's default. It's a shame that they can't be styled more
You mean your browser's. There is no "the browser".
Re: Don't Roll Your Own
#10Unfortunately, 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.