|
|
|
|
|
|
by GiorgioG
1304 days ago
|
|
|
The problem with not using established frameworks for building apps is that you'll wind up creating your own ad-hoc 'framework'. As your app (and the framework) evolves it becomes more feature-rich, it will be difficult for people to ramp up/understand. They won't be able to Google/Stackoverflow for problems they're having because nobody else on earth is using their 'framework'. Then people will want features you've not implemented or thought about, so now you need a framework committee to decide what's in, what's out. No thanks. Give me ASP.NET Core, Django, Spring Boot for a development organization with more than 1 developer. |
|
|