Actually I think a Web IDE is a (potentially) cool solution, but to a slightly different problem. It solves the problem of accessibility of the toolset (i.e. ubiquitous availability and zero setup time - aka SO-machine-compatible), but leaves out any resolution to the dependency on the toolset in the first place.
This is probably more appealing to me, as I'm not anxious to give up my tooling. However, I do still like the thought of exploring something more slimmed down tooling-wise, and am continuing to like the idea of the convention route. But there's also a thought I had of: Why can't the project file (configuration) be in the same file as the code? How about IntelliSense that helps one through that? On Wed, Nov 17, 2010 at 10:32 AM, Justin Bozonier <[email protected]>wrote: > It's ok to come out of > this with no solutions and a head full of dreams. > Actually, sometimes I wonder if Justin prefers it that way ;-) -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
