Rant on application frameworks

Today's rant is about application frameworks.  I'm not above ranting and complaining about these things.  Some people do excellent work. But some of the decisions they make and conventions they follow completely baffle me.

Does anyone really create all their tables with a primary key called "id"? Do you really? One of the guidelines I follow is that a column name in one table that is referenced in another table should have the same name as far as possible. Therefore, in a one to many relationship the column name that links them would have the same name in both tables.  The reason for this is simple. It leads to less mistakes. So when I see an applicaton framework assume that the primary key for a table is "id" I get a little bent out of shape.

Second thing that gets to me is naming of tables and models. For pete's sake people, please name them the same. Having a table named PEOPLE and a model named PERSON is counter productive and confusing.  It is far better to name everything the exact same across the board unless there is a real good reason not to.  And in that case, the exception should be rare.