Apple, Microsoft, Google, Others Join Hands To Form WebPlatform.org
hypnosec writes "Apple, Adobe, Google, HP, Microsoft and many others have joined forces and launched a new resource – the Web Platform in a bid to create a 'definitive resource' for all open Web technologies. The companies have come together to provide developers with a single source of all the latest information about HTML5, CSS3, WebGL, SVG and other Web standards. The platform will also offer tips and best practices on web development as well as web technologies. 'We are an open community of developers building resources for a better web, regardless of brand, browser or platform,' notes the WebPlatform site."
I'll believe that when I see their products running under Free or Open BSD. Unless "any" is really a very narrow definition of specific Linux Distros, MS Windows, and OS X.
So its basically an alpha reimplementation of w3schools?
http://www.w3schools.com/
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
Surely to get those companies together, there must be some nefarious agenda afoot.
What political party do you join when you don't like Bible-thumpers *or* hippies?
i was talking features, not design. this thing is missing stuff http://docs.webplatform.org/wiki/tutorials/optimizing_css http://docs.webplatform.org/wiki/tutorials/css_transforms
Really? A brand new website is not as comprehensive as one that has been around for 13 years? Shocking!!
Actually, get ready! it's going to be web 3.0! That means it'll be incompatible with web 2.0.
Except with any luck unlike w3schools it won't have incorrect information on it because people will be able to fix it like any other wiki.
The big problem with w3schools is that there's all sorts of mistakes on there and they won't fix things if you point out the problems.
what's _really_ shocking is that a brand new website which promises to be COMPLETE AND FULL REFERENCE of platform X, a website not done by AMATEURS but by the biggest companies around with hundreds of billion of dollars available in their pockets, goes live incomplete and unfinished.
On the bottom of the front page are 9 logos, Apple is not one of them. On the Stewards page are 10 organisations/companies, including Apple. But Apple is the only one without a link to a description/statement of the company. They seem to be the neglected stepchild here?
And Slasdot puts them first in the title, and categorizes the article in the Apple section :-)
No, that's pretty unshocking. Documentation takes time to write. It'll get more comprehensive with time.
I can't tell whether it's malice or incompetence. Is it likely that the developers of web browsers bundled with operating systems are leaving certain APIs unimplemented on purpose to encourage the development of OS-specific native apps? I'm talking about SNI, HTML5 offline manifests (with a quota suitable for video), HTML5 local storage (also with a quota suitable for video), WebGL, the video element with the WebM codec, the file API, and getUserMedia. Web apps won't replace native apps until web developers can rely on most of these.
what's _really_ shocking is that a brand new website [...] done [...] by the biggest companies around with hundreds of billion of dollars available in their pockets, goes live incomplete and unfinished.
Not shocking. Google is part of this effort, and it's the poster child for taking a "beta" version live and tweaking it later.
(this time not posted as AC, so it shows up ... )
"Apple, Adobe, Google, HP, Microsoft and many others have joined forces and launched a new resource – the Web Platform in a bid to create a 'definitive resource' for all open Web technologies"
That's awesome, because without explicit corporate collusion, we'd never have ... a ... what? a search engine for referencing 'open' technologies?
Not that they haven't contributed (some more than others) to open source projects, but ... why exactly do we need the corporate technical powerhouses to create a definitive resource on open technologies? What will they provide by corporate committee that open source isn't providing now? ... or is this one of those redefinitions of 'open' that hasn't got anything to do with open source?
Underline the damn links (which are one of the main reasons why the web was invented). Undecorated links, using a color which is very close to the normal text color, makes them indistinguishible from normal text for even lightly color-blind people like me, and like 10% of the male population.
I would think that the big box at the main Docs page explaining that the docs subsite was in alpha would have, you know, explained that.
Funny that you dropped the "web" out of open web technologies. The reason they are important is because they are the main implementors of the open web technologies at issue.
The intent is to provide quality documentation, not implementations. In many cases, the implementations are provided as open source (in some cases, by the same companies involved in this project for informational resources related to the technologies.)
It has nothing to do with open source, but its not a redefinition, either. "Open" in "open web technologies" is used to mean "open specification" rather than "open source", which is a fairly common existing use, not a "redefinition."
Not that they haven't contributed (some more than others) to open source projects, but ... why exactly do we need the corporate technical powerhouses to create a definitive resource on open technologies?
Because together those companies create much of the software and hardware that is interpreting open web protocols and formats. This is hopefully a step towards recognizing that proprietary technologies that only work on one vendor's platform are detrimental rather than beneficial for lock in. Maybe the next time you notice browser C is interpreting that HTML tag differently than everyone else there will be a place to point to that the maker of browser C has their name up as a collaborator.
What he said. Holy crap...
Need Mercedes parts ?
I seriously question the web expertise of anyone who snubs w3schools as a "terrible", "painful" resource for web development. If you are looking for a copy-paste reference of best practices, w3schools isn't it. Nor is w3schools.com a definitive guide. However, there isn't a resource that is more user-friendly than w3schools on many of the web topics.
http://www.w3schools.com/jsref/obj_location.asp V https://developer.mozilla.org/en-US/docs/DOM/window.location
Moreover, w3schools.com does a fantastic job in maintaining the big picture of web development by separating its components in its reference pages; DOM, JavaScript, CSS, HTML, etc..
Anyone stating otherwise is full of it. The tutorials, layout, and "Try it Out' execution environment are quick and fantastic for those not interested in reading a blog. 95% of the reference needed w3schools.com has. The other 5%, as a seasoned web developer you should see blog entries, quirksmode, msdn, mdn, etc. and/or investigate in an execution environment such as firebug.
The subtle nuances, nit-picky details, over-simplification, or the lack of mention of say "getBoundingClientRect" doesn't invalidate the awesomeness of w3schools, and it certainly doesn't make it suck. Mastering a topic shouldn't turn you into a snob.
I strongly recommend w3schools.com to anyone who wants to get a good grasp of web development without diving into the advanced topics or anyone who wants a quick reference look up.
Just my two cents!
www.w3schools.com/js/js_popup.asp. alert() and confirm() dialogs with no explanation that they should generally be avoided. Also no discussion of console.log() for debugging purposes.
Hmmm, lets see...
1. Snub w3schools for not diving into advanced topics as to not overwhelm newcomers.
2. Not acknowledge the cases where alert and confirm dialogs are sufficient solutions.
3. Criticize w3schools.com for lack of giving explanation while you yourself don't give an explanation.
4. Advocating the use of console.log while knowing that console object isn't supported by all browsers.
We have 100 documentation sites on client side web technologies. Hey, let's try to merge them all into one single authoritative site.
We have 101 documentation sites on client side web technologies.