If it is a SourceForge page or similar alowing for user submissions, then submit patches for each part of your work, and in the description for each give a link to a complete tarball of the source including your work.
This allows for the maintainer to easily pickup your changes, plus future users to locate your changes before they get merged upstream.
If the problem is that it gets served out too many times, then make the server slow as molasses. If it takes 1-2 minutes to get the DTD from the server, or more, then it is quickly discovered by the performance teams.
For some reason people tend to see this as a browser alternative (which it is usable for), but the real value of this is that it allows developers to target the iPhone with their development. Apple has declared that Safari is the browser on the iPhone, and that we should write Ajax applications for it.
So, instead of calling it "Safari for Windows" they should just call it "iPhone SDK for Windows" and the original article would never even have been considered:)
I agree fully with that, even if I mainly use TDD for smaller library functions. If you are in the middle of some existing code where you need to add new functionality which will be hard to test and where you just want something that works, TDD is perfect for getting your mind clear on the matter before you actually code anything, and the code tends to be clearer since you don't focus on all kinds of special cases unless you are going to need it. The test cases show exactly how the code is intended to work.
My suggestion is to the original poster that he tries this with a good unit testing package for his favorite language, and see if it improves the design.
An issue that is also frequently overlooked is that the test code is the best documentation on how to use the tested code. It shows usage, special cases and is guaranteed to be correct.
I am playing around with the Developer Express version and it is actually rather nice to use in vmware (after installing the tools).
There are still some things that show that Sun still misses their target.
* In order to download a DVD-ISO you download 5 snippets which you have to _manually_ unzip and _concatenate_ to get the image. Come on - I can live with a large download
* There is no shutdown button - you need to go to root and "init 6".
There are some PATH issues (oh, why would make go in/usr/ccs/bin - which is not in the path) but when that is settled, very nice:)
I recommend it strongly as a Java testing/deployment platform. If your Windows build works there, you are pretty certain it it ok.
A while back I ran nmap against my Airport Express and it reported it to run OS X. It is most likely the embedded version of Darwin which they talk about here, then.
A major problem with using Java for _applications_ have been that the JVM basically has worked as a single application platform, meaning that it was too slow for small applications (as the whole JVM needed to be brought up from zero everytime the application needed to be run).
Hopefully the freely available source will mean that the basic JVM can be up and running all the time, so that running small applications will be very fast, and that GUI applications will start fast.
In order to make a prototype, you should use the language that makes it possible to test out code the fastest. Here it is mathlab. GUI's are often prototyped in excel or Photoshop, for this purpose, instead of C++.
It also allows you to ensure that the prototype is rewritten when being implemented. It is not often that prototype design choices are the best for production, so needing to port guarantees that all code is revised, and you have a working implementation to give test results that the product should conform to.
A similar problem, namely wireless cards on LInux, was solved with a Linux driver which knew how to talk to a Windows binary driver. A similar approach could be adopted here.
What Apple apparently doesn't clearly see is that there is actually people out there who would like to _buy_ OS X if it would run on their Windows PC. I am one of them.
If I had the choice of OS X and Windows Vista for a new machine, I would pick OS X. Unfortunately I cannot currently afford a Mac, so I won't. I would also buy it for my current desktop, and move the XP license to a gaming machine which needs it.
As Apple is already moving its business to the iPod, this might acutally make more money!
Slashdot Mirror
If it is a SourceForge page or similar alowing for user submissions, then submit patches for each part of your work, and in the description for each give a link to a complete tarball of the source including your work.
This allows for the maintainer to easily pickup your changes, plus future users to locate your changes before they get merged upstream.
Ever heard of dtrace?
Programmers tend to like it
Why don't they just go and hire some programmers and TRAIN them in Cobol? Then they won't have to buy a new system...
(Yes, I have colleagues who work in OPM COBOL, those exist)
I'd suggest using a virtual machine, with a suitable (for you) interface.
vmware player/workstation can connect over the network, virtualbox has a remote desktop interface to its console, etc.
Otherwise Xvnc might be just right for you
If the problem is that it gets served out too many times, then make the server slow as molasses. If it takes 1-2 minutes to get the DTD from the server, or more, then it is quickly discovered by the performance teams.
For some reason people tend to see this as a browser alternative (which it is usable for), but the real value of this is that it allows developers to target the iPhone with their development. Apple has declared that Safari is the browser on the iPhone, and that we should write Ajax applications for it.
:)
So, instead of calling it "Safari for Windows" they should just call it "iPhone SDK for Windows" and the original article would never even have been considered
I agree fully with that, even if I mainly use TDD for smaller library functions. If you are in the middle of some existing code where you need to add new functionality which will be hard to test and where you just want something that works, TDD is perfect for getting your mind clear on the matter before you actually code anything, and the code tends to be clearer since you don't focus on all kinds of special cases unless you are going to need it. The test cases show exactly how the code is intended to work.
My suggestion is to the original poster that he tries this with a good unit testing package for his favorite language, and see if it improves the design.
An issue that is also frequently overlooked is that the test code is the best documentation on how to use the tested code. It shows usage, special cases and is guaranteed to be correct.
Couldn't they just pick them out of the copies in the Google Cache?
Or perhaps at the wayback archive!
I am playing around with the Developer Express version and it is actually rather nice to use in vmware (after installing the tools).
/usr/ccs/bin - which is not in the path) but when that is settled, very nice :)
There are still some things that show that Sun still misses their target.
* In order to download a DVD-ISO you download 5 snippets which you have to _manually_ unzip and _concatenate_ to get the image. Come on - I can live with a large download
* There is no shutdown button - you need to go to root and "init 6".
There are some PATH issues (oh, why would make go in
I recommend it strongly as a Java testing/deployment platform. If your Windows build works there, you are pretty certain it it ok.
At that time install your new computer with a basic Linux, install vmware server on that, and install Windows 2000 on top of that.
:)
Enjoy
A while back I ran nmap against my Airport Express and it reported it to run OS X. It is most likely the embedded version of Darwin which they talk about here, then.
A major problem with using Java for _applications_ have been that the JVM basically has worked as a single application platform, meaning that it was too slow for small applications (as the whole JVM needed to be brought up from zero everytime the application needed to be run).
Hopefully the freely available source will mean that the basic JVM can be up and running all the time, so that running small applications will be very fast, and that GUI applications will start fast.
You'll need a TCP/IP stack running on the c64 before a webserver will be any fun to use.
I congratulate you on your efficiency.
But how can you be _certain_ that you got them all, and that your boss is not still infected?
In order to make a prototype, you should use the language that makes it possible to test out code the fastest. Here it is mathlab. GUI's are often prototyped in excel or Photoshop, for this purpose, instead of C++.
It also allows you to ensure that the prototype is rewritten when being implemented. It is not often that prototype design choices are the best for production, so needing to port guarantees that all code is revised, and you have a working implementation to give test results that the product should conform to.
You should try using a AS/400, eh, System 5, eh iSeries, eh, that thingie over there, someday.
IBM defintively got something right here, and - yes - DB2/400 is embedded in the OS.
In a word no. (Except for aggresive inlining of code but I have not measured on that).
"final" allow you to state information _in code_ about what you are doing about invariants, and letting the compiler enforce this.
This allows the designer and maintainer to catch accidential assignments too. Not a bad thing.
You should try out the latest Ubuntu - it is plainly a joy to use.
:)
After trying both KDE and Gnome, i must say that I like their Gnome desktop the most, and I am known to be very picky
A market percentage of around 90% is not having taken over the Web?
;-)
Pardon me
I sincerely don't think it is possible to render it in ASCII so it will be recognizable.
Want to give it a try?
A similar problem, namely wireless cards on LInux, was solved with a Linux driver which knew how to talk to a Windows binary driver. A similar approach could be adopted here.
What Apple apparently doesn't clearly see is that there is actually people out there who would like to _buy_ OS X if it would run on their Windows PC. I am one of them.
If I had the choice of OS X and Windows Vista for a new machine, I would pick OS X. Unfortunately I cannot currently afford a Mac, so I won't. I would also buy it for my current desktop, and move the XP license to a gaming machine which needs it.
As Apple is already moving its business to the iPod, this might acutally make more money!
Quake is a bad example as it has been portet to most platforms including Win32 GL.
What platform are _you_ using?
IBM has an excellent Java for PowerPC Linux. Running it on an iMac.