As usual the answer is probably: That depends... If it's a one off application against a database that was built by a programmer and it will only be used in the "one application one database" scenario, it probably doesn't matter too much. If it's important data that will be accessed by multiple interfaces/applications it's probably better in the database (performance/maintainability/resuability/etc). I've seen very successful deployments where the only access to the data was through stored/procs. The developers were able to focus on the application and the user interface and didn't get bogged down in religious arguments about database design and data management (which they probably had less background/experience in anyway).
In the end the developers liked developing code that way. All they needed to know about the database was inputs and outputs.
You make a week case. The First Amendment does not prohibit anyone except Congress. There is no reference to public property (except perhaps "the free execise thereof...". You should also define what you mean by "state", As the First Amendment does not restrict the individual states in any way. The Tenth Amendment on the other hand...
Your views appear Humanistic, which by the way has been declared a form of religion by the Supreme Court.
I think you really have to look at it from the perspective of why are they teaching computer science.
The answer is: To collect your tuition money. If you don't want to learn java, show them with your wallet and enroll at another school that sees computer science from your perspective.
Another point of view might be that we should be studying Spanish instead of English because Spanish is more common in the world than English.
It really doesn't matter what language you learn, as long as you learn to communicate (natural language) or solve problems (computer language) or is solving problems the point in both? Jobs are hot for java programmers right now, so that's what the colleges are teaching.
Maybe it would be better to start with COBOL, that way you could understand programming from a historical perspective?
And yet I ramble...
Slashdot Mirror
As usual the answer is probably: That depends... If it's a one off application against a database that was built by a programmer and it will only be used in the "one application one database" scenario, it probably doesn't matter too much.
If it's important data that will be accessed by multiple interfaces/applications it's probably better in the database (performance/maintainability/resuability/etc). I've seen very successful deployments where the only access to the data was through stored/procs. The developers were able to focus on the application and the user interface and didn't get bogged down in religious arguments about database design and data management (which they probably had less background/experience in anyway).
In the end the developers liked developing code that way. All they needed to know about the database was inputs and outputs.
You are mistaken...
You make a week case. The First Amendment does not prohibit anyone except Congress. There is no reference to public property (except perhaps "the free execise thereof...". You should also define what you mean by "state", As the First Amendment does not restrict the individual states in any way. The Tenth Amendment on the other hand...
Your views appear Humanistic, which by the way has been declared a form of religion by the Supreme Court.
I think you really have to look at it from the perspective of why are they teaching computer science. The answer is: To collect your tuition money. If you don't want to learn java, show them with your wallet and enroll at another school that sees computer science from your perspective. Another point of view might be that we should be studying Spanish instead of English because Spanish is more common in the world than English. It really doesn't matter what language you learn, as long as you learn to communicate (natural language) or solve problems (computer language) or is solving problems the point in both? Jobs are hot for java programmers right now, so that's what the colleges are teaching. Maybe it would be better to start with COBOL, that way you could understand programming from a historical perspective? And yet I ramble...