4 ms·
I'm not really a fan of having a second source of truth compared to in depth material already on php.net. The two will invariably start to disagree and php.net
by lnanek2 12y ago
I'm not really a fan of having a second source of truth compared to in depth material already on php.net. The two will invariably start to disagree and php.net is much, much better than any spec or documentation I have ever read. Using Android is a nightmare compared to php.net because every single thing on php.net has extensive user generated documentation whereas Android is just some broken official docs. I submitted a bug report with a fix for the Android docs telling people to make dialogs in a way that simply crashed and didn't work and it was never merged in for years and years. So official specs tend to suck.
- Zelphyr 12y agoI think a spec benefits language implementors more than it does every-day users. Sure, it will influence things in every-day PHP programming but ultimately I think the target audience is different. Think of it as what the ECMA spec is to the Node.js API docs. Rarely does a user writing JS code using Node need to reference the ECMA spec (though they should by all means be familiar with it!) but they almost certainly have the API docs bookmarked.
- krallja 12y agoThe ECMAScript spec might be a bad example, simply because Annotated ES5 is so good. http://es5.github.io/ http://es5.github.io/