Open source development is like cycling. The main project is peloton. Normally, everybody goes with the peloton. But sometimes escape groups formed, which is a kind of fork. Some escapes are very short-lived, some continues for a while and swallowed by the peloton through the end of the stage, and some succeeds by getting a stage win.
Sometimes, if you are too slow, you can't keep pace with the peloton and keep touch with them. You never have a chance to catch them alone and abandon the race.
Good bye GlobalAlloc()! Good bye GlobalLock() and their local counterparts! By the way, heap management was damn hard in 16 bit Windows. You only had 8192 memory handles which you must share with other apps. It was a pain to develop applications for it.
Microsoft would have to do a complete make-over on BSD the way Apple did with OSX. It's not that they couldn't do it, it's that they wouldn't. It would upset all of their development users to no end. There are so many developers making their products and living based on the Windows API that to move to something GNU "compatible" would simply be catastrophic in so many ways that I'd prefer not to put brain power into imagining the details. It would be ugly though... very ugly.
You're so right. Just look at the "software component" market which depends on the things that Microsoft didn't solve. For example, if you examine componentsource.com, most components are ActiveX and.NET based; Java and Unix based components have only a marginal share there.
Or, do not tell anything to your boss. Change the code; like changing names of the files, variables, functions. Add more features, cut some features and release it as open source.
Most novices need a bulletproof car that can take them to supermarket, theatre, or to the beach without the hassle of driving. Unfortunately, there is no such thing. You must learn how to drive, not an easy thing to learn. Or take public transportation...
* open(): Sets up a new request to a server.
* send(): Sends a request to a server.
* abort(): Bails out of the current request.
* readyState: Provides the current HTML ready state.
* responseText: The text that the server sends back to respond to a request.
Don't worry if you don't understand all of this (or any of this for that matter)
I think everybody understand all of this, if somehow involved with software development.
This article is useless like 90% of the DeveloperWorks articles.
I bet you are using/have to use Windows platform. Then try Cygwin which gives you a virtual Linux environment on your Windows PC.
You can use every script language like Perl/Ruby/Python there, without thinking about using / and \
You can download all open source software and be able to do the following standart build process:
./configure make make install
You can use the powerful bash shell and use emacs, vi etc.
You can have Apache web server and Postgresql database server there.
And best of all, you can hide all your experiments under c:\cygwin directory.
Re:The real 90s versus outdated 00s software
on
Java Is So 90s
·
· Score: 1
So I may guess that the remaining 28.874% of the programs are still written in Cobol?:-)
About 5 years, I've been constantly saying "Java is te Cobol of the future". Yes, Cobol is still the leader, but you may notice Cobol's decline in recent years if you study the numbers carefully:)
By the way, which language belongs to 2000s and why?
And why, in this era of 3D-accelerated graphics cards and sophisticated user interfaces, are Web pages limited to clunky text boxes and radio buttons for user input?
Why do we need sophisticated user interfaces? The existing controls are easy and universally understood.
If you accept automatically-destroyed stack objects in a GC language, you have to face the possibility of heap objects containing dangling pointers to destroyed stack objects. So there's a tradeoff even in that situation: you allow a certain class of memory errors, or you create a language feature that prevents garbage-collected objects from referring to stack objects.
A stack object may be treated as to be destroyed when goes out of scope at the beginning. But when a global variable is assigned to it, or used as a parameter to some method or function, then it may be qualified as subject to garbage collection
> I don't know what type of security holes they will find in it, It is defiantly bloated because it will not fit 5 1/2 single density floppy disk with enough rooms for a 2000 record table.
I think it must be 5 1/4 floppy disk
Slashdot Mirror
int i = 0;
start:
System.out.println(i);
++i;
if (i == 10) goto end;
goto start;
end:
http://en.wikipedia.org/wiki/Value_chain
Facebook is probably one of the few sites that could have written part of it on fast C++ code. In a F1 race, you will use a F1 car.
Facebook is "24 hours of Le Mans" or "Dakar Rally" than F1.
I know 500 friends who have 500 friends each.
Sometimes, if you are too slow, you can't keep pace with the peloton and keep touch with them. You never have a chance to catch them alone and abandon the race.
Good bye GlobalAlloc()! Good bye GlobalLock() and their local counterparts! By the way, heap management was damn hard in 16 bit Windows. You only had 8192 memory handles which you must share with other apps. It was a pain to develop applications for it.
You're so right. Just look at the "software component" market which depends on the things that Microsoft didn't solve. For example, if you examine componentsource.com, most components are ActiveX and .NET based; Java and Unix based components have only a marginal share there.
Or, do not tell anything to your boss. Change the code; like changing names of the files, variables, functions. Add more features, cut some features and release it as open source.
Most novices need a bulletproof car that can take them to supermarket, theatre, or to the beach without the hassle of driving. Unfortunately, there is no such thing. You must learn how to drive, not an easy thing to learn. Or take public transportation...
To be popular, you must say bold things. And Linus Torvalds do it very well...
When I see "...award winning..." in a text, I stop reading the rest.
I think everybody understand all of this, if somehow involved with software development.
This article is useless like 90% of the DeveloperWorks articles.
You can use every script language like Perl/Ruby/Python there, without thinking about using / and \
You can download all open source software and be able to do the following standart build process:
You can use the powerful bash shell and use emacs, vi etc.
You can have Apache web server and Postgresql database server there.
And best of all, you can hide all your experiments under c:\cygwin directory.
By the way, which language belongs to 2000s and why?
If it was not full, something must be absent in transaction handling before. Was it mission critical?
> I don't know what type of security holes they will find in it, It is defiantly bloated because it will not fit 5 1/2 single density floppy disk with enough rooms for a 2000 record table. I think it must be 5 1/4 floppy disk
Are there any configuration files? If no, there may be some code that's reading supposed to be found conf files.
With this keyboard, I can use my wife's PC and she can't use my PC.
Of course, use WinHelp format.
INI files are obsoleted by Windows Registry database!