New Alliance Hopes To Standardize Web Plug-Ins
mksolutions writes "As reported on heise online and mozilla.org 'Apple, Macromedia, Opera and Sun Microsystems join in push to modernize plugins and create a richer web experience.' They are to develop a common, cross-platform plug-in interface which will be used in Mozilla products as well as Opera and Safari and will be released under an open source license."
Why are they scared of working towards a standardized future?
Maybe now there will finally be some of the missing plugins like Shockwave.
Not that I really want it, but my kids do.
Put identity in the browser.
Or is this only for browsers that are actually useful?
English Articles:2 004/06/30/2 004-06-30.ht ml
http://www.opera.com/pressreleases/en/
http://www.mozilla.org/press/mozilla-
"Apple, Macromedia, Opera and Sun Microsystems"
Spot the odd one out! I misread Macromedia as Mozilla for a second.
Notable by its absence I see. Macromedia obviously want to be in the mix, as they want everyone everywhere to use their lovely Flash and Director.
Sun is a puzzle in this, what do they have to gain? aaah the Java plugin. Well all sorted here, Opera want to pull in a little more weight, feeling the heat from FireFox I guess.
FireFox! Oh I do so kill myself.
#hostfile 0.0.0.0 primidi.com 0.0.0.0 www.primidi.com 0.0.0.0 radio.weblogs.com
I Hope that all browsers involved would allow me to point to my own plugin directory, so I don't have to have a different copy of the same file for each browser I use.
If this could be completed quickly, this would be a huge boon to consumers everywhere, making life much simpler for Joe Sixpack. It would be another step in commoditizing the underlying OS, and the web browser in a sense as well, as you don't have to worry about plug in support as long as it was a compliant browser.
And with CERT saying ditch IE, there's no better time than today to have this type of action. Unfortunately, it doesn't exist yet....
The cesspool just got a check and balance.
I think the internet's broken. That first link, heise online, it's in a whole other language.
I've already tried resetting the defaults on IE...
Can anyone help?
--
I uhm... write stuff, but not well, and not often
Does anyone know how the w3c fits into this?
Great! I, for one, welcome our new Punch The Monkey and Win 10,000 Banana Points overlords.
Har!
RTFA a bit more - Mozilla is pushing it, ah well this is all well and cushy!
:-)
The best part is that writing a plugin should now be easier. SVG plugin anyone?
Good work. Perhaps they will start sharing more code, after all, I only really want one good browser, not 5 alright ones!
#hostfile 0.0.0.0 primidi.com 0.0.0.0 www.primidi.com 0.0.0.0 radio.weblogs.com
Now, regardless of browser, everyone can have 10,372 smileys and valuable advertisements from Hotbar.
Don't reinvent Active-X with all its problems. Maybe browsers *don't* need standard, easy-to-install extensions (think BHO and ActiveX)
Best Buy can have you arrested
There is a difference between standardize and monopolize. You need to be alone to monopolize. Standards *are* good. As long as they are open and everybody can use them.
Slashdot anagrams to "Sad Sloth"
On the other hand, I expect that plugins will get even better once they have an audience beyond the standard Mozilla browsers. And I'm happy they're leaving out Microsoft. Let's finally put to rest that tired Internet Explorer!
...world for some time. There is a widely adopted "open" standard (VST-Virtual Studio Technology). They are not cross platform as they are native software, however I can load up one of a number of sequencers on Windows and use the same plugins.
:o)
There are competing plugin formats such as Direct X, but VST's seem to have the market pretty sewn up - there's even bindings for java
One the mac side of things Apple introduced AudioUnits which seem to be gaining popularity.
The great thing is, since developers no longer have to target a certain platform (i.e. only one sequencer family) you see a huge wealth of plugins available to be used on anything - hopefully we'll see that same kind of developer community flourish around rich-content plugins for the web.
I am NaN
...and release the plug-ins themselves (hear Flash) under an open source license.
.swf more or less an open standard?), at least, could they release their plug-in for other archs?
I'm not playing the open source fanatic here, but I'd really like them (*cough* macromedia *cough*) to realize that Linux is more than Red Hat.
Being a Gentoo PPC user, I still have no way to play flash on my iBook (well, I can boot it on OS X).
If really they want to protect their trade secrets (are there any? Isn't
Instant Karma's gonna get you, Gonna knock you right on the head (John Lennon, 1970)
Remember, your browser is only secure as the least secure plug-in.
What each of these groups needs is an IE ActiveX helper object that automatically downloads and installs their web browser on a visitors computer and then it should make their browser the default while removing "IE" icons from the desktop and start menu.
Whilst it's all very well for us "FireFox on Linux" users to gloat about our immunity from scumware; we must be aware that the developers of scumware only target IE _because_ it is the most prolific browser. The security weaknesses of IE are more likely the second reason.
Now if a critical mass of Internet users migrate to FF/Moz/Saf etc., scumware authors WILL target this shared extension architecture.
Now, it is all very well saying that the Mozilla platform may not allow drive-by installation (to the best of our knowledge); but remember that scumware is often installed through social engineering of the user. "This website requires Hyperviewing 3D Spatial Extension" (bundled with scumware for your convenience); and the user may click "Yes" to install without second thought.
How you go about allowing extension installation whilst maintaining a level of sanity needs carefull thought at this stage.
Ya, they finally got smart. Even though they're all smaller companies than Microsoft, their mindshare and market sway is probably as great together at least in industry circles. Hopefully this just accelerates the whole browser development cycle by letting developers know there's a consortium and there will be standards.
would Apple push for standardization of synchronization between bookmarks (a feature they will be including in Safari for Mac OS 10.4)? Cross-browser synchronization of bookmarks would be very handy for people who want to try more than one browser.
The only plugin that could be said to cater to an otherwise neglected niche is Flash. And hopefully with browsers natively supporting SVG, someday it's usefullness will wither, too.
Plugins are just excuses for Adobe Acrobat in the browser window bullshit. For all those fools that put up Word and PDF all over the place, get a clue already.
Of course, if successful, MS may want to "embrace and extend" here, but they should not be involved in the development, as the spec should not have to consider the special needs of IE as it's being developed.
I survived the Dick Cheney Presidency 7 to 9 AM 7-21-07
There is a Mozilla plug-in called Plugger which itself allows stand-alone programs to be used as plug-ins. This provides the desired feature of in-line viewing of formats not natively understood by Mozilla. But it also does another thing that other plug-in APIs misses, it seprates the stablity of the browser from the stablity of the Plugger'd viewer.
The Netscape plug-in, IE ActiveX and IE BHO APIs all allow the plug-in to crash the browser! Even worse, these APIs make it trival for Spyware to collect information including online banking username/passwords.
For the majority of plug-ins, all the plug-in functionality needed was a display system to provide their "window" in-line with the document. So, why then does plug-in APIs allow the program to run in-process with the browser?
I call it a "virus".
I don't want a "richer" web experience. Things already blink too much. Worse, plug-ins kill a normal standardization process. If there hadn't been any plug-ins, people would have been forced to standardize something like SVG much earlier instead of relying on Flash and similar systems.
Also, the problem with plug-ins is not their availability, it's version hell: you need to have the right constellation of library versions, operating system versions, and application versions. A plug-in standard usually still uses APIs other than those provided through the plug-in standard, so a standard won't change that.
Altogether, I think it's a bad idea. Let's get rid of plug-ins altogether and instead work towards better, universally implemented, open web standards.