4 ms·

I couldn't disagree more with this post. I'm a full-stack engineer, and deal with both the front-end, back-end and server. I've been doing front-end since my ca

I couldn't disagree more with this post. I'm a full-stack engineer, and deal with both the front-end, back-end and server. I've been doing front-end since my career began, so over 13 years now. I've lived through the IE6 days, and I have to say that things are almost as bad now as they were back then. At least IE6 bugs were well documented and we knew how to work around them. Nowadays we work in a fragmented ecosystem where the same operating systems behave differently on different devices (HTML5 video on Android is a prime example). There are all kinds of odd bugs when dealing with mobile browsers, and even on desktop canvas and CSS3 animations don't always behave consistently depending on how you are using them. Just an example of the most obscure of bugs that you might have to deal with: if you try to translate the position using CSS3 of an object that contains Flash in Firefox, the flash object will disappear entirely. Good luck working around that one.

erikpukinskis 13y ago
What you're saying is true, but it's a tautology. It doesn't matter what technology you use, your job will always be "just as bad". As a developer it's your job to push the limits of what you can accomplish until it starts to hurt a little. That will always be true of the web: we'll push what browser capabilities we try to harness all the way to the point where compatibility work really starts to burn. But if you look at things in absolute terms, what you're saying is crazy. I can build, in a week, something that is better in every way than Gmail was when it was originally released, that works on a larger proportion of devices. That's progress Your subjective experience might be that you still work in the weeds but that's because you're insanely more productive for the same effort than you were 8 years ago.
- morganherlocker 13y ago
  When I read the OP's comment all I could think about was what it would be like writing a decent web app in the bad ol' IE days if it also had to work in most of those crappy symbian flip phone browsers. I agree with you completely. Meeting expectations today is really tough, but the expectations are much higher in most ways.
  - mercer 13y ago
    Indeed. As a contractor I often have to use the latest and greatest because project leads read about it somewhere and designers go wild. Which means that the work is not significantly easier because the goal-posts just moved. But for smaller clients that I have full control over, I usually take a subset of functionality that I know is stable and consistent by now, and I only go for bleeding-edge stuff if the budget allows it (because, of course, it is fun to play with shiny new stuff).

erikpukinskis 13y ago

What you're saying is true, but it's a tautology. It doesn't matter what technology you use, your job will always be "just as bad". As a developer it's your job to push the limits of what you can accomplish until it starts to hurt a little. That will always be true of the web: we'll push what browser capabilities we try to harness all the way to the point where compatibility work really starts to burn. But if you look at things in absolute terms, what you're saying is crazy. I can build, in a week, something that is better in every way than Gmail was when it was originally released, that works on a larger proportion of devices. That's progress Your subjective experience might be that you still work in the weeds but that's because you're insanely more productive for the same effort than you were 8 years ago.

morganherlocker 13y ago
When I read the OP's comment all I could think about was what it would be like writing a decent web app in the bad ol' IE days if it also had to work in most of those crappy symbian flip phone browsers. I agree with you completely. Meeting expectations today is really tough, but the expectations are much higher in most ways.
- mercer 13y ago
  Indeed. As a contractor I often have to use the latest and greatest because project leads read about it somewhere and designers go wild. Which means that the work is not significantly easier because the goal-posts just moved. But for smaller clients that I have full control over, I usually take a subset of functionality that I know is stable and consistent by now, and I only go for bleeding-edge stuff if the budget allows it (because, of course, it is fun to play with shiny new stuff).