Originally posted by ssokolow
View Post
Announcement
Collapse
No announcement yet.
Chrome Further Optimizes Its OpenH264 Encoder With More Assembly x86
Collapse
X
-
-
Originally posted by schmidtbag View PostUh... since when does 99% of the userbase do video encoding in their web browser, or use 3D accelerated web pages? The vast majority of people (particularly those who don't use Chrome) have or prefer an external PDF reader. You are heavily exaggerating how useless a browser would be by removing these niche or redundant features.Originally posted by Vistaus View Post
False. GNOME Web (formerly Epiphany) supports WebGL, has a built-in PDF reader and more while still being very lean. I've also had no problems loading websites, everything just works (with the exception of Outlook.com loading in some sort of lightweight mode, but that's easily solveable by changing Web's useragent to Chrome with dconf-editor). I'm using it for a long, long time now.
schmidtbag, just to name a couple of examples, Google Street View uses WebGL for rendering and tools like web.skype.com are already integrating support for WebRTC.
Vistaus, I don't even know what you think you're saying "False" to when Epiphany supporting WebGL and having a built in PDF reader supports my point.
Originally posted by schmidtbag View PostAlso, Firefox does not support built-in video encoding or PDF reader. As for Opera, the modern version is basically just a modified version of Chrome, so very often (but not always) whatever Chrome supports, Opera will eventually too. Anyway, that still doesn't detract from the fact that some of these features are unnecessary. Also, I just used those 3 as examples. There are others too.
Firefox includes PDF.js, which is about as native as the panel UIs for the WebExtensions API they're aggressively migrating to, and the bundled "OpenH264 Video Codec provided by Cisco Systems, Inc." plugin provides encoding and decoding in order to meet WebRTC requirements.
As for "unnecessary", I think we'll have to agree to disagree... especially for WebRTC. Most humans don't share our perspective and don't see text (even rich text) as an acceptable substitute for voice and/or video. The whole point of WebRTC was to remove the need for Flash to implement sites like YouTube and compete with proprietary offerings like Skype. (Since nobody else seems to be able to get "Just Works™" right in app form.)
- Likes 1
Comment
-
Originally posted by mulenmar View PostHey, web browser developers -- here's a shocking thought:
BROWSERS ARE NOT OPERATING SYSTEMS.
Quit making the browser do what the operating system already does -- GUI drawing, video encoding, or anything else. You're duplicating functionality.
- Likes 1
Comment
-
Originally posted by devius View Post
No they weren't... :\ That is, all modern browsers have the same capabilities (mostly) as older browsers, but newer ones have way more features and support a lot more standards.
- Likes 1
Comment
Comment