5 ms·

I learned programming with Eclipse default settings and Java, on a PC with a classic AZERTY straight keyboard with 105 keys layed out in the classic way. At som

I learned programming with Eclipse default settings and Java, on a PC with a classic AZERTY straight keyboard with 105 keys layed out in the classic way. At some point there's not debate, yeah Java is crap, yeah Eclipse is laggy, etc, but my hands, brain and code work completely in concert when all those are united and there's no question that I can get anything done much, much faster with these. I actually gave up on using a macbook after a year and a half of constant practice because it still felt far too tiring to build my android apps compared to the PC, even though it was still Java and Eclipse. It would be the equivalent of speaking your mother language (or native tongue or first language, whatever you english-speaking people call it :P) vs speaking a language with which you're "only" fluent when you just have to express a point very fast. I'm not saying Notch is in the same situation (or anyone else actually), just that there are reasons, beyond being able to get things done using just the available tools, to use a setup that is often seen as suboptimal.

swah 15y ago
Doesn't look laggy on his PC though...
- ditoa 15y ago
  I use vanilla Eclipse on a 3 year old Dell Studio laptop (2.53Ghz C2D, 4GB RAM, 2x320GB 7200RPM HDD, AMD Mobility Radeon 3650 HD, Windows 7 Ultimate SP1 x64) and it runs perfectly smooth. Just as smooth as in Notch's video. I have no idea what people load their computers with to make them run so poorly :-/
  - babebridou 15y ago
    To be honest I don't know either. Eclipse has always runned fine until the rare day when some plugin goes overboard and destroys all hope. Last year for instance I've had bad issues with autocompletion on some huge classes (GLES20 I'm looking at you), but 1) that was when I was struggling on the macbook already, and 2) Someone fixed the problem somehow while I was busy downgrading to a stable version. Eclipse kicks ass. I only said it was laggy out of mercy for the people who can't get productive with it.
  - skore 15y ago
    Eclipse being laggy has a lot to do with what extensions and editors you install. If you know how to configure your setup correctly (ie. not install a huge all-in-one package with tons of crap you will never need, compare different extensions that are similar in functionality and choose for performance), it will be smooth. For me, coding in PHP is a good example - I tried a handful of editors and settled on the dinosaur PHPeclipse instead of some flashy PDT. It has better highlighting (to me, at least - probably only because it's the kind of highlighting I'm used to) and runs fast as a cheetah (I have a shameful couple of files that rank in the 20k+ lines and PDT would stutter on those... when I was moving the cursor). The final issue most people cite is startup time and so far, the only remedy I have found for that is keeping your workspace folder tidy and using an SSD.

swah 15y ago

Doesn't look laggy on his PC though...

ditoa 15y ago
I use vanilla Eclipse on a 3 year old Dell Studio laptop (2.53Ghz C2D, 4GB RAM, 2x320GB 7200RPM HDD, AMD Mobility Radeon 3650 HD, Windows 7 Ultimate SP1 x64) and it runs perfectly smooth. Just as smooth as in Notch's video. I have no idea what people load their computers with to make them run so poorly :-/
- babebridou 15y ago
  To be honest I don't know either. Eclipse has always runned fine until the rare day when some plugin goes overboard and destroys all hope. Last year for instance I've had bad issues with autocompletion on some huge classes (GLES20 I'm looking at you), but 1) that was when I was struggling on the macbook already, and 2) Someone fixed the problem somehow while I was busy downgrading to a stable version. Eclipse kicks ass. I only said it was laggy out of mercy for the people who can't get productive with it.
- skore 15y ago
  Eclipse being laggy has a lot to do with what extensions and editors you install. If you know how to configure your setup correctly (ie. not install a huge all-in-one package with tons of crap you will never need, compare different extensions that are similar in functionality and choose for performance), it will be smooth. For me, coding in PHP is a good example - I tried a handful of editors and settled on the dinosaur PHPeclipse instead of some flashy PDT. It has better highlighting (to me, at least - probably only because it's the kind of highlighting I'm used to) and runs fast as a cheetah (I have a shameful couple of files that rank in the 20k+ lines and PDT would stutter on those... when I was moving the cursor). The final issue most people cite is startup time and so far, the only remedy I have found for that is keeping your workspace folder tidy and using an SSD.