How about HAL in 2001? One of the most scary AIâ(TM)s gone rouge-but-plausible stories Iâ(TM)ve ever seen. Blade runner is not really about AI in the transitional sense.
Definitely a kernel of truth here - 2003 C++ sufferer from very poor compilers that would often fail on complex stuff like stl in hard to fathom ways. The stl is a kind of compiler work out that force them to get it all right.
These days the compilers pass the tests and have good handling of user generated errors.
C++ can be abused, but most people seem to say âdonâ(TM)tâ(TM) these days about operator overloading, heavy use of multiple inheritance, and generally bending the language in hard to read ways.
We work on lots of asset rich projects - often the PSDs folder will span many (hundreds!) gigabytes for a small project, and we'll be working on multiple projects at once. The PSDs then often have source imagery and a whole load of clutter collected from clients. SVN is superb at dealing with this scenario, since as a coder I don't fill my machine with sources I don't need - but we need them archived and backed up none the less.
This is especially a problem if you're a developer with a fancy small SSD and the guy across the room has 6TB at his disposal for videos;-)!
Slashdot Mirror
+1 - the live bookmarks are the way I catch up with all the crap I don't check that often. And they are great.
How about HAL in 2001? One of the most scary AIâ(TM)s gone rouge-but-plausible stories Iâ(TM)ve ever seen. Blade runner is not really about AI in the transitional sense.
Definitely a kernel of truth here - 2003 C++ sufferer from very poor compilers that would often fail on complex stuff like stl in hard to fathom ways. The stl is a kind of compiler work out that force them to get it all right. These days the compilers pass the tests and have good handling of user generated errors. C++ can be abused, but most people seem to say âdonâ(TM)tâ(TM) these days about operator overloading, heavy use of multiple inheritance, and generally bending the language in hard to read ways.
We work on lots of asset rich projects - often the PSDs folder will span many (hundreds!) gigabytes for a small project, and we'll be working on multiple projects at once. The PSDs then often have source imagery and a whole load of clutter collected from clients. SVN is superb at dealing with this scenario, since as a coder I don't fill my machine with sources I don't need - but we need them archived and backed up none the less. This is especially a problem if you're a developer with a fancy small SSD and the guy across the room has 6TB at his disposal for videos ;-)!