Agreed. I've been doing professional software development for too long, so I never have to pay for my tools. I have to admit, that if I didn't have an IDEA license I would probably be an Eclipse user.
Eclipse isn't bad, and you certainly can't beat the price. But once you tried IDEA, it's hard to back to something else.
I really shouldn't post this, since it encourages lazyness, but I'm constantly amazed at the imabiity of sladhdot readers to find information for themselevs. Here's a quote from Sun's FAQ for the Java Desktop System:
15.
Q.
How much does Java Desktop System sell for?
A.
There are two available pricing options for Java Desktop System:
* $100 / desktop / year
* $50 / employee / year for customers who wish to purchase Java Desktop System for all employees of their company.
* A special promotion is also planned that reduces by 50% the first year price of either of the above two options. This promotion is in effect until June 2, 2004.
If you are prepared to pay a little (not much) you really should try IDEA. It's the tool that Ecplipse tries to emulate. Eclipse does have many of the features IDEA has (not all though) but IDEA just does it much faster and with fewer keypresses.
Yes, Eclipse is much faster than NetBeans, but IDEA is faster.
.net follows the typical old Microsoft mantra: "Make the simple things very easy, ignore the complex things (because then you already locked in the user)".
Java on the other hand takes a bit more effort to understand, but it's a lot more flexible than.net. You mentioned some good examples for this. It's very easy to just point and click your way to some remote calls, but when you want to make a real app, and start to think about stuff like security you have to jump through all sorts of hoops to just get it to work, and the solution is everything but elegant.
Some other examples of their attitude are: VB, their "wizards", Windows configuration panels.
Well, that sounds all good. But Microsoft doesn't follow that principle. This is what I heard (parphrased) from one of their support guys after having spoken maybe 10-15 minutes about a problem I had:
Sorry, I have to answer some other customers calls now so I don' thave time to speak to you anymore. Bye.
And that was the end of the call. Before he hung up I managed to wring him out of a support call ID, but I don't think I ever followed up on this.
You mustn't know a lot of Flight Simmers then? These things draw enormous amounts of power from the machines, and not even the highest end machines today can run IL-2 Sturmovik with full graphics in the most complex missions yet. Also, most non-trivial missions in Lock on requires lots of GHz, not to mention a good graphics card.
It all depends on what you use your machine for. Flight sims require a major part of the available CPU to deal with the AI, something not really needed for most other types of games.
There is one big well known fork: The GNU Emacs vs. XEmacs fork.
Re:A first step, but Unicode support is incomplete
on
JOE Hits 3.0
·
· Score: 1
And you know of a lot of keyboards that are able to input the arrow symbols or the mathematical symbols? Those are in the BMP.
My keyboard does not allow me to type in those symboles, but it definately doen't prevent me from using them.
Re:A first step, but Unicode support is incomplete
on
JOE Hits 3.0
·
· Score: 1
Funny you should mention that. What you said is both true and conpletely false at the same time.
Allow me to quote RFC 3629:
ISO/IEC 10646 [ISO.10646] defines a large character set called the Universal Character Set (UCS), which encompasses most of the world's writing systems. The same set of characters is defined by the Unicode standard [UNICODE], which further defines additional character properties...
So, yes, the U means universal, but it refers to the same character set as Unicode.
Re:A first step, but Unicode support is incomplete
on
JOE Hits 3.0
·
· Score: 1
Right, but their UTF-8 support doesnt work. It totally breaks the file for perfectly valid UTF-8.
It only supports a small subset of UTF-8.
Oh, and another thing: The U in UTF means "unicode".
A first step, but Unicode support is incomplete
on
JOE Hits 3.0
·
· Score: 4, Informative
Joe does not have proper unicode support, contrary to what many people claim. It only supports BMP, the fist 64K of characters out of the more than 1 million possible characters.
If you load a file with non-BMP characters in it they will come out as garbage. If you try to input any such characters it will mess up every single characters except those with a code point less than 128.
True enough that IRC was made back in the day when character encoding wasn't a real issue. It is today, however, but I guess I've been using IRC long enough that I just don't think of being able to communicate in Japanese or other such non-roman language.
That's what you think. It happens to me very often that I need to type a single word in cyrrilic, or use some mathematical symbols (very useful when talking maths), or just use some of the nice symbols like arrows or why not the different types of accents available.
The fact is that UTF-8 solves a lot of problems the ASCII generation hasn't even thought about. It adds an extra dimension once you start using them on IRC. I recommend you try it.
And as far as netsplits go.. I'm not really sure how a better written protocol can really defend against DoS attacks and overloading.
I can testify to using DCC for legit reasons. It's a very useful tool when you want to send a file to someone you are talking to.
Maybe you should try to use your computer for something else apart from sending pirated music to your friends and you'll realise that there are other uses for file transfer?
Anyone who ever implemented the IRC procotol knows just how crappy it is. Here's a few reasons:
Nicknames use SW-ASCII, yes that's right, the swedish variant of 7-bit ascii. That's the reason [ and { are equivalent, as is | and \.
There are no standard encoding. Most people use 8859-1, other languages use, well, whatever they happen to agree on. A number of other channels use UTF-8 which is the best solution (supports all languages) but is not supported by mirc.
Takeovers, splits, need I say more?
Server desync
I don't think DCC is a problem at all. It's all the other crap that needs to be fixed. Once you do, I'm pretty sure implementing good file transfers will be quite simple.
Slashdot Mirror
Go back and read the message I was replying to. You really should have done that before replying.
Eclipse isn't bad, and you certainly can't beat the price. But once you tried IDEA, it's hard to back to something else.
15. Q. How much does Java Desktop System sell for?
A. There are two available pricing options for Java Desktop System:
* $100 / desktop / year
* $50 / employee / year for customers who wish to purchase Java Desktop System for all employees of their company.
* A special promotion is also planned that reduces by 50% the first year price of either of the above two options. This promotion is in effect until June 2, 2004.
And posting the correct link woul have been better.
Yes, Eclipse is much faster than NetBeans, but IDEA is faster.
No, I'm saying that if you have problems you should at least make an attempt to solve it before bitching about the quality of the product.
It work here very well. Maybe he should help out to try to solve his problem instead of writing inflammatory articles.
Java on the other hand takes a bit more effort to understand, but it's a lot more flexible than .net. You mentioned some good examples for this. It's very easy to just point and click your way to some remote calls, but when you want to make a real app, and start to think about stuff like security you have to jump through all sorts of hoops to just get it to work, and the solution is everything but elegant.
Some other examples of their attitude are: VB, their "wizards", Windows configuration panels.
Technically, when you use the SunFire link it's not a cluster. It's a single machine, and you can run a single OS image on them.
I called from sweden, and I spoke swedish to the person. I suppose he was located in Stockholm, but I have no way of knowing.
So I still think the original estimate was pretty good.
Maybe they aren't out to fool anyone? Maybe they just don't want to use the "win" term openly? Remember lindows?
It all depends on what you use your machine for. Flight sims require a major part of the available CPU to deal with the AI, something not really needed for most other types of games.
There is one big well known fork: The GNU Emacs vs. XEmacs fork.
My keyboard does not allow me to type in those symboles, but it definately doen't prevent me from using them.
Allow me to quote RFC 3629:
So, yes, the U means universal, but it refers to the same character set as Unicode.And, for your reference, here's the link to the RFC 3629, and the link to the Unicode web site.
It only supports a small subset of UTF-8.
Oh, and another thing: The U in UTF means "unicode".
If you load a file with non-BMP characters in it they will come out as garbage. If you try to input any such characters it will mess up every single characters except those with a code point less than 128.
Don't you think it would be even easier if just mirc got their act together and implemented UTF-8 support?
The fact is that UTF-8 solves a lot of problems the ASCII generation hasn't even thought about. It adds an extra dimension once you start using them on IRC. I recommend you try it.
An automatically-rerouting network perhaps?I happen to be swedish. :-) Still hate the damn protocol though.
Maybe you should try to use your computer for something else apart from sending pirated music to your friends and you'll realise that there are other uses for file transfer?
Nicknames use SW-ASCII, yes that's right, the swedish variant of 7-bit ascii. That's the reason [ and { are equivalent, as is | and \.
There are no standard encoding. Most people use 8859-1, other languages use, well, whatever they happen to agree on. A number of other channels use UTF-8 which is the best solution (supports all languages) but is not supported by mirc.
Takeovers, splits, need I say more?
Server desync
I don't think DCC is a problem at all. It's all the other crap that needs to be fixed. Once you do, I'm pretty sure implementing good file transfers will be quite simple.