meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ancient_history [2020/09/03 12:59] – external edit 127.0.0.1 | ancient_history [2020/10/30 15:57] (current) – [Another name change. JavaCC (21)] revusky | ||
---|---|---|---|
Line 5: | Line 5: | ||
Now, actually, the history of JavaCC is not so easy to piece together. In its early days (the only time it was actively developed) it was bounced around to a few different companies. The version history [[https:// | Now, actually, the history of JavaCC is not so easy to piece together. In its early days (the only time it was actively developed) it was bounced around to a few different companies. The version history [[https:// | ||
- | Since an earlier draft of this page, I had a bit of correspondence with Sriram Sankar, who was the project lead on " | + | Since an earlier draft of this page, I had a bit of correspondence with Sriram Sankar, who was the project lead on " |
===== Let's start at the beginning ===== | ===== Let's start at the beginning ===== | ||
Line 19: | Line 19: | ||
Now, Metamata, Jack's (now JavaCC' | Now, Metamata, Jack's (now JavaCC' | ||
- | t is fairly easy to deduce that Sun did not ever allocate any real development resources to JavaCC in this period. By the time Sun released the code as open source in 2003, it was really an orphan project that had not been actively developed for some time. Whoever made such decisions decided that they might as well release JavaCC as open source. In retrospect, this is probably a very typical pattern for [[https:// | + | It is fairly easy to deduce that Sun did not ever allocate any real development resources to JavaCC in this period. By the time Sun released the code as open source in 2003, it was really an orphan project that had not been actively developed for some time. Whoever made such decisions decided that they might as well release JavaCC as open source. In retrospect, this is probably a very typical pattern for [[https:// |
===== Late 2001. My Own Involvement with JavaCC ===== | ===== Late 2001. My Own Involvement with JavaCC ===== | ||
Line 105: | Line 105: | ||
Now, first of all, to be clear about one aspect of all of this, FreeCC (now //JavaCC 21//) was never a " | Now, first of all, to be clear about one aspect of all of this, FreeCC (now //JavaCC 21//) was never a " | ||
- | As I have stated quite bluntly above, the legacy JavaCC project is just one of these [[https:// | + | As I have stated quite bluntly above, the legacy JavaCC project is just one of these [[nothingburger]] projects. (It is not the only one out there!) Properly understood, it is not even about the people involved in the project currently. I do not recognize the names of most of the people involved in that currently. However, it doesn' |
//Nothing significant can be done with the legacy JavaCC codebase without a massive cleanup and refactoring.// | //Nothing significant can be done with the legacy JavaCC codebase without a massive cleanup and refactoring.// | ||
Line 111: | Line 111: | ||
I undertook that cleanup and refactoring back in 2008 and it is largely done. The only basis for moving forward on the project is [[https:// | I undertook that cleanup and refactoring back in 2008 and it is largely done. The only basis for moving forward on the project is [[https:// | ||
- | A couple of people have expressed misgivings about my taking the JavaCC name. One person said that this would " | + | A couple of people have expressed misgivings about my taking the JavaCC name. One person said that this would " |
- | A [[https:// | + | A [[nothingburger]] is essentially a fraud, because it amounts to artfully arranging your bun and your condiments and creating a //trompe l' |
Meanwhile, //JavaCC 21// is what it is being presented as, the active continuation of work on the codebase that Sun open sourced back in 2003. | Meanwhile, //JavaCC 21// is what it is being presented as, the active continuation of work on the codebase that Sun open sourced back in 2003. | ||
Line 121: | Line 121: | ||
//Nobody has ever filed a trademark in any jurisdiction on the name JavaCC.// | //Nobody has ever filed a trademark in any jurisdiction on the name JavaCC.// | ||
- | In any case, the problem here is that this is the only feasible course of action. In the open source world, it frequently happens that people show up in a community, one of these [[https:// | + | In any case, the problem here is that this is the only feasible course of action. In the open source world, it frequently happens that people show up in a community, one of these [[nothingburger]] projects and propose some ideas and they are arrogantly dismissed and the people are told that they are free to go " |
Well, this is technically true. You can create your own " | Well, this is technically true. You can create your own " |