Safari is the new IE

Post by gnufied » Tue, Jun 30, 2015, 6:04 PM UTC

philwelch wrote: post #116

Someone wrote: post #115

Earlier quoted context omitted.

"the re-ignition of the "browser wars" when Google launched Chrome, and Apple got serious with Safari by moving to WebKit" Moving to WebKit? Only if you count CyberDog, I guess. Safari was always WebKit based. Also, your phrasing could be read as if Chrome came before Safari, but Safari is from 2003 ( https://en.wikipedia.org/wiki/Safari_version_history ), Chrome from 2008 ( https://en.wikipedia.org/wiki/Google_Chrom…

Not only was Safari always WebKit based, WebKit is Apple's browser engine (forked from KHTML and open sourced) that Chrome used to use until they forked it.

Post by rockdoe » Tue, Jun 30, 2015, 6:06 PM UTC

rescendent wrote: post #144

JoeAltmaier wrote: post #103

Earlier quoted context omitted.

WebRTC is not really new any more - a couple of years old (and existed in other forms long before), and still not widely adopted. In fact, not adopted in a single further browser in that time, and the original two are not compatible. I'm thinking, its almost time to consider WebRTC 'failure to achieve traction'?

New version is being worked on: https://www.w3.org/community/ortc/

Post by endemic » Tue, Jun 30, 2015, 6:08 PM UTC

Amezarak wrote: post #257

kedean wrote: post #227

Earlier quoted context omitted.

It doesn't need to be. MS in the late 90's dominated, and you could not do work with someone using MS products unless you also used MS products. One person having an iOS device and another having an Android device does not cause any issues between the two, they are fully able to communicate by the nature of cell phones. I would bet that the lawsuits against MS would not go through if they were brought up today (and,…

I can't tell you how many times I've had to help people who switched away from their iPhone and then saw eternal, intermittent issues with not receiving text messages because their friends iPhones were convinced they should be sending iMessages and not SMS. The situation gets even worse with group messages.

Post by rockdoe » Tue, Jun 30, 2015, 6:10 PM UTC

JoeAltmaier wrote: post #161

mmorris wrote: post #153

Earlier quoted context omitted.

Not an expert, but hopeful that WebRTC will be a success in the end. Maybe I'm just overly optimistic? > still not widely adopted Certainly everyone involved with WebRTC wishes that it had the support of IE and Safari, but Chrome + Firefox + Opera is nothing to sneeze at, particularly if you're targeting a savvy audience. > Original two are not compatible Maybe I'm confused, are you saying that Firefox and Chrome are…

All the important scalable features are incompatible - so-called 'bundling' where many streams use a single port etc. Aggregation of error feedback so an MCU can sensibly report bandwidth limits. Slow connect/reconnect times. No 'supernode' support. Pretty much anything that takes it from a toy with 3 or 4 p2p connections, to a product that can handle up to 100 streams with audio/video switching realtime through an M…

Post by rockdoe » Tue, Jun 30, 2015, 6:12 PM UTC

at-fates-hands wrote: post #121

mhomde wrote: post #113

Earlier quoted context omitted.

Yes, but before that IE fixed the web! :) Remember CSS on Netscape? IE4 was actually a beacon back in its day. Everything is cyclical: Lean - Average - Bloated - Lean - Average - Bloated

Are we currently in the bloated stage? - Chrome sucks up RAM like Photoshop. - Firefox Dev Edition is broken or slow every other build - IE is "ok"but their dev tools are incredibly sluggish and useless.