3 ms·
The author seems to consistently confuse architecture, languages and frameworks. None of his arguments have anything to do with Rails, Ruby, PHP or whatever els
by rickmb 15y ago
The author seems to consistently confuse architecture, languages and frameworks. None of his arguments have anything to do with Rails, Ruby, PHP or whatever else he mentions, except partly Javascript.
This seems to be a recurring pattern with developers who have "discovered" design and architecture through frameworks and can not seem to separate that from the tools used.
- kayoone 15y agothought the same, like he says PHP was shit and still is (which is partly true) but then delivers CRUD Tasks, ORMs etc as the reason for Rails which also are very popular in all other frameworks for other languages nowadays.
- dextorious 15y ago"""but then delivers CRUD Tasks, ORMs etc as the reason for Rails which also are very popular in all other frameworks for other languages nowadays.""" The might be popular for "other languages nowadays", but he delivers those as a reason of Rails success BACK IN THE DAY. And indeed it was. Not many PHP ORMS and scaffolding frameworks existed or where successful back then.
- hello_moto 15y agoI think this is true but in my experience, they are what most people call "Application Developers". Linus is still writing code in C even for a simple GUI app that wxPython can do for him quickly. Josh Bloch is still writing code in Java since 97/98?. Crockford/Resig will probably never write software in a language other than JavaScript. Your Application Developer will quickly move to the latest trend spreading HackerNews. So if you want to be famous writing frameworks or tools, make sure you hit frontpage of HN.