3 ms·

I find it so hard to believe that CRUD software is still largely written by hand. In the ideal tech stack, that wouldn't be the case. The stack would have sa

I find it so hard to believe that CRUD software is still largely written by hand. In the ideal tech stack, that wouldn't be the case. The stack would have sane defaults from top to bottom, so that you wouldn't need to evaluate every .js and .css. Does that seriously not exist?

mettamage 4y ago
Java has some scaffolding options
codingdave 4y ago
There are heaps of low code tools, no code tools, boilerplate generators, and frameworks that abstract the details out. Is there something else that you envisioned that is not encompassed by those solutions?
- WalterGR 4y ago
  I meant frameworks specifically - i.e. something that's 'full-code' but doesn't just emit some boilerplate to get you started. Are there frameworks that will give you - for example - a full CRUD app given data definitions? Bonus points for things like accounts and permissioning. I don't know of any but would absolutely love to be proven wrong.
  - hunter2_ 4y ago
    While it's by no means the best tool for every job, Drupal fits nicely into this category, including bonus points. Out of the box, you can model your entities with whatever types of fields and relationships you want, and grant very granular CRUD permissions to arbitrary roles that in turn get granted to users.
    - WalterGR 4y ago
      Where does Drupal lie on the continuum between framework and no-code / CMS, though? If I'm using Drupal, do I start with code or do I start with a web UI? If I need to tweak something, am I modifying my code or someone else's component?
      - hunter2_ 4y ago
        Squarely "framework" for most sites where Drupal makes sense because if you're not doing something custom you're probably using something else entirely, but you can really get far without writing anything yourself. An installation gets you a pile of code ("core") that you never touch, which is enough to establish the schema of a database resulting in the ability to do many things through the web UI. If you want to do more things, you add more code, either "contrib" (maintained by the community, kind of like a distant cousin to npm packages) or custom (write it yourself, but only create new files that invoke core/contrib hooks, don't modify core/contrib files). The more contrib/custom code you add, the more that the web UI lets you do, typically. It begins as a basic CMS and ends up as a bespoke CMS and/or something that doesn't even resemble a CMS, depending on what you do with it. At some point in the middle of the process, you may approach and then whiz past a CMS roughly as powerful as WordPress.
        WalterGR 4y ago
        Awesome, thanks for your response!

mettamage 4y ago

Java has some scaffolding options

codingdave 4y ago

There are heaps of low code tools, no code tools, boilerplate generators, and frameworks that abstract the details out. Is there something else that you envisioned that is not encompassed by those solutions?

WalterGR 4y ago
I meant frameworks specifically - i.e. something that's 'full-code' but doesn't just emit some boilerplate to get you started. Are there frameworks that will give you - for example - a full CRUD app given data definitions? Bonus points for things like accounts and permissioning. I don't know of any but would absolutely love to be proven wrong.
- hunter2_ 4y ago
  While it's by no means the best tool for every job, Drupal fits nicely into this category, including bonus points. Out of the box, you can model your entities with whatever types of fields and relationships you want, and grant very granular CRUD permissions to arbitrary roles that in turn get granted to users.
  - WalterGR 4y ago
    Where does Drupal lie on the continuum between framework and no-code / CMS, though? If I'm using Drupal, do I start with code or do I start with a web UI? If I need to tweak something, am I modifying my code or someone else's component?
    - hunter2_ 4y ago
      Squarely "framework" for most sites where Drupal makes sense because if you're not doing something custom you're probably using something else entirely, but you can really get far without writing anything yourself. An installation gets you a pile of code ("core") that you never touch, which is enough to establish the schema of a database resulting in the ability to do many things through the web UI. If you want to do more things, you add more code, either "contrib" (maintained by the community, kind of like a distant cousin to npm packages) or custom (write it yourself, but only create new files that invoke core/contrib hooks, don't modify core/contrib files). The more contrib/custom code you add, the more that the web UI lets you do, typically. It begins as a basic CMS and ends up as a bespoke CMS and/or something that doesn't even resemble a CMS, depending on what you do with it. At some point in the middle of the process, you may approach and then whiz past a CMS roughly as powerful as WordPress.
      - WalterGR 4y ago
        Awesome, thanks for your response!