We're 1 month past mid 2005. I know I'm gonna be getting a haircut in 2007 and I know that's good planning, but I know for a fact that my hair is gonna grow longer then (if I'm not bald then). Who knows what's gonna happen to the console world 1.5 years down the road? Maybe this will be out then? ---> http://www.phantom.net/
Re:Installation, bugs, first impressions
on
Eclipse 2.0 Released
·
· Score: 3, Informative
On Windows (NT 4.0 SP6), I didn't get any errors except when I tried to build some big projects (Out of memory error), adding "-vmargs -Xmx256M" to the startup command fixed that.
54MB is huge, but the convenience that the editor brings make it worth the download.
Best thing I like so far is the organize imports feature (it automatically finds classes you have used in the library and and writes import statements for you automatically), no more api lookup and then copy/paste the package names, and it writes the import statements with each class that's used listed line by line so you know exactly what classes you're using in your code.
Only thing I don't like now is the lack of external directory classpath support. Java allows classpath that ends with a directory but Eclipse forces you to jar up your libraries, which is not a major problem in itself but just inconvenient.
Speed is definitely acceptable (on Windows at least). Of course it's no vi's or notepad's speed but then again which IDE is?
Re:VisualAge for Java`
on
Java IDEs?
·
· Score: 2, Insightful
I like the way VAJ is designed. The project/package/class/method (and file-less) organization is logical. The repository might get one in trouble if it's not backed up frequently (though a third party source control tool could overcome that pretty easily). Incremental compilation is good as the project gets bigger and bigger. I still haven't tried writing event-driven systems with it but based on what I read it seems to have pretty good support for event-driven coding.
My only concern are its steep learning curve, difficult to use different version of jdk and pretty slow response. As with other IDEs it requires you to work in a certain way.
On a side note, I think a good IDE should have a good documentation system that integrates with other software design tools so that requirements can be reflected in the code/doc easily. It'd be a dream come true if I look at any part of a project (design/doc/code) and from there get to the other part of the project easily to allow me to view from the big picture all the way to the smallest detail real quick. Then again I don't have experience designing big enough system to really have an idea of how the doc should be integrated with the design. If anyone here has a good idea of how it should work I'd like to hear about it.
Who else are they trying to piss off?
on
$1200 Cheap!
·
· Score: 1
They pissed off Sony and Nintendo, and now they want to piss off the consumers and worst of all, other game publishers.
Huh, now I know why.
I'll probably get flamed for this, but I think the time spent on this research is well worth it. Think about how many people go to showers everyday (except for a few) and few actually realize what's going on with the shower curtain.
Another question answered!
Slashdot Mirror
Man this is cool. Very cool.
Now I know why there's no new episodes of McGyver on TV anymore.
We're 1 month past mid 2005. I know I'm gonna be getting a haircut in 2007 and I know that's good planning, but I know for a fact that my hair is gonna grow longer then (if I'm not bald then). Who knows what's gonna happen to the console world 1.5 years down the road? Maybe this will be out then? ---> http://www.phantom.net/
On Windows (NT 4.0 SP6), I didn't get any errors except when I tried to build some big projects (Out of memory error), adding "-vmargs -Xmx256M" to the startup command fixed that.
54MB is huge, but the convenience that the editor brings make it worth the download.
Best thing I like so far is the organize imports feature (it automatically finds classes you have used in the library and and writes import statements for you automatically), no more api lookup and then copy/paste the package names, and it writes the import statements with each class that's used listed line by line so you know exactly what classes you're using in your code.
Only thing I don't like now is the lack of external directory classpath support. Java allows classpath that ends with a directory but Eclipse forces you to jar up your libraries, which is not a major problem in itself but just inconvenient.
Speed is definitely acceptable (on Windows at least). Of course it's no vi's or notepad's speed but then again which IDE is?
I like the way VAJ is designed. The project/package/class/method (and file-less) organization is logical. The repository might get one in trouble if it's not backed up frequently (though a third party source control tool could overcome that pretty easily). Incremental compilation is good as the project gets bigger and bigger. I still haven't tried writing event-driven systems with it but based on what I read it seems to have pretty good support for event-driven coding.
My only concern are its steep learning curve, difficult to use different version of jdk and pretty slow response. As with other IDEs it requires you to work in a certain way.
On a side note, I think a good IDE should have a good documentation system that integrates with other software design tools so that requirements can be reflected in the code/doc easily. It'd be a dream come true if I look at any part of a project (design/doc/code) and from there get to the other part of the project easily to allow me to view from the big picture all the way to the smallest detail real quick. Then again I don't have experience designing big enough system to really have an idea of how the doc should be integrated with the design. If anyone here has a good idea of how it should work I'd like to hear about it.
They pissed off Sony and Nintendo, and now they want to piss off the consumers and worst of all, other game publishers.
Way to go M$!
Huh, now I know why. I'll probably get flamed for this, but I think the time spent on this research is well worth it. Think about how many people go to showers everyday (except for a few) and few actually realize what's going on with the shower curtain. Another question answered!