I guess I'm a baby steps kinda guy, let me have an open source player, with black box codecs first. The rest will come.
Unlikely. If Real is ensuring the player remains compatable with the codecs then there is no incentive (or no more incentive than before) for people to try and write new ones, since the closed ones will always "just work".
I think the PC artchitecture was probably open to commoditise IBM's parts suppliers since IBM were trying to make a cheap computer. Then they kept the BIOS closed so nobody else could make one (at least until it was reverse engineered). Once the BIOS was duplicated the open architecture bit them in the ass, since there was no big HW advantage to an IBM one.
These are the same people that advocate nightly builds and all that other crap that just gets in the way.
What's wrong with nightly builds?
They ensure that the code is always compilable and basically working, and give the test team something concrete to actually test. They allow you to see at what point regression was introduced, and fix it quickly. They iron out any problems in your build process, well before it comes time to ship. They can be automated. If you use a documentation generator they ensure that the docs are always up to date. They give visibility of SW maturity to management. I think that if a nightly build gets in the way, then the team is not efficient, and doesn't have a good idea of what is it doing in the first place.
Ignore the experience required (within reason of course), and try to get the CV to the hiring manager rather than HR. The only thing that's certain is that if you don't apply for a position, you won't get it. Make sure you tailor your CV to emphasise all the other things that match the job requirements though.
If you can get an interview you can impress enough to get a offer. Maybe not the one you applied for of course, but many companies offer interviewees other positions if they think they are good. At worst you will have gotten some interview experience, and a chance to meet somebody with hiring ability or influence at a company.
My experience: Bsod exists in win2k for sure, rarer than Win98, but certainly not eradicated by any means. I have seen it repeatedly at work.
I haven't seen bsod in my home WinXP yet, though instead it's main explorer.exe crashes fairly frequently. I guess they have found a way to make what was previously a bsod just take down explorer now.
...to whoever develops the warp drive and twice that for the transporter.
Shouldn't you be go for the replicator first? By the time the other two are done you might have replicated enough dollar bills to actually pay for them.
This is probably a dumb question, but is it not possible for ISPs to virus scan all web traffic? Your "service" should not infect your customers computers. In any other walk of life that would be basic expectation.
Yes, but be honest. You can't really "buy" free software, you can only pay for it. Everyone gets it once it's paid for, not just the "buyer"s. Contrast Linux, which some companies and individuals have "paid for" in various ways, against Windows which 95% of the desktop market has "bought". Of course whether that is a good or bad thing depends entirely on your philosophy (and how you make your living at this point in time:-)
Well, I have worked in plces that develop big commercial software, and I agree 100% with the grandparent.
There is almost no excuse for death march projects in modern software development. It is just poor management and/or a team not experienced enough to tell management that they don't know what the hell they are doing (in a diplomatic way naturally).
What will happen if you launch a ship to Mars from Earth? What is the gravity on the way from Earth to Mars? (I guess it varies). Would it be enough to keep you pressed against one side of the ship? Does it go to zero (or as close to zero as makes no difference to our primitive human senses)?
This is the third or fourth time in the last few months that people have asked basically the same questions about open source medical stuff on ask slashdot. What gives?
In practice, however, the macrokernel has been far easier to work with.
Tell me about it. However, I think that proper debugger support for message passing would go a long way to reducing the problems. Debuggers that recognised the OS's messaging passing system, and treaded it like a function call would be great. Beats putting a breakpoint in a some kern_pass_message function anyway.
Most of the 'stupid' users out there are simply lazy, and feel that if they whine long enough the computer will do for them
And the obvious question to ask is why the hell doesn't it? It's perfectly capable of doing so after all.
It is ridiculous to require a user to do things that can be easily automated. That includes compiling a kernel on a system where regular kernel upgrades are a requirement.
I just suggested to my son-in-law that if he wanted a job in IT the place to be was probably in networking - preferably telecom
I don't know about the US, but elsewhere Telecom has been one of the hardest hit sectors of IT. It was one of the first and most severe casualties of the bursting bubble.
Slashdot Mirror
I think the PC artchitecture was probably open to commoditise IBM's parts suppliers since IBM were trying to make a cheap computer. Then they kept the BIOS closed so nobody else could make one (at least until it was reverse engineered). Once the BIOS was duplicated the open architecture bit them in the ass, since there was no big HW advantage to an IBM one.
What's wrong with nightly builds?
They ensure that the code is always compilable and basically working, and give the test team something concrete to actually test. They allow you to see at what point regression was introduced, and fix it quickly. They iron out any problems in your build process, well before it comes time to ship. They can be automated. If you use a documentation generator they ensure that the docs are always up to date. They give visibility of SW maturity to management. I think that if a nightly build gets in the way, then the team is not efficient, and doesn't have a good idea of what is it doing in the first place.
Ignore the experience required (within reason of course), and try to get the CV to the hiring manager rather than HR. The only thing that's certain is that if you don't apply for a position, you won't get it. Make sure you tailor your CV to emphasise all the other things that match the job requirements though.
If you can get an interview you can impress enough to get a offer. Maybe not the one you applied for of course, but many companies offer interviewees other positions if they think they are good. At worst you will have gotten some interview experience, and a chance to meet somebody with hiring ability or influence at a company.
My experience: Bsod exists in win2k for sure, rarer than Win98, but certainly not eradicated by any means. I have seen it repeatedly at work.
I haven't seen bsod in my home WinXP yet, though instead it's main explorer.exe crashes fairly frequently. I guess they have found a way to make what was previously a bsod just take down explorer now.
What they will do is require all TV stations to switch to . Then you can do whatever the hell you like with your VCR for all they care.
This is probably a dumb question, but is it not possible for ISPs to virus scan all web traffic? Your "service" should not infect your customers computers. In any other walk of life that would be basic expectation.
Yes, but be honest. You can't really "buy" free software, you can only pay for it. Everyone gets it once it's paid for, not just the "buyer"s. Contrast Linux, which some companies and individuals have "paid for" in various ways, against Windows which 95% of the desktop market has "bought". Of course whether that is a good or bad thing depends entirely on your philosophy (and how you make your living at this point in time :-)
but you can change between caps and no caps easily in any word processor or editor.
Well, I have worked in plces that develop big commercial software, and I agree 100% with the grandparent.
There is almost no excuse for death march projects in modern software development. It is just poor management and/or a team not experienced enough to tell management that they don't know what the hell they are doing (in a diplomatic way naturally).
What will happen if you launch a ship to Mars from Earth? What is the gravity on the way from Earth to Mars? (I guess it varies). Would it be enough to keep you pressed against one side of the ship? Does it go to zero (or as close to zero as makes no difference to our primitive human senses)?
What's wrong with rapeseed oil?
In reality the typical implementation of corporate knowledge management is some crappy lotus notes application.
This programmer has performed an illegal operation and will now be terminated.
I hear that electricity doesn't offer a strategic advantage anymore these days either.
a lot, but the pictures of "dark energy" can be compressed to this: "0,500000000"
You shouldn't have people doing a computer's job.
the way to increase security is to separate the password from the cryptographic key in the first place.
put the computer generated strong cryptographic key on a physical device, allow simple user chosen passwords.
Your security is 3 guesses of the password, proper cryptographic digital key, user allocated physical device.
finally somebody with a clue!
This is the third or fourth time in the last few months that people have asked basically the same questions about open source medical stuff on ask slashdot. What gives?
Tell me about it. However, I think that proper debugger support for message passing would go a long way to reducing the problems. Debuggers that recognised the OS's messaging passing system, and treaded it like a function call would be great. Beats putting a breakpoint in a some kern_pass_message function anyway.
Most of the 'stupid' users out there are simply lazy, and feel that if they whine long enough the computer will do for them
And the obvious question to ask is why the hell doesn't it? It's perfectly capable of doing so after all.
It is ridiculous to require a user to do things that can be easily automated. That includes compiling a kernel on a system where regular kernel upgrades are a requirement.
I just suggested to my son-in-law that if he wanted a job in IT the place to be was probably in networking - preferably telecom
I don't know about the US, but elsewhere Telecom has been one of the hardest hit sectors of IT. It was one of the first and most severe casualties of the bursting bubble.