I'm not opposed to CFL since I've replaced the incandescent bulbs everywhere except the chandeliers, fridge and stove with CFL.
My large problems are the chandeliers. I tried LED but they were too dim and I can't use CFL because they would e just plain ugly plus they are on a variable dimmer and CFL only seem to do well on two stage dimmers.
You can set a time limit on the threshold. Assume 32 days in a month $50 000 would be $1562 per day that's $65 worth of micro payments in an hour. That's a lot of transactions to be spread around not very many providers.
They could flag anything over a certain amount per hour or per day and catch the worst of the offenders.
I'm guessing the only reason they haven't done that so far is because it didn't occur to anyone that the system could be gamed that way.
These tools require skill. Blindly fixing things that Lint shows up can introduce new bugs or conversely using lint notation to shut the warnings off can mask bugs.
I also don't think new languages help bad programmers much. Bad code is still bad code so now instead of crashing it will just memory leak or just not work right.
On a software project I worked on before our competition spent two years and two million dollars did their code in visual basic and MSSQL and they abandoned their effort when no matter what hardware they threw at it they couldn't get their software to handle more than 400 concurrent users. We did our project in C and with a team for 4 built something in about a year that handled 1200 users on a quad CPU P III 400mhz Compaq. Even when another competitor posed as a client and borrowed some of my ideas (they added a comms layer instead of using the SQL server for communication) they still required a whole rack of machines to do what we did with one out of badly out of date test machine.
C is a fine tool if you know how to use it so I doubt it will go away any time soon.
I found even tools like lint or splint can catch interesting bugs but not nearly as many as the time I enabled GCC's type checking for varargs on a software project a company I work for was developing.
Because Bell is doing the traffic shaping where they have no business dong it: Between the end users and the isp.
Bell rents the lines out by tunneling the pppoe connection right to the reseller isp so the isp can traffic shape if they want to. Bell has right to force business decisions on third party isps since they pay for all of the resources they use.
It's not about the office so much as the tasks. I had an employer come in one day and tell me he was going to start putting together Porn and Bestiality sites and have his new partner (Alan Ralsky) bulk mail advertise them.
The main difference in ADSL is that unlike dialup modems the ADSL equipment has noise level thresholds. Most of the DSLAMs I've worked step up the speed, check the noise against the threshold then if the noise level is low enough it will step up the speed again. The idea is that it backs off before the connection gets unreliable.
If RedHat doesn't provide good service it's customers can go to someone else who can just take over the service and bug repair. No actual need for Red Hat.
If a GPL project stagnates than it can simply be forked. This is what happened to the X11 code base when the X.org people decided they could do better and forked.
GCC is actually a perfect example as well. Several years ago someone thought they could do better and made pgcc. The GCC people woke up and agreed with then and ended up merging much of PGCC's code.
What your missing here is that you never should have had to go to the BIOS at all. That was DOS job.
The fact DOS functions were so blasted slow that everyone just bypassed them was something that would come to haunt MicroSoft for years. Why did MS have to come up with the abortion known as VFAT? Every text book and programming guide for DOS that I've ever owned has come with instructions on how to write to the FAT tables directly. That's bad.. very bad. It made things inflexible and provided no way for the OS to make sure things were done right.
To make it more amusing those third party APIs slog through the win32 API hell so you don't have to.
I think that's why Microsoft is afraid of breaking the old APIs. Once you have to go through the pain of porting to a new API why not just go cross platform?
Ever seen someone go crazy? Good luck grabbing their arms. And when you do try to pin them down try doing it without putting the wrong pressure on the back , neck or vital organs and at the same time try not to put so much pressure on their rib cage that they can't breathe.
Having overwhelming firepower is only effective if the opponent is in a state where they can understand the danger they are in. If someone is sufficiently riled up they may not be able to care or understand that they are likely to be shot. Someone in that state is also likely to get seriously injured (or die) in the process of being physically subdued.
And of course that's on top of the risk of injury to the police from bitting scratching, needles in pocket etc.
Tazer is still the best option in many cases. The only down side is that I think the police have gotten too used to thinking of them as "non lethal" and sometimes end up using them where no confrontation was needed at all.
Because there is a finite number of people who need money and are capable of paying it back. As that pool is used up they increasingly need to look for more risky ventures to inflate the value of their portfolio.
It's the same thing with bank loans. Right now I can't walk into the bank without them trying to sell me on some way they can loan me money. But for the most part people with good credit ratings have borrowed as much as they intend to. The result is that the banks loaned money to people with more risky ratings.
It all works great until something pulls the rug a little and the whole system collapses on itself. Pretty much the exact thing your seeing with the sub prime mortgage crisis.
I imagine that the sub prime crisis will cause SCO more than a bit of trouble refinancing since the pool of money that people are willing to loan out is a lot smaller at the moment.
In downtown Montreal theres a Greek guy flipping burgers. One day he tells me he opened the burger place because he got tired of the computer business.
Same goes for the Pakistani restaurant around the corner from my house which is also run by a guy who used to be in the IT business.
They both tell me they are happier and make better money.
Because quite often hedge fund managers don't care whether each individual investment will make money. If I loan money to SCO I can tell my investors the funds is now grown by the inflated value on paper that SCO agreed to and the bigger numbers brings more investors and hopefully by the time SCO tanks I'll have made the money back elsewhere.
This has the fun advantage of making life easier for people designing websites. Fewer old browsers out there means you don't need as many stupid hacks to make it all work.
I'm not opposed to CFL since I've replaced the incandescent bulbs everywhere except the chandeliers, fridge and stove with CFL.
.. more options are needed.
My large problems are the chandeliers. I tried LED but they were too dim and I can't use CFL because they would e just plain ugly plus they are on a variable dimmer and CFL only seem to do well on two stage dimmers.
So yeah
Not a bank but still considered a form of Banking.
Any messing with systems involving financial transactions can get you bank fraud / wire fraud.
You can set a time limit on the threshold. Assume 32 days in a month $50 000 would be $1562 per day that's $65 worth of micro payments in an hour. That's a lot of transactions to be spread around not very many providers.
They could flag anything over a certain amount per hour or per day and catch the worst of the offenders.
I'm guessing the only reason they haven't done that so far is because it didn't occur to anyone that the system could be gamed that way.
Payment systems are considered a form of banking.
The problem is that I've used whois info to alert mail admins to known problems with their servers.
While I doubt the whole address needs to be in the whois info a contact email/ number would be preferable to blocking everything.
These tools require skill. Blindly fixing things that Lint shows up can introduce new bugs or conversely using lint notation to shut the warnings off can mask bugs.
I also don't think new languages help bad programmers much. Bad code is still bad code so now instead of crashing it will just memory leak or just not work right.
On a software project I worked on before our competition spent two years and two million dollars did their code in visual basic and MSSQL and they abandoned their effort when no matter what hardware they threw at it they couldn't get their software to handle more than 400 concurrent users. We did our project in C and with a team for 4 built something in about a year that handled 1200 users on a quad CPU P III 400mhz Compaq. Even when another competitor posed as a client and borrowed some of my ideas (they added a comms layer instead of using the SQL server for communication) they still required a whole rack of machines to do what we did with one out of badly out of date test machine.
C is a fine tool if you know how to use it so I doubt it will go away any time soon.
I found even tools like lint or splint can catch interesting bugs but not nearly as many as the time I enabled GCC's type checking for varargs on a software project a company I work for was developing.
Because Bell is doing the traffic shaping where they have no business dong it: Between the end users and the isp.
Bell rents the lines out by tunneling the pppoe connection right to the reseller isp so the isp can traffic shape if they want to. Bell has right to force business decisions on third party isps since they pay for all of the resources they use.
It's not about the office so much as the tasks. I had an employer come in one day and tell me he was going to start putting together Porn and Bestiality sites and have his new partner (Alan Ralsky) bulk mail advertise them.
The main difference in ADSL is that unlike dialup modems the ADSL equipment has noise level thresholds. Most of the DSLAMs I've worked step up the speed, check the noise against the threshold then if the noise level is low enough it will step up the speed again. The idea is that it backs off before the connection gets unreliable.
Say what? GPL does the exact opposite of that.
If RedHat doesn't provide good service it's customers can go to someone else who can just take over the service and bug repair. No actual need for Red Hat.
If a GPL project stagnates than it can simply be forked. This is what happened to the X11 code base when the X.org people decided they could do better and forked.
GCC is actually a perfect example as well. Several years ago someone thought they could do better and made pgcc. The GCC people woke up and agreed with then and ended up merging much of PGCC's code.
Bell will do that to keep the DSL modem from trying to synch at a faster rate than it can handle.
Not sure of the logic since it's supposed to autodetect but people tell me it makes things more reliable.
What your missing here is that you never should have had to go to the BIOS at all. That was DOS job.
The fact DOS functions were so blasted slow that everyone just bypassed them was something that would come to haunt MicroSoft for years. Why did MS have to come up with the abortion known as VFAT? Every text book and programming guide for DOS that I've ever owned has come with instructions on how to write to the FAT tables directly. That's bad.. very bad. It made things inflexible and provided no way for the OS to make sure things were done right.
And you believe they actually will? Jokes about Microsoft promising big things and then failing to deliver have been around since the 80s.
To make it more amusing those third party APIs slog through the win32 API hell so you don't have to.
I think that's why Microsoft is afraid of breaking the old APIs. Once you have to go through the pain of porting to a new API why not just go cross platform?
Is this Chinese government or botnets on Chinese computers?
My server gets nailed daily from China but I doubt their government knows anything about it so I'm finding these stories a bit paranoid.
Ever seen someone go crazy? Good luck grabbing their arms. And when you do try to pin them down try doing it without putting the wrong pressure on the back , neck or vital organs and at the same time try not to put so much pressure on their rib cage that they can't breathe.
Having overwhelming firepower is only effective if the opponent is in a state where they can understand the danger they are in. If someone is sufficiently riled up they may not be able to care or understand that they are likely to be shot. Someone in that state is also likely to get seriously injured (or die) in the process of being physically subdued.
And of course that's on top of the risk of injury to the police from bitting scratching, needles in pocket etc.
Tazer is still the best option in many cases. The only down side is that I think the police have gotten too used to thinking of them as "non lethal" and sometimes end up using them where no confrontation was needed at all.
I like the Canadian way. It's free unless you did something stupid like go into an area marked as dangerous (avalanche zone etc).
Because there is a finite number of people who need money and are capable of paying it back. As that pool is used up they increasingly need to look for more risky ventures to inflate the value of their portfolio.
It's the same thing with bank loans. Right now I can't walk into the bank without them trying to sell me on some way they can loan me money. But for the most part people with good credit ratings have borrowed as much as they intend to. The result is that the banks loaned money to people with more risky ratings.
It all works great until something pulls the rug a little and the whole system collapses on itself. Pretty much the exact thing your seeing with the sub prime mortgage crisis.
I imagine that the sub prime crisis will cause SCO more than a bit of trouble refinancing since the pool of money that people are willing to loan out is a lot smaller at the moment.
In downtown Montreal theres a Greek guy flipping burgers. One day he tells me he opened the burger place because he got tired of the computer business.
Same goes for the Pakistani restaurant around the corner from my house which is also run by a guy who used to be in the IT business.
They both tell me they are happier and make better money.
Because quite often hedge fund managers don't care whether each individual investment will make money. If I loan money to SCO I can tell my investors the funds is now grown by the inflated value on paper that SCO agreed to and the bigger numbers brings more investors and hopefully by the time SCO tanks I'll have made the money back elsewhere.
Short sighted? Yep. Evil conspiracy? Not so much.
What it sounds like is that the CNET author didn't know what he was talking about.
Fujitsu says it uses an ATA password so it's most likely using the password to generate the key.
This has the fun advantage of making life easier for people designing websites. Fewer old browsers out there means you don't need as many stupid hacks to make it all work.
But the next time they login they could end up exploited before the patch is installed.