4 ms·
I started out doing that. And inevitably I'd wind up refactoring multiple similar projects into reusable code and conventions. Over many years I arrived at this
by EGreg 10y ago
I started out doing that. And inevitably I'd wind up refactoring multiple similar projects into reusable code and conventions. Over many years I arrived at this:
http://qbix.com/platform http://qbix.com/platform
Now I can assemble a website that works everywhere and has best practices, by expressing exactly what I want in high level code. When modeling a new app or talking to our developers about architecture, we can use a common language of users, communities, streams, access, realtime pushes and offline notifications etc. People know what I mean when I say "the Patients/account streams should be published by the community and have Patients/photo stream templates for the admin role, related to Patients/gallery category stream published by the logged-in user."
Everything is namespaced, reusable, interoperable and works on every device. It took a long time to make the system but now we can assemble apps like out of building blocks, and have anyone work on anything and know what the conventions are. So yeah, it's paid off!!
- adrianratnapala 10y agoWhen I go to the qbix website, and click on the "for Developers" link, nothing happens. Possibly something would happen if I played with my NoScript options. Now I have some choices: allow javascript in order to read plain text, or ignore your web framework. Guess which one I picked.
- buckbova 10y agoUnfortunately the for developers link had no code samples. So you didn't miss anything aside from a sales pitch.
- random_rr 10y agoEdgy
- EGreg 10y agoDon't use it if you don't want. We built it for ourselves and it's available to you if you want to use it. If you don't want to turn on Javascript to get started with the platform, that's up to you.