Type erasure erases they correct type information of paramatized types and replaces it with its super. Call get class on the object it reports the wrong information. This means you can load any type with the same super or that super type into a collection or to a refrance from persistent data. No error until you try to access a method on the bad object. Type erasure produces incorrect run time information, breaks the rules of inhieretance, and destroys the type saftey of the language. The only arguments i have heard so far for it are "no language is perfect", "we need a solution that works with legacy code", and "its better than ". The first and third arguments, well... some real visionaries, huh? That second dog just don't hunt. Type erasure does not play well with legacy code. Imagine trying to find the line of code that crashed your program when your error is thrown in a completly different place. It was a bad move that cannot be taken back. I think time will show that developers will choose a more reliable and logical solution that behaves predictably.
Although Sun has been generous with their source and created great opportunities for clever developers, Java has generated the need for a new cross platform OO language. The decision to implement generisity using type erasure has irrepairably damaged the run-ime integrity of the language. This will become more and more apparent as people become better aquanted with the new specification. Hopefully the open source community will build on the experience gained through working with Java to create a new truly type safe cross-platform OO language. If not... all hail.NET chime... chime... rattle.
i suspect a looming generation will embrace chipping themselves in much the same way tatoos and piercings have been embraced. Multiple specialized chips will be a source of pride for the intiated. Poping popular designs in and out will will be not such a big deal. i would if i were young again. but i am not and i have grown to take comfort in the foibles of pure organic functionality.
By your logic you should be looking for a minimum wage untrained labor job as those will be opening up fast if the feds continue to crack down.
I would recommend reading Steve Jobs commencement speech given last year at Stanford if you are seriously considering computer science. I love it. I am a CS mater's candidate and the future looks very bright. But I love the feild and that makes all the difference. here's the link:
http://news-service.stanford.edu/news/2005/june15/ jobs-061505.html
good luck in whatever you do.
Slashdot Mirror
Type erasure erases they correct type information of paramatized types and replaces it with its super. Call get class on the object it reports the wrong information. This means you can load any type with the same super or that super type into a collection or to a refrance from persistent data. No error until you try to access a method on the bad object. Type erasure produces incorrect run time information, breaks the rules of inhieretance, and destroys the type saftey of the language. The only arguments i have heard so far for it are "no language is perfect", "we need a solution that works with legacy code", and "its better than ". The first and third arguments, well... some real visionaries, huh? That second dog just don't hunt. Type erasure does not play well with legacy code. Imagine trying to find the line of code that crashed your program when your error is thrown in a completly different place. It was a bad move that cannot be taken back. I think time will show that developers will choose a more reliable and logical solution that behaves predictably.
Although Sun has been generous with their source and created great opportunities for clever developers, Java has generated the need for a new cross platform OO language. The decision to implement generisity using type erasure has irrepairably damaged the run-ime integrity of the language. This will become more and more apparent as people become better aquanted with the new specification. Hopefully the open source community will build on the experience gained through working with Java to create a new truly type safe cross-platform OO language. If not... all hail .NET chime... chime... rattle.
i suspect a looming generation will embrace chipping themselves in much the same way tatoos and piercings have been embraced. Multiple specialized chips will be a source of pride for the intiated. Poping popular designs in and out will will be not such a big deal. i would if i were young again. but i am not and i have grown to take comfort in the foibles of pure organic functionality.
By your logic you should be looking for a minimum wage untrained labor job as those will be opening up fast if the feds continue to crack down. I would recommend reading Steve Jobs commencement speech given last year at Stanford if you are seriously considering computer science. I love it. I am a CS mater's candidate and the future looks very bright. But I love the feild and that makes all the difference. here's the link: http://news-service.stanford.edu/news/2005/june15/ jobs-061505.html
good luck in whatever you do.