Came for the discussion, stayed for the watches.
Banned. Sorry for the delay. Was caught with the whole Win10 launch party and didn't check DN all day. Feel free to send me a tweet if you see anything wrong next time.
what the f*ck is going on? why do we have spam comments here?
I'm not sure what the moderation strategy is for DN, but it looks like we'll need a way to flag posts I guess!
e.g: Reddit-like [This comment has been downvoted, expand to read]
More people need to be able to downvote. I see spam comments with +2 or +3 sometimes.
Yo mama is the new IE
I totally disagree with his comparison. Chrome can't be compared to a Browser that added tons of proprietary features and extreme lack of W3C standard support. Damn IE hadn't PNG support until what, IE 8?
Comparisons fo Safari to IE are kinda the same, and noone cried there. In fact, currently no browser is god-like.
- Safari gets not enough updates
- Chrome fails at some minor parts like seen here
- Firefox has some really twerky css rendering problems, especially regarding flexbox
- internet explorer will once again recieve no updates because the follow-up Edge - which is named after the most awkward internet connection on smartphones - won't come to Win Vista, 7 and 8.
- Opera... what is opera?
Opera, is Blink now, same engine as Chromium.
I was referring to its marketshare :)
Then, apart from India it's almost non-existant :)
Wait, Edge won't come to Windows Vista, 7 and 8? That's surprising, even for Microsoft...
it's the same problem as with IE8 (Windows XP didn't get any better release).. Microsoft wants to force users to Windows 10 that way, and we web designers have to deal with IE11 for the next 10 years...
Gradients are very expensive to draw, fixed elements hurt scrolling performance, paint times often prevent you from reaching a steady 60FPS, and so on.
If you can't build a smooth 60fps web app you're doing it wrong. It has nothing to do with the browser; it's because your app is badly coded.
I don't think that judgement is fair. 'Badly coded' is not the same as when a developer lacks the understanding needed about the rendering engine. I do however agree on your sentiment that it's not the browsers fault.
Also, sometimes you need to pull back on resource-heavy design decisions if they're hurting performance.
It might have sounded harsh and I agree that it might not be fair, but if you lack understanding you will write "bad" code. It doesn't mean you can improve or be taught to code better.
Looking forward to the next episode in the series "Edge is the new IE"...
Bold statement. But: 1) nothing is the new IE - IE<9 was the worst for frontenend web dev. The web would be another (better) web, if there was no IE. An IE is a clumsy browser with a shitty update cycle, with huge market share. So: Safari is right now more IE than any other browser.
2) In the article is nothing that proves your statement, no links and benchmarks or tests.
3) I really need a new watch.
As much as I don't think the title is accurate (am hesitant to call it clickbait...), the message certainly seems to be ring true to me. As a front-end developer I honestly don't really care too much about cutting-edge ES6 stuff or IndexedDB and so on, I just want the core features to work correctly.
I would so much rather have
position: sticky;back than the newest cutting edge features nobody's really using. I'm pretty annoyed that got pulled because it "isn't inline with the Chrome dev team's vision for the web" or something asinine like that. They just don't want to implement that feature, so we can't have it.
This makes a good point.
Well, in my experience Safari is slower in performance with all the mentioned stuff (gradients, fixed elements etc.) and more importantly slower with some fairly trivial stuff like CSS opacity or background transitions (and if you place some layers on top of one another for some hover or touch effects it can become really crippling for browser). I've yet to see real world example where Safari outperforms Chrome.
People need to chill with clickbait headlines just to get attention!
All I wanna say is fuck scroll-snap-type.
The only thing I know is that every time I open Chrome on my old 2010 MCP, the poor CPU goes crazy high. Had to switch to Safari to work in silence. So in my case, it had better "User Experience".
I do however feel a bit jealous when seeing all these nice Chrome extensions coming out every now and then whereas for Safari extensions, it feels it was last updated when OSX Dashboard app was released.
Safari is made for Apple devices only, so I do think its doubtful some other browser can achieve the same smooth experience due to having to port it to different OSs.
Weren't the extensions the ones causing the high cpu? I've run chrome on a even older crappier laptop smooth. or did you not run extensions?
I actually did that on a fresh install and the problem persisted. Even folks at Google tried to help me out but I think my mac is way too old for that and the issue with the GPU doesn't help either :/
It's funny because the same happened when I tried to switch to Atom text editor, and because it runs based on Chrome engine, the same has happened.
I might give it another shot and see if somehow the issue is gone with the latest version.
If your MCP is freaking out, check to see whether tron.exe is running. Sometimes that program gets its identity disc stuck in the MCP's security software.