I think he's saying Java is recreating what C made.I don't agree since Java allows writing of code at a higher level. (with a garbage collector etc)
Every programming language sort of recreates the basics. They are the basics after all. The neat programming languages/frameworks are the ones that 'reinvent' something. Do something in a completely new way. On a programminglanguage-level it's difficult. A lot of the practices were already invented in early languages like lisp, eifel & smalltalk.
I like Ruby because it's not ashamed of taking the great parts from other programming languages and putting it together in an easily understandable language.
Nope, i'm saying is that the more you abstract and take out of the way of the coder, the quicker they can write code. Java did this to C type languages, and people got quicker. Ruby and python did this to Java. But the inverse im often told by my C colleagues is that the abstraction means you fundamentally lose control of performance. I don't agree with this statement, but what I do agree with is that if you want high level, human oriented lprogramming languages that you can quickly write code in, you need to solve very similar problems
It might not be wise to go back to bloated JEE. However, it would certainly be unwise to leave the knowledge behind. People working in Rails and Django applications need to learn those important lessons. It can save them from a lot of common pitfalls. I have seen people using a large number of servers for Rails applications while similar load is handled by less half their number of servers using Java.
I am not against fat models. However, the point of separating code into tiers makes it cleaner. The author does approve of concerns. His point is models are becoming too fat over time and people need to follow techniques like concerns and use cases to take out business logic. Essentially something already well known in other platforms is unknown in these communities.
Model classes in Rails inherit ActiveRecord::Base. So, you can call a class method like update_all which is equivalent to an update statement on the table.
'Models could have 0 code of working with database and business-logic only'
Well the business logic creeping in is one of the issues here. That is why there are attempts to separate out the business logic as in case of the use of /app/use_cases [refer to the link of use cases in the article].
There's nothing forcing your model classes to inherit ActiveRecord::Base. It's perfectly acceptable to use other ORMs or even bare Ruby classes as models. If the only thing you want to do is database operations, ORM is a waste of time anyway.
Yeah, even I keep looking at distrowatch from time to time and I agree that some time ago many distros were showing growing popularity. However all the distributions going down in popularity at the same time surprised me.
Ask me here or on the Arch bug page (preferred as I will be notified) and I shall provide all details you might need. For starters, I have BCM4311 card and use broadcom-wl driver, i.e. the open source driver released by Broadcom.
