On 2010.09.07 3:10, droopcat wrote:
Seriously, Eclipse isn't the same thing as Visual Studio. It's not
produced by a monolithic company that imposes cradle-to-grave decisions
on what development to their platform entails (and what it will not entail).
Eclipse is developed by a world-wide community who aren't specifically
remunerated for this. Unlike VS, it supports and targets nearly all
possible platforms.
No Real Name wrote on Tue, 07 September 2010 05:10 |
Compared to visual studio Eclipse is not even worthy of standing in its shadow. |
On 2012.03.01 19:51, Perhaps if you were a little more patient and willing to get help (in
your case, from the Eclipse PDT forum), you'd be successful too.
Eclipse has it's flaws but it's the best out there.
I2.) When editing color schemes, you cant just click on a symbol type in the preview and have it select what you are configuring. You have to select it from a drop down menu... that is totally stupid/frustrating and not fast or easy... were engineers here, time=money.
...
But there is a light at the end of the tunnel. Google decide to finally dump this and create a nice IDE based on probably the only usable java ide.
Android Studio is great so far (although missing some features for now). Speed is as expected, moves very natural, no bugs, no restart. When it will reach production, half of Eclipse users will move to it.
Let's hope this happens soon, I'm about to put a fist through my monitors if I have to see Eclipse for much longer....
Am 23.01.2014 18:06, schrieb Nitin Dahyabhai:
> "Disabling automatic builds may cause content assist and other functionality to fail."
>
> I don't think I've ever seen that message. Where were you in the UI when that message appeared? What version of
> Eclipse was this?
I think that can't be the ppint of this discussion. Clearly all functionality that depends on parsed and compiled
sources has to fail when building is turned off, whether this message appears or not.
We all got used to incremental building and we rely on it not interfering unnecessarily with our manual interactions.
For me the worst is not when something doesn't work, i.e., doesn't deliver the correct result, but when it freezes the
IDE and hinders my further interaction. I can understand those who can't accept that - and have alternatives.
When I use an adjustable wrench working on my car, it works the way it
works. I don't expect it to serve me a Martini in addition to tightening
or loosening bolts. And if I'm in a tight spot, it's going to be hard to
tighten or loosen bolts with it.
Now for example all my breakpoints do not work, restarted Eclipse - did not help. I mean seriously? - breakpoints do not work... debug is gone.