7 ms·
On the one hand, I'm pleased that someone is posting this in the new-fangled bloggy tutorial style popular among the youth of today. It's nice to see my preferr
by ajross 14y ago
On the one hand, I'm pleased that someone is posting this in the new-fangled bloggy tutorial style popular among the youth of today. It's nice to see my preferred environment evangelized.
On the other, it's a giant facepalm that the simplest, best documented, most powerful development tradition of the last 40 years actually needs this treatment. That there is a whole generation of developers who come out of school thinking that "building" is the action of pressing a button in an IDE GUI (and that "writing a program" means launching a big wizard that pukes a dozen files into a new directory) is just depressing.
Oh, and get off my lawn.
- BrainInAJar 14y ago> thinking that "building" is the action of pressing a button in an IDE GUI (and that "writing a program" means launching a big wizard that pukes a dozen files into a new directory) is just depressing. I use UNIX as my IDE almost exclusively. When it comes to Java however, I don't think there's any way to avoid using Eclipse or Netbeans or something. Any nontrivial Java project is going to be convoluted enough that using the traditional tools is an exercise in futility.
- debacle 14y agoant was built specifically for building large Java projects, was it not?
- strictfp 14y agoI thought that it was written to prove that the supposedly declarative data format of xml still is vulnerable to imperative misuse. :)
- mseebach 14y agoNeeding an IDE for Java in my experience has to do with two things: The amount of boiler plate and really good refactoring tools/autocomplete. Building the project is not really that difficult, and make can be made to do it just fine.
- x1 14y agoI grudgingly agree. It is frustrating but something created while using an IDE tends to create specific ways of thinking. For example, most IDE developers tend to love their debuggers... want to learn something? Just run the debugger! Want to debug something, hey run that debugger and watch 'dem breakpoints! When I code without a debugger I tend to write smaller, easier testable code because I lack a real way to step through a convoluted process. I feel this encourages a simpler application (but I have no study to prove that). Another example is most Java/C# work tends to be in the center of the unknown universe. You are editing something twelve layers deep in a mess of public/private/protected objects and you aren't sure if the item you should call is the MarginalFlowStateController or the ControllingMarginalFlowState... with an IDE you would just open up both of them, their unit tests, and any documentation until you discover which one you should be calling. It bothers me because I really enjoy my vi/tmux development environment where every time I :w a file and run a test I am running on virtually the exact same environment as dev/qa/pre/prod.
- nradov 14y agoWhile writing small, easily testable code is a good practice it isn't sufficient. Running your code in a debugger and actually watching things happen exposes a lot of bugs and inefficiencies that tests don't tend to catch. Getting that dynamic view of control flow and state is a huge advantage for improving quality.
- x1 14y agoMeh, I think you are over-inflating the benefits of a debugger. Everything you described can be achieved through proper testing. Want to know if something is efficient? Then build a test to gauge it. That way if it changes and becomes less efficient in the future your test will break. That's a much more solid approach than simply walking through the code a couple times and noticing something out of place.
- eropple 14y ago> Meh, I think you are over-inflating the benefits of a debugger. Everything you described can be achieved through proper testing. You're falling into the trap of "one tool to solve all problems." Why waste your time writing tests to "gauge efficiency" when a profiler tells you more, more effectively?
- bluekeybox 14y agoI don't think anyone is saying that IDEs like Eclipse or Xcode or Visual Studio do not have a place. They absolutely do. HOWEVER: (1) from my experience of working with people fresh out of school who were exclusively familiar only with the IDE way of building programs and who knew little to nothing about the command line tools -- such people were curiously unaware that many tasks (testing for example) could be automated. People who used command line extensively, on the other hand, would be the first ones to write a simple script that performed testing of their program. Testing is just one example (I'm sure there are many IDE-tailored solutions for it). There are other things that are done repetitively; using an IDE can mold one into thinking that such tasks are impossible to automate and that they can only be performed by clicking buttons. (2) (Again this is about people either in school or fresh out of it -- certainly not about highly professional IDE users). People who were taught IDE first and who are not familiar with the command line will often assume that running command line utilities is an old-fashioned way and that they are more "modern" (therefore somehow "better") programmers just because they are using a GUI. Such people will then go on to write programs that completely ignore the standard way of interacting with the shell, even if their programs do run from the command line. One example: One of the programmers (who used exclusively GUIs for building programs) would write command-line utilities which, when outputting a text file, would place '\n' at the beginning of each line and not at the end, which then resulted in parts of the output being truncated when I ran them through sed/gnuplot/whatever. Firthermore, even though his programs were quite complicated (read: painful to debug), he had no idea what the difference between stderr and stdout was, and would write any errors that would come up to stdout. The same programmer was then curiously defensive when I told him that his way of doing it was wrong (his answer basically was: "I've been programming for a long time, and I've always done it that way, and I don't care that my programs don't play nice with that sed thing with which I'm not familiar with").
- roguecoder 14y agoI have encountered the inverse: 1) People who exclusively use the command line, especially when recently graduated, have extreme difficulty thinking in an OO fashion, because they have not had the tools to support exploring inheritance and call stacks the way someone with a visual OO development environment has (Smalltalk is ideal for this.) 2) People who have used the command line exclusively are content without visualizations, which can be massively more effective at conveying information, especially about performance and architecture. 3) People who have used the command line exclusively are less likely to employ refactoring tools and more likely to tolerate long, poorly factored code because vim/emacs makes it easy to navigate and ignore the ugliness. 4) People who have used the command line exclusively, especially when they are recent graduates, believe that their approach is inherently better and necessary in order to be a good developer. They get curiously defensive if you expect them to be able to instantly jump to the definition of a method in question or actually use the Strategy pattern.
- lftl 14y agoHaving just picked up Android development (and my first real usage of Java), I've been pretty happy using eclim (http://eclim.org/ http://eclim.org/). It bridges the gap nicely, I get eclipse's error checking, decent completion, automated import statements, refactoring, etc. all inside vim. The only two features I've found myself bouncing into eclipse for are the debugger, and android GUI layout previews.
- stonemetal 14y agoUnderstanding the process of building has zero to do with knowing how to type make, or knowing the exact command line parameters GCC needs. Confusing a few cli commands with the process of building is just as bad as believing in the big magic button.
- ajross 14y agoOf course. But one environment scales and the other doesn't. A IDE user who only knows how to modify projects by adding files and clicking checkboxes for optimization settings will do that for the rest of their career. A CLI user who needs to edit makefiles will eventually have a vastly more powerful tool in the shed.
- cooldeal 14y ago>A CLI user who needs to edit makefiles will eventually have a vastly more powerful tool in the shed That is true if the user didn't already give up and leave programming completely due to the obtuseness and complexity of autotools,makefiles, m4,macros and workarounds like cmake.I survived it, but many others in my Masters class did not. http://esr.ibiblio.org/?p=1877 http://esr.ibiblio.org/?p=1877 If even ESR finds them troublesome, what hope does a beginner have? >Of course. But one environment scales and the other doesn't. A IDE user who only knows how to modify projects by adding files and clicking checkboxes for optimization settings will do that for the rest of their career Using an IDE does not mean that you cannot do advanced configuration, including setting options that change the commandline of the compiler used. Don't almost all GUIs call commandline compilers on the backend? Visual Studio even shows you the commandline being used when you hit the Build button. SQL Server usually has a "Script" button to generate script for a admin GUI option and you can do anything you can do in the IIS GUI with Power Shell. The power should be there for when you need it, but making everyone go through arcane options has the unfortunate side effect of making the tool less popular though it does show the power of the tool to the novice user.
- ajross 14y agoThis is the kind of discourse that shows the disconnect. I'm sorry, but programming is complicated. You're seriously claiming that someone who can intelligently navigate the rats nest that is the J2SE library environment can't handle autotools (and for the record: autotools really isn't what I'm talking about)? Please. It's just laziness and aesthetics. One looks shiny and new, and the other crufty and old. People like to play with shiny new toys. And, sigh, "advanced configuration" is certainly something more than setting compiler flags. That was sarcasm, intended to show the limit that IDE users hit trying to extend their tools. For a practical example, how about this: conditionally build the modules of your C/C++ project such that they can be either linked in statically to the main binary or loaded dynamically, and generate both versions in a standard build. Someone who knows how the linker works and how to write a makefile can do this in a day, easily. Someone who only knows the IDE will be lost; there's no button for that. They'd probably hack up some monstrosity involving thousand-line boilerplate like building all the modules as separate subprojects or some nonsense.
- horsehead 14y agoI take it from reading this and other posts that cutting my programming teeth by learning to code in gedit and the command line, sans dev tools, is a good approach then?
- x1 14y agoI wouldn't go that far. The best way to learn something is through whatever method encourages you to learn. For some that is starting from zero, others want to start at the highest level and work backwards, others start in the middle and jump around. Whatever can keep you interested.
- phren0logy 14y agoI agree with x1 that you should start with whatever will keep you going. If the command line appeals to you, check out Zed Shaw's "Learn C the Hard Way." It is not at all sans dev tools, but it will have you using sophisticated CLI tools rather than a GUI. I have found it to be a good fit for me personally, and I suspect I'm not alone.
- shanemhansen 14y agogedit's not bad, but try and work your way into vim/emacs. This will allow you to use the same development/debugging environment that you use on your laptop on remote servers, which will vastly improve your earning potential.
- horsehead 14y agoThanks. (to all the commenters under this thread). I was thinking about vim just a bit ago (I hear emacs pinky is a real bitch). Maybe I'll put eclipse on my ubuntu too and check it out (dunno if it has support for python or not. I tried IDLE and didnt like it ... ) I have kind of stalled out a bit lately. maybe it's time for an IDE anyway
- mixmastamyk 14y agoI like geany, it is a lot more powerful than gedit, but still a lot simpler than most ide/mega editors. You can hide the features you don't use. Despite the advice that you must use a terminal editor to edit files remotely, nautilus (& others) let you mount remote folders over ssh and edit them locally with the editor of your choosing. I find it very convenient. I hit a bookmark and start editing, keeping the terminals reserved for commands instead.
- j_baker 14y ago> That there is a whole generation of developers who come out of school thinking that "building" is the action of pressing a button in an IDE GUI Why? I mean, the fact that a newbie developer just needs to know how to press one button to build their code is actually pretty amazing. Plus, how many school projects are complex enough to require much more than that?
- Goladus 14y agoMy problem with make and autoconf, as a young student, was the difficulty of finding quality, intermediate examples. Textbook examples were trivial, professional examples were too dense to understand. There was nothing to bridge the gap. Trying to read the configure scripts and Makefiles for software like Apache httpd server was overwhelming. There's obviously many man-months of work there as well as unknown styles, conventions, and tricks. How (and why) would I go from "gcc -lexample -o program csci201.c" and maybe a simple Makefile to a 10,000-line ./configure script? I never had any idea.
- segmond 14y agodo you want to know how to understand it? one line at a time! as a programmer and a non UX guy, i cringe when i see css files with ridiculous amount of rules. being the cheap person i'm and deciding to tackle a layout redesign myself. i started studying css, and understanding it one line at a time, by the time i was done reskinning my site, i had a whole bunch of stylesheets with about 4000 lines. It then dawned on me, that's how I figured out Make files and the config scripts. I started by writing 5 line makefiles, and one day, uh oh, what's this 2000 line file?
- joelthelion 14y agoFortunately there are better build systems available nowadays. CMake is a lot easier on the beginner, and yet it is used by large projects like KDE.
- joe_the_user 14y agoSadly, my experience with CMake makes miss the otherwise annoying make. This is mostly from trying to compile tar balls that used it. It didn't seem to give error messages for missing parts as well as simple make.
- padraigm 14y agoThe reason you couldn't find a quality, intermediate example of autoconf is that there is no such thing; it's an obtuse and painful tool. As someone else mentioned, cmake is a much better choice.
- zem 14y agoi've been developing under linux since 1993, and i would love it if building were pressing a button in an ide gui (without having to drag the rest of the ide development process along). it seems like a genuinely superior development model to me - write your code, have your dependencies figured out automatically, and hit a button to build. writing makefiles by hand is just a sign my toolset is not powerful enough, or my language insufficiently well designed to automate dependency analysis.
- Peaker 14y agoFunny, I find it sad that we need so much tinker-knowledge about obscure command lines of build tools to program stuff.