I think that the fact that frivolous lawsuits exist should have no bearing on a citizen's decision to use the court system (which he's paying for, after all) to enforce the law.
I currently have the issue where the machine simply turns off when the battery has reached around 30-40%, according to the operating system's battery meter.
Funny... I have the exact same problem on my (~3 year old) G4 Powerbook.
The plants were grandfathered in because we can not pass laws that are retroactive - you can not currently be held to laws that will be passed in the future. That is in the constitution - the law had to have been made that way. That's the logic in that.
The Constitution has nothing to do with it. If you couldn't pass laws outlawing or regulating existing behaviors, you couldn't ever pass laws at all.
There are other reasons, some good and some not, why we don't require utilities to immediately comply with new regulations, but compliance with the Constitution isn't one of them.
I've worked on two mid sized web/db projects now with a couple of old skool Oracle hackers. They are quite sharp, but not really up on all the hot new O/R mapping technology. Hibernate. Castor. etc.
So I figure I'd teach them a bit about the "right" way of doing this. Use the database to store data. Period. Model business objects as Java classes. Implement business rules in Java, and code the views in terms of those objects.
The thing is, the more we talked about this, the more I came to question the way I had done things in the past. For example, it's not always possible (or at least convenient) to define a single set of business objects. A Widget might look one way from a manufacturing perspective, and another from a sales perspective, to take an absurd example. Often I end up fetching more data that I really need, because the BOs have been defined to be as general as possible. And so on.
My particular case is special, because there will more likely always be people with heavy Oracle expertise to maintain these systems than people with Java experience. So the risk of sticking all the rules into the database, only to end up with a maintenance nightmare after the Oracle guys have left doesn't really exist. But even so, I've come around to thinking quite a bit differently about the role of the database in a multi-tier application.
Slashdot Mirror
The plants were grandfathered in because we can not pass laws that are retroactive - you can not currently be held to laws that will be passed in the future. That is in the constitution - the law had to have been made that way. That's the logic in that.
The Constitution has nothing to do with it. If you couldn't pass laws outlawing or regulating existing behaviors, you couldn't ever pass laws at all.
There are other reasons, some good and some not, why we don't require utilities to immediately comply with new regulations, but compliance with the Constitution isn't one of them.
I've worked on two mid sized web/db projects now with a couple of old skool Oracle hackers. They are quite sharp, but not really up on all the hot new O/R mapping technology. Hibernate. Castor. etc.
So I figure I'd teach them a bit about the "right" way of doing this. Use the database to store data. Period. Model business objects as Java classes. Implement business rules in Java, and code the views in terms of those objects.
The thing is, the more we talked about this, the more I came to question the way I had done things in the past. For example, it's not always possible (or at least convenient) to define a single set of business objects. A Widget might look one way from a manufacturing perspective, and another from a sales perspective, to take an absurd example. Often I end up fetching more data that I really need, because the BOs have been defined to be as general as possible. And so on.
My particular case is special, because there will more likely always be people with heavy Oracle expertise to maintain these systems than people with Java experience. So the risk of sticking all the rules into the database, only to end up with a maintenance nightmare after the Oracle guys have left doesn't really exist. But even so, I've come around to thinking quite a bit differently about the role of the database in a multi-tier application.
great post.
(some) universities are starting to come to the same conclusions. see for example the Sakai project: http:www.sakaiproject.org/