Anyone who says JBuilder is better has most likely never used anything but JBuilder, short of installing and compiling Hello World.
When I first started using JBuilder instead of gvim, I was pretty impressed - there were all sorts of things it did that you just couldn't do in a standard text editor - code completion, refactoring, etc.
Then I tried Eclipse, and I saw how good those features can be when they actually work.
At my workplace most of the other Java developers use JBuilder, because that's what we paid (obscenely) for, and because they've never used anything else. I use it when I need to ensure that my Eclipse projects still work with JBuilder, and when dealing with their projects for one off fixes that don't warrant migrating the project to Eclipse.
From what I can tell, JBuilder is the best IDE in the industry for pretty wizards that break your code, and check box features you never need that PHBs use to justify their $6000(Au) per developer investment. Eclipse on the other hand just makes writing code easy.
I haven't used any other IDEs so I can't comment as to whether or not Eclipse is any better than them, but I _do_ know that JBuilder doesn't even come close when it comes to the everyday writing of Java code.
How sure are you that the other person really _does_ know what you're (not your) talking about?
Sometimes poor grammar and spelling is harmless, but other times a single missed comma or misspelt word is enough to completely change the meaning of a sentence.
Also, a lot of people seem to think that it's a black and white issue - but it's not. Not all mistakes are equal. There are often people that get overly worked up about things that are more a matter of style rather than grammar, but in other cases people will strongly defend their "right" to create completely nonsensical sentences and call it "communication".
A few seconds extra to proofread and run a spell checker over your emails and posts is a small price to pay to improve the chances that you'll be understood and decrease the likelihood that you'll look like an idiot.
> Exactly. Which is dramatically different from the claim that 'Linux scales to 512 processors for general purpose work'. Yes, but is much closer to the original statement (before the clustering and SGI silliness) of 'Obviously you wouldn't want to run Linux on a massive 64 processor server'.
> Which it is reasonable to do with Linux on carefully designed 16-way or 32-way systems. Once you get to 32 way or above then the system is going to have to be carefully designed regardless of the operating system running on it.
Why did you use all that C++ crap to discuss an example that could have just as easily been standard C (which is what I immediately assumed), C# or Java?. Simply saying "When i rolls over, it'll eventually become <= 0", or using pseudo code would have been sufficient, and prevented those of us who aren't C++ programmers from digging through verbose, unfamiliar syntax to try to figure out what you're saying. When communicating with others, it usually pays to be clear and concise, not clever if you want to get your message across.
But in any case, the actual _point_ on the statement was not that the loop would be infinite (or not), but that it was obviously wrong. Your point that we couldn't tell that it was obviously wrong because we didn't know what it was supposed to do in the first place just goes to further prove the original point. Whilst you couldn't be _certain_ that while(i > 0)i++; is wrong, it _looks_ wrong, (or at least the wrong approach if the outcome happens to be correct) to anyone with any programming experience. Getting a computer to instantly tell that something "looks" wrong would be quite an achievement.
Texture quality, 5.1 sound, hard drive (have you seen the size of Morrowind saved games!) and out of the box support for > 2 controllers are why I prefer the XBox.
Better controller and smooth framerate with no tearing or stuttering is why I prefer the PS2.
In general, both have some games that look better than some games on the other - but most are pretty much the same, though I do appreciate the better textures on the XBox.
It looks like the PS3 and XBox 360 will be more or less identical from my point of view. But I have a feeling I'll be leaning towards the XBox 360 due to not having to pay extra for the hard drive. It'll all come down to the games though.
> Perhaps you missed that the individual who submitted the article to slashdot is the author of the review, and owner of the site it is on?
That's how book reviews on Slashdot _always_ work.
Someone writes a review and submits it to slashdot. They don't submit someone else's review - that would be a copyright issue at best, and plagiarism at worst. It just happens that in this case the person who submitted the review also has it on his web site, so he linked to it. That's fair enough if you ask me, and a few reviewers have done that in the past.
If the concept bugs you, then turn off the review section in your preferences, because pretty much every review will be like that.
use MyEclipseIDE instead... Excellent Struts support, as well as plenty of other J2EE features. Not free, but _very_ cheap considering it makes Eclipse a serious competitor to JBuilder Enterprise (or probably more accurately makes JBuilder not any threat to Eclipse).
Eclipse includes its own incremental compiler. You never have to do a separate "build" step for most Java projects, just save the file and run the app.
> Mu covers your answers and all possible ones like it. No it doesn't, because to the average english speaking person, "Mu" is quite rightly a nonsense answer.
You might as well answer "Ekky-ekky-ekky-ekky-z'Bang, zoom-Boing, z'nourrrwringmm"
If you _really_ want to answer "Mu", rather than something useful and specific, then why not answer with "Your question cannot be answered because it depends on incorrect assumptions"? That way you don't have the other person staring at you blankly trying to figure out if you've admitted to beating your wife.
If it's permissible to answer a yes / no question with something other than yes or no, then it must be permissible to answer with something a little less nonsensical, such as "I don't have a wife", or "I have never beaten my wife".
> How do these poor people (the new authors, not the library crowd) survive They have a real job, or they have a partner with one.
very few published authors could even think of living off their writing - and if they do, it's not through book sales, it's through things like giving talks at schools and offering writing workshops...
Actually, from what I understand it's the kde-education package that will probably see the most use from this. In particular applications like KStars - possibly one of KDE's best (and least publicised) applications.
Clicking on a star or galaxy and getting the information from Wikipedia from it would be brilliant.
Q: "Like WinSite? Or TuCows?" A: "You mean time limited, cripled, and full of ads and nag screens? No, nothing like WinSite or TuCows. Completely free, unencumbered, unrestricted, nag free, ad free, forever. And you get the source if you want, but you probably don't care about that"
Switching to Linux is worth it just to escape the insane world of Windows shareware where people seriously expect you to pay $50 for the crapy semi functional app they spent 2 hours in VB on. At least in the open source world the crappy semi functional app that someone spent two hours in perl on doesn't cost you anything;)
The point is that the interest in reto computing is keeping the _knowledge_ required to convert the stream of data to something useful. Things like old manuals and spec sheets that might tell you exactly what encoding is used in the data. (Since manuals actually contained real information in those days, rather than being purely a vehicle for "Screw you, don't blame us" EULAs and disclaimers)
No, the point is that if you go back in time and try to change things the reality you experienced before you did so was already the result of you going back in time and trying to change things.
So when you went back, you could try to do all sorts of things, but whatever you did, the result would be what had already happened before you did so, because it's already happened.
I'm sure someone could take this and warp it to prove that there is no free will, and that we are all marching towards our predetermined fate.
I know that was a joke, but destructive actions should never be the result of a GET request anyway - for exactly that sort of reason. GET should just get a page, and should be (relatively) repeatable. Modification should only happen on a POST.
why the hell are you making GET requests modify data? That's what POST is for.
GET should only do just that, and a user agent should be allowed to reload a page that is the result of a GET request without fear of side effects.
You'll have trouble from more than bots if you've got an app written like that - you'll have users hitting the back and forward buttons on their browsers causing multiple entry.
[OT] Slow Down Cowboy!
Slashdot requires you to wait 2 minutes between each successful posting of a comment to allow everyone a fair chance at posting a comment.
It's been 8 minutes since you last successfully posted a comment
Good to see slashcode living up to its usual high quality standards [/OT]
Slashdot Mirror
heh - that's the thing - IANAGC (I Am Not A GUI Coder).
I can't comment on JBuilder's usefulness for GUI programming, and in fact most of the time it never even occurs to me that people write GUIs in Java.
Most of my work is in command line applications, libraries and server applications.
It probably is a personal preference thing then, because for the most part, you experiences with JBuilder seem to match mine with Eclipse.
;)
Though I will note that the first thing I disable is the auto quote closing
Anyone who says JBuilder is better has most likely never used anything but JBuilder, short of installing and compiling Hello World.
When I first started using JBuilder instead of gvim, I was pretty impressed - there were all sorts of things it did that you just couldn't do in a standard text editor - code completion, refactoring, etc.
Then I tried Eclipse, and I saw how good those features can be when they actually work.
At my workplace most of the other Java developers use JBuilder, because that's what we paid (obscenely) for, and because they've never used anything else.
I use it when I need to ensure that my Eclipse projects still work with JBuilder, and when dealing with their projects for one off fixes that don't warrant migrating the project to Eclipse.
From what I can tell, JBuilder is the best IDE in the industry for pretty wizards that break your code, and check box features you never need that PHBs use to justify their $6000(Au) per developer investment.
Eclipse on the other hand just makes writing code easy.
I haven't used any other IDEs so I can't comment as to whether or not Eclipse is any better than them, but I _do_ know that JBuilder doesn't even come close when it comes to the everyday writing of Java code.
How sure are you that the other person really _does_ know what you're (not your) talking about?
Sometimes poor grammar and spelling is harmless, but other times a single missed comma or misspelt word is enough to completely change the meaning of a sentence.
Also, a lot of people seem to think that it's a black and white issue - but it's not.
Not all mistakes are equal. There are often people that get overly worked up about things that are more a matter of style rather than grammar, but in other cases people will strongly defend their "right" to create completely nonsensical sentences and call it "communication".
A few seconds extra to proofread and run a spell checker over your emails and posts is a small price to pay to improve the chances that you'll be understood and decrease the likelihood that you'll look like an idiot.
> Exactly. Which is dramatically different from the claim that 'Linux scales to 512 processors for general purpose work'.
Yes, but is much closer to the original statement (before the clustering and SGI silliness) of 'Obviously you wouldn't want to run Linux on a massive 64 processor server'.
> Which it is reasonable to do with Linux on carefully designed 16-way or 32-way systems.
Once you get to 32 way or above then the system is going to have to be carefully designed regardless of the operating system running on it.
This one big enough for you?
up to 64 processors - 32 Xeons, and 32 Itanic 2s
And yes it runs Linux.
Obviously you'd only get a maximum of 32 processors per partition though.
Unisys only offer Windows, Linux and their own legacy mainframe OS - no Solaris in sight, though they used to support SCO as their Unix OS.
Unisys's market is very definitely enterprise servers for running databases, business processing and application servers, not HPC.
Why did you use all that C++ crap to discuss an example that could have just as easily been standard C (which is what I immediately assumed), C# or Java?.
Simply saying "When i rolls over, it'll eventually become <= 0", or using pseudo code would have been sufficient, and prevented those of us who aren't C++ programmers from digging through verbose, unfamiliar syntax to try to figure out what you're saying.
When communicating with others, it usually pays to be clear and concise, not clever if you want to get your message across.
But in any case, the actual _point_ on the statement was not that the loop would be infinite (or not), but that it was obviously wrong.
Your point that we couldn't tell that it was obviously wrong because we didn't know what it was supposed to do in the first place just goes to further prove the original point.
Whilst you couldn't be _certain_ that while(i > 0)i++; is wrong, it _looks_ wrong, (or at least the wrong approach if the outcome happens to be correct) to anyone with any programming experience.
Getting a computer to instantly tell that something "looks" wrong would be quite an achievement.
Texture quality, 5.1 sound, hard drive (have you seen the size of Morrowind saved games!) and out of the box support for > 2 controllers are why I prefer the XBox.
Better controller and smooth framerate with no tearing or stuttering is why I prefer the PS2.
In general, both have some games that look better than some games on the other - but most are pretty much the same, though I do appreciate the better textures on the XBox.
It looks like the PS3 and XBox 360 will be more or less identical from my point of view. But I have a feeling I'll be leaning towards the XBox 360 due to not having to pay extra for the hard drive.
It'll all come down to the games though.
> Perhaps you missed that the individual who submitted the article to slashdot is the author of the review, and owner of the site it is on?
That's how book reviews on Slashdot _always_ work.
Someone writes a review and submits it to slashdot. They don't submit someone else's review - that would be a copyright issue at best, and plagiarism at worst.
It just happens that in this case the person who submitted the review also has it on his web site, so he linked to it. That's fair enough if you ask me, and a few reviewers have done that in the past.
If the concept bugs you, then turn off the review section in your preferences, because pretty much every review will be like that.
use MyEclipseIDE instead...
Excellent Struts support, as well as plenty of other J2EE features. Not free, but _very_ cheap considering it makes Eclipse a serious competitor to JBuilder Enterprise (or probably more accurately makes JBuilder not any threat to Eclipse).
Eclipse includes its own incremental compiler.
You never have to do a separate "build" step for most Java projects, just save the file and run the app.
> Mu covers your answers and all possible ones like it.
No it doesn't, because to the average english speaking person, "Mu" is quite rightly a nonsense answer.
You might as well answer "Ekky-ekky-ekky-ekky-z'Bang, zoom-Boing, z'nourrrwringmm"
If you _really_ want to answer "Mu", rather than something useful and specific, then why not answer with "Your question cannot be answered because it depends on incorrect assumptions"?
That way you don't have the other person staring at you blankly trying to figure out if you've admitted to beating your wife.
Except that it's not.
If it's permissible to answer a yes / no question with something other than yes or no, then it must be permissible to answer with something a little less nonsensical, such as "I don't have a wife", or "I have never beaten my wife".
> How do these poor people (the new authors, not the library crowd) survive
They have a real job, or they have a partner with one.
very few published authors could even think of living off their writing - and if they do, it's not through book sales, it's through things like giving talks at schools and offering writing workshops...
Actually, from what I understand it's the kde-education package that will probably see the most use from this.
In particular applications like KStars - possibly one of KDE's best (and least publicised) applications.
Clicking on a star or galaxy and getting the information from Wikipedia from it would be brilliant.
Looks like you put the wrong link in.
From the project description
did you mean this -
Q: "Like WinSite? Or TuCows?"
;)
A: "You mean time limited, cripled, and full of ads and nag screens? No, nothing like WinSite or TuCows.
Completely free, unencumbered, unrestricted, nag free, ad free, forever. And you get the source if you want, but you probably don't care about that"
Switching to Linux is worth it just to escape the insane world of Windows shareware where people seriously expect you to pay $50 for the crapy semi functional app they spent 2 hours in VB on.
At least in the open source world the crappy semi functional app that someone spent two hours in perl on doesn't cost you anything
The point is that the interest in reto computing is keeping the _knowledge_ required to convert the stream of data to something useful.
Things like old manuals and spec sheets that might tell you exactly what encoding is used in the data. (Since manuals actually contained real information in those days, rather than being purely a vehicle for "Screw you, don't blame us" EULAs and disclaimers)
when do you send your credit card information over the internet in plaintext?
No, the point is that if you go back in time and try to change things the reality you experienced before you did so was already the result of you going back in time and trying to change things.
So when you went back, you could try to do all sorts of things, but whatever you did, the result would be what had already happened before you did so, because it's already happened.
I'm sure someone could take this and warp it to prove that there is no free will, and that we are all marching towards our predetermined fate.
Hmmm, I think I've been there once.
;)
It was scary
I know that was a joke, but destructive actions should never be the result of a GET request anyway - for exactly that sort of reason.
GET should just get a page, and should be (relatively) repeatable. Modification should only happen on a POST.
that doesn't work.
xa-b != x(a-b)
> Anyone coming from a disgusting culture such as that should leave that culture and its horrible indecent practices behind.
Well presumably in the example put forth that is exactly what has happened.
why the hell are you making GET requests modify data? That's what POST is for.
GET should only do just that, and a user agent should be allowed to reload a page that is the result of a GET request without fear of side effects.
You'll have trouble from more than bots if you've got an app written like that - you'll have users hitting the back and forward buttons on their browsers causing multiple entry.
[OT]
Slow Down Cowboy!
Slashdot requires you to wait 2 minutes between each successful posting of a comment to allow everyone a fair chance at posting a comment.
It's been 8 minutes since you last successfully posted a comment
Good to see slashcode living up to its usual high quality standards
[/OT]