Ask HN: What are you working on this year?

- User authentication & authorization - Background worker & scheduler - Roles & permissions management - Pre built UI layouts and themes

https://github.com/tarunvelli/rails-tabler-starter

Think about email. Your emails aren't on everyone's devices. They're just on your devices. If you go offline, you can still read and reply to emails. But the emails you send won't actually get sent until you go online again. Its like that; but instead of sending messages back and forth, you can edit things and the changes you make get synced while you're online.

You would think that 20+ years in Python and PHP would make any modern framework a breeze. Not so for an Adobe product! (yes, I know that Adobe purchased the framework, but did not develop it... I suspect that the purchase appeal was the developer "experience")

Apparently PHP is just too hard to use, so to make customization possible by content managers without needed a PHP developer, Magento employs an XML config system. Because XML is so much easier to use, right? Because there exist easy to use XML tools that warn of misconfigurations, bad syntax, typos in element names, typos in attribute names, typos in attribute values, and typos in tag values. Because content managers can safely SSH into the server to recompile the entire XML config from a CLI. Because content managers can read the docs - not that there are much in practice anyway - and understand how to configure the XML. Because content managers can grep and sed and perl and awk and sort their way to finding what depends on what. Because content managers understand when a namespace needs a leading backslash, and when a leading backslash is forbidden, and case sensitivity, and the difference between an underscore and a dash and a space and a   and whatever nonprinting unicode character they managed to copy off Raj's blog post. Because content managers understand that config relevant to Magento 1 is not relevant Magento 2 (which share only name and logo) so that needs to be checked _before_ you put that in the live config and recompile while users are trying to browse the site. Because content managers understand that _this_ element needs CamelCase, but the same string must be snake_case when used in that attribute over there.

Don't get me started on the PHP aspects of Magento! Or the Magento ORM. Or the Magento docs. Or the Magento deploy process. Or the heavy dependency on a patched minor JS framework for all backend UI elements. Or the server spec requirements. Or the heavy reliance on PHP magic methods. Or the fact that the entire community seems to exist due to the benefit of one prolific blogger who burned out two minor versions back.