It is more developer friendly. The project structure is very clean, easy to configure and deploy. Using flat files instead of a SQL database might be limiting for some, but it's perfect for most standard sites like blogs, agency websites and even E-commerce. Twig for templates leads to cleaner code and a better separation of concern (Almost impossible to mix business logic in your templates). I guess the only downside is lack of plugins and templates for now. Guest • Jan 2018 • 1 agrees and 1 disagrees Disagree Agree
Video backgrounds and animations are no problems whatsoever. This website builder gets SEO right, too. Portfolio pages, in particular, turn out really good, and most importantly, without being difficult to create. They have many business-focused apps (e.g. for hotels or restaurants) that can make your life easier if you are in one of these industries.
I agree with you that Pulse CMS offers an interesting way to go, without databases. Before moving all my sites to WP over the past two years, I had always felt reluctant to use databases: but testing WP had convinced me to go ahead. Although I do not use it at this point (I played a little bit with previous versions), I bought a Pulse CMS license, if only in order to support that interesting project. I do not rule out using it for a site some day, at least experimentally.