3 ms·

Great work and very good presentation. (These comments are just from watching the first video.) But how is this next-generation? It seems to be very inspired

by chvid 11y ago

Great work and very good presentation. (These comments are just from watching the first video.) But how is this next-generation? It seems to be very inspired by established widely used web frameworks such as Ruby on Rails. With elements such as ORM, routing, controllers, HTML templates. It also seems to require a lot of code generation. Is that really constructive? (What happens if I edit the various generated files, would I still be able to add field to a record using the command line tools). Couldn't you have moved some of the boilerplate into the framework? Why not use ES6 imports? (Rather than require / Nodal.require) Why create an ORM rather than use a JavaScript-orientated NoSQL database? (mongo, couch etc.)

bpicolo 11y ago
Because time has shown again and again the benefits of transactional SQL dbs?
brazzledazzle 11y ago
>Why create an ORM rather than use a JavaScript-orientated NoSQL database? (mongo, couch etc.) I could be way off here (and I probably am) but shouldn't frameworks abstain from being too opinionated about the particular technologies that you use? The database (or type of db) you choose seems like something that should be based on what your application's requirements dictate not what your framework prefers right?
- adrusi 11y ago
  My opinion differs: if you're going to package your tool as a "framework" rather than a "library", you should integrate a large vertical section of the technology being used. This doesn't mean you have to be coupled with a particular database server, but you should at least have special support for one that can be swapped out for something else. If a framework can't offer me this kind of functionality, why would I want to use it over a library with all the control benefits that brings.
vectorpush 11y ago
> Why create an ORM rather than use a JavaScript-orientated NoSQL database? (mongo, couch etc.) NoSQL has its place, but it's usually not the best choice. Any "comprehensive" web framework should cater to the needs of RDBMS users at a minimum, with support for NoSQL as a plus.
jessaustin 11y ago
Why not use ES6 imports? (Rather than require... What are the benefits of "import" over "require"?
- mnutt 11y ago
  The main benefit I see of import is for client-side code, so that you can statically determine a file's imports ahead of time without actually having to run the code. Require is a regular function rather than a directive, and is probably needed for this framework to automatically find and load all controllers, models, etc.

by chvid 11y ago

bpicolo 11y ago

Because time has shown again and again the benefits of transactional SQL dbs?

brazzledazzle 11y ago

>Why create an ORM rather than use a JavaScript-orientated NoSQL database? (mongo, couch etc.) I could be way off here (and I probably am) but shouldn't frameworks abstain from being too opinionated about the particular technologies that you use? The database (or type of db) you choose seems like something that should be based on what your application's requirements dictate not what your framework prefers right?

adrusi 11y ago
My opinion differs: if you're going to package your tool as a "framework" rather than a "library", you should integrate a large vertical section of the technology being used. This doesn't mean you have to be coupled with a particular database server, but you should at least have special support for one that can be swapped out for something else. If a framework can't offer me this kind of functionality, why would I want to use it over a library with all the control benefits that brings.

vectorpush 11y ago

> Why create an ORM rather than use a JavaScript-orientated NoSQL database? (mongo, couch etc.) NoSQL has its place, but it's usually not the best choice. Any "comprehensive" web framework should cater to the needs of RDBMS users at a minimum, with support for NoSQL as a plus.

jessaustin 11y ago

Why not use ES6 imports? (Rather than require... What are the benefits of "import" over "require"?

mnutt 11y ago
The main benefit I see of import is for client-side code, so that you can statically determine a file's imports ahead of time without actually having to run the code. Require is a regular function rather than a directive, and is probably needed for this framework to automatically find and load all controllers, models, etc.