We are Ruby shop and push to production every 2 weeks. We are looking to make that shorter and do full blown continuous delivery. We have 95% coverage of the user interface automated with a lot of complicated scenarios. IMHO it is a must to automated tests to push to a feature rich application to production so often along with environments and automated continuous integration.
First new methods for copy and move, then a new file explorer with a 6" toolbar and now mount ISO images? Whoa! There is a company with innovation! Bards, book authors and bloggers will be singing Microsoft praises for such innovations in Windows 8!
Yawn. Now to go back straighten out my sock drawer.
CreateProcess is not the same as a fork. When you fork a program it will maintain the same global state. CreateProcess will create a new process without the state of the current running program.
To do a fork, you have to copy the program memory and then jump to the execution point. Very expensive under NT.
Windows does not have any concept of a fork. Cygwin reimplements this as well as a unix like process table. It limits the number of processes to 127 and fork are very expensive with all the context switching going on to make it happen.
"using the same code base on multiple platforms and multiple languages"
Same code base with multiple languages? How about just doing it with one language. Smalltalk.
VisualWorks Smalltalk from Cincom runs on a boatload of platforms including Linux and has distributed features. The application can be generated once and dropped on any platform and will run without modifications (Where did you think Sun got the idea?)
Also, IBM VisualAge for Smalltalk (VAST) has similar features that make it easy program distributed apps. However, you will have to "recompile" for each targeted OS. They have not release VAST for Linux yet, however it is coming soon since VisualAge for Java is on Linux (VA/J was written using Smalltalk).
In terms of development time, coding/testing a Java application would be faster then coding/testing a C/C++ application. Coding/testing a Smalltalk application would be faster then coding Java.
I was pissed about the Netscape thing, but my wife uses 95 for Quicken so I just signed up there. Had some trouble with the PPP side of Linux, but it turned out to be a problem on their end that was cleared up after a day. All in all, I'm using it under Linux without a problem and it saves me about $50 a month over Sprint and Surfree.
Pick any industry that produces commercial software and you'll find lack of design, testing, documentation and shorten deadlines.
My advice is to do your 8 hours and do what the pointy-hair managers want and CYA out the wahzoo. Or become an hourly employee and profit from the overtime that will be coming your way when the project managers screw up (and they will screw up).
Back in '94 I started my own company and tried to release a commerical product. What I have found is you have about a 6 month window to design, code test, and release before you miss the window of opportunity. I was my own worse boss and worked 14 hour days, 7 days a week, for 7 months.
I've consulted and done the salary thing since and have seen a lot of companies flush millions of dollars into projects with nothing to show for it. All the same reasons you sited in your article.
Slashdot Mirror
Ugh, I cannot imagine a reason to do this at all.
We are Ruby shop and push to production every 2 weeks. We are looking to make that shorter and do full blown continuous delivery. We have 95% coverage of the user interface automated with a lot of complicated scenarios. IMHO it is a must to automated tests to push to a feature rich application to production so often along with environments and automated continuous integration.
First new methods for copy and move, then a new file explorer with a 6" toolbar and now mount ISO images? Whoa! There is a company with innovation! Bards, book authors and bloggers will be singing Microsoft praises for such innovations in Windows 8!
Yawn. Now to go back straighten out my sock drawer.
"But Microsoft has probably stopped listening, despite their now large ties to the entertainment industry."
Guess you missed this post
http://tech.slashdot.org/article.pl?sid=09/02/16/2259257
Free - ACE/TAO
Pay - Rogue Waves Tools.h++ dbtools.h++ net.h++
CreateProcess is not the same as a fork. When you fork a program it will maintain the same global state. CreateProcess will create a new process without the state of the current running program.
To do a fork, you have to copy the program memory and then jump to the execution point. Very expensive under NT.
Windows does not have any concept of a fork. Cygwin reimplements this as well as a unix like process table. It limits the number of processes to 127 and fork are very expensive with all the context switching going on to make it happen.
I wonder if they did anything different
"using the same code base on multiple platforms and multiple languages"
Same code base with multiple languages? How about just doing it with one language. Smalltalk.
VisualWorks Smalltalk from Cincom runs on a boatload of platforms including Linux and has distributed features. The application can be generated once and dropped on any platform and will run without modifications (Where did you think Sun got the idea?)
Also, IBM VisualAge for Smalltalk (VAST) has similar features that make it easy program distributed apps. However, you will have to "recompile" for each targeted OS. They have not release VAST for Linux yet, however it is coming soon since VisualAge for Java is on Linux (VA/J was written using Smalltalk).
In terms of development time, coding/testing a Java application would be faster then coding/testing a C/C++ application. Coding/testing a Smalltalk application would be faster then coding Java.
I was pissed about the Netscape thing, but my wife uses 95 for Quicken so I just signed up there. Had some trouble with the PPP side of Linux, but it turned out to be a problem on their end that was cleared up after a day. All in all, I'm using it under Linux without a problem and it saves me about $50 a month over Sprint and Surfree.
Pick any industry that produces commercial software and you'll find lack of design, testing, documentation and shorten deadlines.
My advice is to do your 8 hours and do what the pointy-hair managers want and CYA out the wahzoo. Or become an hourly employee and profit from the overtime that will be coming your way when the project managers screw up (and they will screw up).
Back in '94 I started my own company and tried to release a commerical product. What I have found is you have about a 6 month window to design, code test, and release before you miss the window of opportunity. I was my own worse boss and worked 14 hour days, 7 days a week, for 7 months.
I've consulted and done the salary thing since and have seen a lot of companies flush millions of dollars into projects with nothing to show for it. All the same reasons you sited in your article.