There is a difference between saying "I don't want to rent it to men" and saying "I will not rent it to men". If you are a landlord advertising an apartment for sale, and state "men need not apply" in an ad, you're running afoul of anti-discrimination laws. It has nothing to do with your right to state your feelings on how men treat apartments.
You are one clueless fuck if you can't distinguish the difference between being prosecuted for saying "I'll give you $5 for a blowjob" to a prostitute and being prosecuted for soliciting a prostite. I'll give you a hint; you're not being prosecuted for the content of your speach, but rather your actions and intent.
You are indeed free to say and print whatever you want. That does not mean that you can say whatever you want and escape the consequences of those actions.
CLI in this context is a TLA for Common Language Infrastructure. CLI is a three letter acronym, which are by no means unique. The only people freaking out about this are morons such as yourself. Oh nos! A name for something has three words which start with C, L, and I! What ever shall we do!
It's a TLA. It isn't like Command Line Interface is the only set of words that start with C, L, and I that make sense. If it were we wouldn't need words in the first place.
Every time I'm walking through a house with a home inspector, they've noted that the insulation voids the waranty on the water heater. Personally, I don't give a crap, but...:)
Certainly -- an oven is a poor subsitute for a heater, and I didn't mean to give the impression that it was. But it is certainly cheaper to make something in the oven during the winter than it is in the summer and the "fireplace" effect is comforting.:)
Follow that one by shoping for clothes at the local version of Goodwill, turn down the heat, plug the drafts, and unplug appliances not in use. Consider adding an insulating blanket to your hot water heater, if it's not an instant-on type.
Doing this actually voids the warranty on most water heaters. You'd be better off inserting a foam insulation pad between the water heater and the floor -- most of the heat lost gets away through the ground.
You can make a HUGE difference in your heating bill by being more "frugal" with the heat. I cut my bill from $150 to $85 by letting the house get colder during the day, turning on the heat later and turning it off sooner. As my place is heated by electricity, I can have each room heated at different times. Turning off the heat in rooms I don't use also helped, as does keeping all of the doors between "zones" closed.
The hallway downstairs ends up being a bit chilly but I don't exactly spend a lot of time there...
An interesting side effect of this is that it helps you "keep" your schedule; if you've got to get up to turn the thermostat back up, you might as well just go to bed...
If you have flextime, you can also change your work schedule so that you spend more of your after dark hours at work (free heat!:)).
It all seems a bit excessive, but it's worth saving $250/year.
The other downside is that they aren't dimmable. (well, most arn't)
Not a huge deal for most people, but it is an issue if your light switches double as dimmers. Halogens are a good alternative if you're in that situation.
* If you are going to be consuming code you don't own, for the love of god run it in an external process. Create a defined plug-in like interface that your customers will use, and have a shim process designed to load the plug-in and perform communication back and forth with your real app. Your real app should assume that every attempt to communicate with the external process will fail and respond accordingly.
* Don't assume that hardware is fault free; assume that any and every operation than can fail will. I have personally tracked down application crashes that were the result of faulty hardware; in one instance, a machine had failure rates 20% higher than the rest of the machines -- turned out the mobo was faulty. In another instance, a harddrive was failing. I had one case where an object was allocated, verified not null, and passed in as a reference to a function -- which failed because the object was null...
I've dealt with software that automatically restarts a dead process, and in my experience, it doesn't work so good. If you want ultra-stable software, you want to know what caused the crash and why.
It works better if your application does logging and creates dumps of the faulting process before restarting. Post mortem debugging can be incredibly useful.
a) You aren't tied to the IDE; you can compile managed code using make if you prefer (which is, in fact, how it is done at my employer) b) Dumbing down has nothing to do with it. Making sure the language doesn't get in my way or throw up obstacles while tring to get something done has everything to do with it. (What, I don't have to spend a day wasting time writing redundant code and updating installer logic to create a new com server? Gee, what a downer.) c) Arguing that autocompletion is bad is akin to arguing that an English major shouldn't use the spellchecker in a wordprocessor. Autocomplete saves you time looking things up; you still have to remember how the "word" starts and what it means.
Trading at 45 times future earnings is a sign that the stock is overvalued and driven by speculation. I won't invest in a stock like that; too much risk, feels more like gambling than investing. If Microsoft were currently trading at 50-100 times earnings, I wouldn't be investing in it either. And given that Microsoft is now trading around 20-25 times earnings, I suspect that would have been a good decision a few years ago as well.
The last attempt I'm aware of to brute force a key in a console was for the Jaguar, and if I recall correctly they had roughly a dozen dev units trying key after key for a few years before finally cracking it (I'm not even sure they succeeded; I think the company that owned the rights at that time actually released it into the public domain). The encryption on that box was weak; we don't know what size the key they chose to use is, nor what method they use for signing the binary. A brute force approach is, in my opinion, impracticle; I'm not even sure it would be possible to do without burning test discs...
I don't know how the binaries on disc get signed. However, securing a private encryption key doesn't seem to be something they've ever had any difficulty with, given that they've managed do so with the keys they sign their binaries with since they started signing binaries; this also isn't something other companies seem to have much difficulty with... Hoping for the answer to fall into your lap from out of the sky doesn't seem to be a practicle solution to me either.
Most people believe that the key is stored in a boot rom INSIDE the cpu. Kind of hard to replace the public key without replacing the processor, and good luck getting ahold of a customized replacement...
Re:Fuzzing and Obfuscation
on
Mitnick on OSS
·
· Score: 1
Fuzzing is a technique that can be used to find buffer overflows, not exploit them.
So? 3D hardware wasn't supported AT ALL until DX5. DirectX was 2d only until '97. Back in the day Microsoft was planning on using OpenGL for 3d games, but the standards body moved at such a glacial pace (and had such a snobbish "opengl is for high end graphics only" attitude) that they said "screw it" and did their own thing.
For the same reason cross platform developers don't all use Java. You end up having to tweak things for every platform anyway. Just because something compiles doesn't mean it works right.
Early on in a console's life market share and adoption is more important than breaking even on the hardware. Market share attacts developers, which increases the number of games available for the system, which increases consumer interest, which in turn increases marketshare.
Losing money early on isn't a terribly big deal, as you expect to make it back over the life of the console when customers purchase new games or controllers/peripherals. Remember, early adopters will be "in" for much longer than people who purchase the hardware late in its life cycle. Later in the console's life cycle hardware costs become more important, as there is less time to make up the loss on the hardware.
So WHY didn't the original xbox never really wander into profitability? Hardware costs. Microsoft was unable to cost reduce their hardware; they didn't own any of the IP -- they were just buying off the shelf parts from nvidia and intel. Essentially, they were stuck paying the same prices for parts when they launched the unit as they are today; it was a GIGANTIC error on Microsoft part, and I'm sure Nvidia and Intel were trying to hold back some giant grins as the contracts were being signed.
With the 360, Microsoft owns all of the IP. They can have whoever they want manufacture the parts, they can shrink the chips, etc. The theory being that over time they'll be able to reduce costs and break even on hardware.
Microsoft sold 1.5 million consoles by the end of 2005. 900,000 in North America, 500,000 in Europe, and 100,000 in Japan. These figures were announced with their FY06Q2 results.
Slashdot Mirror
There is a difference between saying "I don't want to rent it to men" and saying "I will not rent it to men". If you are a landlord advertising an apartment for sale, and state "men need not apply" in an ad, you're running afoul of anti-discrimination laws. It has nothing to do with your right to state your feelings on how men treat apartments.
You are one clueless fuck if you can't distinguish the difference between being prosecuted for saying "I'll give you $5 for a blowjob" to a prostitute and being prosecuted for soliciting a prostite. I'll give you a hint; you're not being prosecuted for the content of your speach, but rather your actions and intent.
You are indeed free to say and print whatever you want. That does not mean that you can say whatever you want and escape the consequences of those actions.
CLI in this context is a TLA for Common Language Infrastructure. CLI is a three letter acronym, which are by no means unique. The only people freaking out about this are morons such as yourself. Oh nos! A name for something has three words which start with C, L, and I! What ever shall we do!
It's a TLA. It isn't like Command Line Interface is the only set of words that start with C, L, and I that make sense. If it were we wouldn't need words in the first place.
CLI = Common Language Infrastructure
Every time I'm walking through a house with a home inspector, they've noted that the insulation voids the waranty on the water heater. Personally, I don't give a crap, but ... :)
Certainly -- an oven is a poor subsitute for a heater, and I didn't mean to give the impression that it was. But it is certainly cheaper to make something in the oven during the winter than it is in the summer and the "fireplace" effect is comforting. :)
Follow that one by shoping for clothes at the local version of Goodwill, turn down the heat, plug the drafts, and unplug appliances not in use. Consider adding an insulating blanket to your hot water heater, if it's not an instant-on type.
Doing this actually voids the warranty on most water heaters. You'd be better off inserting a foam insulation pad between the water heater and the floor -- most of the heat lost gets away through the ground.
You can make a HUGE difference in your heating bill by being more "frugal" with the heat. I cut my bill from $150 to $85 by letting the house get colder during the day, turning on the heat later and turning it off sooner. As my place is heated by electricity, I can have each room heated at different times. Turning off the heat in rooms I don't use also helped, as does keeping all of the doors between "zones" closed.
...
...
:)).
The hallway downstairs ends up being a bit chilly but I don't exactly spend a lot of time there
An interesting side effect of this is that it helps you "keep" your schedule; if you've got to get up to turn the thermostat back up, you might as well just go to bed
If you have flextime, you can also change your work schedule so that you spend more of your after dark hours at work (free heat!
It all seems a bit excessive, but it's worth saving $250/year.
In the winter, the energy you use for cooking will heat the place, and in the summer is easy to vent it out the window.
In a small apartment/condo, this really does make a difference. My diet actually involves more "oven-baked" goods in the winter for that very reason.
The other downside is that they aren't dimmable. (well, most arn't)
Not a huge deal for most people, but it is an issue if your light switches double as dimmers. Halogens are a good alternative if you're in that situation.
People used to say the same thing about cable ...
A few areas I haven't seen covered:
* If you are going to be consuming code you don't own, for the love of god run it in an external process. Create a defined plug-in like interface that your customers will use, and have a shim process designed to load the plug-in and perform communication back and forth with your real app. Your real app should assume that every attempt to communicate with the external process will fail and respond accordingly.
* Don't assume that hardware is fault free; assume that any and every operation than can fail will. I have personally tracked down application crashes that were the result of faulty hardware; in one instance, a machine had failure rates 20% higher than the rest of the machines -- turned out the mobo was faulty. In another instance, a harddrive was failing. I had one case where an object was allocated, verified not null, and passed in as a reference to a function -- which failed because the object was null...
I've dealt with software that automatically restarts a dead process, and in my experience, it doesn't work so good. If you want ultra-stable software, you want to know what caused the crash and why.
It works better if your application does logging and creates dumps of the faulting process before restarting. Post mortem debugging can be incredibly useful.
a) You aren't tied to the IDE; you can compile managed code using make if you prefer (which is, in fact, how it is done at my employer)
b) Dumbing down has nothing to do with it. Making sure the language doesn't get in my way or throw up obstacles while tring to get something done has everything to do with it. (What, I don't have to spend a day wasting time writing redundant code and updating installer logic to create a new com server? Gee, what a downer.)
c) Arguing that autocompletion is bad is akin to arguing that an English major shouldn't use the spellchecker in a wordprocessor. Autocomplete saves you time looking things up; you still have to remember how the "word" starts and what it means.
Trading at 45 times future earnings is a sign that the stock is overvalued and driven by speculation. I won't invest in a stock like that; too much risk, feels more like gambling than investing. If Microsoft were currently trading at 50-100 times earnings, I wouldn't be investing in it either. And given that Microsoft is now trading around 20-25 times earnings, I suspect that would have been a good decision a few years ago as well.
The last attempt I'm aware of to brute force a key in a console was for the Jaguar, and if I recall correctly they had roughly a dozen dev units trying key after key for a few years before finally cracking it (I'm not even sure they succeeded; I think the company that owned the rights at that time actually released it into the public domain). The encryption on that box was weak; we don't know what size the key they chose to use is, nor what method they use for signing the binary. A brute force approach is, in my opinion, impracticle; I'm not even sure it would be possible to do without burning test discs...
... Hoping for the answer to fall into your lap from out of the sky doesn't seem to be a practicle solution to me either.
I don't know how the binaries on disc get signed. However, securing a private encryption key doesn't seem to be something they've ever had any difficulty with, given that they've managed do so with the keys they sign their binaries with since they started signing binaries; this also isn't something other companies seem to have much difficulty with
Most people believe that the key is stored in a boot rom INSIDE the cpu. Kind of hard to replace the public key without replacing the processor, and good luck getting ahold of a customized replacement ...
Fuzzing is a technique that can be used to find buffer overflows, not exploit them.
Read up on LUA in Vista. I think you'll be pleasantly suprirsed.
So? 3D hardware wasn't supported AT ALL until DX5. DirectX was 2d only until '97. Back in the day Microsoft was planning on using OpenGL for 3d games, but the standards body moved at such a glacial pace (and had such a snobbish "opengl is for high end graphics only" attitude) that they said "screw it" and did their own thing.
For the same reason cross platform developers don't all use Java. You end up having to tweak things for every platform anyway. Just because something compiles doesn't mean it works right.
Early on in a console's life market share and adoption is more important than breaking even on the hardware. Market share attacts developers, which increases the number of games available for the system, which increases consumer interest, which in turn increases marketshare.
Losing money early on isn't a terribly big deal, as you expect to make it back over the life of the console when customers purchase new games or controllers/peripherals. Remember, early adopters will be "in" for much longer than people who purchase the hardware late in its life cycle. Later in the console's life cycle hardware costs become more important, as there is less time to make up the loss on the hardware.
So WHY didn't the original xbox never really wander into profitability? Hardware costs. Microsoft was unable to cost reduce their hardware; they didn't own any of the IP -- they were just buying off the shelf parts from nvidia and intel. Essentially, they were stuck paying the same prices for parts when they launched the unit as they are today; it was a GIGANTIC error on Microsoft part, and I'm sure Nvidia and Intel were trying to hold back some giant grins as the contracts were being signed.
With the 360, Microsoft owns all of the IP. They can have whoever they want manufacture the parts, they can shrink the chips, etc. The theory being that over time they'll be able to reduce costs and break even on hardware.
Microsoft sold 1.5 million consoles by the end of 2005. 900,000 in North America, 500,000 in Europe, and 100,000 in Japan. These figures were announced with their FY06Q2 results.