I think the real application of denser and faster CPUs will be scientific study. In Canada we have a serious deficite of super computer access for research projects, so the academia is increasingly farming out stuff like protein sequencing to shared clusters and remote processing applications similar to GENOME@HOME. However should the 64-bit CPU sucker in enough average home PC users, the price will stay low, which will likely create a tremendous opportunity for advancing affordable scientific research in slightly less affluent nations like my own.
What would prevent someone from reading the data and retransmitting it exactly as it was received? You wouldn't be destroying anything, you'd just be buffering the data before splitting and repeating it. A little more complex than a traditional electrical vampire tap (not to mention the PITA of splicing fibre), but I'd think just as effective, particularly if the tap existed prior to the initial signal timing negotiation being sent. It would then appear to be seamless.
Anyway, coming from a layman, I'm curious to hear if this holds water or not.
End user responsibility..
on
802.11 RF Amp
·
· Score: 1
I wonder when ISPs are going to stop soft-pedaling the anti-NATing provisions in their terms of service.
The point in having these is largely to emphasize that the end user is responsible for the way the connection is used. If someone does a drive by hack using your insecure WAP, it's your fault directly, not an 'accident', not the ISPs responsibility.
What I'm waiting for is not a bigger pipe, but cheaper bandwidth. The last thing I need is technology that will help me spend the same amout of money twice as fast.
M$ makes the GUI I use most often, but in terms of my data (stuff I actually give a s**t about) I ONLY use *nix based servers (OpenBSD primarily). My email, my programming, everything meaningful to my life and career is done on *nix. My money IS where my mouth is. I'm not willing to spend hour$ upon frustrating hour$, trying to get *nix drivers to work for my sound card or my high end video capture card. I'd rather play with my 2yo son when I get home from work.
Maybe once I'm a better hand at C programming, then I'll actually contribute to developing the drivers I currently lack. Til then... M$ is the GUI my end users will be seeing my product on, and I need to use the same OS to debug my work. I also have access to OSX, but for my general purpose, it's not as practical.
The thing you have to think about is that even a misguided stray fleck of paint can potentially obliterate another satellite on impact. The growing amount of obital material also increases the potential for destructively colliding objects in orbit. Such a chain reaction which could effectively create a wall of space debris, preventing safe and economical space flights for the foreseeable future. It's just like the old analogy of dropping a penny off a 10 story building, except in this case you don't have air resistance to limit the velocities involved. In otherwords, moving another satellite into any new vector is necesarily a very delicate precision operation.
How long will it take developers to realize that.doc *is* the standard, regardless of whether we like it or not.
Actually, RTF has always been the standard. The fact that noone takes advantage of that built in cross platform compatibility in almost every word pro on the planet, is just a matter of common ignorance. Consider this an M$ user's education: File -> Save As... -> Save as type: RTF. Voila! Instant cross platform 'standardisation'.:)
-Guanno
PS. To my understanding, M$.doc's are actually Active-X applications. Therefore, they're a security risk. I don't touch them with a 50' barge pole. If it's not ascii.. I don't need to read it that badly.
When I was young and stupid... we had an old refridgerator with a short circuit. If you placed one hand on the metal hinge and the other on the kitchen sink the AC would arc through you. Wow that was fun. We would line up in chains with one guy in the middle and a guy on either side pointing at his temples. It's amazing how fast one's eyes can vibrate with an alternating current running through your brain. Who needs drugs?:)
And what's going to prevent some electronically saavy folks from posting instructions for DVR Mods to their web-sites? If you know what chip is what, it's not exactly rocket science... or is it? LOL Anyway, it's no different from pirate satellite TV. Piece of cake.
If it weren't for adventurous spirits who are willing innovate a home made solution, the computer industry would never have gotten as far as it has, or be going in such interesting and potentially rewarding directions.
The 'Real' way actually amounts to mundane unimaginative and stagnant. At worst it amounts to millions of servers on an IP near you being adminstrated by lazy incompetant boobs, who don't know any better than to call a 'Real' technician (read/. fan) when the innevitable problems occur. And the rest of us suffer greatly for it. I wouldn't pay someone any more than minimum wage to do things the 'Real' way.
Some of you code monkeys gotta start writing games for Linux. I'm talking hard core Playstation/XBox/GameCube kind of stuff. Get the kiddies nagging mommy and daddy for it, and you'll have Linux in every home in the wired world just to shut them up.:) The rest will become history. I do like the ideas "psicE" and "TFloore" were tossing around in the "I've got an interface for you" thread. The sunglasses idea, with the ROM embedded Linux sounds slamming. Occam's razor together with a cattle prod (the christmas list) is the sure way to Joe six pack's wallet.
If you want to do something revolutionary, then put the emphasis on the whole reason most Open Source geeks became Open Source geeks in the first place. Offer a GUI you can make completely your own down to the last niggling pixel. Call it myX or something.
What comes to mind is a mark up language specifically for the myX GUI. Reduce the GUI itself to little more than a basic script compiler with a handful of default scripts/skins to keep joe six pack happy and lazy.
LOL. If I were a real code monkey, I'd do more than just make the suggestion. Alas... I'm not.
Got news for you... It's already happened. It's called Mac OSX.
If Linux is ever going to get big on it's own it needs a BRAND. Like "LINUX BRAND LINUX" or something like that. Red hat is getting close to mainstream, even though it sucks. The average person, and even me (I'm a BSD guy) finds the convoluted quagmire of Linux flavours daunting, and pointless to keep track of.
The advantage for Linux geeks is the ultimate customisability. You have your system by the short and curlies, and if you're a real propeller head, you can even get it to brew your coffee for you in the morning. Yippee!
However for the average joe six pack, this is not the way to spend a hard day after work. Therefore it's not where joe six pack's money gets spent. If you want to appeal to joe six pack and find your way into the pocket book of his beer swilling boss, you have to think like them. You have to want to be lazy.
Slashdot Mirror
I think the real application of denser and faster CPUs will be scientific study. In Canada we have a serious deficite of super computer access for research projects, so the academia is increasingly farming out stuff like protein sequencing to shared clusters and remote processing applications similar to GENOME@HOME. However should the 64-bit CPU sucker in enough average home PC users, the price will stay low, which will likely create a tremendous opportunity for advancing affordable scientific research in slightly less affluent nations like my own.
What would prevent someone from reading the data and retransmitting it exactly as it was received? You wouldn't be destroying anything, you'd just be buffering the data before splitting and repeating it. A little more complex than a traditional electrical vampire tap (not to mention the PITA of splicing fibre), but I'd think just as effective, particularly if the tap existed prior to the initial signal timing negotiation being sent. It would then appear to be seamless.
Anyway, coming from a layman, I'm curious to hear if this holds water or not.
I wonder when ISPs are going to stop soft-pedaling the anti-NATing provisions in their terms of service.
The point in having these is largely to emphasize that the end user is responsible for the way the connection is used. If someone does a drive by hack using your insecure WAP, it's your fault directly, not an 'accident', not the ISPs responsibility.
-Guanno
What I'm waiting for is not a bigger pipe, but cheaper bandwidth. The last thing I need is technology that will help me spend the same amout of money twice as fast.
M$ makes the GUI I use most often, but in terms of my data (stuff I actually give a s**t about) I ONLY use *nix based servers (OpenBSD primarily). My email, my programming, everything meaningful to my life and career is done on *nix. My money IS where my mouth is. I'm not willing to spend hour$ upon frustrating hour$, trying to get *nix drivers to work for my sound card or my high end video capture card. I'd rather play with my 2yo son when I get home from work.
... M$ is the GUI my end users will be seeing my product on, and I need to use the same OS to debug my work. I also have access to OSX, but for my general purpose, it's not as practical.
Maybe once I'm a better hand at C programming, then I'll actually contribute to developing the drivers I currently lack. Til then
-Guanno
Can be found here. Sorry if this duplicates anyone else's post. I don't have time to read everything.
-Guanno
EMP-Bomb
Ahhh. If only we good husbands could enjoy Bill Gates' salary too. LOL
ultimate foolproof network security model
The thing you have to think about is that even a misguided stray fleck of paint can potentially obliterate another satellite on impact. The growing amount of obital material also increases the potential for destructively colliding objects in orbit. Such a chain reaction which could effectively create a wall of space debris, preventing safe and economical space flights for the foreseeable future. It's just like the old analogy of dropping a penny off a 10 story building, except in this case you don't have air resistance to limit the velocities involved. In otherwords, moving another satellite into any new vector is necesarily a very delicate precision operation.
-Guanno
No more going to jail for cannibalism. You can grow your own human tissue and eat it with a side of eggs for breakfast.
Is there a moderator value of "6 and twisted" yet...? LOL
You seem to have misread or overlooked the following: " Fully-featured word processor: ... Using an RTF format, HomeBase DESKTOP's word processor lets you send documents to others who use a variety of formats, and import and work with their docs (including Microsoft Word) as well. "
How long will it take developers to realize that .doc *is* the standard, regardless of whether we like it or not.
Actually, RTF has always been the standard. The fact that noone takes advantage of that built in cross platform compatibility in almost every word pro on the planet, is just a matter of common ignorance. Consider this an M$ user's education: File -> Save As... -> Save as type: RTF. Voila! Instant cross platform 'standardisation'. :)
-Guanno
PS. To my understanding, M$ .doc's are actually Active-X applications. Therefore, they're a security risk. I don't touch them with a 50' barge pole. If it's not ascii .. I don't need to read it that badly.
When I was young and stupid... we had an old refridgerator with a short circuit. If you placed one hand on the metal hinge and the other on the kitchen sink the AC would arc through you. Wow that was fun. We would line up in chains with one guy in the middle and a guy on either side pointing at his temples. It's amazing how fast one's eyes can vibrate with an alternating current running through your brain. Who needs drugs? :)
-Guanno
Here's a sure fire way to do the trick. EMP Bomb. Same principal, but unspeakably more devastating. :)
-Guanno
And what's going to prevent some electronically saavy folks from posting instructions for DVR Mods to their web-sites? If you know what chip is what, it's not exactly rocket science ... or is it? LOL Anyway, it's no different from pirate satellite TV. Piece of cake.
BB -Yew
If it weren't for adventurous spirits who are willing innovate a home made solution, the computer industry would never have gotten as far as it has, or be going in such interesting and potentially rewarding directions.
/. fan) when the innevitable problems occur. And the rest of us suffer greatly for it. I wouldn't pay someone any more than minimum wage to do things the 'Real' way.
The 'Real' way actually amounts to mundane unimaginative and stagnant. At worst it amounts to millions of servers on an IP near you being adminstrated by lazy incompetant boobs, who don't know any better than to call a 'Real' technician (read
BB -Guanno
Some of you code monkeys gotta start writing games for Linux. I'm talking hard core Playstation/XBox/GameCube kind of stuff. Get the kiddies nagging mommy and daddy for it, and you'll have Linux in every home in the wired world just to shut them up. :) The rest will become history. I do like the ideas "psicE" and "TFloore" were tossing around in the "I've got an interface for you" thread. The sunglasses idea, with the ROM embedded Linux sounds slamming. Occam's razor together with a cattle prod (the christmas list) is the sure way to Joe six pack's wallet.
-Guanno
If you want to do something revolutionary, then put the emphasis on the whole reason most Open Source geeks became Open Source geeks in the first place. Offer a GUI you can make completely your own down to the last niggling pixel. Call it myX or something.
... I'm not.
What comes to mind is a mark up language specifically for the myX GUI. Reduce the GUI itself to little more than a basic script compiler with a handful of default scripts/skins to keep joe six pack happy and lazy.
LOL. If I were a real code monkey, I'd do more than just make the suggestion. Alas
-Guanno
Got news for you... It's already happened. It's called Mac OSX.
If Linux is ever going to get big on it's own it needs a BRAND. Like "LINUX BRAND LINUX" or something like that. Red hat is getting close to mainstream, even though it sucks. The average person, and even me (I'm a BSD guy) finds the convoluted quagmire of Linux flavours daunting, and pointless to keep track of.
The advantage for Linux geeks is the ultimate customisability. You have your system by the short and curlies, and if you're a real propeller head, you can even get it to brew your coffee for you in the morning. Yippee!
However for the average joe six pack, this is not the way to spend a hard day after work. Therefore it's not where joe six pack's money gets spent. If you want to appeal to joe six pack and find your way into the pocket book of his beer swilling boss, you have to think like them. You have to want to be lazy.
-Guanno