Advice to Young Web Developers
tumblr.beesbuzz.biz
Advice to Young Web Developers
1–10 of 328 posts
Re: Advice to Young Web Developers
#2Re: Advice to Young Web Developers
#3Re: Advice to Young Web Developers
#4Re: Advice to Young Web Developers
#5I wish this was listed at the top of the list, in the middle, and at the end. It’s super annoying when a site or application isn’t “supported” because it wasn’t tested in a separate browser (i.e. non-Chrome browsers).
I know it’s not always easy with a fair amount of nuance which the Chrome Compatibility post[0] touches on, but developing the web platform should be done openly, with the browser vendors working together to be compatible with each other and not introduce developer or user inconvenience. Otherwise you end up with web ownership and a fragmented platform.
Re: Advice to Young Web Developers
#6Re: Advice to Young Web Developers
#7This sounded more like a anti-SPA post. Maybe the title should be "Reasons for not building a SPA".
Let's rebuild html rendering, navigation history, forms, etc, all with Javascript, because it's the hip thing to do.
Re: Advice to Young Web Developers
#8Unfortunately I think it's going to be a long time before web apps stop using dark patterns like infinite scroll. It's not good for their bottom line.
Re: Advice to Young Web Developers
#9This sounded more like a anti-SPA post. Maybe the title should be "Reasons for not building a SPA".
SPAs are an anti-pattern. Let's rebuild html rendering, navigation history, forms, etc, all with Javascript, because it's the hip thing to do.
Please don't misuse words, especially in a negative context to mean "something I don't like", it cheapens the word in legitimate cases.
No comment on whether SPAs are worth anything though, I reserve my opinion.