3 ms·

IMO one of the key missing points here that is not really considered, is that when you use a well documented and relatively mature framework, it greatly simplif

by fareesh 10y ago

IMO one of the key missing points here that is not really considered, is that when you use a well documented and relatively mature framework, it greatly simplifies some of the non-programming related aspects of software development, particularly with regard to getting new developers up to speed, and ensuring that even your junior-most developers are able to contribute without having to become heavily acquainted with your specific implementation of authentication, file uploads, routing, etc.

catuskoti 10y ago
Well, I always write a command line (CLI) program first, without worrying at all, about what kind of user interfaces (UI) I may do later on. Frameworks do it the other way around. They generate a skeleton for a web user interface or a mobile app, and next, the real program gets unidentifiably shoehorned in. There are so many different ways to call a program function: by the user, by one of your own scripts that does it in batch, by an external program through an API, through a web user interface, by a mobile app, by a desktop app, ... Isn't the most stupid way of building a program, to shoehorn it into a web user interface? It pretty much guarantees that you will have to implement the same logic many times all over again. That kind of applications can never be consistent. Furthermore, my CLI programs are trivially easy to containerize properly with tools like docker. How can you do that with a monolithic framework monster?