11–20 of 43 posts
"Without JavaScript or CSS, or without mobile Webkit, my site may not look pretty but will still be functional." There goes backbone.js and other javascript MVC patterns. This is something I'm still unsure about. What do (you) people think of keeping your "data out of the DOM"?
content_pageweb_app
Scrolling through that was very annoying. Page up/down obviously won't move by exactly one of the "pages".
And the scrolling is annoying.
"I will educate my friends and family that WEB BROWSER CHOICE MATTERS" and "Most importantly and above all, I will put the needs of the USER FIRST over my own needs as a developer." So please do, put the needs of your USERS first. Your users do not NEED to be educated by you. It is not your business what browser they use.
You can cater to the variety of platforms your users want to use whilst at the same time having useful and meaningful conversations with friends and family about what the best browser is for them. You don't annoy your users by trying to 'educate' them, but collectively we see a move forward.
I thought it was a blank page at first... some sort of less is more statement.
You failed to interpret the page author's 100% custom scrollbar (on the left edge of the screen) as an indicator that there was more content? That's ... odd. He clearly had your interests in mind when implementing that, since browser vendors just think about themselves with their annoying scrollbars that look the same on every page, even. Simplistic fools.
I'm not sure why one high-end abstraction finds favour over another slightly higher high-end abstraction, but this sure sounds a lot like the people who insist that you can't be a good programmer unless you've learned some kind of assembler.
On the "shoulders of giants" means we don't need to know javascript as well as jQuery. It means we don't have to know assembler as well as pascal. It means that we don't need to learn IP when we can just learn TCP/IP, and we don't need to learn TCP/IP when we can just use REST over HTTP.
Learning at the root goes a lot further down than you want to go, need to go or are capable of going.
"I will educate my friends and family that WEB BROWSER CHOICE MATTERS" and "Most importantly and above all, I will put the needs of the USER FIRST over my own needs as a developer." So please do, put the needs of your USERS first. Your users do not NEED to be educated by you. It is not your business what browser they use.
> Your users do not NEED to be educated by you.
I think educating clients and users is actually crucial. For a lot of users browser was conscious choice, but there is big group that don't even know that there are different/newer browsers. First group can ignore advice but second group might benefit a lot.
>It is not your business what browser they use.
It absolutely is.
Silly car metaphor: I'm taking my car to a service station. I expect mechanic to tell me that oil I'm using is not the optimal one. Whether or not I take his advice is my business. But informing me about substandard oil is very much his business.
Also - If all of my users used modern browsers, I could save money by not spending time on ensuring my site performs well on old buggy browsers.
So just put this in a full static page. Why the scrolling? And also color/font choice is quite terrible. No responsiveness for small screens. Apparently, he didn't follow his own advice.