4 ms·
I'm not sure why the title is referring to Calypso as "experimental." It's the production codebase.
by rralian 11y ago
I'm not sure why the title is referring to Calypso as "experimental." It's the production codebase.
- dang 11y agoGiven that the submitted title ("Experimental WordPress Calypso Written Purely in JavaScript") broke the HN guidelines, we just reverted it to the article title. Submitters: the HN guidelines ask you to use the original title unless it is misleading or linkbait. If you want to say what you think is important about a story, don't do so by rewriting the title—editorializing is against the rules here. Instead, add a comment to the thread, on a level playing field with other commenters.
- lloydde 11y agoSorry, my mistake. WordPress co-founder Matt Mullenweg on his own site describes it more as the project and the "experiment" behind it. My understanding is this can be used as an interface to all WordPress blogs. My take is that although this is acting through WordPress.com as an API intermediary, it is only steps away from peeling out the whole PHP layer for these interfaces. WordPress co-founder Matt Mullenweg described it as: > At the beginning of last year, we decided to start experimenting and see. > Today we’re announcing something brand new, a new approach to WordPress, and open sourcing the code behind it. The project, codenamed Calypso, is the culmination of more than 20 months of work by dozens of the most talented engineers and designers I’ve had the pleasure of working with (127 contributors with over 26,000 commits!). https://github.com/Automattic/wp-calypso https://github.com/Automattic/wp-calypso
- rralian 11y agoNo worries. I just wanted to make it clear this is not a toe in the water. :-) > My understanding is this can be used as an interface to all WordPress blogs. Yes, that's correct. It works for WordPress.com blogs of course. But self-hosted blogs can also make use of Calypso by installing our Jetpack plugin (https://wordpress.org/plugins/jetpack/ https://wordpress.org/plugins/jetpack/) which adds some API endpoints that allow Calypso to communicate with the self-hosted site. > it is only steps away from peeling out the whole PHP layer for these interfaces I don't think I would go that far exactly. The php codebase is still there, and users can still use "wp-admin" if they prefer. And the API is also powered by PHP. But now that Calypso only communicates with a site through the API it allows us to separate the view logic and focus on making those endpoints as efficient as possible. I think it's possible the API could be written in a language other than PHP. But that hasn't happened yet and would be a significant task. I should probably mention I am one of the authors, if that wasn't obvious. :-)
- rralian 11y agoOh yeah, there's also the whole "every page a reader sees" on the front-end of the site.
- lloydde 11y ago> We still have a ton to figure out around plugins, extensibility, contributions, Windows and Linux releases, API speed, localization, and harmonizing the WordPress.com API and WP-API so it can work with core WordPress. Thousands more PHP developers will need to become fluent with JavaScript to recreate their admin interfaces in this fashion. I'm also really excited to revisit and redesign many more screens now that we have this first version out the door. http://ma.tt/2015/11/dance-to-calypso/ http://ma.tt/2015/11/dance-to-calypso/