dougwithau, yes, it seems like it would be a good idea. Yet when I talked about it on Microcontroller Central there was a lot of resistance. And how do you adequately monetize it? THose, rather than the technical, issues seem to be the stumbling blocks.
It seems like multideveloper big distributed teams would benifit from a cloud environment. Git hub hosts hug code reposistories. Colaboration is what the web is all about.
Seems to me reuse and open collaboration would be even easier in a web based tool. Remote work where the actual files never touch my drive could be more secure. No more lost a drive or left the laptop in Starbucks, so the whole project is gone. Oops.
No, Q clearence people will not use it, but lots of people may. It is an interesting idea.
A good provider would archieve tools along with the code and project. That is what a good process requires. If it is super easy, maybe more developers will follow the best practice.
Rich Quinnell said: Installing, configuring, and maintaining a complex development environment on a computer workstation can be a laborious and sometimes frustrating activity.
The question that immediately occurs to me is "why bother with a complex development environment at all?" If your fancy IDE with myriad features starts looking like you're "flying an airliner with 100,000 switches" (as one of my profs used to say), perhaps you should go to something simpler like an ASCII text editor, command line compiler/linker, and a well-designed Make file. RISC is not only for CPUs. The principles of RISC apply equally well to software, e.g., each feature must improve productivity more than the complexity it adds.
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...