Oracle doesn't seem to give a crap about history here. There takeover strategy has always been to try to destroy the old brand of the company and absorb what is left.
It's funny, the internet was not really common until quite a bit after highschool for me. But I honestly don't really remember what people did for many common tasks before the internet. It's like that entire part of my memory was wiped clean by simple, quick and convenient access to global communication and LOLcats.
Anything that is in the world when you're born is normal and ordinary and is just a natural part of the way the world works. Anything that's invented between when you're fifteen and thirty-five is new and exciting and revolutionary and you can probably get a career in it. Anything invented after you're thirty-five is against the natural order of things.
I don't get it. Currently www.sun.com redirects to some oracle.com page, just like www.digital.com redirects to hp.com. What will be the change exactly? Some parts of the site will disappear, but the current site already has little in common with what was sun.com before the acquisition.
Exactly. Interesting way to kill loads of programming links already available via google. Then again - they already worked hard on moving the content around without leaving any redirects behind.
It's not a bad idea as far as conventions go. It makes it fairly easy for nearly anybody to distribute interoperable software without having to either register with Sun/Oracle for some sort of key or to deal with the possibility of collisions. I think it's a pretty smart decision to piggyback atop an already extant naming system. Further, it's just a convention - there's nothing in the language design that requires that packages use your own domain names or even domain names at all.
There are plenty of legitimate gripes to have with Java, but I'm not sure that their namespacing decision is one of them.
I remember when I was first learning Java many years ago...about this convention and asking why one would use this as a namespacing convention. Even back then domain ownership was fast and fleeting and it never seemed to serve any particular purpose. I think because it was always couched that the Java namespace convention was supposed to help you track down the originator of the code even without documentation that I always found it strange. Now with this change, vast swaths of the primary codebase no longer map to the originator of the code!
Are namespace issues such a big deal in other languages that something like this is needed? http://search.cpan.org/ seems to muddle through more or less okay without it. (But then it requires a centralized namespacing system as you pointed out).
So yeah, I do see your point regarding leveraging an existing system. It has just always struck me as a bit oddball.
Fair point, but remember that this convention predates modern search engines. I'm sure you remember what the Internet was like in 1995, for example, and how difficult it could be to find precisely what you were looking for. That's the world Java and its package convention was born into, and in that world it made more sense for the reason you pointed out.
That said, at least Sun was smart enough to not package core classes as com.sun.* - they reserved the java.* packaging for core language constructs, so at least that's not broken.
Is there really any good reason for this, or is it just asserting dominance? I know it's often ignored, but I think with a site as important (and as entrenched in links around the web) as Sun's old site really should heed this:
It was a serious and looming mistake for the web to rely so critically on the identities of content publishers, because it gives some knuckle-dragger in marketing a motivation to break working URLs for pure branding reasons. This could be a valuable service for someone like archive.org, a view of the web as if everyone were competent stewards of their namespaces.
http://thesunalsosets.com/Editorials.html -- "This writer started this website on September 1, 2003, with a mission of removing Scott McNealy as CEO of SUN Microsystems. With the help of many of my readers, this goal was accomplished on
April 21, 2006. One reader asked, "…having achieved your goal against all odds , why don’t you just declare victory, close your website, and end your other activities related to SUN?" My answer is to do so would leave SUN continuing in the same direction. To quote Shakespeare, 'The fault, dear
Brutus, lies not in the stars but in ourselves.' We cannot allow McNealy to continue his failed policies and practices by letting him use his hand-picked puppet on a string continue to lead SUN Microsystems."
