Slashdot Mirror

Eh what? I'm using "commercial quality Open Source products" all the time. GIMP, Inkscape, Eclipse, Fedora Linux, Apache, Archiva, Maven, gcc, VLC, LibreOffice, XBMC, ArgoUML, Avidemux, Latex, Kile, KDE, Amarok, (that was a very short list of a much bigger list of software that I think are "commercial quality" and I'm using every day). The documentation is also very well.

"it's even rarer that you see actual documentation apart from "read the source" Eh what again? For example: Fedora Docu, GIMP Docu, Maven Docu, Inkscape Docu. "read the source" my ass.

What have the development method (open source) to do with quality anyway? I think you wanted to say: " It's rare that you see commercial quality hobby and in free time developed products".

Google in production using something else I'm sure.

I'm pretty sure Google is using containers (or at least something like cgroups) for most of their workloads to do what they do:

http://www.wired.com/wiredenterprise/2013/03/google-borg-twitter-mesos/

http://incubator.apache.org/mesos/

Here's an explanation. Click "next" for more details.

the real details and answer about what "Apache Cloudstack" really is available at http://cloudstack.apache.org/cloudstack-faq.html
.
Maybe apache is trying to make sure that the managers and bosses can be sure to play buzzword bingo and win when they choose Apache Cloudstack. I completely agree with you that an "about" page really ought to tell you what the software is really about. It's frustrating to have to go to the FAQ page and still see a lot of buzzword baloney (bologna / baloney, it's still compressed meat either way).

Orchestration? Srsly?
;>p
Private and public clouds? Would that be the same as restricted access internal facing "intranet" and public-facing "internet" access? I'm glad that Apache is joining the band of buzzword warriors, but I'm also glad that the real details and answer about what "Apache Cloudstack" really is available at http://cloudstack.apache.org/cloudstack-faq.html :

Orchestration? Srsly?
;>p
Private and public clouds? Would that be the same as restricted access internal facing "intranet" and public-facing "internet" access? I'm glad that Apache is joining the band of buzzword warriors, but I'm also glad that the real details and answer about what "Apache Cloudstack" really is available at http://cloudstack.apache.org/cloudstack-faq.html :

...with moronic tard-sounding names like "Jitsi" ?? Maybe we can call it JIZZME instead.

Other examples:

- Apache Hadoop, I mean come on.

- Or any of the other idiotically named products on the Apache Hadoop page: http://hadoop.apache.org/

- Any component of KDE that overemphasizes the K to show how KOOL ir is, and how Kompletely Kudo worthy it is. Fail fail fail fail fail fail!

- GNU/Linux says it all. I mean, holy $#@!. Just Linux is fine, thanks; dork-morons who call it GNU/Linux are just that, dork-morons.

- Gnome. Get out of here.

- Chandler calendar software. Not only is this software an utter pile of steaming shit, but the name makes it sound like something you'd never want to use.

In conclusion, Open Source groups need to work hard on giving the fruits of their labour better names.

log4net and Json.Net are two prime examples. We are also using a bunch of open source media libraries (e.g. ffmpeg and opencv) on my current project and have been for years. The only resistance is that we are shipping closed source software so anything that is GPLed is out, but if the business reality changed to where we could a GPLed product there wouldn't be a second thought about using code under the GPL.

The best approach is for you to check the domain on the link (usually hovering over the link works fine for this), rather than expecting no links.

Unfortunately, "legitimate" e-mail is known to use links where the href's domain is different than the link's text.

Says me and many other people.

https://issues.apache.org/ooo/show_bug.cgi?id=15501
https://issues.apache.org/ooo/show_bug.cgi?id=65293
https://issues.apache.org/ooo/show_bug.cgi?id=118739
https://issues.apache.org/ooo/show_bug.cgi?id=118790

As you can see the bugs aren't fringe stuff that only 0.1% of the people will encounter.

Maybe those OOo bugs are all fixed now, but we were talking about the past and why it was hard to make money from the product. My claim remains that the product was too crap to make substantial money from. How much would you pay for such crap? I wouldn't pay anything at all.

Says me and many other people.

https://issues.apache.org/ooo/show_bug.cgi?id=15501
https://issues.apache.org/ooo/show_bug.cgi?id=65293
https://issues.apache.org/ooo/show_bug.cgi?id=118739
https://issues.apache.org/ooo/show_bug.cgi?id=118790

As you can see the bugs aren't fringe stuff that only 0.1% of the people will encounter.

Maybe those OOo bugs are all fixed now, but we were talking about the past and why it was hard to make money from the product. My claim remains that the product was too crap to make substantial money from. How much would you pay for such crap? I wouldn't pay anything at all.

Says me and many other people.

https://issues.apache.org/ooo/show_bug.cgi?id=15501
https://issues.apache.org/ooo/show_bug.cgi?id=65293
https://issues.apache.org/ooo/show_bug.cgi?id=118739
https://issues.apache.org/ooo/show_bug.cgi?id=118790

As you can see the bugs aren't fringe stuff that only 0.1% of the people will encounter.

Maybe those OOo bugs are all fixed now, but we were talking about the past and why it was hard to make money from the product. My claim remains that the product was too crap to make substantial money from. How much would you pay for such crap? I wouldn't pay anything at all.

Says me and many other people.

https://issues.apache.org/ooo/show_bug.cgi?id=15501
https://issues.apache.org/ooo/show_bug.cgi?id=65293
https://issues.apache.org/ooo/show_bug.cgi?id=118739
https://issues.apache.org/ooo/show_bug.cgi?id=118790

As you can see the bugs aren't fringe stuff that only 0.1% of the people will encounter.

Maybe those OOo bugs are all fixed now, but we were talking about the past and why it was hard to make money from the product. My claim remains that the product was too crap to make substantial money from. How much would you pay for such crap? I wouldn't pay anything at all.

I am pleased with OpenOffice (v3.4.1). I have not seen any need to try LibreOffice personally. My take is that both are developing new features.

Regarding new features in OpenOffice, https://blogs.apache.org/OOo/entry/merging_lotus_symphony_allegro_moderato talks about what is being merged into OpenOffice from IBM's Lotus Symphony. As long as IBM continues to develop Lotus Symphony, I think that OpenOffice will benefit earlier than LibreOffice as IBM tends to do a lot with the Apache foundation. I say earlier since LibreOffice can always get the code from OpenOffice.

Spamassassin handles SPF, reasonably intelligently, that is, not trusting it completely, not giving it more weight than it deserves.
Hanging your spam fighting hat on any single hook is problematic. and SA uses a wealth of tools with constantly updating itself via
scripts. Its been largely trouble free, and we have it set up so that it will learn false positives and false negatives when users
move these to the corresponding folders.

I've been well served by Spamassassin for some time now, it runs quietly
on our mail server. SA does not block mail. It flags it. Our mail server will evaluate these flags and trash outright the most
egregious spam, but we have the limits set low enough such that we will allow the questionable things through.

We error on the side of caution, but we still dump a lot of mail right after SA flags it. (Our business can do that, your business
may not be able to do that.)

If you're going for speed, you'd be better off serving the HTTP direct from Tomcat and cutting Apache or IIS out of the loop entirely.

Tc-native supports HTTP, HTTPS, and AJP, so you still get native code to handle your sockets whether you want to put a separate HTTP in front of Tomcat or not. The Java-based connectors might be fast, but the native connectors are even faster.

If the author will not publish his source code I will: http://pastebin.com/CkJB6h2K

This is a 32 line Scala program. Yes Scala instead of Java but it is based on the exact same SocketServer that the author claims his program uses. It will sit there and listen for a connection, then do a simple imitation of HTTP. It even optionally supports HTTP Keep Alive.

Now to the test. I use the Apache AB tool: http://httpd.apache.org/docs/2.2/programs/ab.html

First without using -k (keep alive):

baldur@neaira:~/tmp$ ab -c 4 -t 10 -n 1000000 http://localhost:5555/
Time taken for tests: 10.000 seconds
Complete requests: 136991
Requests per second: 13698.99 [#/sec] (mean)

So about 13,000 requests per second processed on my old laptop. The author did 2000 requests in 2687 ms = 1344 requests per second or about 10 times slower than my program.

Lets try again with Keep Alive enabled:

baldur@neaira:~/tmp$ ab -c 4 -t 10 -n 1000000 -k http://localhost:5555/
Time taken for tests: 10.000 seconds
Complete requests: 692424
Requests per second: 69242.23 [#/sec] (mean)

So now we are doing 69.000 requests per second or 50 times faster than the authors program.

It might be that my old laptop is 10 or 50 times faster than the setup the author uses. But somehow I do really not think that is it. I think it is extremely likely that the author is a .NET programmer that has insufficient knowledge of Java to code this simple test correctly and that his program is simply wrong. More specifically I suspect that he did not know that you need to use a thread pool to process the connections, or if he did use one, that he used it wrong.

... he then completely does an about-face and deploys the Tomcat on Windows-- a configuration I've actually never seen and which has to give C# a bit of an advantage...

The official Tomcat installer for Windows (as in, the one that you'd download from tomcat.apache.org installs the Tomcat Native Connector, which improves performance considerably. And there's a lot of vertical market applications for Windows that bundle Tomcat.

Only applets run in sandbox so there's nothing to leave.

Wrong. Anything can be placed, optionally, in a sandbox.

- shared hosting (Tomcat): everyone uses the same VM just like with PHP so we are sparing memory, but increasing the security risk

Look up the Tomcat -security option, which enables a SecurityManager and places each individual web application in its own sandbox. It's an option, it "works," and this vulnerability would circumvent it.

Now, granted, no one bothers actually using the option, but it is there.

ActionScript is alive and well!

The Apache Software Foundation Blog
  The Apache Software... | Main
Wednesday Jan 02, 2013

The Apache Software Foundation Announces Apache Cassandra v1.2

High-performance, super-robust Big Data distributed database introduces support for dense clusters, simplifies application modeling, and improves data cell storage, design, and representation.

Forest Hill, MD –2 January 2013– The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of nearly 150 Open Source projects and initiatives, today announced Apache Cassandra v1.2, the latest version of the highly-scalable, fault-tolerant, Big Data distributed database.

Successfully handling thousands of requests per second, Apache Cassandra powers massive data sets quickly and reliably without compromising performance –whether running in the Cloud or partially on-premise in a hybrid data store. Apache Cassandra is successfully used by an array of organizations that include Adobe, Appscale, Appssavvy, Backupify, Cisco, Clearspring, Cloudtalk, Constant Contact, DataStax, Digg, Digital River, Disney, eBay, Easou, Formspring, Hailo, Hobsons, IBM, Mahalo.com, Morningstar, Netflix, Openwave, OpenX, Palantir, PBS, Plaxo, Rackspace, Reddit, RockYou, Shazam, SimpleGeo, Spotify, Thomson-Reuters, Twitter, Urban Airship, US Government, Walmart Labs, Williams-Sonoma, Inc., and Yakaz.

"We are pleased to announce Cassandra 1.2," said Jonathan Ellis, Vice President of Apache Cassandra. "By improving support for dense clusters —powering multiple terabytes per node— as well as simplifying application modeling, and improving data cell storage/design/representation, systems are able to effortlessly scale petabytes of data."

Highlights for the second generation high-performance, NoSQL database includes clustering across virtual nodes, inter-node communication, atomic batches, and request tracing. In addition, Cassandra v1.2 also marks the release of CQL3 (version 3 of the Cassandra Query Language), to simplify application modeling, allow for more powerful mapping, and alleviate design limitations through more natural representation.

"We are really excited to begin taking advantage of all the new features Apache Cassandra v1.2 has to offer – particularly virtual nodes and atomic batches. Both of these new features will play a central role in future enhancements to our architecture," said Ed Anuff, VP, Mobile Platform at Apigee.

"It's great to see the core of Apache Cassandra continue to evolve," said independent software developer Kelly Sommers. "In Cassandra v1.2 the introduction of vnodes will simplify managing clusters while improving performance when adding and rebuilding nodes. v1.2 also includes many new features, performance improvements and further heap reduction to eleviate the burden on the JVM garbage collector."

"The much anticipated release of Cassandra 1.2 brings with it features that simplify application development. Atomic batches provide a mechanism for developers to ensure transactional integrity across a business process, instead of relying on idempotent operations and retry mechanisms," said Brian O’Neill, Lead Architect at Health Market Science. "Additionally, native support for collections is attractive and a compelling reason to explore CQL 3."

"Apache Cassandra continues to be a leading option for scalability and high availability without compromising performance and, with the improvements provided in v1.2, reinforces our commitment to growth while preserving backwards compatibility," added Ellis.

Availability and Oversight
As with all Apache products, Apache Cassandra v1.2 is released under the Apache License v2.0, and is overseen by a self-selected team of active contributors to the project. A Project Management Committee (PMC) guides the Project’s day-to-day operations, including community development and product releases. Apache Cassandra source code, documentation, and related resources are available at http://cassandra.apache.org/.

the whole http://blogs.apache.org/ domain seems to return this 502 error right now. Maintenance, other problem or just slashdotted even if it is an apache domain ?

They seem to be using "Apache/2.0.63 Server at blogs.apache.org Port 80" in reverse-proxy mode and my guess is the server behind it is down.

is called HTML5. A lot of the stack can be found and used elsewhere (i.e. Apache Cordova) and shared by a lot of mobile OSs (webos, tizen, bada, sailfish, mer, and probably others, and more important, could be installed in the other platforms, including desktop.

Every time there's a story that mentions OpenOffice, I check to see whether this bug has been fixed yet. It hasn't. The comments are probably TL;DR, but the idea is that if you attempt to join two paragraphs into one paragraph that would be longer than 65535 characters, it discards all text beyond that point. No warning, no way to undo, and worst of all, absolutely no interest from the developers in fixing it. The standard response? "You shouldn't make paragraphs that long". It's a word processor - it should handle text. Microsoft Office has no such issue.

..or Apache multiviews using the content-accept header. :)

URLs should identify resources, not files anyway, so "/images/background10.jpg" should have the URL "/images/background10" anyway, then you're free to have multiple formats that can supply said resource on the server and vary depending on the client's preferences.

I think the point from TFA was "why create a new Open Source project when you could add a new feature to an existing project?"

That is exactly what they did, Accumulo is an extension of Hadoop

Office does cut it, but so does LibreOffice and it does it better.

At least in MS Word one can select everything in a text document that begins with a table. In LibreOffice, you can't - it's officially been "not fixable" in LibreOffice for almost 10 years, and the only way you can work around it is by adding a paragraph prior to the table. To me, that's ridiculous, and even more so to be told by the developers that it's not an important issue for so long. For your particular need, LibreOffice may work well. It usually is "good enough" for me for most things, but I definitely wouldn't put it at the same level as MS Office.

Especially with product like deltacloud ( http://deltacloud.apache.org/ ), and the fact that there seems to have no specific API or products , ie, that's just centos and ubuntu servers. You can deploy your code everywhere, it doesn't use specific google stuff ( unless you want to, but that was already the case before ).

I have yet to see how far this will go. They will surely have people because that's Google, but I wonder if they do not simply aim to attack Amazon directly at the important point, the purse. AWS give them recuring money, and permit them to negociate good deal regarding to traffic, Amazon reuse android to compete againt google play ( by directly asking to publishers ).

its a nice, utopian idea - a single cross-platform meta environment in which to code that has really easy GUI elements, with a really easy programming language to glue it all together with super-fast 3d vector graphics toolkit....

meanwhile, back in reality. You get the best we've got with native code, which can host an OpenGL environment if you really wanted and you get as fast a runtime as you can get. If you really want your HTML environment (which, to be fair is a good platform for some types of games) then wait for Apache Cordova to get ported. I've found that to be good for the other platforms, there's no reason why it shouldn't arrive for WinPho8.

(PS websockets... don't scale to millions of simultaneous users)

for those curious what they meant by "commercial friendly open source".

http://www.apache.org/licenses/LICENSE-2.0.html

SPDY solves *a* problem, but not *the* problem. The root of the problem today is that loading a simple web page requires 20 or more separate connections: images, ad networks, tracking systems, social network links, 3rd party comment systems, javascript libraries, css, etc. Somehow all of that content needs to be coalesced into fewer connections.

You are wrong use netstat and a modern browser to test it out. With servers configured to do HTTP request keepalives, most browser open a maximum of 2 connections to one server and keep them up and everything is sent through those persistent connections.

The browser also needs to open at least one connection to any third party server without regards for the protocol used.

I see an average of 5 to 20 seconds timeout on most sites. The the server waits for other requests on the SAME connection. Use telnet and watch for the "close connection" delay after entering the query:

telnet www.yahoo.com 80
Trying 98.139.183.24...
Connected to www.yahoo.com.
Escape character is '^]'.
HEAD / HTTP/1.1
host: yahoo.com

HTTP/1.1 301 Moved Permanently
Date: Sun, 17 Jun 2012 18:49:19 GMT
Location: http://www.yahoo.com/
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Cache-Control: private
Age: 0
Connection: keep-alive
Server: YTS/1.20.10

Connection closed by foreign host.

Yahoo's server took about fifteen seconds to close the connection.

http://httpd.apache.org/docs/2.4/mod/core.html#keepalivetimeout

I can see that you have not adjusted your thinking to the concept of the absence of copyright.

For instance you wrote: "it's the copyright on it that legally guarantees the source code will remain free."

Your software will be free if there is no copyright.

Then: "Without copyright, another organization could appropriate it, close it up, and release a derivative work without so much as an acknowledgement that they got it from me, costing me potential reputation,"

Just release the closed version yourself, with credits embedded.

And really, its not so hard or expensive to set up a domain. Mine cost me an old computer and the power to run it. UBUNTU is free, APACHE is free, FREEDNS is free. And a few bucks a year to Godaddy for DNS registry. As you can write code, doing all that should be as easy as pi. (oops, pie).

And as an independent programmer, how can you have any street cred without your own domain?

Get a Tomcat server up and running and deploy your app there. Use Struts/Servlets for you Java structure and navigation, and Velocity to populate the templates. This is Tier 3 development (Keep the Logic, DataAccessObjects, and Templates separate). Velocity takes all of one day to learn and will save you a ton of time in the long run so you can focus on the HTML and the JAVA

http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html

Do NOT go the PHP route. As someone that works for a Fortune 500 company and who has been in the business for 12 years, you don't want to get mixed up in the mess that is PHP debugging and updating. With PHP you will have to learn a new language that doesn't extend very well, is a pain in the ass to debug, and you'll have a tendency to intertwine your application logic with your template, which will make it an absolute bitch when you come around a year later and want to change the look and feel of your site.

have a look at Apache camel : http://camel.apache.org/enterprise-integration-patterns.html
I have the feeling that it is the kind of problems you have to solve...

Yeah, I guess that rules it out seeing as Java doesn't have any code conventions that developers are expected to adhear to or an easy to use tool to check for them.

a majority of our unplanned downtime was due to CouchDB issues

Nowhere on the CouchDB home page is reliability even mentioned. And that's the real issue. Developing a reliable database system is a difficult design and programming task. It requires real software engineering. The hacks who write PHP and use JSON aren't up to a job like that. The "aw, we'll fix it in the next release" attitude doesn't cut it in databases.

I was referring to the Hadoop File System, although it seems that the correct acronym is HDFS (all people I work with seem to drop the D for brevity). My mistake :-)

I wasn't quoting myself "as a source" - instead of just repeating myself I was acknowledging that I've said it before, and I linked to my previous post because it included more details for people who were interested. For sources, most of what Rob Weir says on the AOO incubator dev list will show my point. I haven't followed it in the last few months but when I was reading it frequently stuff like this was going on all the time

I wasn't quoting myself "as a source" - instead of just repeating myself I was acknowledging that I've said it before, and I linked to my previous post because it included more details for people who were interested. For sources, most of what Rob Weir says on the AOO incubator dev list will show my point. I haven't followed it in the last few months but when I was reading it frequently stuff like this was going on all the time

While the source for those libraries was eventually released by Sun, it's not clear to me what license applies to the library source, and it's definitely not clear that the source was released before Google's work on Android. The issue may be water under the bridge as Sun did open source the vast majority of Java, but it kind of flies in the face of "clean room" claims.

How is it not clear? Download OpenJDK from the OpenJDK site and read the License file.

Here's a spoiler: It's mainly GPLv2, although there are apparently still some binary blobs out there with proprietary licenses, plus some parts have the Classpath exception.

However, it's a moot point as Google uses Apache Harmony's class library, not OpenJDK, meaning that this license wouldn't apply.

Likewise, Google claiming they made a cleanroom implementation is moot, as it'd be Apache Harmony's people who would need to claim that.

And the fact that a very large majority of the non-trivial portions of the code clearly do what they do in different ways to Oracle's implementation. And the fact that the developers of the code (in this case Apache, not Google) have stated several times that it is clean room. And that it was an open source project where the practice was to obtain a signed statement from developers providing complete details of exposure to Sun's IP prior to accepting patches from them (see http://harmony.apache.org/auth_cont_quest.html ), so it seems to be pretty clear that either it was clean room, or there is a developer who lied to them in a written warranty and therefore *that developer should be liable*, not Google.

Your basically right, however if a developer hired by google cheated and snuck a look, then it would be google itself who is liable. Companies can't really push liability down to employees like that. *GOOGLE* could sue the employee for breaching contract, but it can't clean its hands of the act. When you work for a company, you represent the company. Thats why if a low level chump makes an insane deal with a third party he's not authorized to make on behalf of the company he's working for , the company is still liable to the third party , the chump is liable to his employer, but the chump is not liable to the third party.

And the fact that a very large majority of the non-trivial portions of the code clearly do what they do in different ways to Oracle's implementation.

That's nice, but it's not evidence of a clean-room implementation. It is a good way to avoid copyright infringement.

And that it was an open source project where the practice was to obtain a signed statement from developers providing complete details of exposure to Sun's IP prior to accepting patches from them (see http://harmony.apache.org/auth_cont_quest.html [apache.org] ),

OK, that is evidence of a clean room implementation. How did Sun code end up in Android then?

Also, what was this guy doing working on Android? Having one of the original developers work on Android is certainly not a clean room implementation.

It's not clear to me you understand what a clean room implementation is. It is perfectly possible to make a clean-room implementation of an SDK, or a chip, that implements the behavior accurately, without looking at the original code. There is no reason to believe Google did this (except for the sketchy testimony by their CEO).

And the fact that a very large majority of the non-trivial portions of the code clearly do what they do in different ways to Oracle's implementation. And the fact that the developers of the code (in this case Apache, not Google) have stated several times that it is clean room. And that it was an open source project where the practice was to obtain a signed statement from developers providing complete details of exposure to Sun's IP prior to accepting patches from them (see http://harmony.apache.org/auth_cont_quest.html ), so it seems to be pretty clear that either it was clean room, or there is a developer who lied to them in a written warranty and therefore *that developer should be liable*, not Google.

Using Apache-licensed software from a GPLv3 code base is perfectly legal:

http://www.apache.org/licenses/GPL-compatibility.html

However, I would contend that a runtime is far more than a library, and it would seem that you can't include GPLv3 code into an Apache codebase, so the question is whether Google kept the license boundaries between the Java-sourced GPLv3 code and the Dalvik compiler/runtime. i.e. They were not allowed to incorporate pieces of the GPLv3 code into Dalvik itself. Recompiling the GPLv3 code with the Dalvik compiler would not violate the GPL, though, because the compiler is merely a tool and does not imply any license restrictions on the code it's used to compile.

Otherwise you could only use gcc to compile GPL code, which clearly is not the case in practice.

Wave is still there. Check it out from http://incubator.apache.org/wave/

...one might wonder why Google has to push their own social network instead of working on open protocols for sharing.

Could it be because they tried working on open protocols for sharing and it didn't work? Hate to reign in the $MEGACORP bashing here, but Google really HAVE tried in this area - G+ looks like a last-ditch attempt to gain some traction amongst the big players in "social".

And how much of that 20TB changes from day to day? How fast is the data set growing? What is your business case for doing a full daily backup versus incremental / transaction log backups?

20TB isn't really all that huge by Big Data standards. The project I'm working on currently uses a ~60TB data set which grows at around 1TB/month. Without knowing specifics I can't architect a solution for you or estimate costs, but I've built several systems using Hadoop to solve this kind of problem. "Affordable" is relative, but Hadoop-based solutions are very cost-effective. What is your current TCO for your backup solution? I'm willing to bet I can architect something that's going to lower that by 25% or more while giving you additional analytical capabilities. My gmail name is the same as my name here.

The nice thing about Hadoop (or any cluster-based system) is that it scales linearly. You don't need to provision 7 years worth of capacity up front; you can add additional nodes as they are needed.

My gmail ID is the same as my name here if you want to talk specifics.

Java is very much alive and thriving on web/enterprise application servers and on mobile devices. What do you think Android apps developers program with? What about sites that make use of JSPs, struts and spring? Here's a partial list of sites built by struts: http://wiki.apache.org/struts/PoweredBy

If this is the bug you're talking about, it appears a bug report was filed, discussed, and a temporary workaround was offered (perhaps more than one). Although free software has bugs just like proprietary software, the way they are reported and handled is night and day.

That appears to be the very same bug, yes. And I'm not disputing the handling of the bug, but merely pointing out that even with "many eyes", this bug existed not so very long ago. Open Source is not immune to the same kinds of problems, though I grant you I probably should have been checking for the latest compatible libraries.

As it turns out, I was using a particularly old version of Apache Commons-Net library (this jar file was from 2005) which had a leap-year bug. It simply would not show me files with modification dates of 2/29.

If this is the bug you're talking about, it appears a bug report was filed, discussed, and a temporary workaround was offered (perhaps more than one). Although free software has bugs just like proprietary software, the way they are reported and handled is night and day.