What is Boomla?

To give you an idea:

  • Generally speaking, Boomla solves the same problem as Content Management Systems do, but in a very different way.
  • Boomla is a platform for building websites.
  • You can program Boomla in sync Javascript (no async callback hell).
  • The entire platform is transactional, like the Web, unlike Linux.
  • Forget the LAMP + WordPress stack, Boomla is a replacement for all of it. Just sign up and go.
  • Boomla comes with built-in version control: enjoy undo; access branches on subdomains like branch.example.com. (No, it is not built on Git, but it’s similar.)
  • Boomla is object oriented. Objects and classes are files and file types in Boomla.
  • Everything is a file.

Why?

  • Simplicity. Both for end-users and developers.
  • Linux was never designed as a platform for a concurrent environment, which the Web is.
  • Encapsulation is a huge problem on the Web. CSS files and assets directories are a mess.
  • You have to deal with lots of legacy. 3 users (Linux, DB, CMS), 3 kinds of access control, 2 totally different data stores (DB, FS). Not in Boomla.
  • The LAMP stack is a stack, not a platform. Because your website has external dependencies, version controlling it is extremely complex (eg. PHP extensions are not part of your website’s codebase).

Ideal user?

In the short term:

  • non-technical users, who just want a simple website,
  • less experienced web developers who want gain powers faster,
  • JavaScript developers who need a sane CMS alternative,
  • hardcore developers who want to play with crazy new tech.