60 Hz is just too low a frequency. I suggest we switch to the 400 Hz which was widely used to make aircraft transformers lighter and would also reduce mechanical vibration. We could call it HDAC and require it, along with backward compatibility, in all new electronics.
Re:"Buisness" as usual
on
QA != Testing
·
· Score: 1
Because functional design requirements have stated input and output. Applying every input exercises every accessible code path. Note that input includes parameters to a function and any external state which is used by the function. Output includes explicit return values and state changes.
Re:"Buisness" as usual
on
QA != Testing
·
· Score: 1
straw man: a weak or sham argument set up to be easily refuted
The checkers I wrote were for 64-bit graphics chips. There were millions of cases involving overlapping rectangles, regions with different strides and address boundaries. Thats why its easiest to use for loops that generate every possible case and just burn a lot of CPU cycles.
We ran production code on the simulations before masking out so we didn't have to feed test cases to hardware. Waiting to test the logic until you've built the hardware sounds pretty inefficient to me.
By the way, 7 chips, zero bugs.
Re:"Buisness" as usual
on
QA != Testing
·
· Score: 1
I didn't say the test suite was written from looking at the source code. I used to write exerciser/checker pairs for pretty complex functions. Once you've written a few, a day is pretty reasonable, unless you're one of the QA people "with no deadlines" described above. Exercisers are typically a few loops with a call in the middle. Checkers are usuaully a few dozen if-then-else statements. What's so hard?
Re:"Buisness" as usual
on
QA != Testing
·
· Score: 1
Imagine a complex program containing many code paths that deal with rare error conditions (a typical device driver). Now imagine you have two methods of verifying the code.
Release it to the field and let the users find the bugs.
QA spends a day to code a test suite which exercises every code path and checks for the correct response.
I think you're right. In the EULA for Office, it's careful to never say that you are required to run it on Windows, because that would be an abuse of their desktop monopoly.
The question is, when you buy Office, are you also buying updates? If so, its anticompetitive to refuse to update on non-Windows platforms.
I think MS's position is that there are a lot of Wine users with illegal copies of Office, but they are crossing the line refusing to update anyone that's not a Windows user.
That's funny because XOR is logically the same as isNot. The output is true when the two inputs are not equal. The Cadtrak patent on XOR is 4,197,590. A company that I worked for got the threatening letter for using this patented technique for graphics displays.
I always thought that a good example of prior art is analog TV sync signals. The H and V sync are XORed because its easy to separate them using another XOR.
For the standard small office cube - unplug the ghastly flourescent fixture and put in a floor lamp with incandescent bulb and a cheap oriental rug. Instant class.
If you can't do that and you like your neighbor, pull an Office Space. Tear out the intervening wall and share a double cube. This makes your area look roomier even though you still have the same space.
If anybody asks, tell them Derek told you it was OK. Unless your company actually has someone named Derek, in which case use Sheldon.
Not responsible for the reactions of Maintenance or Supervisory staff when they find out about these changes.
Doesn't this just mimic the same arguments that have been used about browser vulnerabilities? Apache is on more servers, so more vulnerabilities have been found. As for the time to implement and release fixes, the important issue is how quickly people update their own servers. That might make Linux come out worse, since its a PITA to update Apache and people who believe Linux is more secure may not update often enough.
A more interesting study might be about actual website defacements? How many on each type of server and how many used already known vulnerabilities.
He said he keeps all the state in globals so he's not messing around with stack or heap variables. If you know the compiler allocates the globals in order you just need a sentinel at the beginning and end and save everything in between. This is how hibernation mode works on a PC. Its a technique that's been around since FORTRAN common blocks.
The question wasn't how to do that. That works. Its how to do something that efficient (a single read or write call) using good OOP techniques.
Its not a narrow exception. Your statement about how it should work is pretty much correct. Making a skin is, essentially, making a computer program. Not to a CS major, maybe, but to a lawyer its just binary code executed on a computer. Making a skin work with a game is interoperability.
I've been following most DMCA decisions because I do reverse engineering for a living. Look at the Lexmark decision:
"Congress did not intend to allow the DMCA to be used offensively in this manner, but rather only sought to reach those who circumvented protective measures 'for the purpose' of pirating works protected by the copyright statute."
Basically, if you aren't reverse engineering to crack the copy protection, then you are safe, according to the Lexmark decision.
Except reverse engineering is allowed under DMCA. Tecmo has no case here, since the defendents were not copying the game or breaking copy protection.
"Reverse engineering (section 1201(f)). This exception permits circumvention, and the development of technological means for such circumvention, by a person who has lawfully obtained a right to use a copy of a computer program for the sole purpose of identifying and analyzing elements of the program necessary to achieve interoperability with other programs, to the extent that such acts are permitted under copyright law."
Its been a while, but ISTRC 32-bits/pixel R-G-B-Alpha. Total frame buffer depended on the number of cards installed, around 32MBytes or maybe Mpixels in ours. Rendering a single image took a few minutes.
And, yes, the granite colors and cube shape were cool compared to the beige plastic boxes.
Typical CRT has at least 1Kg of lead. But the LCD backlight uses mercury, which I don't think anyone is recycling now. One advantage is that LCDs have a longer life than CRTs. Unfortunately, manufacturers striving for least cost do not make either of them repairable, so one failure and they're gone.
Its not too surprising that they don't have a native Linux client for Lotus Notes, that would be a huge undertaking. But its really funny that they haven't fixed their own internal help desk software. Some managers should be getting replaced for that.
I notice that any email documents I get from IBM are RTF now instead of DOC, so I am guessing that some parts of the company have taken the directive to heart.
First time I've ever heard a company CEO ask for a "Windowless Office".
Global variables have to be initialized in a multiuser operating system. Otherwise you could allocate big arrays and scan through them for other people's data. The stack is (supposedly) less interesting.
Slashdot Mirror
This was not always true. Anyone remember the pineapple?
It was an Apple clone that copied the ROMs. Apple sued and won. That case established the precedent that binary ROM code was covered by copyright.
Its also an early example (1984) of misusing an apostrophe to pluralize an acronym: "ROM's"
60 Hz is just too low a frequency. I suggest we switch to the 400 Hz which was widely used to make aircraft transformers lighter and would also reduce mechanical vibration. We could call it HDAC and require it, along with backward compatibility, in all new electronics.
Because functional design requirements have stated input and output. Applying every input exercises every accessible code path. Note that input includes parameters to a function and any external state which is used by the function. Output includes explicit return values and state changes.
straw man: a weak or sham argument set up to be easily refuted
The checkers I wrote were for 64-bit graphics chips. There were millions of cases involving overlapping rectangles, regions with different strides and address boundaries. Thats why its easiest to use for loops that generate every possible case and just burn a lot of CPU cycles.
We ran production code on the simulations before masking out so we didn't have to feed test cases to hardware. Waiting to test the logic until you've built the hardware sounds pretty inefficient to me.
By the way, 7 chips, zero bugs.
I didn't say the test suite was written from looking at the source code. I used to write exerciser/checker pairs for pretty complex functions. Once you've written a few, a day is pretty reasonable, unless you're one of the QA people "with no deadlines" described above. Exercisers are typically a few loops with a call in the middle. Checkers are usuaully a few dozen if-then-else statements. What's so hard?
I suggest the group change their name from RIAA to MPEC - the Music Professionals & Entertainment Cartel.
I think you're right. In the EULA for Office, it's careful to never say that you are required to run it on Windows, because that would be an abuse of their desktop monopoly.
The question is, when you buy Office, are you also buying updates? If so, its anticompetitive to refuse to update on non-Windows platforms.
I think MS's position is that there are a lot of Wine users with illegal copies of Office, but they are crossing the line refusing to update anyone that's not a Windows user.
That's funny because XOR is logically the same as isNot. The output is true when the two inputs are not equal. The Cadtrak patent on XOR is 4,197,590. A company that I worked for got the threatening letter for using this patented technique for graphics displays.
I always thought that a good example of prior art is analog TV sync signals. The H and V sync are XORed because its easy to separate them using another XOR.
For the standard small office cube - unplug the ghastly flourescent fixture and put in a floor lamp with incandescent bulb and a cheap oriental rug. Instant class.
If you can't do that and you like your neighbor, pull an Office Space. Tear out the intervening wall and share a double cube. This makes your area look roomier even though you still have the same space.
If anybody asks, tell them Derek told you it was OK. Unless your company actually has someone named Derek, in which case use Sheldon.
Not responsible for the reactions of Maintenance or Supervisory staff when they find out about these changes.
A Mersenne number is all ones when written in binary. If its prime, it is a Mersenne prime.
Doesn't this just mimic the same arguments that have been used about browser vulnerabilities? Apache is on more servers, so more vulnerabilities have been found. As for the time to implement and release fixes, the important issue is how quickly people update their own servers. That might make Linux come out worse, since its a PITA to update Apache and people who believe Linux is more secure may not update often enough.
A more interesting study might be about actual website defacements? How many on each type of server and how many used already known vulnerabilities.
He said he keeps all the state in globals so he's not messing around with stack or heap variables. If you know the compiler allocates the globals in order you just need a sentinel at the beginning and end and save everything in between. This is how hibernation mode works on a PC. Its a technique that's been around since FORTRAN common blocks.
The question wasn't how to do that. That works. Its how to do something that efficient (a single read or write call) using good OOP techniques.
There probably isn't one.
Its not a narrow exception. Your statement about how it should work is pretty much correct. Making a skin is, essentially, making a computer program. Not to a CS major, maybe, but to a lawyer its just binary code executed on a computer. Making a skin work with a game is interoperability.
I've been following most DMCA decisions because I do reverse engineering for a living. Look at the Lexmark decision:
"Congress did not intend to allow the DMCA to be used offensively in this manner, but rather only sought to reach those who circumvented protective measures 'for the purpose' of pirating works protected by the copyright statute."
Basically, if you aren't reverse engineering to crack the copy protection, then you are safe, according to the Lexmark decision.
Its been a while, but ISTRC 32-bits/pixel R-G-B-Alpha. Total frame buffer depended on the number of cards installed, around 32MBytes or maybe Mpixels in ours. Rendering a single image took a few minutes.
And, yes, the granite colors and cube shape were cool compared to the beige plastic boxes.
Typical CRT has at least 1Kg of lead. But the LCD backlight uses mercury, which I don't think anyone is recycling now. One advantage is that LCDs have a longer life than CRTs. Unfortunately, manufacturers striving for least cost do not make either of them repairable, so one failure and they're gone.
What makes you think that CheckFree, Intuit and Microsoft would make it easy for a bunch of OSS developers to work with "their" standard.
4/1 - 4/3 + 4/5 - 4/7 ...
Its not too surprising that they don't have a native Linux client for Lotus Notes, that would be a huge undertaking. But its really funny that they haven't fixed their own internal help desk software. Some managers should be getting replaced for that.
I notice that any email documents I get from IBM are RTF now instead of DOC, so I am guessing that some parts of the company have taken the directive to heart.
First time I've ever heard a company CEO ask for a "Windowless Office".
Combined with text-to-speech and GPS you'll be able to call up your laptop after its been stolen and ask it where it is.
They folded.
Hah! I kill me.
Global variables have to be initialized in a multiuser operating system. Otherwise you could allocate big arrays and scan through them for other people's data. The stack is (supposedly) less interesting.
"one place that set me down with a bug report and a development box with their code on it and wanted to see how I'd approach it..."
That wasn't a real interview. They just couldn't find that one nasty code bug so they brought people in until someone found it.