What is missing is the lack of ability of modern programming languages to grab type information from the database and generate new types on the fly.
Database types are per column, *AND* per tuple.
Every SQL query results in a new type, or an instance of a known type.
General purpose programming languages need to support sets as a first class object, as opposed to iterable collections. Do that, and you don't need hacky ORMs. But then, most modern "OO" languages aren't designed to be extensible.
As a pedestrian, I prefer to be seen but not blinded. Blinded, I am just as likely to wander into your path instead of safely moving out of your way (if I am on the road by chance).
Your city gets goods transported internally by road, and commuters and intercity transport happens via rail. The city then shapes itself to support rail, and a lot of shops move.
We make the mistake of comparing coding with factory assembly lines.
The code is the blueprint, the binary is the assembly line. We have automated the factory which churns out multiple product instances and optimised it away.
The design (and engineering) process remains.
We replaced the machinist by a small piece of code. Then we confuse between the engineer and the machinist.
Slashdot Mirror
Or Haskell like?
Actually, it's tech support and sysadmins who get the flak.
What is missing is the lack of ability of modern programming languages to grab type information from the database and generate new types on the fly.
Database types are per column, *AND* per tuple.
Every SQL query results in a new type, or an instance of a known type.
General purpose programming languages need to support sets as a first class object, as opposed to iterable collections. Do that, and you don't need hacky ORMs. But then, most modern "OO" languages aren't designed to be extensible.
Pedestrians can see oncoming cars and get out of the way. Blinded pedestrians have it far harder. Deer in the headlights.
As a pedestrian, I prefer to be seen but not blinded. Blinded, I am just as likely to wander into your path instead of safely moving out of your way (if I am on the road by chance).
Nah, if there's sufficient demand, people will move to IPv6. So the telcos just have to move.
Yeah, but the fuckups have long-term effects. Short term profit, long term loss.
So you suggest the government stop building roads?
Your city gets goods transported internally by road, and commuters and intercity transport happens via rail. The city then shapes itself to support rail, and a lot of shops move.
Eternal September.
I work for a domain registrar. It's possible to run a registrar as a low cost service, but it's purely a volume business.
In fact, the only way you can run a registrar is by pushing volumes and that needs low prices.
http://en.wikipedia.org/wiki/Universal_jurisdiction
You can't make method calls. You can communicate via explicit message passing, like a Unix pipeline. That's why we have bidirectional sockets.
Threads were a lightweight fork(2) replacement.
Nuremberg is the legal precedent.
Too big to fail?
You had me until you tried to prove that Apple was more open.
In terms of effect, what's the difference?
Running applications remotely with the display local? That's what X *does*.
X over HTTP?
If you thought remote X was slow, imagine the performance.
His only obligation is to follow the lawful orders given to him by his seniors.
And what does your soldier do about unlawful orders, or other people following unlawful orders?
The last time this issue was raised in court was at Nuremberg.
Only if your cellphone rates are stupidly high.
http://wiki.openmoko.org/wiki/GTA04_revisions I saw the samples. Nice stuff.
The Indian editions are cheap. Cheaper paper and binding, but each of V1,2 and 3 are ~ 12 USD each.
What does ICANN have to do with IPv4 running out? IP is IETF territory, and the IETF has done it's job by putting IPv6 out there.
IPv6 adoption is now a business problem, and you can see the lack of business innovation in that space.
Programming is *all* design work. Prototyping.
We make the mistake of comparing coding with factory assembly lines.
The code is the blueprint, the binary is the assembly line. We have automated the factory which churns out multiple product instances and optimised it away.
The design (and engineering) process remains.
We replaced the machinist by a small piece of code. Then we confuse between the engineer and the machinist.