Jikes authors are TERRORISTS
I’m glad I don’t know anyone who has commit access to jikes. I’m glad that when I wish ill onto those people, when I want them to die slow painful agonising deaths, it’s not causing harm to a friend or acquaintance.
I had previously ranted and raved about the obscenity that was jikes 1.19; how it so gleefully quoted from a book. I was assured by many people that they’ve gone way overboard, and will tone down the output to be sane and a lot less offensive.
Foolishly, I upgraded to jikes 1.21. Every time I compile now, I want to immolate those chocolate log miners. I am filled with such rage, such fury, that no punishment or torture method seems severe enough to slake my thirst for revenge and retribution.
Why in god’s name do I need to be informed, by default, of every time I use a local variable to shadow a member field? Why can’t I not specify a break in my switch statements if I so choose? The language allows both and has VERY explicit clear rules about what happens and how it’s treated. If it’s good enough for the goddam JLS, it’s good enough for me. You, jikes twats, have NO right deciding my coding habits for me. You’re a bunch of fuckwitted angsty IBMers who think that all they need to do is tug some linux/OSS penis to be admired and loved by all.
It’s one thing to write a custom compiler for children just taking their first java steps. It’s quite another to foist this disgusting filth onto people who supposedly know what they’re doing. I mean, we can forgive the fact that it emits different bytecode to javac (look at the code generated for asserts, for example), we can forgive the fact that its website is one of the most difficult to navigate or find any info at, but really, even us seasoned bitter cynics have our limits.
The problem is that the language has moved on since jikes 1.18 (the last usable version). The ONLY reason I prefer using jikes is to avoid the JVM startup time. It’s depressing and frustrating that one is forced to choose between taking the startup hit with javac, or sticking to an old version of jikes before it was taken over by a horde of braindamaged fuckwits unable to accept that there might be developers out there who aren’t quite as dimwitted or spastic as they are. On the bright side, those folks make a very powerful argument for the merits of genetic cleansing.
September 12th, 2004 at 3:30 pm
Yo wazzup my niggaz, dis dat Epesh nigga hangin’ in da hood with mah bling bling
Yo bitch ass muthas wanna trip? Epesh be slangin’ his gat and puttin’ a hole in yo head punk
Yo me and mah dawgz in #java be talkin’ like dis:
September 12th, 2004 at 3:32 pm
someone unebonyfy epesh
September 12th, 2004 at 4:15 pm
Someone will end up sueing you for emotional distress, Hani!
“Terrorists”… sheesh! You should stop playing with your MOM and EJBs. Otherwise, who can tell what will happen?!
September 12th, 2004 at 4:30 pm
Shut the fuck up. It’s free software. If you don’t like it, write your own version, you big pansy.
September 12th, 2004 at 4:32 pm
Hani,
Have you benchmarked JDK 1.4’s javac? We used to use jikes on a large build because it cut about a minute off of the build time. When we switched to 1.4, we found that javac was now about 20 seconds faster than jikes, and so we stopped supporting jikes. It really is a shame that jikes has been standing still while the rest of the world continued to progress.
September 12th, 2004 at 6:06 pm
You obviously have no concept of what “terrorist” means so I suggest you stop using it. People will not only think you are a fool, they will know it.
September 12th, 2004 at 6:21 pm
Hani,
I moved from Jikes to javac 1.4.2. Javac is at least fast as jikes. Give it a try.
September 12th, 2004 at 8:22 pm
You use switch????! In OO code?
September 12th, 2004 at 10:01 pm
I’m pretty sure “chocolate log miner” is lifted from an Ani Difranco song. It’s one of the 32 flavors. You should add an attribution.
September 12th, 2004 at 11:29 pm
Did you mean, “Jikes authors are ERRORISTS”?
September 13th, 2004 at 2:59 am
The good IDEs let you run ant in the same JVM, and you can call javac from the same JVM as ant, thus using only one JVM for everything. No startup hit, although you may run into problems in some rare cases.
And javac-1.4.2 is really really faster.
September 13th, 2004 at 3:33 am
But Jikes is so Groovy!!! Whoops.
September 13th, 2004 at 4:52 am
According to this post, they’ve also made a very powerful argument for the merits of not using Java!
September 13th, 2004 at 7:37 am
“On the bright side, those folks make a very powerful argument for the merits of genetic cleansing.”
Yeah, right. And on the other side you make a very powerful argument for punishment of people ignorant enough of taking fascist ideas too lightly. Prick!
September 13th, 2004 at 11:18 am
For gods sake people lighten up. It is the Bileblog.
September 14th, 2004 at 5:31 am
Go Hani, go! Never mind all these PC dick-tuggers. Just line up on their chocolate starfishes and ram it home.
TERRORIST. There! I said the “T” word. Oooohh! Have I uspset some widdle Americans then?
September 14th, 2004 at 1:00 pm
“It’s one thing to write a custom compiler for children just taking their first java steps. It’s quite another to foist this disgusting filth onto people who supposedly know what they’re doing.”
–WHAT!!! If you’re using switch statements in your code and overshadowing field names with local variable names then it’s you that don’t know what the hell you’re doing, either that or you’re trying to win an obfuscated code contest for Java!
September 14th, 2004 at 5:05 pm
Surely Jikes authours are too shit and lazy to be terrorists. Terrorism requires discipline, planning and stealth rather than bleating knob-tugging finger-wagging mediocrity. I suppose they have weird fanatical obsession in common. And Kris, sorry but switch statements aren’t really that shocking. Thank your lucky stars we’re not using GOTOs any more.
September 14th, 2004 at 5:07 pm
Another step down on the path to a police state…the FBI knocks on your door for simply bandying around the T word publicly.
September 14th, 2004 at 5:20 pm
And another thing - is Bob American by any chance? Good grief, a coupla thousand people die and suddenly Americans have a patent on being all solemn and uptight. Jesus guys, this shit happens ALL THE TIME ALL OVER THE WORLD and MOSTLY funded with AMERICAN MONEY but you never HEAR about it because you’re so GODDAMN PAROCHIAL (and of course because it mainly happens to poor people who aren’t important). Of course it’s like BAD and shit, but it’s no excuse for getting all holier-than-thou on our ass. Blah blah blah ‘no concept of terrorist’. Ever lived in a poor country Bob? Thought not.
September 15th, 2004 at 6:41 am
Hehe…
Add the “T” word to the name “Hani Suleiman” and you make a perfect target for the FBI.
In any case, me being from the .NET world, it’s refreshing to take a look at the Java side of things thru your bile-blog.
The biggest problem with Java imho - the stupid names. Ok, I can live with jikes (yikes!), but Java really lost me whe I heard for Enterprise Beans and POJOs. Come on - Enterprise.. beans! How do you expect me to code well when I’ll be laughing my ass out making instances of Enterprise… Beans and POJOs.
September 15th, 2004 at 8:28 am
“The biggest problem with Java imho - the stupid names”
This from a guy who’ll be coding exclusively on a platform called “long horn” and a development environment called “Whidbey”
September 15th, 2004 at 10:12 am
“Whidbey” comes a kid with a lisp from a town called Whitby in England. So he’ll fit right in here then.
September 19th, 2004 at 9:29 pm
Good grief, do we have a bunch of pussies here - reacting to a some commentary by one of us. Just because Hani is of Jordanian descent - is he prohibited from using the “T” word?
Are we now going to refer to the “T” word just like the pussies refer to the “N” word during the OJ trial?
Hani’s blog is one of the best around - and those who cannot handle it are afflicted with a terminal case of being politically correct.
September 20th, 2004 at 11:54 am
RTFM?
October 20th, 2004 at 11:41 pm
You’re upset because the IBM’s Jikes team imposes changes and they don’t appear to be interacting with the community to process and consider feedback.
They do respond to constructive feedback and bugs, I’ve done that once, and was treated quite well.
Going overboard isn’t helpful.
Myself, I’m also increasingly disappointed with Jikes. Both Sun and IBM do not fully realize the importance of the Jikes project. Jikes looks behind in features, and arbitrarily imposes changes - this is not good.
Strong suggestion to the IBM team: new features and warning should be by default only be enabled through a command line option. This applies to warning about coding habbits especially.
Another suggestion: makes jikes figure out classpath or jikespath for itself, just like javac is able to do. Look for the JAVA_HOME env var or something. Or how about the ability to drop the jikes.exe or jikes right besides javac.exe or javac, making it an easier drop in solution.
And does Jikes fully support Java 5 now?
November 13th, 2004 at 2:05 pm
Jikes is no longer developed by any IBM folks,
and it has not been since a few years. Idiots.