If Bill the Stone started writing as a journalist and the other Bill were a bit more famous, yes, Bill the journalist would have the right to force Bill the musician to make it clear.
Basically, you can always use your own name, but if someone else with the same name has a great reputation, the burden can be placed on you to avoid confusion.
Settle down, he's actually right. If Bill the author released an album, he'd have to make it clear that he wasn't Bill the former Rolling Stone. Now whether or not he has to make it clear that his journalistic pieces aren't made by Bill the former Rolling Stone is another issue altogether and one that's up for debate.
People will be up in arms the same way they were when the local McDonalds went and changed the sizes and prices so what used to be a small is now called a medium and costs more.
Oh, wait, that didn't happen. Maybe people accept what they're given because they don't pay attention to 90% of what goes flying by. Yes, that applies to you and me as well. We just miss/ignore a different set of items. (Did a t-shirt always cost $25?)
Frankly, you are the exception to the rule in every sense. Most employees in the tech industry are having to follow rules more closely. At the same time most of them have under 5 years with their current company and under 10 in the industry. Around here [large software company] some folks have to snap in line with the recent changes while other developers whose work is more profitable get away with murder. Well, maybe not murder, but poor dress and borderline sexual harassment.
In my neck of the woods (SE Michigan) the cost of your average dial-up and seperate phone line is actually higher than broadband. I got a cable modem to save money, the speed was a bonus.
And what if it shows the same IP hitting different websites at 10:48:01, 10:48:13, and 10:48:37? Is that a single user jumping around or multiple users behind a proxy? Hard to say.
Bottom line, tracking by IP address doesn't work. Too many users work through proxies or beind NAT routers and then DHCP and dial-up further complicate things.
Getting "creative" with data is a way to fool a customer. Real results require solid methods.
Tracking by IP only works if the users have static IP addresses and aren't using proxy servers. So that basically takes care of dial-up, most broadband, and corporate web surfers. Cookies, however, are per user (when the browser allows them).
I work in software development and in speaking to our customers (yes, I actually talk to my users directly so I know what they want/need) many of them are working on much better and more useful applications than they were two years ago.
Less online phone directories more online report generation from divergent systems. Moving data from paper booklets to online is cute, but what does it save? Create real time reports using data from different systems (internal and external) and suddenly you have something that makes life much better.
Right on the Moxi product page: "Conditional Access Decryption". Well of course they're going to put in restrictions on how and when you view things. This is a product for the cable industry to help them make more money. If it was intended to make TV better for the consumer, you'd see them on sale at Circuit City and Best Buy.
If you check out the Moxi product page you'll that feature is still listed. I'm sure the journalist/press release writer just didn't feel that was one of the "cooler" features.
The reason is to get you to go back and try all the other options so you learn the respective consequences. About the only thing they missed was going to the band's website to see if they had any mp3's available for download.
The citing of Ars Technica was to show how powerful a "budget" box can be. Of course they update the listings, but only because they build those configurations to a price, not a fixed level of functionality.
As for the "gee whiz" apps you refer to, my ancedotal evidence doesn't agree with yours (and neither of us are offering real evidence, now are we?). Taking into account my mother-in-law, father-in-law, wife, mother, brother, sister-in-law, grandmother, and other "average" users only my mother-in-law tends to install little applications that run in the back ground sucking up CPU time. Of course, she still runs a P-II 266 so a 1GHz would off set anything she's installed in the last year.
"[I]mprove the ability of the system to respond
to the users needs". Which of course begs the question: "What do users need?" I'll stand by my position that user needs are already being met and in many cases exceeded. In the late 80's people already knew they wanted a GUI, but early Windows was just too painfully slow to run. We aren't back in 1994 when some of us would have killed for a machine that could encode MP3's in a reasonable amount of time. Today, only a small segment of the population wants faster machines. The only thing I hear complaints about are Internet access speeds.
Maybe someone will develop an uber-transfer encoding that'll require 3GHz processors and speed up net access by 5%. People will buy/need that.
Something or something useful? For a growing segment of computer users there is nothing beyond 1GHz. Certainly office applications, "basic" gaming, and even graphics work can be done with hardware that is a far cry from the cutting edge.
Check out Ars Technica Budget Box. Aside from video editing (which most users don't do) and lastest generation first-person shooters, what could more CPU get you? There simply isn't a killer app for these bigger processors. IMHO, their best hope is that they can become big and fast enough that on board video will be as feasible as on board audio and ethernet
If a support developer doesn't know what a little used third party function does and I don't comment it, who loses? Short answer: everyone. Support development team loses, I lose, QA and/or tech support loses as they wait for a fix.
Now, what if I (like so many other programmers and yourself apparently) have my head firmly up my ass so I think all my code is obvious in function and I only need to explain my intent? Well, after being humbled a few times, I'll figure out that it is more useful for everyone if I just use lots of comments, even things that may seem obvious once written, the role of support is vastly improved and my need to help with support is greatly reduced.
Of course, maybe you like doing support programming, it takes all kinds I guess.
At my local drug store, they don't bother to ask for a signature for purchases under $10. I was told it was for convience. Whatever. Of course, they never checked the signature with my driver's license or even the back of the credit card so I could sign pretty much any way I wanted to.
Point of that rambling, is there isn't anything more secure about using a credit card at the gas pump (or this particular store) than a speed pass. In my case, showing up at the gas station means wearing full motorcycle gear and the speed pass I attaced to my jacket sleeve saves me about a minute of fussing with zippers and gloves and other saftey gear.
Considerations for long duration
on
HTTP's Days Numbered
·
· Score: 3, Insightful
Capabilities like chunked-encoding allow HTTP to not know how long the response will be before transmission begins. Explicit instructions for weather the connection is to remain open or closed after the request is complete. Support for acknowledgment before large data chunks are sent to server. Mandatory backward compatibility certainly hasn't taken anything away from the party. All of this is perfect for Client-Server, yes even "monolithic" actions.
Now if you want to use HTTP to do P2P, then most likely you're only doing it so corporate users can flow out from behind their various firewalls without getting special permission from the IS department. Perhaps, HTTP isn't right in those situatins, but that doesn't mean something is wrong with HTTP. Put the blame where its due.
First off let me say that I wear electric clothing on a regular basis. Of course, mine is the somewhat low-tech variety. More cheap electric blanket, less lithium-ion.
The main reason I wear them, is for when you need to be stationary in the elements for an extended period of time. Sure, I'd be warm if I were moving about, but if you have to sit still for 60 minutes it's going to take a *LOT* of insulation to equal the warmth of a good electric vest.
There's another subtle difference between heavy insulation and active heating. Alterness. You'd be amazed at how fast your reaction time sinks when you get a little cold. That's not so bad when your hiking along a trail, but if you're driving a motorcycle (like me) or holding a gun (soliders) then a half second can be critical.
is better than just higher resolution. If you just keep uping the resolution of the cameras, you also need to up the memory or use some lossy compression. With this tech (if it proves to be cost effective), you can keep your images to a reasonable size and make them clearer and better suited to using in print.
No two programmers are working on the exact same bug/feature. You can't expect to just copy someone else's code or get them to do most of the work for you. At best, you can ask for help, but that's not what the article is talking about. It's talking about straight copying of code (with minor changes to fool a cursory examination).
And it'd be 10 times more of a pain to lug around a laptop. Honestly, do you carry a laptop with you run out to pick up milk? How about when you go to the movies? Probably not. Of course, its very easy to run into someone you know at either of these spots and need something off of your machine. (Contact information for a third person, dates, public keys, etc.)
The big advantage to these really high powered PDA's is that they can do more than act as a digital date book. Ever try manipulating a large data set on a Palm so you can show your boss what the results of your tests were? (if your boss has time to sit down and read e-mail, you work in a different environment than I do) Sometimes you need ultra portable computing that you can use while you move, not computing that you can move to different work locations.
If Bill the Stone started writing as a journalist and the other Bill were a bit more famous, yes, Bill the journalist would have the right to force Bill the musician to make it clear.
Basically, you can always use your own name, but if someone else with the same name has a great reputation, the burden can be placed on you to avoid confusion.
Settle down, he's actually right. If Bill the author released an album, he'd have to make it clear that he wasn't Bill the former Rolling Stone. Now whether or not he has to make it clear that his journalistic pieces aren't made by Bill the former Rolling Stone is another issue altogether and one that's up for debate.
People will be up in arms the same way they were when the local McDonalds went and changed the sizes and prices so what used to be a small is now called a medium and costs more.
Oh, wait, that didn't happen. Maybe people accept what they're given because they don't pay attention to 90% of what goes flying by. Yes, that applies to you and me as well. We just miss/ignore a different set of items. (Did a t-shirt always cost $25?)
Frankly, you are the exception to the rule in every sense. Most employees in the tech industry are having to follow rules more closely. At the same time most of them have under 5 years with their current company and under 10 in the industry. Around here [large software company] some folks have to snap in line with the recent changes while other developers whose work is more profitable get away with murder. Well, maybe not murder, but poor dress and borderline sexual harassment.
In my neck of the woods (SE Michigan) the cost of your average dial-up and seperate phone line is actually higher than broadband. I got a cable modem to save money, the speed was a bonus.
And what if it shows the same IP hitting different websites at 10:48:01, 10:48:13, and 10:48:37? Is that a single user jumping around or multiple users behind a proxy? Hard to say.
Bottom line, tracking by IP address doesn't work. Too many users work through proxies or beind NAT routers and then DHCP and dial-up further complicate things.
Getting "creative" with data is a way to fool a customer. Real results require solid methods.
So um, quit being stubborn!
Tracking by IP only works if the users have static IP addresses and aren't using proxy servers. So that basically takes care of dial-up, most broadband, and corporate web surfers. Cookies, however, are per user (when the browser allows them).
;)
So um? get educated!
500 dollars * 3,000,000 per day * 365 day per year * 4 years = 2.2 trillion
the poster made an error, but the link has $2.2 trillion as well. Yes, it is an insane number, but spaming with a fax is insane as well.
I work in software development and in speaking to our customers (yes, I actually talk to my users directly so I know what they want/need) many of them are working on much better and more useful applications than they were two years ago.
Less online phone directories more online report generation from divergent systems. Moving data from paper booklets to online is cute, but what does it save? Create real time reports using data from different systems (internal and external) and suddenly you have something that makes life much better.
Right on the Moxi product page: "Conditional Access Decryption". Well of course they're going to put in restrictions on how and when you view things. This is a product for the cable industry to help them make more money. If it was intended to make TV better for the consumer, you'd see them on sale at Circuit City and Best Buy.
If you check out the Moxi product page you'll that feature is still listed. I'm sure the journalist/press release writer just didn't feel that was one of the "cooler" features.
The reason is to get you to go back and try all the other options so you learn the respective consequences. About the only thing they missed was going to the band's website to see if they had any mp3's available for download.
As for the "gee whiz" apps you refer to, my ancedotal evidence doesn't agree with yours (and neither of us are offering real evidence, now are we?). Taking into account my mother-in-law, father-in-law, wife, mother, brother, sister-in-law, grandmother, and other "average" users only my mother-in-law tends to install little applications that run in the back ground sucking up CPU time. Of course, she still runs a P-II 266 so a 1GHz would off set anything she's installed in the last year.
"[I]mprove the ability of the system to respond to the users needs". Which of course begs the question: "What do users need?" I'll stand by my position that user needs are already being met and in many cases exceeded. In the late 80's people already knew they wanted a GUI, but early Windows was just too painfully slow to run. We aren't back in 1994 when some of us would have killed for a machine that could encode MP3's in a reasonable amount of time. Today, only a small segment of the population wants faster machines. The only thing I hear complaints about are Internet access speeds.
Maybe someone will develop an uber-transfer encoding that'll require 3GHz processors and speed up net access by 5%. People will buy/need that.
Check out Ars Technica Budget Box. Aside from video editing (which most users don't do) and lastest generation first-person shooters, what could more CPU get you? There simply isn't a killer app for these bigger processors. IMHO, their best hope is that they can become big and fast enough that on board video will be as feasible as on board audio and ethernet
What's worse? Not getting cybersex or finding out you just did it with some guy pretending to be a Ferengi female. *shudder*
If a support developer doesn't know what a little used third party function does and I don't comment it, who loses? Short answer: everyone. Support development team loses, I lose, QA and/or tech support loses as they wait for a fix.
Now, what if I (like so many other programmers and yourself apparently) have my head firmly up my ass so I think all my code is obvious in function and I only need to explain my intent? Well, after being humbled a few times, I'll figure out that it is more useful for everyone if I just use lots of comments, even things that may seem obvious once written, the role of support is vastly improved and my need to help with support is greatly reduced.
Of course, maybe you like doing support programming, it takes all kinds I guess.
If you had read the original article, you would have noticed that the device has PCS connectivity so it can call out and let its information be known.
At my local drug store, they don't bother to ask for a signature for purchases under $10. I was told it was for convience. Whatever. Of course, they never checked the signature with my driver's license or even the back of the credit card so I could sign pretty much any way I wanted to.
Point of that rambling, is there isn't anything more secure about using a credit card at the gas pump (or this particular store) than a speed pass. In my case, showing up at the gas station means wearing full motorcycle gear and the speed pass I attaced to my jacket sleeve saves me about a minute of fussing with zippers and gloves and other saftey gear.
So who's the guy between us?
Capabilities like chunked-encoding allow HTTP to not know how long the response will be before transmission begins. Explicit instructions for weather the connection is to remain open or closed after the request is complete. Support for acknowledgment before large data chunks are sent to server. Mandatory backward compatibility certainly hasn't taken anything away from the party. All of this is perfect for Client-Server, yes even "monolithic" actions.
Now if you want to use HTTP to do P2P, then most likely you're only doing it so corporate users can flow out from behind their various firewalls without getting special permission from the IS department. Perhaps, HTTP isn't right in those situatins, but that doesn't mean something is wrong with HTTP. Put the blame where its due.
First off let me say that I wear electric clothing on a regular basis. Of course, mine is the somewhat low-tech variety. More cheap electric blanket, less lithium-ion.
The main reason I wear them, is for when you need to be stationary in the elements for an extended period of time. Sure, I'd be warm if I were moving about, but if you have to sit still for 60 minutes it's going to take a *LOT* of insulation to equal the warmth of a good electric vest.
There's another subtle difference between heavy insulation and active heating. Alterness. You'd be amazed at how fast your reaction time sinks when you get a little cold. That's not so bad when your hiking along a trail, but if you're driving a motorcycle (like me) or holding a gun (soliders) then a half second can be critical.
is better than just higher resolution. If you just keep uping the resolution of the cameras, you also need to up the memory or use some lossy compression. With this tech (if it proves to be cost effective), you can keep your images to a reasonable size and make them clearer and better suited to using in print.
No two programmers are working on the exact same bug/feature. You can't expect to just copy someone else's code or get them to do most of the work for you. At best, you can ask for help, but that's not what the article is talking about. It's talking about straight copying of code (with minor changes to fool a cursory examination).
And it'd be 10 times more of a pain to lug around a laptop. Honestly, do you carry a laptop with you run out to pick up milk? How about when you go to the movies? Probably not. Of course, its very easy to run into someone you know at either of these spots and need something off of your machine. (Contact information for a third person, dates, public keys, etc.)
The big advantage to these really high powered PDA's is that they can do more than act as a digital date book. Ever try manipulating a large data set on a Palm so you can show your boss what the results of your tests were? (if your boss has time to sit down and read e-mail, you work in a different environment than I do) Sometimes you need ultra portable computing that you can use while you move, not computing that you can move to different work locations.