Gold cabling makes the problem *worse* by increasing resistance at the connectors.
The connectors on pretty much all hifi gear is *not* gold, so you have a transition between two different metals. Even if you get some uber hifi with gold connectors what's going on inside.. gold internally? I guess not... same problem transferred elsewhere.
As far as air in the silver cables... you've fallen for the 'oxygen free' one as well I see. No cable is going to corrode in your living room, unless you happen to live on a boat.
You accept viruses happen, and make them less likely.
That means making it impossible for an email package to run executables. It means running as an unprivileged user by default. It means not having write access to anything but your own sandbox by default. It means all services being off by default and enabling what you need.
AOL users can still run AOL, Word or whatever so they aren't affected. Except even if they do download $CRAPWARE then the probably won't know enough to give it the rights to screw up their box.
I've reinstalled the OS half a dozen times (even tried 10.4 for a bit) and it does exactly the same thing... even the console won't close unless you force it to close by right clicking on the task bar... it's like something is keeping the app open. If it was Windows I'd suspect a virus, but this thing has nothing but the default software + gcc & I rarely if ever browse with it, and have never used the email app.
Finder dies just by doing something like trying to browse a network share where the machine has disappeared for some reason (it happens...).. unfortunately once it's gone the whole UI goes with it. Throw the dodgy firewire driver into the mix (access dead drive... bang.) then it doesn't make for a happy user experience.
7200rpm doesn't make that much difference... I tried a 7200 in my mini and couldn't tell a difference in boot times really. It got hotter though (noticable because although the mini is quite warm it's not really hot in normal use).
10.3 is *much* more stable, and a fair bit faster on a Mini too.
OTOH I never got into the Mac either... I use mine as a compile box but couldn't use it as my main machine, since Finder has a habit of falling over if the wind changes (it doesn't like my firewire hard drive... after about 10 minutes non use the driver locks up... the same drive works fine on Linux and Windows so it's definately an OSX bug. I once plugged the drive via USB... OSX threw a complete wobbly and died.. I guess nobody uses USB on the Mac).
There are UI things I don't like - for example options missing from the context menu that are only on the main menu.. so you have to go hunting around for them instead of just getting on with what you want to do. Finder seems to have a problem shutting apps down too.. you can close them and they'll keep running. Not sure if that's a bug or if someone designed it that way (??).
I was prepared to believe it until I saw the audio jack labeled as 'Removable NvIOpRAM' (http://atomchip.com/_wsn/page3.html).. that is just such an obvious joke (didn't see the photoshopped system properties screenshot until much later.. 1TB? Windows XP can't address 1TB...)
Actually it has a lot in common - look at the function names available... a lot of them have direct Win32 equivalents. The behaviour of those functions is the same as the Win32 functions they call.
No matter how hard you try to port that to Linux it's a different underlying system.. the documented behaviour might work, it might not. Anything use COM or PInvoke definately won't.
Since.NET is 99.9% Windows pretty much all.NET apps will have windows dependencies eg. COM objects, file paths with backslashes, assumed case independence, etc.
Making cross platform code has to be done from the ground up... just because you have some kind of binary (well, pcode) compatibility means nothing if you weren't thinking of Unix when you wrote it.
Even trivial things will break you... assuming Mono has written the ADO+ classes (no mean feat if so) most ADO+ code is written to MSDE/SQL Server and will just die if you run it against MySql..
I wouldn't trust user management to an external machine over the internet. ever. If that machine is ever compromised *every* app that uses it would be compromised. This is why MS Passport never took off.
Handling users and permissions is generally done by the OS anyway.. doesn't need an external module. Application-only permissions (things like 'can edit page', 'can ride quad-bike', etc.) are not generic and change for every application, so can't be stored externally anyway.
Really you're talking about something that probably takes about an hour of some junior programmers time, is about 20 lines long and never needs to be touched. Why introduce the complexity of a web service for something like that? Heck, just borrow it from the last application that needed it...
I used to have a manager that used to ask 'is it generic?' every time we discussed something.
Unfortunately for him generic meant 'solves every problem, even ones I haven't thought of yet'. Hugely complex APIs were designed, filling a bookshelf.
As you can imagine, some of the modules that were in use were utterly horrendous... months were spent writing routines that could do *everything* even extremely unlikely things. There were functions that were 2500 lines long, mostly switch statements on the input (I'm not exaggerating.. I had to debug them).
Sure they had code reuse. Unfortunately for them, the code sucked. I remember spending a couple of weekends resurrecting some of their ancient stuff (before the 'generic' fad) which was neat, small and well written, classing it up, and dropping it into the new code... which miraculously started to work about 10 times faster with fewer bugs.
Sure, the interfaces had to be changed over time.. *horror of horrors* the database interface layer only had 10 useful functions not 350 useless ones! How could it be generic!!! I reckon the time gained by not trying to second guess what you'll possibly need in 5 years was more than worth it.
I guess what had happened there was that 'code reuse' had become more of a mantra than a tool for getting product out of the door. I reckon it won't be the last time I see it.
Try to use functions, objects, services, etc and you get your ass stuck at the bottom of the ladder
I'd love to be somewhere where they don't use functions.....and they may not look like they're using objects, but I bet they are (passing context handles around functions is still objects, just a bit more opaque).
First thing to do in a new project: call a meeting. Management like that. Go over the design, and discuss the best way to implement it. If it's services (and your teammates agree) then management won't object.
What you can't do is go off on your own and say 'I think $FLAVOUR_OF_THE_MONTH is cool, so I'm going to write the entire project in that no matter who it screws up'.
If you're maintaining old code and it's crap every time you take too long tell management why (they like explanations too). They'll eventuall come around to the idea of a rewrite.
OTOH in most teams I've worked on we've had 'black-ops' projects going on rewriting the worst of the crap. Sounds risky but as long as the workload gets done they won't notice, and the look on their faces (dollar signs, mainly) when you show them a cool new interface/faster, more stable code is worth it.
In other words... ye olde 80's style modular programming. Whether it's XML or a.lib file it's still a module.
Why not call it that... we've buried good style in acronyms these days. I've seen stuff written by otherwise good programmers that makes me want to tear my hear out and scream - new programmers often aren't taught to think in terms of small, discrete objects, less still layers (I'm big on layering... it's saved my bacon more than once.. you can tell any project I've been on for a while because structurally it starts to look like a layer cake... plus I get a reputation for being able to implement the silly spec changes without breaking everything...).
Not at all.. to write objects you have to think in an OO way.. that should come easily to an experienced programmer but I've seen a lot of things that are just linear programs with the word 'class' at the top.
Web services are a bitch... I've yet to find a really compelling use for them though - I could imagine an application that uses them but have never actually been called upon to write such a beast.
Wasn't OO supposed to be the panacea for reuse a few years ago? Never happenned... (it turned out that massively complex multiple inheritence trees were worse than the rewritten objects they were trying to replace).
Then 'Extreme Programming' did the rounds... use twice the number of programmers to produce the same code... yeah rock on dude... Not sure what they were aiming at there... My last boss took one look at it and said 'over my dead body'. End of that one.
Then UML... Everyone I ever met took one look at that and laughed.. PHBs tried to push it for a while though... was almost forced to do a project in it, until we pointed out that the design phase alone would take longer than the entire project deadline (which admittedly was only 2 weeks).
Now we have a new (unexplained... SOA to me means DNS records) fad that is supposed to make programs perfect, solve world peace, etc. As ever, it's 10% good ideas, 90% hype (I bet they sell a few books on the back of it though).
Good programming is about using every technique available, within the constraints of commercial reality - and that means tight deadlines, bosses who understand nothing but results, and users who are worse.
Code reuse is a very good idea, but in practice tends to happen within small teams (who often have a library of routines that they are familiar with and work with).. Commercial libraries often suck donkey (in fact very often... since they're subject to the commercial constraints listed above) - I once had to rewrite an entire development library because it sucked so hard.. took nearly 4 days (mind you, the original developer seemed quite proud he'd done it in less than 6 months... given the complexity of what he'd produced I could believe it - they still don't teach KISS in universities I see).
OTOH you can't become too wedded to code reuse.. sometimes the spec is just different, and constantly modifying the same routine to do multiple things it wasn't designed to do creates an unmaintainable mess real quickly.. that's where refactoring and rewriting starts (seems to happen in phases... you collect and modify the libraries over a period of years, then someone says 'look at this pile of steaming crap', and it gets rewritten... years later the cycle repeats.. if your stuff is modular enough you can do it without introducing bugs).
If you combine this with the new florida law that makes it legal to shoot someone if they piss you off or maybe look a bit foreign, then it'd work very well... find phisher/spammer, shoot them in the head... profit!
It's a testimony to the continuing influence of the US that people treat the 6000 year thing as a mainstream position.. it's a tiny minority outside the US (1% I'd guess.. seems to be near 100% of christians in the US.. didn't one state mandate teaching it as science? Scary stuff...).
The Flying Spagetti Monster has more credibility to it though (we *know* spagetti exists - what more proof do you need?)... IMO Christianity has a lot going for it, without the lunatic fringe screwing everything up.
Re:But are the problems only limited to the one ch
on
Airbus A380 Under Fire
·
· Score: 1
You can't. It's impossible to prove a negative.
Untrue.
I can prove that I am not a 20 foot nymphomaniac amazon woman.
I can prove that there are no big green martians sat on this chair with me.
I can prove *lots* of negatives.. it's as easy to prove a negative as a positive, given enough evidence - since they're essentially the same thing just phrased differently.
Not gonna happen... for the same reason people didn't switch to Linux, Beos or any of the others.
Desktops are a natural monopoly - you want to be running what everyone else is running, so you can read their documents, etc.
Not to mention the OSX integration with active directory sucks donkey & it isn't even going to get a look in in business until that's sorted (even on tiger, the only thing they really support is login.. and even that's half-assed - OSX doesn't treat the user as 'real', so they can't share files, etc.)
She play FFXI a lot, which on the graphics intensive stuff (waterfalls, etc.) with lots of other players in the same area as you (once counted 200) can bury anything less than a 6800GT . She gets really uppity if the frame rate drops below 30fps, so her machine has more memory, a faster processor and much better graphics than any of mine. It also has to have uber fans to cope with it...
Slashdot Mirror
Gold cabling makes the problem *worse* by increasing resistance at the connectors.
The connectors on pretty much all hifi gear is *not* gold, so you have a transition between two different metals. Even if you get some uber hifi with gold connectors what's going on inside.. gold internally? I guess not... same problem transferred elsewhere.
As far as air in the silver cables... you've fallen for the 'oxygen free' one as well I see. No cable is going to corrode in your living room, unless you happen to live on a boat.
You accept viruses happen, and make them less likely.
That means making it impossible for an email package to run executables.
It means running as an unprivileged user by default.
It means not having write access to anything but your own sandbox by default.
It means all services being off by default and enabling what you need.
AOL users can still run AOL, Word or whatever so they aren't affected. Except even if they do download $CRAPWARE then the probably won't know enough to give it the rights to screw up their box.
I've reinstalled the OS half a dozen times (even tried 10.4 for a bit) and it does exactly the same thing... even the console won't close unless you force it to close by right clicking on the task bar... it's like something is keeping the app open. If it was Windows I'd suspect a virus, but this thing has nothing but the default software + gcc & I rarely if ever browse with it, and have never used the email app.
Finder dies just by doing something like trying to browse a network share where the machine has disappeared for some reason (it happens...).. unfortunately once it's gone the whole UI goes with it. Throw the dodgy firewire driver into the mix (access dead drive... bang.) then it doesn't make for a happy user experience.
7200rpm doesn't make that much difference... I tried a 7200 in my mini and couldn't tell a difference in boot times really. It got hotter though (noticable because although the mini is quite warm it's not really hot in normal use).
10.3 is *much* more stable, and a fair bit faster on a Mini too.
OTOH I never got into the Mac either... I use mine as a compile box but couldn't use it as my main machine, since Finder has a habit of falling over if the wind changes (it doesn't like my firewire hard drive... after about 10 minutes non use the driver locks up... the same drive works fine on Linux and Windows so it's definately an OSX bug. I once plugged the drive via USB... OSX threw a complete wobbly and died.. I guess nobody uses USB on the Mac).
There are UI things I don't like - for example options missing from the context menu that are only on the main menu.. so you have to go hunting around for them instead of just getting on with what you want to do. Finder seems to have a problem shutting apps down too.. you can close them and they'll keep running. Not sure if that's a bug or if someone designed it that way (??).
I was prepared to believe it until I saw the audio jack labeled as 'Removable NvIOpRAM' (http://atomchip.com/_wsn/page3.html).. that is just such an obvious joke (didn't see the photoshopped system properties screenshot until much later.. 1TB? Windows XP can't address 1TB...)
Actually it has a lot in common - look at the function names available... a lot of them have direct Win32 equivalents. The behaviour of those functions is the same as the Win32 functions they call.
No matter how hard you try to port that to Linux it's a different underlying system.. the documented behaviour might work, it might not. Anything use COM or PInvoke definately won't.
Since .NET is 99.9% Windows pretty much all .NET apps will have windows dependencies eg. COM objects, file paths with backslashes, assumed case independence, etc.
Making cross platform code has to be done from the ground up... just because you have some kind of binary (well, pcode) compatibility means nothing if you weren't thinking of Unix when you wrote it.
Even trivial things will break you... assuming Mono has written the ADO+ classes (no mean feat if so) most ADO+ code is written to MSDE/SQL Server and will just die if you run it against MySql..
Bad example.
I wouldn't trust user management to an external machine over the internet. ever. If that machine is ever compromised *every* app that uses it would be compromised. This is why MS Passport never took off.
Handling users and permissions is generally done by the OS anyway.. doesn't need an external module. Application-only permissions (things like 'can edit page', 'can ride quad-bike', etc.) are not generic and change for every application, so can't be stored externally anyway.
Really you're talking about something that probably takes about an hour of some junior programmers time, is about 20 lines long and never needs to be touched. Why introduce the complexity of a web service for something like that? Heck, just borrow it from the last application that needed it...
I used to have a manager that used to ask 'is it generic?' every time we discussed something.
Unfortunately for him generic meant 'solves every problem, even ones I haven't thought of yet'. Hugely complex APIs were designed, filling a bookshelf.
As you can imagine, some of the modules that were in use were utterly horrendous... months were spent writing routines that could do *everything* even extremely unlikely things. There were functions that were 2500 lines long, mostly switch statements on the input (I'm not exaggerating.. I had to debug them).
Sure they had code reuse. Unfortunately for them, the code sucked. I remember spending a couple of weekends resurrecting some of their ancient stuff (before the 'generic' fad) which was neat, small and well written, classing it up, and dropping it into the new code... which miraculously started to work about 10 times faster with fewer bugs.
Sure, the interfaces had to be changed over time.. *horror of horrors* the database interface layer only had 10 useful functions not 350 useless ones! How could it be generic!!! I reckon the time gained by not trying to second guess what you'll possibly need in 5 years was more than worth it.
I guess what had happened there was that 'code reuse' had become more of a mantra than a tool for getting product out of the door. I reckon it won't be the last time I see it.
Try to use functions, objects, services, etc and you get your ass stuck at the bottom of the ladder
..and they may not look like they're using objects, but I bet they are (passing context handles around functions is still objects, just a bit more opaque).
I'd love to be somewhere where they don't use functions...
First thing to do in a new project: call a meeting. Management like that. Go over the design, and discuss the best way to implement it. If it's services (and your teammates agree) then management won't object.
What you can't do is go off on your own and say 'I think $FLAVOUR_OF_THE_MONTH is cool, so I'm going to write the entire project in that no matter who it screws up'.
If you're maintaining old code and it's crap every time you take too long tell management why (they like explanations too). They'll eventuall come around to the idea of a rewrite.
OTOH in most teams I've worked on we've had 'black-ops' projects going on rewriting the worst of the crap. Sounds risky but as long as the workload gets done they won't notice, and the look on their faces (dollar signs, mainly) when you show them a cool new interface/faster, more stable code is worth it.
In other words... ye olde 80's style modular programming. Whether it's XML or a .lib file it's still a module.
Why not call it that... we've buried good style in acronyms these days. I've seen stuff written by otherwise good programmers that makes me want to tear my hear out and scream - new programmers often aren't taught to think in terms of small, discrete objects, less still layers (I'm big on layering... it's saved my bacon more than once.. you can tell any project I've been on for a while because structurally it starts to look like a layer cake... plus I get a reputation for being able to implement the silly spec changes without breaking everything...).
Objects are easier than functions?
Not at all.. to write objects you have to think in an OO way.. that should come easily to an experienced programmer but I've seen a lot of things that are just linear programs with the word 'class' at the top.
Web services are a bitch... I've yet to find a really compelling use for them though - I could imagine an application that uses them but have never actually been called upon to write such a beast.
Wasn't OO supposed to be the panacea for reuse a few years ago? Never happenned... (it turned out that massively complex multiple inheritence trees were worse than the rewritten objects they were trying to replace).
Then 'Extreme Programming' did the rounds... use twice the number of programmers to produce the same code... yeah rock on dude... Not sure what they were aiming at there... My last boss took one look at it and said 'over my dead body'. End of that one.
Then UML... Everyone I ever met took one look at that and laughed.. PHBs tried to push it for a while though... was almost forced to do a project in it, until we pointed out that the design phase alone would take longer than the entire project deadline (which admittedly was only 2 weeks).
Now we have a new (unexplained... SOA to me means DNS records) fad that is supposed to make programs perfect, solve world peace, etc. As ever, it's 10% good ideas, 90% hype (I bet they sell a few books on the back of it though).
Good programming is about using every technique available, within the constraints of commercial reality - and that means tight deadlines, bosses who understand nothing but results, and users who are worse.
Code reuse is a very good idea, but in practice tends to happen within small teams (who often have a library of routines that they are familiar with and work with).. Commercial libraries often suck donkey (in fact very often... since they're subject to the commercial constraints listed above) - I once had to rewrite an entire development library because it sucked so hard.. took nearly 4 days (mind you, the original developer seemed quite proud he'd done it in less than 6 months... given the complexity of what he'd produced I could believe it - they still don't teach KISS in universities I see).
OTOH you can't become too wedded to code reuse.. sometimes the spec is just different, and constantly modifying the same routine to do multiple things it wasn't designed to do creates an unmaintainable mess real quickly.. that's where refactoring and rewriting starts (seems to happen in phases... you collect and modify the libraries over a period of years, then someone says 'look at this pile of steaming crap', and it gets rewritten... years later the cycle repeats.. if your stuff is modular enough you can do it without introducing bugs).
Appeal to ICANN... A company I was with had this problem and got their domain back for free (after being sent a bill for $50,000 by the squatter...)
Domain squatting is against the rules, and yours seems like a pretty clear cut case.
If you combine this with the new florida law that makes it legal to shoot someone if they piss you off or maybe look a bit foreign, then it'd work very well... find phisher/spammer, shoot them in the head... profit!
As long as 10.3 gets higher ranking...
10.4 is currently sitting in its box on the shelf... kept it for nearly a month before I got so pissed off with it I just wiped and went back.
It's a testimony to the continuing influence of the US that people treat the 6000 year thing as a mainstream position.. it's a tiny minority outside the US (1% I'd guess.. seems to be near 100% of christians in the US.. didn't one state mandate teaching it as science? Scary stuff...).
The Flying Spagetti Monster has more credibility to it though (we *know* spagetti exists - what more proof do you need?)... IMO Christianity has a lot going for it, without the lunatic fringe screwing everything up.
You can't. It's impossible to prove a negative.
Untrue.
I can prove that I am not a 20 foot nymphomaniac amazon woman.
I can prove that there are no big green martians sat on this chair with me.
I can prove *lots* of negatives.. it's as easy to prove a negative as a positive, given enough evidence - since they're essentially the same thing just phrased differently.
Uh.. no. what 'personalized home'? You're getting paranoid.
The google homepage is just search, plus a pretty google graphic.
If they did that then there would a lawsuit of gargantuan proportions even before the third dupe of the story on slashdot.
Not even microsoft can deliberately attempt to kill a competitor like that... they have to be a *bit* more subtle.
Not gonna happen... for the same reason people didn't switch to Linux, Beos or any of the others.
Desktops are a natural monopoly - you want to be running what everyone else is running, so you can read their documents, etc.
Not to mention the OSX integration with active directory sucks donkey & it isn't even going to get a look in in business until that's sorted (even on tiger, the only thing they really support is login.. and even that's half-assed - OSX doesn't treat the user as 'real', so they can't share files, etc.)
My wife has a better machine than me!
She play FFXI a lot, which on the graphics intensive stuff (waterfalls, etc.) with lots of other players in the same area as you (once counted 200) can bury anything less than a 6800GT . She gets really uppity if the frame rate drops below 30fps, so her machine has more memory, a faster processor and much better graphics than any of mine. It also has to have uber fans to cope with it...
So do mobile phones. Which don't suffer from this nearly as badly (or at all, in my experience).
Apple skimped on the plastic to keep their costs down, and it's come back to bite them in the ass.
Or mobile phones.
My phone is a year old, has been in my pocket inc. keys, various abrasive objects over that time. Zero scratches.