News for hackers. Stuff that matters.
Re:The Story Behind the New WordPress.com by pan69 on Monday November 23, 2015 @02:20PM (#10616605)
OK. So basically this is an Adobe Air-esque app that is a user interface to WordPress which at the moment only works on Mac.

I'm sorry but I don't really understand what the value proposition here is, maybe I missed it in the article? WordPress already has a pretty good user interface, which was build in HTML/CSS/Javascript.

When people complain about WordPress being an outdated architecture it's not the UI they're referring to..

Re:The Story Behind the New WordPress.com by rralian on Monday November 23, 2015 @02:43PM (#10616767)
There are two things here. WordPress.com has been rewritten as a SPA written in React, communicating with the back-end via REST-API. That codebase is now open source for anyone to review and hopefully learn some neat things about scaling a really big React application (or even better, teach us a few things). That codebase is here: https://github.com/Automattic/wp-calypso

Secondly, Automattic has also launched a desktop app (osx for now, but linux and windows forthcoming) that makes use of this new codebase... which is possible now because everything is now going through our REST API.

Re:The Story Behind the New WordPress.com by marcuskaz on Monday November 23, 2015 @02:51PM (#10616832)
The desktop app is using Electron, the same framework used by Atom, Slack and Visual Studio Code and others to bundle up a JavsScript app + Chromium to be a stand-alone desktop application.

The main benefit of this is speed having the entire app local it makes it really fast. As we continue to develop the app, we'll build in more desktop options and features.

Plus its easier to launch and switch to when its an app in your dock instead of just a tab in your browser.

Re:The Story Behind the New WordPress.com by criley2 on Monday November 23, 2015 @03:35PM (#10617126)
"Plus its easier to launch and switch to when its an app in your dock instead of just a tab in your browser."

If every website I visited refused to be in a tab and instead required its own place on my launcher... well, my desktop would be about as useless as my smartphone launcher. 100 applications spread across 8 separate pages, who knows what's open, annoying and time consuming to organize...

I really love tabs.

Are we really killing them now? Sucks to be anyone who isn't Facebook, because 98% of websites aren't going to make the "put it on the dock" cut, and will just be ignored.

Re:The Story Behind the New WordPress.com by coldtea on Monday November 23, 2015 @05:02PM (#10617654)
>If every website I visited refused to be in a tab and instead required its own place on my launcher... well, my desktop would be about as useless as my smartphone launcher.

Thank's god it's just ONE client for ONE specific app then. Which you can STILL use through a browser.

Re:The Story Behind the New WordPress.com by whoopdedo on Monday November 23, 2015 @04:09PM (#10617320)
Get mad at your desktop window manager, then. Tabs are a hack compensating for insufficient control of the workspace. Well, initially it was for saving memory. But we've since moved to executing tabs in their own process.

KWin used to allow title-bar level tabs but it didn't work in a lot of clients that expected to have complete control of the frame.

Re:The Story Behind the New WordPress.com by paulryanrogers on Tuesday November 24, 2015 @08:21AM (#10620501)
Actually I see tabs as a form of multiple document interface inside a single window. It's a valid approach to layering complexity as users multi task more. Excel sheets have worked this way for a long time.

Separate windows are not the only way.

Re:The Story Behind the New WordPress.com by rch on Monday November 23, 2015 @04:12PM (#10617342)
I used to really love least recently used tab lists, with alt-tab switching.

That's not available in Chrome without extensions, as far as I know anyway.

Re:The Story Behind the New WordPress.com by pknight on Monday November 23, 2015 @03:52PM (#10617216)
Are rich offline capabilities part of the roadmap? For a long time I've been wondering if there would be any benefits from the Simperium project flowing to WordPress.
Re:The Story Behind the New WordPress.com by rralian on Monday November 23, 2015 @05:09PM (#10617689)
Yes, definitely on our list and something we're excited about. We just didn't get there for this release.
Re:The Story Behind the New WordPress.com by pan69 on Monday November 23, 2015 @02:48PM (#10616807)
I understand the technical mumbo jumbo, my question is; what problem does this solve?
Re:The Story Behind the New WordPress.com by tjsix on Monday November 23, 2015 @02:55PM (#10616865)
"Our existing codebase and workflows had served us well, but ten years of legacy was beginning to seriously hinder us from building the modern, fast, and mobile-friendly experiences that our users expect." - Taken from the second paragraph of the article. The reasons behind the project are explained in more detail here: http://ma.tt/2015/11/dance-to-calypso/
Re:The Story Behind the New WordPress.com by jeffgolenski on Monday November 23, 2015 @02:25PM (#10616637)
The desktop app is currently only for Mac, but we're working on other platforms. WordPress.com, which is a very similar experience, is obviously web based and can be used in any browser on any platform. This entire upgrade utilizes the new WordPress rest API and the new WordPress.com is open source.
Re:The Story Behind the New WordPress.com by pan69 on Monday November 23, 2015 @02:39PM (#10616749)
Sorry, maybe my previous comment wasn't very clear, let me try again;

I don't understand what problem this project solves and whom it solves it for. We can already manage multi-site WordPress installations and usually that's done by site admins, not the average content Joe, so does it really need a super fancy new UI?

And what exactly does it mean when you say "WordPress.com is open source"? Maybe I'm out of the loop but the way I understand it is that wordpress.com is a hosted (commercial) service of wordpress.org.

My experience with WordPress is not that the UI is a problem at all, neither multi site management, which I think is in the scheme of things quite niche. The problem with WordPress I hear other developers complain about is the out dated PHP system architecture.

Re:The Story Behind the New WordPress.com by umurkontaci on Monday November 23, 2015 @02:52PM (#10616833)
It exactly means as you hear actually, WordPress.com, as we all know, was written in React, is now open-source.

In WordPress.com, "average content Joe", can manage multiple sites, including self-hosted WordPress.org sites (through JetPack plugin).

Disclosure: I'm one of the authors.

Re:The Story Behind the New WordPress.com by oldmanjay on Monday November 23, 2015 @03:33PM (#10617106)
That's a disclosure, not a disclaimer. Unless you intend to disavow the work.

Sorry, it's my pet peeve. Downvote away!

Re:The Story Behind the New WordPress.com by vineet on Monday November 23, 2015 @04:06PM (#10617297)
Don't you mean Wordpress.com was rewritten in React (and Node)?
Re:The Story Behind the New WordPress.com by coldtea on Monday November 23, 2015 @05:11PM (#10617698)
>I don't understand what problem this project solves and whom it solves it for.

Faster (through SPA techniques) admin UI.

>We can already manage multi-site WordPress installations and usually that's done by site admins, not the average content Joe, so does it really need a super fancy new UI?

Yes, since the current UI leaves a lot to be desired. And why keep it to "site admins" and not make it approachable by the "average content Joe"?

Besides "sites admin" in this context is just a fancy name for a person that needs to manage more than one Wordpress sites from the same UI -- it doesn't mean he's super-technical or that the UI shouldn't be made more approachable, faster and better.

Re:The Story Behind the New WordPress.com by rmccue on Monday November 23, 2015 @07:08PM (#10618259)
> This entire upgrade utilizes the new WordPress rest API and the new WordPress.com is open source.

To clarify: this uses the WordPress.com REST API, which has been around for a number of years, not the core REST API being integrated into WordPress (the software). Also, not all of WordPress.com is open source (i.e. you can't just clone down WP.com and run it), just the new interface. :)

Re:The Story Behind the New WordPress.com by nanoojaboo on Monday November 23, 2015 @02:51PM (#10616830)
what is the purpose of the desktop app?
Re:The Story Behind the New WordPress.com by coldtea on Monday November 23, 2015 @04:58PM (#10617622)
>So basically this is an Adobe Air-esque app that is a user interface to WordPress which at the moment only works on Mac.

Nope, it's a full web app -- if you mean the desktop client, that too. Adobe Air was Flash/AS based. And that's not a just a po-tay-to/po-tah-to distinction.

>I'm sorry but I don't really understand what the value proposition here is, maybe I missed it in the article?

Yeah, especially since it includes a full comparison matrix type chart with the benefits and changes from the new stack.

Re:The Story Behind the New WordPress.com by username223 on Tuesday November 24, 2015 @01:20AM (#10619409)
> Nope, it's a full web app -- if you mean the desktop client, that too. Adobe Air was Flash/AS based. And that's not a just a po-tay-to/po-tah-to distinction.

Either is a bag of shit sitting on my desk, whatever the consistency of the contents.

> Yeah, especially since it includes a full comparison matrix type chart with the benefits and changes from the new stack.

The "handy chart"? Or do you have something better in mind than that piece of typical meaningless marketing lip-flapping reformatted as a chart?

Re:The Story Behind the New WordPress.com by coldtea on Tuesday November 24, 2015 @02:42PM (#10623070)
Maybe take it to Reddit?