The Two Cultures of Computing (2013)

Re:The Two Cultures of Computing (2013) by coldtea on Friday August 05, 2016 @09:32PM (#12236648)

>Except that IDEs and GUIs are buggy. They are finicky and they fail often and usually their failure can only be debugged by someone who understands what is actually going on, i.e. the command line and build process.

People having been coding years on end on modern IDEs like IntelliJ and Eclipse and VS without them "failing" for basic stuff.

And it's not like setting up e.g. Vim or whatever with just some of the niceties an IDE has not challenging.

>Consider teaching a CS class. Everyone has a different machine, of a different age, with a different operating system. Getting all of them on some posix type CLI where you can type 'make' or 'python' is fairly easy and once it's working, foolproof.

You'd be surprised. Try getting them to run Python on Windows and discover all the subtle changes, libs that only play on Linux etc, use the same Unix userland with slight OS X/Linux changes, run that terminal stuff on Windows etc.

Besides, tons of programming teaches classes, seminars, etc use or recommend an IDE.

[ Parent | on HN ]

Re:The Two Cultures of Computing (2013) by AstralStorm on Sunday August 07, 2016 @07:18AM (#12241761)

Ha, don't even get me stated on infallibility of modern IDEs. Forgot to index? 90% functionality is off or broken. Want more than one project open? Better have 10 GB memory on the ready. Oh, did someone customizer their key bindings? Or window manager, and the binding now collides?

Ah wait, the integrated debugger has crashed again, so I cannot figure things out. Hey, the thing cannot even open a text data file, because it is not part of the project, whatever that means.

Etc. Most "industrial" IDEs male quote a few simple things way unnecessarily complex.

[ Parent | on HN ]