232 karma · joined August 21, 2012
But yes, they came aboard with the LearnBoost / CloudUp acquisition nearly almost two years ago.
A lot of devs -- both pre-hire background and post-hire focus -- have little or nothing to do with the WordPress back-end.
I'm the team lead of the Jetpack plugin for WordPress. I've passed it upstream to our in-house counsel just for a cursory review should it conflict with trademark scope or something.
(What do I know, I'm a dev, not one of those lawyer-types)
(But as the Mozilla Jetpack thing existed before we did, and we both coexist, I'm not expecting a kerfluffle, but who knows -- I am not a Lawyer!)
> There are a million plugins available that extend your site’s functionality, but each plugin increases your security risk and your maintenance overhead.
but with LocomotiveCMS
> Since LocomotiveCMS is built on Ruby on Rails, you get tons of power without having to rely on a bunch of plugins that can compromise the security of your site.
So, what, is that saying that LocomotiveCMS doesn't have a plugin architecture for porting in additional functionality? Or is it just hubris to the point of saying all extensions are naturally more secure? Or that users would never need to install plugins, because LocoCMS has lots of features already? 'cuz, y'know, WordPress has lots of features too.
Plus:
> [In WordPress, to] make many site changes, you have to download a copy of the database and the entire content folder back to your local installation.
Nope. That's just factually wrong.
> [In WordPress] some assets are stored in a database, and others are in templates or additional places.
... no? Content and configuration is stored in the database, templates and assets are in files. Really wondering wtf they're talking about here.
> And forget about trying to make those custom types relate to each other without significant code slinging.
Nope. Easy plugin. No code slinging required. https://wordpress.org/plugins/posts-to-posts/
> While WordPress has multi-site capability, you often run into compatibility issues that can hamstring the production of your sites.
Really? Like ... what? The only things I've ever seen break in multisite was when the developer was doing things incorrectly, trying to hack one thing into another without understanding the system they were working in.
> If you've worked with WordPress, you already know what we're talking about.
I've worked with WordPress for six plus years now, and have no idea what you're talking about.
I'd fully support their modules that connect to the cloud servers being open source / GPL / etc, but to expect them to open them up to unauthenticated requests is untenable and leaves them way open to abuse / lack of rate limiting / making the service a bad time for all involved.