It can help to find a niche where you have some expertise. At one company I worked for, I designed a plugin architecture for their product suite. Once vendors found out about it, my name got around and I've had plenty of extra work porting and implementing plugins using my own API.
Whatever your niche is, the most important thing is to get your name around somehow.
It's supposed to be entirely CGI. And it sounds like Freeman will be a principal contributor to the project - not necessarily just a (voice/cyberscan) actor.
Now about the size of your project ? 10G+ was it ? ? exactly what are you going to be storing ? ? Thats a whole lot of code, and as i keep telling ppl. here, data does not belong in the repo..... only code that you want to get back to.... DATA should be kept on a FS with good naming, like a simple (filename)_(date)_(version).* BUT ten G's is going to be one hell of a freaking checkout!!!!
Data most certainly needs to be revision-controlled.
Data/config files, images/icons, documentation, anything that goes into a release needs to be under control. If you ever fix a bug in a product you want to be able to build the identical file-set that went into that project. Over time, data files get updated, images/icons change, and if you have to go poking around on backup tapes for the original images, you are wasting time. I've worked on several large commercial products using ClearCase and EVERYTHING went into the database, even directory structures (something I wish you could do for real with CVS).
It sounds like you don't like SGI because it's not enough like BSD or Linux for you. Yes, their sales model is different than purchasing off-the-shelf parts, but so what? You get what you pay for, and like it or not, SGI machines continue to be relevant workhorses in many markets.
BTW - the 'smart people' are probably all off doing interesting things with these machines.
Not only that, there are useful cases where you might want to see what is going on during the commecials - for example, sometimes for "preview" commercials used to indicate up-coming episodes or new shows, an icon will appear during the commercial, allowing you to press SELECT and have Tivo automatically add that program to your TODO list. Even skipping at full speed you can usually see the icon and press SELECT, or at least go back and see what the deal was. You wouldn't even be aware of this feature if you simply skipped blindly ahead 30 seconds.
And as the previous poster points out, it's actually better to skip the Tivo way, because you have control over when you jump back to real time.
Yeah, if you turn the option on you can't compile any of the headers included by Microsoft, EVEN THEIR IMPLEMENTATION OF THE STL! About the only thing you *can* compile is the above-mentioned example! It's a totally worthless 'tool' that MS only provided so they could claim standards-compliance.
At my previous company, I implemented a "tear-off tabs" interface for a graphics application (Windows and IRIX). After meeting several times with our legal department, we decided that Adobe's patent was effectively too broad to be enforced, so we went ahead anyway.
The gist of our arguments were that the patent sounds suspiciously like tear-off menus, which have been around (in OpenLook) since before Adobe filed the patent.
(Aside: implementing tear-off tabs in X/Motif/ViewKit was a seriously fun and annoying excercise!)
In the case of iterators, though, you usually want to prefer prefix, since it's faster (it doesn't need to make a copy of the iterator, which you then just throw away).
In fact, you're exactly correct. They used Mainwin or somesuch Windows API emulation layer to do the port, just like they'll do in the Office port (if it really happens. 90% of the installation is basically a virtual windows machine with all the support libraries, fonts, registry crap, etc.
Slashdot Mirror
It can help to find a niche where you have some expertise. At one company I worked for, I designed a plugin architecture for their product suite. Once vendors found out about it, my name got around and I've had plenty of extra work porting and implementing plugins using my own API.
Whatever your niche is, the most important thing is to get your name around somehow.
It's supposed to be entirely CGI. And it sounds like Freeman will be a principal contributor to the project - not necessarily just a (voice/cyberscan) actor.
I suppose you live in your parents' basement rent-free and get pizza money from your newspaper route? Or maybe you sell drugs on the side.
Some of us do have bills to pay. And I for one prefer my own house to living at home.
Now about the size of your project ? 10G+ was it ? ? exactly what are you going to be storing ? ? Thats a whole lot of code, and as i keep telling ppl. here, data does not belong in the repo..... only code that you want to get back to.... DATA should be kept on a FS with good naming, like a simple (filename)_(date)_(version).* BUT ten G's is going to be one hell of a freaking checkout!!!!
Data most certainly needs to be revision-controlled.
Data/config files, images/icons, documentation, anything that goes into a release needs to be under control. If you ever fix a bug in a product you want to be able to build the identical file-set that went into that project. Over time, data files get updated, images/icons change, and if you have to go poking around on backup tapes for the original images, you are wasting time. I've worked on several large commercial products using ClearCase and EVERYTHING went into the database, even directory structures (something I wish you could do for real with CVS).
It sounds like you don't like SGI because it's not enough like BSD or Linux for you. Yes, their sales model is different than purchasing off-the-shelf parts, but so what? You get what you pay for, and like it or not, SGI machines continue to be relevant workhorses in many markets.
BTW - the 'smart people' are probably all off doing interesting things with these machines.
Not only that, there are useful cases where you might want to see what is going on during the commecials - for example, sometimes for "preview" commercials used to indicate up-coming episodes or new shows, an icon will appear during the commercial, allowing you to press SELECT and have Tivo automatically add that program to your TODO list. Even skipping at full speed you can usually see the icon and press SELECT, or at least go back and see what the deal was. You wouldn't even be aware of this feature if you simply skipped blindly ahead 30 seconds.
And as the previous poster points out, it's actually better to skip the Tivo way, because you have control over when you jump back to real time.
Use the internet - that's what his series is about anyway!
http://www.bbc.co.uk/radio4/douglas_adams
Well at least your signature explains your opinion. :-)
Why invent a new BASIC when we already have a better basic: Python ?
Yeah, if you turn the option on you can't compile any of the headers included by Microsoft, EVEN THEIR IMPLEMENTATION OF THE STL! About the only thing you *can* compile is the above-mentioned example! It's a totally worthless 'tool' that MS only provided so they could claim standards-compliance.
At my previous company, I implemented a "tear-off tabs" interface for a graphics application (Windows and IRIX). After meeting several times with our legal department, we decided that Adobe's patent was effectively too broad to be enforced, so we went ahead anyway.
The gist of our arguments were that the patent sounds suspiciously like tear-off menus, which have been around (in OpenLook) since before Adobe filed the patent.
(Aside: implementing tear-off tabs in X/Motif/ViewKit was a seriously fun and annoying excercise!)
Let's not be too hasty here. Have you taken a browse through many open-source projects lately?
In the case of iterators, though, you usually want to prefer prefix, since it's faster (it doesn't need to make a copy of the iterator, which you then just throw away).
In fact, you're exactly correct. They used Mainwin or somesuch Windows API emulation layer to do the port, just like they'll do in the Office port (if it really happens. 90% of the installation is basically a virtual windows machine with all the support libraries, fonts, registry crap, etc.
Yeah, Mozilla could stand be another 5 or 10 megabytes bigger...