Look, I realize you don't like it, but why would you start with the thread off with "Eclipse Sucks.", with a period too. It sounds really aggressive, and like you are about to devolve into a rant. But, weirdly enough, the title is much more rage-y then the post itself, which tries to stay calm? Make up your mind, are you really crazily mad and think everyone else should hate eclipse too or trying to find like minded people who also have alternatives.
Quote:
Originally Posted by mathking
When I first started teaching, a lot of the "old timers" argued that we should always teach Assembly first, and command line compiling, so students understand "how it really works." They somehow always used a race car analogy: "You wouldn't want a race car drive who didn't understand how the engine works." There are two main problems with this, in my opinion. The first is that they are arguing that Java (or when I first started Pascal, Fortran or C) is an abstraction so students should learn Assembly first.
|
Totally agree with you. Back in my day, we didn't deal with abstractions. If a programmer wanted to contribute to the code, they would have to join as a freshman, spend three years progressing through the ranks of wiring up GAL programmers, learning how to bit-bang memory instructions, studying advanced electron theory, memorizing the architecture and pin diagrams of all the components of the cRIO, and writing a custom *nix kernel. Finally, once they had completed all these tasks, they would be allowed to spend their final junior summer reverse-engineering the Netbeans program and FRC deployment tools. Unfortunately, it was all in vain because FIRST decided to switch to the roboRIO and deprecate the Netbeans plugins, and because our programming team had no idea how to abstract, we lost years of experience and none of the second, third, or fourth-year programmers understand how the robot works. We were all out of luck until, of all people, a freshman came into the programming department and told us about wpilib.screenstepslive.com. After a few minutes of him explaining to us why we could not just curl the website, but would have to use an internet browser (who knew people hosted images on their server to be displayed right next to text!), we finally realized our mistake. We didn't need to know the architecture! Or the pin diagrams! We can simply let someone write different code, on different platforms, across all devices, but the code all operates the same way! That way, no matter what device we are on, every memory address is accessed an approximately similar command. If only people had realized this decades before us!