I assume that a rebated product is overpriced to compensate for the rebate. I don't like processing rebates, so on numerous occassions, I have purchased a competitors product instead to avoid getting overcharged on a product I would have bought anyway at the non rebate price. The rebate made me change my mind.
IANAL either but you could interpret "origin" as meaning what ISP account the communication is orginating from, in which case NAT is not a problem since it does nothing to disguise that. So is there really a problem here or is this just an exercise to burn off all that excess sugar and caffeine?
Given the mobo manufacturers' tendency to leave legacy connectors on long after the need for them has all but disappeared, i.e. parallel & serial connectors, I suppose we'll still see PATA connectors on the mobo's for years.
So instead of have to run a separate utility to screw up your filesystem by replacing bad blocks with good ones so there will be no indication that data was lost or corrupted, scsi will corrupt your files for you automatically.
SATA is just a start. There are other things that contribute to the problem. There's the wiring harness on the power supply. That's one mess of spagetti. Also, they still need to get ATAPI supported in SATA so you can get DVD/CDROM off of parallel cables. Case design is also a factor. Apparently, wire and cable routing is not one of the issues addressed in case design. Position and layout of physical components always seems to be the worst possible from a cable layout point of view. You always seem to be taking the long way around, forcing sharp right angle turns in fat cable/wire bundles and competing for too little space to place separate cables along side each other.
I haven't messed with XML yet but I did look at some books on XML. And that is where there is an indication of the problem. These books are way too damn thick. Thick books mean way too complicated interfaces.
What's going on? I think the problem started because pure XML is semantic free. It's just syntax. Semantics are added on with other layers of software. And therein lies the problem. Anybody could add these layers. And it was sort of a race. So anybody who spent a lot of time trying to design a simple intuitive api lost out to those who rush out half baked, over complicated and inconsistent apis.
When I design an api, I put in a huge amount of though to it. How do you fit it into and exploit the current abstraction model? Are the features absolutely necessary? It it intuitive, i.e. are the semantics straightforward and understandable?
I am one of the few people who've actually simplified api's on 2nd releases. If I'd been in charge of Java, Swing would have never happened. I'd have taken the AWT and simplified and fixed that up.
Fight bloatware! Put minimalists in charge of api design.
Yeah. A bunch of them. Got work in the last recession no problem. In fact my first job out of college was during a recession with a company with a hiring freeze in effect. This is different from the other recessions. But I'm only speaking from experience as someone who got work during other recessions so what the hell do I know.
That would be the MMU or virtual memory stuff. The address translation tables would be able to address more than 32 bits of memory, but any program or the kernel would still only be able to see or address 32 bits of memory. Like sticking two pc's next to each other. Between them, they would be able to address or access 33 bits of memory, but any one program would only see at most 32 bits.
We've already known why software development is screwed up, and known that for 25 years. Any new book that can't articulate what the known problems are and exactly how the new technique addresses some of those problems is a complete waste of time. And any reviewer who can't convey in his review whether the book is addressing some of these issues is completely wasting our time.
Are they kidding? I heard that the powergrid in India was so unstable it will kill US made surge protectors/power conditioners. You have to use Indian ones which are designed to handle that kind of abuse. And you want to hook that up to what?
on one of the talk shows about the econonmy (being unenmployed means way too much time to listen to talk shows). Apparently the sucking sound has a sucking sound of its own. The fear of outsourcing places like India and Russia is places even cheaper than they are, like China. They mentioned Hungary (Eastern Europe being relatively cheap) losing production of the Xbox to China(even cheaper). See here.
>>So what do you have to say about Network Television editing movies for >>Broadcast Television. Why hasn't there been such a huge outcry?
This was on NPR a while back. The network edits are approved by the original content owners. If ClearPlay negotiated with the content owners for approval of the edits there would be no problem.
If you think this is not fair, I tell you what. Start your own web site that frames slashdot.org with some slight content editting, say don't show first posts and "In Soviet Russia..." posts. With or without the editting, I bet you hear from VA Software lawyers.
The dead code that I had experience with was reached through conditional logic. The expert opinion what that the conditions necessary to reach that code section could not occur. But it's opinion, not something that is provable. Certainly not with the size of the system we were working with, millions of lines of code.
The proper way to deal with code that has a lot of problems is to rewrite it. You are making a trade off, that you are removing more bugs caused by the old croufty code than you are introducing by the new code including the ones you introduced by not completely understanding the old code.
On rewrites, I used to leave out everthing that I couldn't figure out, and end up putting back in about half. You learn a lot on rewrites, even if you thought you knew the old code really well to begin with.
Dead code is most likely found in really old code that has been modified many many times. Does really old code that has been modified many many times have lots of bugs? Quite likely.
Is this dead code going to get removed?
No.
Why not?
Because, one, it's only an opinion that it's dead code. There could be some obscure case that no one imagined that could use it. Two, if some programmer removed it and it turned out that it was needed or the programmer screwed up the removal, the programmer would be blamed and take a lot of grief for it. If it ain't broke, don't fix it.
Now, it could be that the dead code doesn't work properly for the obscure case. But how could you tell? Do you want to write a test case for code that no one can figure out how it gets invoked?
Not to be confused with Ian Banks which is the same guy. Does "space operas". 'Excession' is particularly good. Has things like small planetoid sized A.I. space ships that while transporting the entire population of a planet in stasis, creates tableaus of famous battles with said same passengers. With their permission of course. Apparently humans in stasis make good simulated corpses with the right makeup. There are human subplots of course but the plots involving the space ships are very interesting. And there are plots, literally. And ship on ship battles that beat the hell out of any samurai movie for "quick".
Richard Calder. 'Dead Girls', 'Dead Boys', 'Dead Things',... Lots of sex. Mostly all sex. Don't read them if you have suicidal tendencies though. Incredibly depressing. Starts out like a junkie completely at the end of his monkey chain and goes downhill from there. Most depressing scifi series of all time (after Gormenghast). Did I say depressing?
A lot this competitiveness is based on differences in cost of living or cost of doing business. Well, after deflation hits the US, $8000 a year is going to look like a good salary to a US programmer.
It's the end applications that counts. *It* won't run unless it's running on a trusted operating system which in turn won't run unless it's booted by a trusted boot loader which in turn won't run unless it's on trusted hardware. As long as there are enough applications that don't require this trusted environment then there will continue to be a use for Linux. Don't give up the apps! Free the apps!
Slashdot Mirror
It seems to be out print. All of them actually. It's going for over $40 used. Presumeably it means that a special edition is in the works.
I assume that a rebated product is overpriced to compensate for the rebate. I don't like processing rebates, so on numerous occassions, I have purchased a competitors product instead to avoid getting overcharged on a product I would have bought anyway at the non rebate price. The rebate made me change my mind.
IANAL either but you could interpret "origin" as meaning what ISP account the communication is orginating from, in which case NAT is not a problem since it does nothing to disguise that. So is there really a problem here or is this just an exercise to burn off all that excess sugar and caffeine?
Given the mobo manufacturers' tendency to leave legacy connectors on long after the need for them has all but disappeared, i.e. parallel & serial connectors, I suppose we'll still see PATA connectors on the mobo's for years.
So instead of have to run a separate utility to screw up your filesystem by replacing bad blocks with good ones so there will be no indication that data was lost or corrupted, scsi will corrupt your files for you automatically.
SATA is just a start. There are other things that contribute to the problem. There's the wiring harness on the power supply. That's one mess of spagetti. Also, they still need to get ATAPI supported in SATA so you can get DVD/CDROM off of parallel cables. Case design is also a factor. Apparently, wire and cable routing is not one of the issues addressed in case design. Position and layout of physical components always seems to be the worst possible from a cable layout point of view. You always seem to be taking the long way around, forcing sharp right angle turns in fat cable/wire bundles and competing for too little space to place separate cables along side each other.
What's going on? I think the problem started because pure XML is semantic free. It's just syntax. Semantics are added on with other layers of software. And therein lies the problem. Anybody could add these layers. And it was sort of a race. So anybody who spent a lot of time trying to design a simple intuitive api lost out to those who rush out half baked, over complicated and inconsistent apis.
When I design an api, I put in a huge amount of though to it. How do you fit it into and exploit the current abstraction model? Are the features absolutely necessary? It it intuitive, i.e. are the semantics straightforward and understandable?
I am one of the few people who've actually simplified api's on 2nd releases. If I'd been in charge of Java, Swing would have never happened. I'd have taken the AWT and simplified and fixed that up.
Fight bloatware! Put minimalists in charge of api design.
Yeah. A bunch of them. Got work in the last recession no problem. In fact my first job out of college was during a recession with a company with a hiring freeze in effect. This is different from the other recessions. But I'm only speaking from experience as someone who got work during other recessions so what the hell do I know.
is "cheaply" available antibiotics. Cheap in the sense of easy to overuse. And when you overuse antibiotics, guess what?
That would be the MMU or virtual memory stuff. The address translation tables would be able to address more than 32 bits of memory, but any program or the kernel would still only be able to see or address 32 bits of memory. Like sticking two pc's next to each other. Between them, they would be able to address or access 33 bits of memory, but any one program would only see at most 32 bits.
here is one of my favorites.
Cabaret Mechanical Theatre. There does seem to be some mechanistic resemblence here.
We've already known why software development is screwed up, and known that for 25 years. Any new book that can't articulate what the known problems are and exactly how the new technique addresses some of those problems is a complete waste of time. And any reviewer who can't convey in his review whether the book is addressing some of these issues is completely wasting our time.
Are they kidding? I heard that the powergrid in India was so unstable it will kill US made surge protectors/power conditioners. You have to use Indian ones which are designed to handle that kind of abuse. And you want to hook that up to what?
See here for some more information.
here from Hungary's point of view. (sorry the other link was good but this one was better)
on one of the talk shows about the econonmy (being unenmployed means way too much time to listen to talk shows). Apparently the sucking sound has a sucking sound of its own. The fear of outsourcing places like India and Russia is places even cheaper than they are, like China. They mentioned Hungary (Eastern Europe being relatively cheap) losing production of the Xbox to China(even cheaper). See here.
>>Broadcast Television. Why hasn't there been such a huge outcry?
This was on NPR a while back. The network edits are approved by the original content owners. If ClearPlay negotiated with the content owners for approval of the edits there would be no problem.
If you think this is not fair, I tell you what. Start your own web site that frames slashdot.org with some slight content editting, say don't show first posts and "In Soviet Russia..." posts. With or without the editting, I bet you hear from VA Software lawyers.
The proper way to deal with code that has a lot of problems is to rewrite it. You are making a trade off, that you are removing more bugs caused by the old croufty code than you are introducing by the new code including the ones you introduced by not completely understanding the old code.
On rewrites, I used to leave out everthing that I couldn't figure out, and end up putting back in about half. You learn a lot on rewrites, even if you thought you knew the old code really well to begin with.
Is this dead code going to get removed?
No.
Why not?
Because, one, it's only an opinion that it's dead code. There could be some obscure case that no one imagined that could use it. Two, if some programmer removed it and it turned out that it was needed or the programmer screwed up the removal, the programmer would be blamed and take a lot of grief for it. If it ain't broke, don't fix it.
Now, it could be that the dead code doesn't work properly for the obscure case. But how could you tell? Do you want to write a test case for code that no one can figure out how it gets invoked?
Richard Calder. 'Dead Girls', 'Dead Boys', 'Dead Things',
according to this Inquirer article.
A lot this competitiveness is based on differences in cost of living or cost of doing business. Well, after deflation hits the US, $8000 a year is going to look like a good salary to a US programmer.
I can see peer to peer money swapping becoming popular. The Treasury Dept will be after us next after the RIAA and MPA are finished with us.
It's the end applications that counts. *It* won't run unless it's running on a trusted operating system which in turn won't run unless it's booted by a trusted boot loader which in turn won't run unless it's on trusted hardware. As long as there are enough applications that don't require this trusted environment then there will continue to be a use for Linux. Don't give up the apps! Free the apps!