News for hackers. Stuff that matters.
Re:The IDE Divide (2004) by MichaelGG on Thursday November 01, 2012 @02:54PM (#4729075)
Tooling isn't such a linear improvement as this article makes it out to be.

In VS 2005, Microsoft spent a huge amount of effort adding edit-and-continue support. This is a feature that requires collaboration from all parts of the environment. The additional boost to productivity is minimal, compared to having colouring, auto-complete, and a REPL, and those 3 features combined are probably less work than EnC.

I'd argue that auto-complete, one of the major IDE/editor features, is alone responsible for most of the boost I get from coding in an environment. Instantly, thousands of symbols can move out of my brain and into a list that appears as I type.

Re:The IDE Divide (2004) by iyulaev on Thursday November 01, 2012 @03:17PM (#4729201)
"I'd argue that auto-complete, one of the major IDE/editor features, is alone responsible for most of the boost I get from coding in an environment. Instantly, thousands of symbols can move out of my brain and into a list that appears as I type."

This is exactly what I had in mind reading this article. My experience with IDEs and languages has been that they are, for the developer, orthogonal to one another. Throughout school I never even touched an IDE - ended up writing a 100KLOC+ program (C compiler) with a text editor and debugging using print statements, no debugger or anything. It was a ball of mud but it worked great.

Where IDEs have really helped me is for larger scale projects, especially where I integrate lots of new-to-me 3rd party libraries. Being able to contextually explore the namespace of the libraries without sorting through all the documentation is a huge time-saver. Refactoring is also a plus; I don't end up using the refactoring tools that often but Eclipse's refactoring beats find-replace any day.

I guess what I'm trying to say is, languages help developers implement algorithms and data structures. These tend to be the 2-by-4s and screws of software development; a high-quality language is a straight, square, well-finished set of building materials that are sized & shaped for the structure you're building. IDEs help explore namespace and refactor, they're your drills and saws. Understandably the building materials can influence how easy it is to work on them with high-powered tools, but from a development perspective, they're complements, not substitutes.

Re:The IDE Divide (2004) by subb on Thursday November 01, 2012 @03:27PM (#4729244)
My feeling is similar as your, that is, I consider my IDE to be something that helps me understand and inspect my code. Language features, on the other hand, helps me write code.
Re:The IDE Divide (2004) by kevhsu on Thursday November 01, 2012 @04:17PM (#4729484)
no gcc in school?
Re:The IDE Divide (2004) by iyulaev on Thursday November 01, 2012 @04:24PM (#4729521)
No, we had gcc :-P but for a compilers class the goal is to write your own. Lots of people used gdb for debugging their assembly programs and probably at least half the people I know used Eclipse for development.
Re:The IDE Divide (2004) by eru on Thursday November 01, 2012 @05:18PM (#4729759)
Did you have to write your compiler in C? (I wonder, because OCaml or Haskell seem like much better choices. Or even Java, just for the GC.)
Re:The IDE Divide (2004) by iyulaev on Thursday November 01, 2012 @07:28PM (#4730352)
We wrote it in Java. We had some tools for the parsing (something like yacc for Java), we built a parser but it was in another class.
Re:The IDE Divide (2004) by gfhsdfy on Thursday November 01, 2012 @04:33PM (#4729548)
>The additional boost to productivity is minimal

For me the biggest problem with edit-and-continue in Visual Studio is that you can only edit code when program is paused at breakpoint. You can't change drawing routine formula and observe effects on animation on the second screen. I've seen Notch doing that in Java and it was cool. In VS you get "Changes are not allowed while code is running" error when you start typing.

Even php/javascript feels more interactive than C#, just press F5 and watch the page change. In VS ASP.NET you have to restart whole site (10x longer).

Also edit-and-continue works only for very local changes.

Re:The IDE Divide (2004) by mattmanser on Thursday November 01, 2012 @03:10PM (#4729169)
Woah, woah, you're saying edit and continue, which everyone's flipping out about in Light Table, isn't that much of an improvement?

I think the problem is more that most people don't know it exists and it's almost impossible to get Edit and Continue working properly in Visual Studio. I think I've only ever managed once for console programs, but then it completely breaks debugging for ASP.net.

There's a load of things I wish worked properly in Visual Studio that don't that I know would make a massive difference in my productivity. It's almost impossible to drop into .Net library code, load external symbols, etc. When you get a gnarly problem where it's due to some 'helpful' utterly insane choice that the ASP.Net framework guys made the time I would save just dropping into the code from the IDE is massive, rather than popping open ILSpy, figuring out the flow and trying to figure out the path the program is taking.

My workflow is code, read through the code, test the code, fix the code, test the code, fix the code. Annoyingly during testing I can't edit the damn code to fix the simple mistakes I've missed. Edit and continue would be great if it actually worked.

Re:The IDE Divide (2004) by seanmcdirmid on Thursday November 01, 2012 @04:37PM (#4729570)
Light Table goes way beyond "edit and continue," which is small potatoes left over from Smalltalk (and early systems that support hot code swapping). Light Table supports much more feedback (we call it live programming), the code is actually re-evaluated when changed; edit and continue only holds for future, not previous execution, which is why it breaks so easily.
Re:The IDE Divide (2004) by meaty on Thursday November 01, 2012 @04:54PM (#4729651)
+1 for edit and continue not working. It rarely does what it says on the tin. Usually in our case as we have 64-bit COM binary dependencies, we can't use it anyway as it doesn't work in 64-bit CLR processes. In 32-bit processes it throws the HRESULT of death MsgBox and dies.

Regarding ASP.Net debugging, I have to resort to the same thing. We actually have a set of custom framework assemblies as a last resort debugging tool that we load into the GAC in a VMware instance which have gone through a tool I wrote using Mono.Cecil that makes all members and classes public and not sealed. They all have exported PDBs as well from MS symbol server so we can step through :)

However, Visual Studio would get a fuck ton more love from me if it didn't crash 8 times a day as well. It's so damn unreliable.

My "other world" of gcc + C + vim + Linux is far more pleasant.

Re:The IDE Divide (2004) by MichaelGG on Thursday November 01, 2012 @08:10PM (#4730531)
Light Table looks like a REPL on steroids, E-n-C is like REPL on tranquilizers. It has limited use, allowing only limited changes. There's little interactive environment (immediate window), and even that's pretty limited.

So no, I don't think edit and continue is that big of a deal. A REPL would have been easier and more useful, see F# Interactive.

As far as stepping into code, I find the MS symbol server and .NET source code stepping to "just work". But I sympathize with the pain of debugging a deep stack in ASP.NET, trying to figure out how their abstraction worked. For 3rd party libraries, would it not be up to that publisher to publish their own symbols/source?