Uh... my correction.. It says "shipping 4/8" (i suspect that's the 8th of April) in the advertisement link above... so the official announcement will probably be tomorrow, and all mirrors will be working, but "the official box" won't be shipping for a couple of days.
Im speculating, but this is the usual procedure with Red Hat releases, if I remember correctly. As a side-note, I think all official announcements of new RedHat versions have been on Mondays... anybody want to clarify on this one?
Seems like the ads for 6.2 professional are already out on Freshmeat and Slashdot... I got one, and it took me here. Seems like elinux.com is expecting an official release of 6.2 tomorrow so they can start shipping, or else I don't understand the ad, since 6.2 isn't officially released yet...
6. Contact nVidia and tell them exactly what you did and why.
Re:How about rack mounting PowerBooks?
on
Rack An iMac
·
· Score: 1
I suspect that Powerbooks are a lot more expensive than the corresponding iMacs, so that wouldn't be economical for a business. Remember that the person in the article didn't do the iMac rackmounting just for the coolness of it, but maybe more because of the fact that the iMac is cheap Apple hardware. But the idea of rackmounting Powerbooks is still cool though.;-)
Nowadays truly "hip" geeks flame over Gnome vs. KDE instead.
Re:SuSE making inroads in the North American marke
on
SuSE 6.4 Announced
·
· Score: 1
RedHat is less expensive than RedHat depending on the stuff you get.
I don't get your point here.;)
Seriously though, I assume you mean that SuSe will get you more stuff for the money. However, a lot of what is shipped with SuSe on that impressive pile of CDs is unstable stuff. Plus, as soon as it makes it on that CD, will be outdated by new versions. So I don't really think that this is much of a value for people with faster Net connections and/or an obsessiveness for the latest and greatest stuff. And most of the Linux people I know have both of that;)
Re:SuSE making inroads in the North American marke
on
SuSE 6.4 Announced
·
· Score: 1
People in the US seem to assume that everyone in Europe uses SuSE. While it may have a stranglehold on the German market, that's certainly not the case in the UK. Yes, it's available, but Red Hat seems to be more prevalent.
I'll second that for Sweden and probably the rest of Scandinavia. Red Hat is far more used and in the "spotlight" (press, media) than any other distro. Heck, I doubt that any other people than experienced Linux or UNIX users in Sweden know that Red Hat is not synonymous with Linux.
If I go to a random bookstore and look for Linux books (guides to Linux, "dummies" books, etc.), chances are 90% of them will cover Red Hat and Gnome. On the other hand, I've visited bookstores in Germany and there those 90% of the books were about SuSe and KDE. The rest was generic. I couldn't find anything Red Hat-specific at all. So Germany is pretty SuSe-centric, to say the least.
But it always amuses me when I read headlines or comments on Slashdot implying that since I'm European I should be using SuSe "like we know all Europeans do".
Most of the talk was about the Windows 2000 DNS system beeing incompatible with most other OSes (Windows 2000 using dynamic DNS) and the fear that IT departments would probably soon "be forced" to use the Windows 2000 DNS system.
I admit that NetBEUI isn't the coolest thing on earth, but this is definately good news. I know a company that makes embedded printer servers and one thing stopping them from using Linux as the base OS for those servers was that NetBEUI was a proprietary protocol and because of that without a decent Linux implementation.
But there's much new stuff. This Intel page explains a lot of the history behind Bluetooth.
Basically, (the Intel page doesn't say this) some engineers at Ericsson thought about designing a new protocol for communication between their (Ericsson's) devices in 1994, and started developing it. The project wasn't initially called Bluetooth, but "MC link" (MC = Multi-Communicator). But somewhere during the development, they started to realize that the chips needed for this would be much cheaper if it was a widely adopted standard, so they started talking with their arch rival Nokia about sharing the technology and making it a common standard. They formed a Special Interest Group (SIG) in 1998, together with some other well-known companies (amongst others IBM, Intel, Motorola, 3Com, Casio, Cirrus Logic, TDK, Compaq, Dell, Xircom, Lucent, Toshiba, Psion, Qualcomm and Axis). Last year they released the specification for version 1.0 of the standard. And experimental Bluetooth devices have been built using the standard and shown on various expos last year, and real devices are under development now. I think we'll see many of these devices released this year. That's the brief history of Bluetooth.
Basically, Bluetooth is a short-range (less than 10 metres or so) radio communication protocol for digital devices. It is aimed towards mobile devices (laptops, cellular modems, cellphones, palms, winces etc.) so that you won't need cables to connect them with each other anymore. Since it's radio, it has some clear advantages over IR protocols (you don't need a clear view between the devices, so your cellular modem could stay in your case, for example).
Hope this explains a bit. If you want to read more, browse the Bluetooth SIG site . They used to have a non-flash site before, but info about Bluetooth should be all over the net. I wrote an essay a year ago about Bluetooth, with basically just meterail from the net, so maybe I could find some links for you.
I don't think Microsoft will kill it, as they're now also members of the SIG (Special Interest Group behind the Bluetooth standard). Granted, they joined in very late, but as most laptops, cellphones, cellular modems and palm devices will have Bluetooth inside really soon now (tm), I think it would be utterly stupid of them not to support it.
Really cool to see this from Axis. If you don't know Axis, they make printer servers, CDROM-servers, and now also web cams. Their latest web cams run on their own hardware (the ETRAX100 processor, see their developer page linked above for the specs) and contains a fully integrated web server, and everything is powered by Linux =) (see this page)
They've released all their patches (it's a custom 2.0.36 kernel, see their developer page) and they're thinking of switching all their devices from a proprietary, custom in-house os, to Linux (well, maybe not the printer servers, because they have to be very cheap and cannot have megs of RAM) but all their other devices. So if you want to support an upstart company using Linux, buy their stuff =)
They work close together with Ericsson, so I'm not surprised about Axis beeing one of the first with Bluetooth drivers...
I think Word went directly from 2.0 to 6.0 on the Windows side, with no versions inbetween. And then of course, it was followed by Word 95, which was basically the same as Word 6 but with Windows95-stylish dialog boxes.
It's simply not true that it is impossible to make a good modern web site design in IE, Netscape and others and on the same time make it usable in lynx.
In fact, it's far easier to support lynx than the 3.x series of IE and NS. Whereas those browsers will try to render your CSS with their broken implementations (to say the least), lynx won't try to render CSS at all, and this is of course how it should be. Lynx just prints the text, no colours, fonts and font sizes to worry about. Same thing with Javascript. No mouseover incompabilities to worry about. So I think you're off the wrong foot here.
If you're still not convinced that a lynx-friendly page could look other than the "festering backside of a unwashed gibbon", have a look at the URL provided in my comment.
As a web designer (albeit very hobbyist) myself, I'm wondering why some of "us" never learn. In fact, it's a rather huge percentage that never get's it. By "getting it", I mean that they realize that making their sites accessible should be one of their biggest priorities.
I think the main reason for this is that most web designers are focused on layout and not the other parts, the "boring" stuff.
In bigger web site developments, the work is often divided into "design" (as in layout and overall graphics) and actual "coding" (as in splitting images up, reducing image sizes, and most important, implementing everything in HTML), and done by different persons. But everything starts with the site design and a good HTML coder can not always compensate for a bad design, from the accessability viewpoint, at the beginning. If the project manager, the customer and the designer have agreed on "we want a site in Flash", you may have a tough job explaining to them why you should implement an alternative design for those without Flash or even without graphics at all. The customer is often a non-techie, and won't even understand the problem at all, the designer won't be your friend if you critisize his flashy layout and point out accessability errors, and will always argue "Why won't everybody run IE 5.0? In a matter of months, everybody will, and should, and our problem is solved", and finally, your boss will argue that it's a minor problem (that what the customer does not care about or is not interested in will always be a minor problem) and that you have a deadline.
So it's not that easy to convince people. These arguments are far too common.
But personally, I'm convinced that it's really simple to do a good site design, given that you have it in mind from the very start of the designing process. As many slashdotters know, a simple tool as lynx is often good enough to measure accessabilty. To make a site viewable in lynx, you should:
Avoid frames. If you don't, you should make sure that you provide means for easy navigation. Also, of course, make sure that no information gets lost in the no-frames version and that it's always up-to-date with the frames version. This of course speaks for some kind of database solution. But you can avoid this problem completely by avoiding frames. Granted, most bigger sites today have to use frames, but they also often use databases for storage of content, so it should be no problem.
Apply ALT= attributes. Everybody reading this on Slashdot should know that by now. However, don't do it on every darn image, but where it has to be. By that I mean that spacer images should preferably have ALT="", so that they don't mess up the readability in lynx, but all other images that contain some sort of information in text should have. And use some sense when you set the ALT= attributes. Some bad examples are "company logo" and "horisontal ruler", use "Company, Inc." and "" instead, ie. use someting that makes sense in a text-only browser, and avoid the graphical information that really isn't needed in those.
If you use style sheets, beware that browsers render the paragraph tags differently. If you put something in a "block" (DIV or P), Netscape will automatically put a paragraph before the next block, although it really isn't there in the HTML, and thereby maybe fool you not to use paragraphs were they really should have been. Browsers that don't render CSS of course don't do this, so make sure you use your paragraphs properly, or everything will be a big text block.
There is probably more, but I can't come up with more right now. But by now you should have a pretty lynx-friendly site. Simple? It is.
As a side note, I tried out this myself on a small and simple site project I had lately, and in addition to the latest Netscape and IE browsers, it also works great great in lynx. (If anybody cares, it's here and in Swedish).
I disagree. This may seem natural since I do program translations. I do them for free, so my views are completely unaffected of economical reasons, if anybody thought that.
While I agree that the world would be better if everybody spoke the same language, I also think that this is never going to happen. Even if it was, I don't think that "locking out" potential users from using a computer by not translating programs is the right way to go. This just makes the language barrier even worse - many people would love to learn English well, but they may not be able to do it for various reasons. My parents, for example, don't understand English very well (they learned it in school in the 50ies) and speak it even worse - but that's not going to change. For old people (over 45-50), a language is hard to learn. Some say that the ability to easily learn a language is already decreasing in the age of 10 to 15 - this is why we learn languages early in school. Then think about countries as the former USSR and the other former communist countries, where English wasn't even an option at school. How much of this population grew up under this era and have trouble with English? Well, one could guess that that would be the majority. And even in countries where English is learned as a second language in school, the quality of the education may differ. I have a cousin in Germany, and I once visited his school and sat by during their English class. My opinion was that even I spoke English better than their teacher, and English isn't my first language either. My cousin and his friends shared this opinion =)
These are some of my arguments why I translate programs:
People may still have the ability to be computer-savvy, if programs are translated into their native tongue. It will definately speed the learning process up for many, by avoiding having to learn another language, just to learn how to use a computer.
Language is very important part of culture. And one shouldn't try to take away the culture from people - among the worst tragedies in history are those were people were (and are) repressed by not letting them have their culture. I'm not saying that the people in the world are being repressed by non-translated computer programs, but the thought is not very far away, at least for me.
There's no special reason why computer programs should not be translated, when books, manuals, and other things are.
Freedom of choice. Maybe the most important part. If I want to use a program in English, I should be able to do so. If I want to use it translated into my mother tongue, I should be able to do so. And this is exactly what translation is alla about.
I don't think that everything about an application should be internationalized. It's the UI of the application, and the documentation, that needs translation.
Internationalization of comments? This would indeed be useful to the non-English world, but I don't think that it's a high-priority thing. Many source code comments are not even understandeable by other people than who wrote them, and since the source may change very often (but not necessarily the UI) it would be hard to keep up. This goes also for function and variable names. Translation of these could also very easily break things. Not saying that there isn't translation of programming languages out there - an example that comes to mind is the macro language (VBA?) in MS Office applications that is translated (function calls etc.) in localized versions. However, I don't understand the point in this - most programmers or other computer-savvy people in the world know English well enough to be able to read the name (!) of a function call in the documentation and use it. Again, it's the documentation that should be translated, not the function calls, variable names, etc, where translation could break things.
I'm translating programs myself (GNU utilities into Swedish) and there's a reason why we (translators) have a strict policy not to translate such things as command-line switches. This would break things. So "--verbose" should be left intact in the translated strings, no matter if it is Hindi, Swahili, Esperanto, Dutch or Swedish. But the explaination of "--verbose" in "--help", and the documentation, is translated.
To sum things up: Since many wonderful programs lack proper UI translation in many languages (not to mention the documentation!), I think this is where the main efforts should be concentrated. Also, internationalization is more than just translation. For example, I'd love to have more applications understand localization settings and properly react to them - I hate when an application defaults to inches as a measure, weeks beginning on Sundays, Legal as the paper format, AM/PM clock, "," as thousand delimiter, etc, etc. All things that are NOT the "standard" outside the USA, and things that many programmers overlook. Even worse is when these annoying things are hard-coded - it goes from being merely annoying to a chronic pain, and often makes me refuse to use the program at all.
So even if programs are translated, there's still more left to do to make it internationalized.
Check that you have the correct output plugin selected in xmms. I'f you're using Gnome, chances are that you already have the Enlightenment sound deamon (esd) up and running. In that case use the ESD plugin (if it isn't there, install the xmms-esd package. If it doesn't work with ESD try the OSD output plugin. Should work in KDE.
To my best knowledge, there is no Winamp for Linux. What you may be using is a program called xmms, formerly known as x11amp, that looks and feels like Winamp (and can use its themes).
But it's an entirely different program, and in contrast to Winamp fully GPL, which is why it sometimes get's its own thread on sites like Slashdot. Hope this clears up things a bit.
I don't know if this really is your problem, but I had a similar one. I couldn't get my HP DeskJet 660C to work with RH6.1, printtool wouldn't recognize that there was a printer attached to the parport, and therefore didn't write anything to/etc/printcap, no matter how hard I tried.
This is appearantly a bug in modutils in Redhat 6.1, you can read about it here. It did solve my problem, and printing now works smoothlessly.
Well, I want to say a serious "Thanks!" to Rob and the rest on Andover responsible for this too!
Moderators: Even if this may be redundant, I don't think that Rob & Co. could get enough thanks to compensate for the bitching and harassments they have recieved previously, trust me, I was one of those thinking Bad Things (tm) about Rob and thought "hypocrisy", even if I didn't post those thougts on Slashdot, but merely agreed with every other person bitching.
I feel truly sad for myself and my judgement today, and happy for Rob and all others who have quietly worked behind the scenes to make this happen, even with the flames and bad thoughts from qlueless people like me. Not only has Rob listened to those who wanted the source up-to-date, he has made it GPL too, made one Andover employee code maintainer, and fulfilled every other wish Slashdotters had. That's nice work. Again, thanks, and keep the good work going. And my apologies for our behavior.
Slashdot Mirror
Sorry for my triple-posting.
Im speculating, but this is the usual procedure with Red Hat releases, if I remember correctly. As a side-note, I think all official announcements of new RedHat versions have been on Mondays... anybody want to clarify on this one?
6. Contact nVidia and tell them exactly what you did and why.
Nowadays truly "hip" geeks flame over Gnome vs. KDE instead.
I don't get your point here. ;)
Seriously though, I assume you mean that SuSe will get you more stuff for the money. ;)
However, a lot of what is shipped with SuSe on that impressive pile of CDs is unstable stuff. Plus, as soon as it makes it on that CD, will be outdated by new versions. So I don't really think that this is much of a value for people with faster Net connections and/or an obsessiveness for the latest and greatest stuff. And most of the Linux people I know have both of that
I'll second that for Sweden and probably the rest of Scandinavia. Red Hat is far more used and in the "spotlight" (press, media) than any other distro. Heck, I doubt that any other people than experienced Linux or UNIX users in Sweden know that Red Hat is not synonymous with Linux.
If I go to a random bookstore and look for Linux books (guides to Linux, "dummies" books, etc.), chances are 90% of them will cover Red Hat and Gnome.
On the other hand, I've visited bookstores in Germany and there those 90% of the books were about SuSe and KDE. The rest was generic. I couldn't find anything Red Hat-specific at all. So Germany is pretty SuSe-centric, to say the least.
But it always amuses me when I read headlines or comments on Slashdot implying that since I'm European I should be using SuSe "like we know all Europeans do".
FreshMeat is for application records and announcements, SourceForge is for projects in development.
Am I the only one wondering about the last sentence?
Most of the talk was about the Windows 2000 DNS system beeing incompatible with most other OSes (Windows 2000 using dynamic DNS) and the fear that IT departments would probably soon "be forced" to use the Windows 2000 DNS system.
Now, with this, everything changes.
But there's much new stuff. This Intel page explains a lot of the history behind Bluetooth.
Basically, (the Intel page doesn't say this) some engineers at Ericsson thought about designing a new protocol for communication between their (Ericsson's) devices in 1994, and started developing it. The project wasn't initially called Bluetooth, but "MC link" (MC = Multi-Communicator). But somewhere during the development, they started to realize that the chips needed for this would be much cheaper if it was a widely adopted standard, so they started talking with their arch rival Nokia about sharing the technology and making it a common standard. They formed a Special Interest Group (SIG) in 1998, together with some other well-known companies (amongst others IBM, Intel, Motorola, 3Com, Casio, Cirrus Logic, TDK, Compaq, Dell, Xircom, Lucent, Toshiba, Psion, Qualcomm and Axis).
Last year they released the specification for version 1.0 of the standard. And experimental Bluetooth devices have been built using the standard and shown on various expos last year, and real devices are under development now. I think we'll see many of these devices released this year. That's the brief history of Bluetooth.
Here is also Ericsson's Bluetooth site. Here's the specs.
Hope this explains a bit. If you want to read more, browse the Bluetooth SIG site . They used to have a non-flash site before, but info about Bluetooth should be all over the net.
I wrote an essay a year ago about Bluetooth, with basically just meterail from the net, so maybe I could find some links for you.
They've released all their patches (it's a custom 2.0.36 kernel, see their developer page) and they're thinking of switching all their devices from a proprietary, custom in-house os, to Linux (well, maybe not the printer servers, because they have to be very cheap and cannot have megs of RAM) but all their other devices. So if you want to support an upstart company using Linux, buy their stuff =)
They work close together with Ericsson, so I'm not surprised about Axis beeing one of the first with Bluetooth drivers...
(Note: I'm not affiliated with Axis)
And then of course, it was followed by Word 95, which was basically the same as Word 6 but with Windows95-stylish dialog boxes.
It's simply not true that it is impossible to make a good modern web site design in IE, Netscape and others and on the same time make it usable in lynx.
In fact, it's far easier to support lynx than the 3.x series of IE and NS. Whereas those browsers will try to render your CSS with their broken implementations (to say the least), lynx won't try to render CSS at all, and this is of course how it should be. Lynx just prints the text, no colours, fonts and font sizes to worry about. Same thing with Javascript. No mouseover incompabilities to worry about. So I think you're off the wrong foot here.
If you're still not convinced that a lynx-friendly page could look other than the "festering backside of a unwashed gibbon", have a look at the URL provided in my comment.
I think the main reason for this is that most web designers are focused on layout and not the other parts, the "boring" stuff.
In bigger web site developments, the work is often divided into "design" (as in layout and overall graphics) and actual "coding" (as in splitting images up, reducing image sizes, and most important, implementing everything in HTML), and done by different persons.
But everything starts with the site design and a good HTML coder can not always compensate for a bad design, from the accessability viewpoint, at the beginning. If the project manager, the customer and the designer have agreed on "we want a site in Flash", you may have a tough job explaining to them why you should implement an alternative design for those without Flash or even without graphics at all. The customer is often a non-techie, and won't even understand the problem at all, the designer won't be your friend if you critisize his flashy layout and point out accessability errors, and will always argue "Why won't everybody run IE 5.0? In a matter of months, everybody will, and should, and our problem is solved", and finally, your boss will argue that it's a minor problem (that what the customer does not care about or is not interested in will always be a minor problem) and that you have a deadline.
So it's not that easy to convince people. These arguments are far too common.
But personally, I'm convinced that it's really simple to do a good site design, given that you have it in mind from the very start of the designing process. As many slashdotters know, a simple tool as lynx is often good enough to measure accessabilty. To make a site viewable in lynx, you should:
- Avoid frames. If you don't, you should make sure that you provide means for easy navigation. Also, of course, make sure that no information gets lost in the no-frames version and that it's always up-to-date with the frames version. This of course speaks for some kind of database solution. But you can avoid this problem completely by avoiding frames. Granted, most bigger sites today have to use frames, but they also often use databases for storage of content, so it should be no problem.
- Apply ALT= attributes. Everybody reading this on Slashdot should know that by now. However, don't do it on every darn image, but where it has to be. By that I mean that spacer images should preferably have ALT="", so that they don't mess up the readability in lynx, but all other images that contain some sort of information in text should have. And use some sense when you set the ALT= attributes. Some bad examples are "company logo" and "horisontal ruler", use "Company, Inc." and "" instead, ie. use someting that makes sense in a text-only browser, and avoid the graphical information that really isn't needed in those.
- If you use style sheets, beware that browsers render the paragraph tags differently. If you put something in a "block" (DIV or P), Netscape will automatically put a paragraph before the next block, although it really isn't there in the HTML, and thereby maybe fool you not to use paragraphs were they really should have been.
There is probably more, but I can't come up with more right now.Browsers that don't render CSS of course don't do this, so make sure you use your paragraphs properly, or everything will be a big text block.
But by now you should have a pretty lynx-friendly site. Simple? It is.
As a side note, I tried out this myself on a small and simple site project I had lately, and in addition to the latest Netscape and IE browsers, it also works great great in lynx. (If anybody cares, it's here and in Swedish).
While I agree that the world would be better if everybody spoke the same language, I also think that this is never going to happen. Even if it was, I don't think that "locking out" potential users from using a computer by not translating programs is the right way to go. This just makes the language barrier even worse - many people would love to learn English well, but they may not be able to do it for various reasons. My parents, for example, don't understand English very well (they learned it in school in the 50ies) and speak it even worse - but that's not going to change. For old people (over 45-50), a language is hard to learn. Some say that the ability to easily learn a language is already decreasing in the age of 10 to 15 - this is why we learn languages early in school.
Then think about countries as the former USSR and the other former communist countries, where English wasn't even an option at school. How much of this population grew up under this era and have trouble with English? Well, one could guess that that would be the majority.
And even in countries where English is learned as a second language in school, the quality of the education may differ. I have a cousin in Germany, and I once visited his school and sat by during their English class. My opinion was that even I spoke English better than their teacher, and English isn't my first language either. My cousin and his friends shared this opinion =)
These are some of my arguments why I translate programs:
Internationalization of comments? This would indeed be useful to the non-English world, but I don't think that it's a high-priority thing.
Many source code comments are not even understandeable by other people than who wrote them, and since the source may change very often (but not necessarily the UI) it would be hard to keep up. This goes also for function and variable names. Translation of these could also very easily break things.
Not saying that there isn't translation of programming languages out there - an example that comes to mind is the macro language (VBA?) in MS Office applications that is translated (function calls etc.) in localized versions. However, I don't understand the point in this - most programmers or other computer-savvy people in the world know English well enough to be able to read the name (!) of a function call in the documentation and use it. Again, it's the documentation that should be translated, not the function calls, variable names, etc, where translation could break things.
I'm translating programs myself (GNU utilities into Swedish) and there's a reason why we (translators) have a strict policy not to translate such things as command-line switches. This would break things. So "--verbose" should be left intact in the translated strings, no matter if it is Hindi, Swahili, Esperanto, Dutch or Swedish. But the explaination of "--verbose" in "--help", and the documentation, is translated.
To sum things up: Since many wonderful programs lack proper UI translation in many languages (not to mention the documentation!), I think this is where the main efforts should be concentrated.
Also, internationalization is more than just translation. For example, I'd love to have more applications understand localization settings and properly react to them - I hate when an application defaults to inches as a measure, weeks beginning on Sundays, Legal as the paper format, AM/PM clock, "," as thousand delimiter, etc, etc. All things that are NOT the "standard" outside the USA, and things that many programmers overlook. Even worse is when these annoying things are hard-coded - it goes from being merely annoying to a chronic pain, and often makes me refuse to use the program at all.
So even if programs are translated, there's still more left to do to make it internationalized.
I'f you're using Gnome, chances are that you already have the Enlightenment sound deamon (esd) up and running. In that case use the ESD plugin (if it isn't there, install the xmms-esd package. If it doesn't work with ESD try the OSD output plugin. Should work in KDE.
But it's an entirely different program, and in contrast to Winamp fully GPL, which is why it sometimes get's its own thread on sites like Slashdot.
Hope this clears up things a bit.
This is appearantly a bug in modutils in Redhat 6.1, you can read about it here. It did solve my problem, and printing now works smoothlessly.
Moderators: Even if this may be redundant, I don't think that Rob & Co. could get enough thanks to compensate for the bitching and harassments they have recieved previously, trust me, I was one of those thinking Bad Things (tm) about Rob and thought "hypocrisy", even if I didn't post those thougts on Slashdot, but merely agreed with every other person bitching.
I feel truly sad for myself and my judgement today, and happy for Rob and all others who have quietly worked behind the scenes to make this happen, even with the flames and bad thoughts from qlueless people like me.
Not only has Rob listened to those who wanted the source up-to-date, he has made it GPL too, made one Andover employee code maintainer, and fulfilled every other wish Slashdotters had. That's nice work.
Again, thanks, and keep the good work going. And my apologies for our behavior.