One of the hardest things to do in technology is disrupt yourself.
But we’re trying our darndest, and have some cool news to introduce today. When I took on the responsibility of CEO of Automattic January of last year, we faced two huge problems: our growth was constrained by lack of capital, and the technological foundations of the past decade weren’t strong enough for the demands of next one.
The first has a relatively straightforward answer. We found some fantastic partners, agreed on a fair price, issued new equity in the company to raise $160M, and started investing in areas we felt were high potential, like this year’s WooCommerce acquisition. This “war chest” gives us a huge array of options, especially given our fairly flat burn rate — we don’t need to raise money again to keep the company going, and any capital we raise in the future will be purely discretionary. (Since last May when the round happened we’ve only spent $3M of the investment on opex.)
The second is much harder to address. The WordPress codebase is actually incredible in many ways — the result of many thousands of people collaborating over 13 years — but some of WordPress’ greatest strengths were also holding it back.
The WordPress codebase contains a sea of institutional knowledge and countless bug fixes. It handles hundreds of edge cases. Integrates constant security improvements. Is coded to scale. Development moves at a fast clip, with six major releases over the past two years and more around the corner. Its power and flexibility is undeniable: WordPress just passed a huge milestone, and now powers 25% of the web. You can run it on a $5-a-month web host, or scale it up to serve billions of pageviews on one of the largest sites on the web, WordPress.com.
The basic paradigms of wp-admin are largely the same as they were five years ago. Working within them had become limiting. The time seemed ripe for something new, something big… but if you’re going to break back compat, it needs to be for a really good reason. A 20x improvement, not a 2x. Most open source projects fade away rather than make evolutionary jumps.
So we asked ourselves a big question. What would we build if we were starting from scratch today, knowing all we’ve learned over the past 13 years of building WordPress? 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!).
- Incredibly fast. It’ll charm you.
- 100% API-powered. Those APIs are open, and now available to every developer in the world.
- A great place to read, allowing you to follow sites across the web (even if they’re not using WordPress).
- Social, with stats, likes, and notifications baked in.
- Fully responsive. Make it small and put it in your sidebar, or go full-screen.
- Really fun to write in, especially the drag-and-drop image uploads.
- Fully multi-site for advanced users, so you can manage hundreds of WordPresses from one place.
- Able to manage plugins and themes on Jetpack sites, including auto-upgrading them!
- 100% open source, with all future development happening in the open.
- Available for anyone to adapt to make their own, including building custom interfaces, distributions, or working with web services besides WordPress.com.
This is a beginning, not an ending. (1.0 is the loneliest.) Better things are yet to come, as all of you dig in. Check out these links to read more about Calypso from different perpsectives:
- Download the Mac desktop app, or sign up to be notified about Windows or Linux.
- Learn about Calypso from the developer’s point of view.
- See the user announcement on WordPress.com.
- Browse the GitHub repository.
- Hear about the backstory from Calypso’s lead, Andy Peatling.
This was a huge bet, incredibly risky, and difficult to execute, but it paid off. Like any disruption it is uncomfortable, and I’m sure will be controversial in some circles. What the team has accomplished in such a short time is amazing, and I’m incredibly proud of everyone who has contributed and will contribute in the future. This is the most exciting project I’ve been involved with in my career.
With core WordPress on the server and Calypso as a client I think we have a good chance to bring another 25% of the web onto open source, making the web a more open place, and people’s lives more free.
If you’re curious more about the before and after, what’s changed, here’s a chart:
124 replies on “Dance to Calypso”
[…] Calypso is available for download from WordPress.com now. You can also see the developer features, and see both WordPress.com’s announcement, as well as Matt’s. […]
[…] Great post from “The Boss” Matt Mullenweg from the main project we have been working on for what feels like, forever. You can read about it here. […]
Wow, this is exactly what I have been hoping would happen. Well done. Can’t wait to start digging into this.
[…] More details on the release can be found here. […]
[…] Matt Mullenweg mentions in his post, there’s still a lot of work left to do, “This is a beginning, not an ending. (1.0 is […]
[…] think Matt explains it best in his blog when he […]
Is Calypso tied to WP.com, or will it handle self-hosted .org as well?
You’ll need to install the Jetpack plugin in order to manage a self-hosted site through Calypso as it uses the WordPress.com REST API. The REST API that’s going into core doesn’t have all of the endpoints that’s required for it to work.
Do we have any way of knowing what the gaps are? Seems like we should be able to easily bridge the gap between core and what Calypso needs if the team released a “diff” of sorts on the endpoints.
Currently WordPress.com runs a completely custom REST API as it heavily predates the one going into WordPress core. We’ll be working to migrate over to using the WordPress core functionality in the future and when we do, it’ll be more straight-forward figuring out what’s custom.
However many features and endpoints are WordPress.com-specific such as paid upgrades for example.
Getting Calypso to talk directly to a WP.org install would likely not be easy, even after we switch REST APIs.
[…] Matt today officially announced the new WordPress.com: Dance to Calypso. […]
[…] details, and the official launch site presents the story of Calypso in beautiful form. Our CEO Matt wrote beautifully about Calypso and what it means to our […]
I can’t believe this! WordPress + React? GitHub? Awesome work guys. I’m going to install Calypso right now.
Good lord! This sounds fun and a little bit awesome.
Congratulations on the next big chapter of WordPress!
Pretty clever codename too (if you are referring to Calypso from Odyssey). I’m a sucker for Greek mythology…
Congratulations! And it is fast.
Wow! Exciting news. What a great move forward for WordPress. If Automattic continues down this path, with enough new plugins, perhaps WordPress might someday provide the critical mass to define common metadata standards to support a widely-adopted “social semantic desktop”?
See for example: http://semanticweb.org/wiki/Semantic_Desktop
From there (source text under the GFDL): “The Internet, electronic mail, and the Web have revolutionized the way we communicate and collaborate – their mass adoption is one of the major technological success stories of the 20th century. We all are now much more connected, and in turn face new resulting problems: information overload caused by insufficient support for information organization and collaboration. For example, sending a single file to a mailing list multiplies the cognitive processing effort of filtering and organizing this file times the number of recipients – leading to more and more of peoples’ time going into information filtering and information management activities. There is a need for smarter and more fine-grained computer support for personal and networked information that has to blend the boundaries between personal and group data, while simultaneously safeguarding privacy and establishing and deploying trust among collaborators. …
Furthermore we are in danger of resulting in many fragmented efforts, each of which will not reach critical mass and thus will not be able to penetrate the user space wide enough to result in mass adoption. …”
I’ve just shared this news with our dev team at The Next Web. We were about to start building our latest design iteration the week, but this changes things 🙂 If it’s up to me (lead designer with some proficiency in Node.js/Meteor and React) we’ll build our redesign on Calypso instead, and bid our adieus to PHP for good.
[…] Wow, WordPress not only revamped itself with current tech stuff but it's now open-source. https://ma.tt/2015/11/dance-to-calypso/ […]
WOW! This is all really exciting, WordPress now has a official take on Node.js, React and REST API. Thank you Matt for open sourcing it. I’m pretty sure developers will dig deep and try to contribute and create better UI/UX, at least I will :).
Typo: has an* official take
[…] Matt Mullenweg just introduced a new management interface for WordPress: […]
[…] just saw WordPress admin is now running on node/react/flux. That is pretty huge. I’ve downloaded their mac desktop app and I’m writing my first […]
[…] We’re proud to be able to open source all of the hard work we’ve put in, and to continue to build on the product in an open way. You can read more about opening up Calypso development on our CEO Matt Mullenweg’s site. […]
Wow 🙂 I just became a WordPress expert 😀
This is exciting news! Congrats! However, when I read the 11 items under “Calypso is”, I didn’t notice “accessible” as one of those awesome items. This troubles me, but I’m hoping to be troubled for absolutely no reason. After all, it’s being created in 2015, so I’m hoping that accessibility such as is laid out by the WCAG 2.0 guidelines are being followed? WordPress has done a lot in terms of your commitment to accessibility, and I hope that this commitment can be truly realized with a brand new code base and a fantastic lack of legacy to deal with. There are so many projects in which if accessibility were only considered at the beginning, millions more users could benefit and interact fully with them. I’m hoping that Calypso has a systemic commitment to accessibility and that the community won’t need to build accessibility on as an afterthought. This is really critical.
It’s not my area of expertise, but worst case using the new APIs an accessibility-focused client could be created, or even different ones for different use cases be it mobility or vision. The WP-admin is still there as well for fallback.
Definitely trying to prevent worst-case senario. The last thing needed is fragmentation in regard to accessibility. And yes, I’ve gotten involved. 🙂
I’m just giddy about this change. I think this is precisely the shot in the arm that was needed to move WordPress forward, and I hope that .org will follow the lead. Kudos to you and your team Matt. Really impressive.
[…] Mullenweg, CEO of WordPress announced today that it was time for something big, something new, something with codename Calypso. With more than […]
Amazing Matt. I love the part when you said ” A lot of people thought we should keep this proprietary, but throughout my life I’ve learned that the more you give away, the more you get back”
Thanks for the effort to make wordpress and web environtment better.
I’ve noticed the stats have changed between the new interface and the old one. Is that something that is yet to get attention or will it stay that way?
[…] Download the Mac desktop app Learn about Calypso from the developer’s point of view See the user announcement on WordPress.com Browse the GitHub repository Hear about the backstory from Calypso’s lead, Andy Peatling Matt Mullenweg’s announcement […]
[…] you noticed today release of WordPress Calypso. It is completely new administrative interface to WordPress (wp-admin). It is written in Node.JS […]
Why I think it is a smart step: http://www.ferschmann.cz/en/wordpress-and-node-js/
[…] (AQUÍ EL POST DE MULLENWEG EN SU BLOG OFICIÁL ) […]
You can still visit sites, this is just for the admin area.
Do you anticipate the future of themes and plugins turning from PHP to JS as well? I mean I realize this is more wp-admin and core but curious if you think it will all move that direction with time.
I don’t think the need is as urgent there.
Move it all to Node 😉 it will worth it
Well this sounds absolutely incredible. My team and I were only discussing the need in the ever evolving world of user experience the necessity to drive towards a more consistent API approach.
This will be getting the full dissection tomorrow and comes at a time where our digital marketing agency are about to start work on a game changing platform for local services here in Ireland.
Excited doesn’t quite cut it.
[…] What I didn’t know was that Matt would announce it as Calypso less than a month later. […]
[…] “在技术领域，最难的事就是颠覆你自己。”WordPress背后的公司Automattic的CEO Matt Mullenweg这样形容这次改版。 […]
[…] WordPress.comは、オープンソースブログ・CMSソフトウェアであるWordPress.orgをWebホスティングするレンタルブログサービス。同社のマット・マレンウェッグCEOによると、Webの25%以上でWordPressが使われているという。 […]
Calypso sounds great! Its a little bit ironic that you have to manage self hosted sites through jetpack though, since that plugin in particular was known for slowing your admin and site down.
That’s a misconception, there is a lot in Jetpack like Photon that actually makes your site faster.
Speed of JS has always fascinated me. But when it comes to SEO, I hold back and take the good old way.
Anyone has figured out how to solve SEO issue while creating a fast JS site using RestAPI? Solving this could truly open a lot of doors in WP theming/plugin scenario.
This is just for the admin, so the front end of the site is still served via PHP and totally accessible to search engines.
Google can now crawl Ajax sites as of October 2015: http://googlewebmastercentral.blogspot.co.uk/2015/10/deprecating-our-ajax-crawling-scheme.html
This is exciting! .. I’m going to install Calypso right now.
I think what I love best about the Calypso project is the incredible opportunity it’s going to provide for accessibility. Unfortunately, the accessibility efforts with WordPress.org got off to a late start, which has meant that we’ve been under a backlog of stuff along with new features. With Calypso, if the opportunity is seized upon, we don’t have to have that same problem. So congratulations on this Automattic.
Totally agree a fresh start is an opportunity and a fascinating challenge for accessibility too 🙂
[…] jste zaznamenali vydání WordPress Calypso. Jedná se o kompletně nové adminstrativní rozhraní pro WordPress (wp-admin). Je napsáno v […]
[…] את יתרונות המערכת ואת אופן השימוש בה, והנה פוסט של מאט מלנווג על הדרך שהובילה אותנו להקמת מערכת שונה כל כך ומה אנו […]
[…] alle novità grafiche, il sito divenuto (finalmente) responsive e più veloce, sicuramente la notizia impressionante è venuta da parte del CEO Matt Mullenweg, ed è quella di rilasciare Calypso (il nome in codice della nuova interfaccia di WordPress.com) […]
Sweet jesus. The day has come.
[…] Mullenweg, le PDG d’Automattic, la maison mère de WordPress.com, vient d’annoncer le lancement d’un nouvel outil d’administration pour le système de gestion de contenu […]
[…] સાથ નિભાવ્યો છે. તાજેતરમાં તેના સીઇઓએ નવી સિસ્ટમની જાહેરાત કરી અને વર્ડપ્રેસ.કોમમાં […]
[…] engine behind one out of every four Web sites, rolled out a new editor last week. It was part of a complete rewrite of all of WordPress.com. Their old technologies just couldn’t stretch to where the world was moving. So they threw […]
[…] Yesterday, we lived by that line. I am super proud to share that the code that my friends and colleagues have been working so hard on these past 20 months was released to the world yesterday: the code is now Open Source, and you can find it right here. As our CEO Matt Mullenweg said in his announcement post: […]
[…] Many reports are circulating that WordPress is now completely free of it’s legacy with the Calypso Project. But even Matt Mullenweg, the technical minded founder is carefully missing the words PHP and MySQL in his blog post: […]
[…] Web’in yüzde 25’ini tek başına omuzlayan WordPress‘in blog servisi WordPress.com baştan sona yenilendi. 13 yıllık geliştirmenin ardından geçtiğimiz yıldan itibaren Calypso kod adıyla başlanan WordPress.com’u sıfırdan tasarlama projesiyle gelen ilk ve büyük değişiklikleri, Automattic’in kurucusu ve CEO’su Matt Mullenweng, 23 Kasım’da kendi blogundan duyurdu. […]
[…] Today I downloaded this WordPress Desktop Application on my MacBook Pro and started using it. As soon as I saw the initial screen I understood that this is the same inteface that we all have seen on WordPress.com to manage all our sites from a single page website. Also the WordPress application for Android / iOS and Windows works on the same framework. I liked the MAC version and I am using it, in fact I am writing this post using this WordPress Desktop Application. If you are interested in knowing more about the framework which is open source and developed by Automattic, check this post by Matt. […]
Matt – I understand that Calypso is used in WordPress iOS App?
Nope, but the design in the template for it, but the iOS app is fully native code.
[…] Lastly, the announcement on Matt’s blog has been “interestingly” worded. Why do I say that? Because my Twitter timeline has […]
Looking forward to it.
[…] Read his post, too (here). […]
Congratulations! I am so impressed. This is huge step for WordPress and the future of developing web, publishing content and sharing knowledge. Love that you’re first-moving on new technologies like React. Great choice, by the way. You are setting a great example.
[…] 18 months of work, built on a completely new tech stack, and an example of how big of a job it is to reinvent yourself when you’re in the middle of running a service for millions of […]
Thank you so much. Drag and drop images! This is great.
[…] now powering 25% of the web, this really is huge news. The move has taken place as part of Project Calypso, which is now available as open source code – all the better for nurturing more extensive […]
While conceptually I applaud Calypso as a huge advance for WordPress, as far as underlying technological choices, one big reason I chose Mithril over React for a big project was Facebook’s overly-broad patent termination policy for React. Hopefully Automattic has reviewed that policy in detail and fully assessed the legal risks to Automattic and the WordPress community versus technical benefits of using React in Calypso versus other workable technical alternatives like Mithril? If picking React was not a fully-informed choice accepting a substantial theoretical long-term legal risk in exchange for short-term practical benefits or various community momentum effects, I’d suggest starting to convert Calypso from React to Mithril (or a similar system) *today*. Switching the codebase to TypeScript 1.6+ first might facilitate that refactoring.
==== Ironic consequence
I tried to post a longer version of this and it did not go through, probably because of too many supporting links. You can see that version there:
Feel free to delete the long version I posted here previously which may well be awaiting moderation and is essentially identical to that issue.
Ironically, immediately after posting that issue to GitHub about patent risks of Facebook and React cutting off free speech about patents on the internet, GitHub decide I was not human and has now hidden my profile. 🙁 This also hides all the free software I’ve developed and published on GitHub. 🙁 That may well in practice ruin my career etc. unless GitHub decides to reinstate my profile. 🙁 I asked nicely just now, so I can be hopeful. 🙂 I guess it’s really true that no good deed goes unpunished — but I guess you still have to do them anyway. 🙂 And what kind of good career could it be if I foolishly let it become dependent on one centralized service like GitHub? 🙂
Anyway, that issue will not be available for viewing by others unless GitHub decides to reinstate my profile.
Thankfully, Andrew at GitHub has decided to reinstate my profile. Whew. 🙂 So that link mentioned above is now working for others who are interested in Facebook-scale licensing issue and React vs. Mithril. It was obviously disconcerting to see years of work disappear in terms of telling people to go to some place to get code or talk about it. That experience is something to reflect further on for everyone — how easy it is for a big centralized service you’ve become dependent on to suddenly cut you off or disappear (whether it folds for business reasons or for legal reasons like patents, or whether it cuts you off because of something you said that a spam-detecting robot did not like). Decentralization is one reason I like WordPress so much over, say, Facebook or Google+. Even when hosting at WordPress.com, you can move the site to other hosting and it will look pretty much the same (well, with some needed plugins perhaps). WordPress.com will even help you do that (for a fee). You can’t do that with Facebook, Google+, or even GitHub.
For example, months ago I asked GitHub why I could not get copies of issues or posts that I had made emailed to me as notifications as I created them. They did not have much of an answer for me. Their position seems to be that the current system only “notifies” you about changes you did not make (because any change you made you already know about, so their is no point in “notifying” you about it). Which conveniently contributes to vendor lock in as well, since it is not easily possible to have a full record of a GitHub project maintained as changes are made — unlike, say, WordPress where you can be asked to be emailed about all changes to a site. (Although it is true you can manually download web pages from GitHub with issues.) I did choose to use GitHub issues for one project, but I can wonder if that will ultimately turn out to be a mistake, as like above, when the whole thing just disappears and I don’t have a complete record of all issues? As Mr. Rogers sings: “What do you do with the mad that you feel?” That is true even when you feel mad with yourself about some dumb decision you made out of convenience without enough forethought… 🙂
To link this back to the Calypso project, imagine something like GitHub but running as decentralized social semantic desktop software under Calypso where you could easily move the entire project from one hosting provide to another, issues and all. 🙂 And maybe with just a little Domain Name System (DNS) magic similar to moving web hosting providers. To me, that is the ultimate potential of something like Calypso when considered broadly — to make all sorts of sophisticated collaborative software easier to write and maintain.
Paul, as an attorney and a WordPress developer, I mostly agree with your assessment.
Using react.js leaves WordPress seriously vulnerable to Facebook. It’s not unfathomable that Facebook can shut down WordPress should there be any legal dispute in the future.
However, I am quite certain that WordPress legal team has reviewed the legal ramification of using react.js and decided to proceed after determining that such a risk is too remote not to use react.js.
But…no PC version? Why?
It’s around the corner!
It looks like your profile has now been reinstated. Did they explain what happened?
Thanks for asking, Chris. Andrew at GitHub had written back to me with: “Sorry about that! Sometimes our spam-detecting robots get a little overzealous and need to be reprogrammed. I’ve reset your profile, so your repositories and gists should be available again, and you shouldn’t see that message anymore.”
So, that’s all I know.
I wrote more just now about the issue, how it made me feel, and how it might relate to future Calypso innovations (as the desktop and the web blur together and as public keys perhaps get used as IDs for modding posters up and down). That essay can be found at the following link on my own website:
I wrote the new content here at first, but decided not to post it so as not to bog down Matt’s blog with another long comment by me and otherwise distract more from an amazing new product like Calypso. In general, real life discussions tend to meander, and it would be good to have better tools on the web for following discussion themes without having to otherwise limit side discussions. Too bad there is not an easy way to mark content as “tangential” on a WordPress blog — probably some WordPress plugin for that perhaps though? Or maybe Calypso might have one soon? 🙂
[…] (Source) […]
I’ve not been able to find any documentation on how plugins might be created for Calypso. Ideas?
There isn’t a framework for it yet, it’s something we’ll have to figure out.
[…] https://ma.tt/2015/11/dance-to-calypso/ […]
[…] millones de líneas de código y un enorme trabajo por parte de decenas de programadores, ayer se anunciaba la versión pública de Calypso, la nueva interfaz de WordPress.com, y quizás mucho […]
[…] I am inspired because, in the face of so many trying to stay afloat and sometimes even willing to sacrifice what they stand for in order to optimize profits, WordPress.com takes the risk of changing everything for the sake of freedom. […]
[…] Matt Mullenweg: […]
I would be more excited if the backend was also changing – still, it’s great news 🙂
[…] reaction to yesterday’s Calypso announcement has really blown me away.Here’s a tiny selection of of the coverage, analysis, and reactions […]
This is an awesome news! I have dreamed for a long time for the GIT support in WordPress, and you guys give a lot more by bringing node and react as well. This is a big big big milestone and I believe it can work!
You mentioned in your post re figuring out plugins etc.
I built this little JS Hook System a while ago. It works like the WP hook system. Might be useful.
And keep up the good work. Looking forward to this coming to core!
[…] lo cuenta de la siguiente manera: una de las cosas más difíciles en tecnología es hacer productos disruptivos contra ti mismo, aunque sea fundamental para sobrevivir. A nivel negocio, un cambio de este calado promete […]
I thought this was great until I heard that they’re ditching MySQL and using an api route instead. I’d like to see WordPress powered by Node using MySQL or flat file JSON
[…] ۳ آذر ۹۴): امروز خبری جالبی خواندم: انتشار Calypso که نسخه Desktop وردپرس برای سیستم عامل Mac است. این نسخه ۱۰۰% […]
[…] Matt Mullenweg founded Automattic, a company that offered commercial WordPress services. In a blog post by Matt Mullenweg, he mentioned how the most difficult thing to do in technology is to disrupt […]
[…] Read more. […]
Supporting Markdown in the native Mac app – nice. Thanks for that (although there still seems to be a little problem with the preview).
[…] I was scrolling through Twitter, and came across Matt’s post on the new WordPress.com. I logged in, expecting a completely unusable mess in regard to screen readers. And I was very […]
[…] just it…according to Matt Mullenweg, it is. Dance to Calypso | Matt Mullenweg Mind you, this is part of the reason I say that they've done a horrible job of explaining what it […]
[…] new development related to all these thoughts about content management systems for actual writing: WordPress is doing something lots of people are doing, moving to fancy modern node.js frameworks for…, not just for what I would usually call reader-facing […]
[…] explica Matt en su blog, Calypso nace después de 20 meses de trabajo muy duro con la intención de hacer algo nuevo […]
[…] Matt Mullenweg makes it clearer. […]
[…] “Dance to Calypso . Calypso, 24 Hours Later […]
[…] Dance to Calypso Matt Mullenweg, the creator of WordPress and CEO auf Automattic (that runs WordPress.com), writes about how WordPress.com is being reinvented and about the risks that come with such a move. […]
Is “Calypso” named after the goddess? or the music?
[…] was pretty exciting for the WordPress community: Matt Mullenweg, the CEO of Automattic, introduced Calypso, a project they’ve been working on for the past 20 […]
[…] Dance to Calypso […]
This is great news! I was building the same thing using React/REST API, pointless now 🙂 Can’t wait to play with/extend it.
Wow! This is a revolution… React is awesome. But am also so happy that PHP is still going to be used for the front-end and theme development… But yet I’m concerned is it going to fade away as time goes on or PHP is still going to stay?
PHP is great for some things, not for others.
Any idea when the PC version will be out?
We’re working on it.
[…] “A lot of people thought we should keep this proprietary, but throughout my life I’ve learned that the more you give away, the more you get back,” Mullenweg said in his announcement. […]
[…] “front-end”, as the Calypso– is just one way of doing it. It could be done differently, and I assume Matt wants to see […]
@Matt, nice news bud but you got a lot of devs confused a bit. We are themes/plugins developers that work with multiple theme frameworks ( about 11k of us in 2 major GPL theme frameworks ) and we are all kinda guessing what this means to us.
Learning is not an issue but preparing for new way of doing things is, since we all are currently working on WP projects as we speak.
I did see Wendy asking you something along these lines http://prntscr.com/99iaug
but let us ask you direct questions so that we can continue the projects.
The questions are :
1) Are you planing to drop WP PHP completely and if when ? ( eta if possible )
2) Can we continue standard WP themes and plugins development or should we take a brake and learn new way of doing things ?
3) Is standalone WP going to be affected by Calypso ?
Hope you can find time to answered these. You can tell that we need more info so please try to direct us as much as possible so that we can focus on further development.
Thank you and keep up the great work!
1. PHP still makes a lot of sense for the server side of WordPress, to power the API.
2. Themes and front-end display of a blog are also still PHP, and there are no plans to change that currently. But plugins will need to evolve to be API-driven.
3. Today you can manage and publish to your standalone WP sites from Calypso, including auto-upgrading plugins. If Calypso is successful, I could see the core wp-admin interface taking a similar technical direction in the future.
Thnx for the reply. This clear up the confusion.
[…] was a huge decision. I applaud it for many of the same reasons that Matt Mullenweg lists out in his announcement: SPAs, once loaded, provide a speedier user experience that’s usually much easier to model and […]