It was introduced whit: "It's friday, it`s 5 to 5, it's CRACKERJACK !"
The prizes were pretty crap - you could win a cabbage, or a crackerjack pencil. Later I guess they must have gotten a budget and you could win a crackerjack pen.
One of the things the show had, was that anytime any of the hosts said the word "crackerjack" the audience would yell out "crackerjack" really loudly.
Read "Start Up" by Jerry Kaplan. It shows some startling insight into the way that MS is paraniod to kill off a product just in case.
Kaplan had formed a startup to try and produce PDA's - long before Palm. As a condition of the funding he received he had to look at using Windows CE. MS made him sign a very one sided NDA and IP form.
Several months later, Kaplan was on the verge of signing a massive contract with an Insurance firm to provide these PDA's to agents. It would have ensured the survival of his company and allowed him to expand his operations.
Suddenly found that this customer was no longer willing to buy his product. Why? Because MS had approached his customers and sold them on an MS PDA solution.
Kaplans company tanked because venture capatilists were no longer willing to invest in a company that was trying to compete in the same market space as Microsoft.
If this doesn't highlight that customers haven't been harmed, I don't know what does.
He talks about being a uniter. Traditionally the way politicans did this was to create something that distracted people away from politics and got them arguing over something else.
Thatcher did this in Britan by blowing a small diplomatic incident in the Falklands into a war. Before this she was deemed to be one of the worst prime ministers Britan had, and was about to lose an election so bad, the liberals would probably have been the second party.
I see this in Bush's missile shield plan. Who exactly is he trying to shield America from? USSR is split up; most of those countries don't have the money to keep thier people fed never mind developing and upkeeping ICBMs. China needs the US to keep money going into the country. It's a ploy to distract people from the more thorny issues.
Bush may well prove to be the bait and switch president.
Depends. Some of the AXP platforms use standard PCI hardware.
Some software on AXP I've used ran a system configuration utility and listed the relevant items to a file. You took a copy of this and phoned the supplier and they gave you the licence code over the phone. This worked ok for a small supplier who probably didn't get that many calls.
Can you imagine the hit that MS will get when their multi-million machine install base hits the license reg line? Their support system is bad enough already. This may break their system entirely.
Wierd thing is that PARC accomplishments always appear many years after they actually invented them. They produced all sorts of neat stuff and then sat on it until Steve Jobs or Bill Gates etc borrowed the idea and made it successful.
This is about the continuation of music. Most of my MP's are from bands long since split, and the record company hasn't any CD's. Many of the bands I like were pre-CD so none exist, and all thats there is from other fans that have digitized thier cassettes and LP's to ensure that people can still listen to the work.
The normal reaction from microsoft usually is "we set the standard for others to follow".
This is an excellent example of this. By forcing in all these extension, and by having a large market share, they will force other developers to include these extension in thier products or force people to use IE 5.5.
When I come across a site thats IE oriented I either try to ignore the complaints that mozilla puts up, or I hunt around for that sites nearest competitor and use them instead.
Develop on what your target customer base is...
on
Why Develop On Linux?
·
· Score: 5
I am a multi-platform developer. I write and maintain code on VMS, Windows, and Linux.
I've used nearly every type of tool there is to develop on, so heres my 2 cents:
General: All systems support whatever language you want to code in. C++, Pascal, Basic - these are all available. CVS is available on all systems. What differs is the user interface on the development tools on the systems, and the amount of learning time you have to spend before commencing coding.
Windows: Developing on windows is a good way to get to know the closed source system. Documentation is hard, and is often expensive to come by. Mostly people develop code using Microsoft tools. These tools look pretty and work ok. They allow you to edit, compile and run code. As a development environment is good. Whatever you want it there within easy reach. To start developing seriously for windows you are best off buying the Microsoft developer tools. You need to be prepared to continue to upgrade everytime Microsoft release a new OS. This is very costly, and not something a teenager can easily get into. There are free tools for developing under windows, but the windowing system calls make it a nightmare to be productive. Learning time is almost zero - mostly if you draw up your screen and hit run, it will. This can be a drawback in a large app if you need to maintain it on a daily basis - it can be hard to get to module you want quickly.
VMS: This is not something that is often done in someones bedroom. Alpha machines can be expensive, and follow the Apple style of making sure you use everything that Compaq can produce. The tools are good, and the documentation is excellent. The librarys are well documented, and do exactly what the docs say they will. Only in rare cases will these change radically enough to break your code. Developing under VMS is about the same as linux. You have good tools and good documentation, nothing too flash or pretty, but it's all very functional. Standards are so rigoursly enforced that as long as you obey the rules you'll never have to worry about your code crashing because of a conflict with some other piece of code. The drawback is that VMS developers are rare these days and good help is hard to get. Learning time is short, as the tools are basic enough to do exactly what everybody needs to do.
Linux: Developing under linux is nice. There are a lot of tools and a lot of people available to help when something happens. Newbies are very welcome. The range of linux distros and linux ports make it hard to write code once and forget about it. You need to figure out tools such as autoconfigure if you plan on being multi-vendor/multi-platform. Linux isn't as easy to code for as windows is, but if you are developing under open source you will get excellent peer review if your code is something everyone wants. Many of the tools are similar to other systems, but many have been scaled up to support world-wide development. Learning time can be long if you have to start a project from scratch, but is simple enough if you just want to contribute.
Youc an see with when you see people getting so protective of thier money, to the point of trying to strangle new technology to keep it within thier grasp.
You can see it when these people go infront of the worlds press and are able to make all sorts of statements full of facts and figures off thier head and have an answer to any and all questions.
Put them on the stand where people have a chance to ask questions and delve for the truth behind the facts and figures, and they suddenly develop a bad memory and can't quite figure out where they heard some facts and figures.
Courtney Love's rant in salon.com shows what the artists at the recieving end are really getting from all the protection: next to nothing.
The sooner that things like the RIAA die off the sooner you will find local bands getting success because they are actually good musicians, and not getting success because they have a manager that knows someone.
The same goes for DVD technology. Robert Rodrigeuz was the exception to the rule when a small filmmaker could actually make a film for nothing and get it taken by a studio. Locking up the DVD distribution and technology will allow executives to have control over who gets to pay them money to buy films.
Why isn't there more use of minidiscs or zip disks. In the case of minidiscs the technology has been long established is availabe and is pretty reliable.
I wonder how many people will get a coaster full of memories when the CD-R fails to burn or drains the last few amps from the batteries.
Digital Cameras are at the stage where they don't need marketing gimmicks (floppy disks, CD-R etc). What people need is something as usuable as a 35mm camera - you take your pictures, fill up a media storage unit, change it and take more.
"You don't even need to download drivers when plugging a USB device into your CPU."
This jargon was as common as asking someone for an aspirin or to pass the salt. After that first meeting, I needed the aspirin - what a headache!
And the tech tips get worse:
6.This is a hard one for most of us - but you really must make sure you read and follow the product directions carefully to make sure you set it up properly. Taking the time to review the instructions the first time will save you many headaches later on. (I promise!)
No wonder there is an uproar. If this was a parody site I'd understand. I don't think too many women would take this air-headed rubbish for very long before going off and getting better information from somewhere else.
This an Alan Cox ftp server. He named it parcelfarce after the mail delivery system (Parceforce) managed to break the original server really well during delivery.
I gave up the option of programming for a games company to go do a CS degree. It was a bad mistake for me, as the degree started out good but drifted away from what was relevant and cutting edge and in the end I came out behind of where I would have been.
The most important thing is knowing how a program should be written and the most effiecient way of writing it while making it maintainable. Some people have the knowledge naturally, but its not a thing that can be taught.
When I'm hiring people I hire based on how quickly they can catch onto ideas and implement them, not on how many degrees they have. One of the best programmers I have came straight out of high school.
I ended up as systems programmer by accident. I drifted into the field when it was noticed I knew more about what held the systems together than anyone else in the company. A lot of systems programming these days seems to be making jobs easier for non-tech staff. I write a lot of user interface stuff that shows the staff in charge of changing backup tapes exactly when theres an error and what to do about it. I write utilites that automatically let me know when the system is having a problem that needs my attention. The greatest goal I have as a systems programmer is to have a long stretch where I can sit back and do not very much at all apart from keep up to date on new technology.
I'd agree with this, but with a few additions. I find that as a system programmer my job is to write code that works well enough that nobody actually notices that there is a lot of hardware that they rely on. Making sure that everything remains linked together and that the users have 365 days of uptime is the most important goal of a systems programmer. Mostly I end up writing utilities that make life easier to manage the systems.
The more stuff like this goes up the more people will get interested in space. The more this happens the more politicians are willing to fund projects like this.
Instead of actually increasing the security of thier mailer and stopping the ease of access to the address book, the various gaping holes allowing access to the O/S and the general probelms of macro scripts, they block access to certain filetypes.
This won't actually stop the problems that Outlook has or causes, but it will slow it down a little. Now people will save them off to thier disks and run the programs from there allowing more access to Back Orifice, and a.BAT containing "Deltree/y c:\"
This is typical of what happens when a corporation becomes stale.
Good riddance I say. The more more people are scared away from Microsoft the better.
They have missed the point of open source, but there are precedents for doing this, eg a developer notices a way mozilla could leak credit card info. However:
1. By hiding the hole they are blocking interested developers from having a chance to explore and fix the problem
2. In many cases the bug would probably be talked about (and possibly exploited) on Bugtraq anyway
3. They should be secure enough in thier beliefs that if a serious security bug is found instead of hiding the fact, they should issue an announcement saying there is a bug, and leave it up to people to decide if the software should be used until a solution is found. There could be levels of this, eg: a) Bug is serious, and being exploited in the wild, b) Bug is serious and not being exploited c) Bug is minor, but some people may be affected
Once a fix is found this could be distributed on a mailing list.
Doesn't this conflict with the Human Rights? I would treat my encrypted data the same as the right not to answer questions (although looking at thier anti-terrorist laws that didn't stop them removing the right to silence and juryed trials.)
Slashdot Mirror
jwz has a 24/7 webcam running in his nightclub that is being reconstructed. So far people have stolen:
o The webcam
o Two amplifiers
o The controller for the emulator lights
All he managed to get was a few blurry shots of the guy that stole the webcam.
Crackerjack was a UK kids TV pantomime/game show.
It was introduced whit: "It's friday, it`s 5 to 5, it's CRACKERJACK !"
The prizes were pretty crap - you could win a cabbage, or a crackerjack pencil. Later I guess they must have gotten a budget and you could win a crackerjack pen.
One of the things the show had, was that anytime any of the hosts said the word "crackerjack" the audience would yell out "crackerjack" really loudly.
It was a very strange show.
Heres a short clip
Read "Start Up" by Jerry Kaplan. It shows some startling insight into the way that MS is paraniod to kill off a product just in case.
Kaplan had formed a startup to try and produce PDA's - long before Palm. As a condition of the funding he received he had to look at using Windows CE. MS made him sign a very one sided NDA and IP form.
Several months later, Kaplan was on the verge of signing a massive contract with an Insurance firm to provide these PDA's to agents. It would have ensured the survival of his company and allowed him to expand his operations.
Suddenly found that this customer was no longer willing to buy his product. Why? Because MS had approached his customers and sold them on an MS PDA solution.
Kaplans company tanked because venture capatilists were no longer willing to invest in a company that was trying to compete in the same market space as Microsoft.
If this doesn't highlight that customers haven't been harmed, I don't know what does.
Sounds like something Gibson would write.
He talks about being a uniter. Traditionally the way politicans did this was to create something that distracted people away from politics and got them arguing over something else.
Thatcher did this in Britan by blowing a small diplomatic incident in the Falklands into a war. Before this she was deemed to be one of the worst prime ministers Britan had, and was about to lose an election so bad, the liberals would probably have been the second party.
I see this in Bush's missile shield plan. Who exactly is he trying to shield America from? USSR is split up; most of those countries don't have the money to keep thier people fed never mind developing and upkeeping ICBMs. China needs the US to keep money going into the country. It's a ploy to distract people from the more thorny issues.
Bush may well prove to be the bait and switch president.
Depends. Some of the AXP platforms use standard PCI hardware.
Some software on AXP I've used ran a system configuration utility and listed the relevant items to a file. You took a copy of this and phoned the supplier and they gave you the licence code over the phone. This worked ok for a small supplier who probably didn't get that many calls.
Can you imagine the hit that MS will get when their multi-million machine install base hits the license reg line? Their support system is bad enough already. This may break their system entirely.
Wierd thing is that PARC accomplishments always appear many years after they actually invented them. They produced all sorts of neat stuff and then sat on it until Steve Jobs or Bill Gates etc borrowed the idea and made it successful.
This is about the continuation of music. Most of my MP's are from bands long since split, and the record company hasn't any CD's. Many of the bands I like were pre-CD so none exist, and all thats there is from other fans that have digitized thier cassettes and LP's to ensure that people can still listen to the work.
The normal reaction from microsoft usually is "we set the standard for others to follow".
This is an excellent example of this. By forcing in all these extension, and by having a large market share, they will force other developers to include these extension in thier products or force people to use IE 5.5.
When I come across a site thats IE oriented I either try to ignore the complaints that mozilla puts up, or I hunt around for that sites nearest competitor and use them instead.
I am a multi-platform developer. I write and maintain code on VMS, Windows, and Linux.
I've used nearly every type of tool there is to develop on, so heres my 2 cents:
General: All systems support whatever language you want to code in. C++, Pascal, Basic - these are all available. CVS is available on all systems. What differs is the user interface on the development tools on the systems, and the amount of learning time you have to spend before commencing coding.
Windows: Developing on windows is a good way to get to know the closed source system. Documentation is hard, and is often expensive to come by. Mostly people develop code using Microsoft tools. These tools look pretty and work ok. They allow you to edit, compile and run code. As a development environment is good. Whatever you want it there within easy reach. To start developing seriously for windows you are best off buying the Microsoft developer tools. You need to be prepared to continue to upgrade everytime Microsoft release a new OS. This is very costly, and not something a teenager can easily get into. There are free tools for developing under windows, but the windowing system calls make it a nightmare to be productive. Learning time is almost zero - mostly if you draw up your screen and hit run, it will. This can be a drawback in a large app if you need to maintain it on a daily basis - it can be hard to get to module you want quickly.
VMS: This is not something that is often done in someones bedroom. Alpha machines can be expensive, and follow the Apple style of making sure you use everything that Compaq can produce. The tools are good, and the documentation is excellent. The librarys are well documented, and do exactly what the docs say they will. Only in rare cases will these change radically enough to break your code. Developing under VMS is about the same as linux. You have good tools and good documentation, nothing too flash or pretty, but it's all very functional. Standards are so rigoursly enforced that as long as you obey the rules you'll never have to worry about your code crashing because of a conflict with some other piece of code. The drawback is that VMS developers are rare these days and good help is hard to get. Learning time is short, as the tools are basic enough to do exactly what everybody needs to do.
Linux: Developing under linux is nice. There are a lot of tools and a lot of people available to help when something happens. Newbies are very welcome. The range of linux distros and linux ports make it hard to write code once and forget about it. You need to figure out tools such as autoconfigure if you plan on being multi-vendor/multi-platform. Linux isn't as easy to code for as windows is, but if you are developing under open source you will get excellent peer review if your code is something everyone wants. Many of the tools are similar to other systems, but many have been scaled up to support world-wide development. Learning time can be long if you have to start a project from scratch, but is simple enough if you just want to contribute.
Youc an see with when you see people getting so protective of thier money, to the point of trying to strangle new technology to keep it within thier grasp.
You can see it when these people go infront of the worlds press and are able to make all sorts of statements full of facts and figures off thier head and have an answer to any and all questions.
Put them on the stand where people have a chance to ask questions and delve for the truth behind the facts and figures, and they suddenly develop a bad memory and can't quite figure out where they heard some facts and figures.
Courtney Love's rant in salon.com shows what the artists at the recieving end are really getting from all the protection: next to nothing.
The sooner that things like the RIAA die off the sooner you will find local bands getting success because they are actually good musicians, and not getting success because they have a manager that knows someone.
The same goes for DVD technology. Robert Rodrigeuz was the exception to the rule when a small filmmaker could actually make a film for nothing and get it taken by a studio. Locking up the DVD distribution and technology will allow executives to have control over who gets to pay them money to buy films.
Why isn't there more use of minidiscs or zip disks. In the case of minidiscs the technology has been long established is availabe and is pretty reliable.
I wonder how many people will get a coaster full of memories when the CD-R fails to burn or drains the last few amps from the batteries.
Digital Cameras are at the stage where they don't need marketing gimmicks (floppy disks, CD-R etc). What people need is something as usuable as a 35mm camera - you take your pictures, fill up a media storage unit, change it and take more.
This is what users need right now.
Fromt the microsoft digital diva site:
"You don't even need to download drivers when plugging a USB device into your CPU."
This jargon was as common as asking someone for an aspirin or to pass the salt. After that first meeting, I needed the aspirin - what a headache!
And the tech tips get worse:
6.This is a hard one for most of us - but you really must make sure you read and follow the product directions carefully to make sure you set it up properly. Taking the time to review the instructions the first time will save you many headaches later on. (I promise!)
No wonder there is an uproar. If this was a parody site I'd understand. I don't think too many women would take this air-headed rubbish for very long before going off and getting better information from somewhere else.
This an Alan Cox ftp server. He named it parcelfarce after the mail delivery system (Parceforce) managed to break the original server really well during delivery.
I gave up the option of programming for a games company to go do a CS degree. It was a bad mistake for me, as the degree started out good but drifted away from what was relevant and cutting edge and in the end I came out behind of where I would have been.
The most important thing is knowing how a program should be written and the most effiecient way of writing it while making it maintainable. Some people have the knowledge naturally, but its not a thing that can be taught.
When I'm hiring people I hire based on how quickly they can catch onto ideas and implement them, not on how many degrees they have. One of the best programmers I have came straight out of high school.
I ended up as systems programmer by accident. I drifted into the field when it was noticed I knew more about what held the systems together than anyone else in the company. A lot of systems programming these days seems to be making jobs easier for non-tech staff. I write a lot of user interface stuff that shows the staff in charge of changing backup tapes exactly when theres an error and what to do about it. I write utilites that automatically let me know when the system is having a problem that needs my attention. The greatest goal I have as a systems programmer is to have a long stretch where I can sit back and do not very much at all apart from keep up to date on new technology.
I'd agree with this, but with a few additions. I find that as a system programmer my job is to write code that works well enough that nobody actually notices that there is a lot of hardware that they rely on. Making sure that everything remains linked together and that the users have 365 days of uptime is the most important goal of a systems programmer. Mostly I end up writing utilities that make life easier to manage the systems.
The more stuff like this goes up the more people will get interested in space. The more this happens the more politicians are willing to fund projects like this.
Instead of actually increasing the security of thier mailer and stopping the ease of access to the address book, the various gaping holes allowing access to the O/S and the general probelms of macro scripts, they block access to certain filetypes.
.BAT containing "Deltree /y c:\"
This won't actually stop the problems that Outlook has or causes, but it will slow it down a little. Now people will save them off to thier disks and run the programs from there allowing more access to Back Orifice, and a
This is typical of what happens when a corporation becomes stale.
Good riddance I say. The more more people are scared away from Microsoft the better.
The following things must be remembered:
1) We own our posts
2) There still is freedom of speech
3) Microsoft can't always get its own way on things.
I think it's come to the moment when Microsoft are employing more lawyers than programmers, and thats not a good thing.
The more this happens the less people will trust Microsoft, even after a breakup.
don't forget that jwz left mozilla/netscape on april 1st, and that was no joke.
They have missed the point of open source, but there are precedents for doing this, eg a developer notices a way mozilla could leak credit card info. However:
1. By hiding the hole they are blocking interested developers from having a chance to explore and fix the problem
2. In many cases the bug would probably be talked about (and possibly exploited) on Bugtraq anyway
3. They should be secure enough in thier beliefs that if a serious security bug is found instead of hiding the fact, they should issue an announcement saying there is a bug, and leave it up to people to decide if the software should be used until a solution is found. There could be levels of this, eg:
a) Bug is serious, and being exploited in the wild,
b) Bug is serious and not being exploited
c) Bug is minor, but some people may be affected
Once a fix is found this could be distributed on a mailing list.
I think someone needs to have a word with this guy. Usually these attacks are done with custom written programs, not a OS.
Any OS with an IP stack can be used for these attacks.
This guy is hyping a fear for the clueless so that these upper management people will rush out and buy his "software".
He's mixed up worms, viruses and DoS in one big muddled heap.
I would not even think about touching this protection software, if this is what they say it can fix.
I think he needs an editor. This is something that would have been caught elsewhere.
Doesn't this conflict with the Human Rights? I would treat my encrypted data the same as the right not to answer questions (although looking at thier anti-terrorist laws that didn't stop them removing the right to silence and juryed trials.)