Matt Mullenweg makes it clearer.
Calypso is a new js-based, single-app. admin application that talks to the standard WP back-end via its ReST API. And it’s open-sourced.
Brunet thinks it’s not going to affect free WP users. Maybe.
What would, I think, be a radical move, would be to recreate the PHP model with node.js.
Did WordPress just translate itself to node.js?
Big question, will they also open-source this code-base for users to host on their own sites? If so, this is probably the beginning of the end for PHP? WP is certainly the only PHP application I run. And probably the most widely used PHP program in the wild. (Not counting FB here.)
If they aren’t going to open-source it, is this the beginning of the end for WordPress as the world’s most popular Open Source social-software? Is WordPress.com going to try to turn itself into a more closed, “gated” community? With new features only available to users hosting within it? Is it going to become more like Tumblr … or Medium or even FB?
Update : It’s all open-sourced.
Deciphering Glyph : Your Text Editor Is Malware
Worth a listen : Podcast: What’s going on behind the scenes at Scripting News
Interesting to go back to Stevey’s Blog Rant from 2006.
Quite perceptive … the ascendent Lisps today, at least the ones that have caught my attention, are Clojure and Racket. Neither of which really existed at the time he was writing (although Racket’s ancestor, Dr. Scheme did). Both of which do, indeed, have offered a layer of practicality and accessibility that perhaps other Lisps of the time lacked.
Here’s a thought. Wouldn’t it be awesome if editors / environments that could open multiple windows / tabs could have a “stack” semantics for it.
I mean in browsers, the terminal application etc. It would be great when I have something new to do to be able to open a new environment / tab to do the new thing, have it replace the existing one (rather than have 20 open at the same time) but when I finish, be able to fall back to the previous state / history etc.
Actually, maybe this is more or less how screen works. Still it would be useful in other places, eg. the browser.
This blog is now cleaned of infection and back online.
Still working through other applications on my server.
Some of my websites seem to be under attack at the moment. Or rather, WordPress hosting is infected by some kind of PHP virus.
So, I’m in the process of containing and fixing the issues. First I’m using the extremely useful HTTrack to make flat copies and swap the live-sites for these.
In fact, I’m using too many WordPress sites for small static sites. Time to move them to Project GeekWeaver.
Then, I’ll be exporting the databases of the bloggier blogs and either creating fresh new WordPress installs or looking into alternatives.
So for a while, this blog, and other of my self-hosted blogs will be going fairly static.
Don’t worry though, I’ll be back soon.