You're confused. The FTC is probably one of the most useful and generally non-sucky government agencies. It's like the various state attorney generals offices on a larger scale. Bascailly all they do is shut down scams and the like. You're thinking of the evil that is the F*C*C. No relation, other than both being government agencies.
My point is they get so mired down in doing everything "by the book" and overspecing everthing 3000% that they actually DECREASE safety by making things overly complex and adding new failure modes that wouldn't exist in a simpler system.
It's rather ironic I think. NASA does things "rigoursly" in the name of safety, but in the end I think safety is compromised because systems are so complex. No one person can have a high level view of such as system.
Haven't done any ruby in a while, so I don't have any code handy, but blocks are great for things like GUI callbacks. You can put the code right where it would logically fit, and you don't end up with a 1001 quitButtonOnClick() type functions cluttering your namespace.
The problem is not usually, as is often thought, bandwidth. So even fairly large static files are okay as long as your own a decent link (Say, at least 10mbp/sec upstream). Problems are usually poorly coded dynamic sites, where either the DB shits itself, or the server grinds to a halt from the cpu load.
Seems like every time I see a UK govt IT project in the headlines, words like "Disaster", "Overbudget", "Late", and "Useless" tend to appear with alarming frequency.
Shared libs aren't used much in practice, although because so much is built into the OS (Cocoa, etc) there is less need. The needed libs are part of the bundle. Causes a bit of bloat, maybe, but harddrives and RAM are cheap, and it side steps the whole dependency / DLL|RPM Hell issue.
The best approach I've seen to this is Mac OS X's "App bundles". Basically these are directories with a name that ends in.app, with a certain internal layout. To the user in the file manager, it looks and acts like a file. If you click on it it launches the app. Easy drag-and-drop installation/removal, and the program can include as many support files as it needs, without even NEEDING an installer.
At which time these twits will be the first with their backs against the wall...
Sounds like a bunch of pricks trying to pretend they are intelligent...
Well, if something is truly abandonware, who could sue you?
Ever pop a hole in a ballon?
Ever pop a hole in a sidewalk?
Wouldn't it just be easier to run a multiplayer neverwinter nights session and project THAT on a table?
You're confused. The FTC is probably one of the most useful and generally non-sucky government agencies. It's like the various state attorney generals offices on a larger scale. Bascailly all they do is shut down scams and the like. You're thinking of the evil that is the F*C*C. No relation, other than both being government agencies.
He has the sense to make movies people will actually WANT to see.
Well, it'd be self correcting. If, say, the roads started to suck (even more), that would lead the people most annoyed to allocate money towards them.
My point is they get so mired down in doing everything "by the book" and overspecing everthing 3000% that they actually DECREASE safety by making things overly complex and adding new failure modes that wouldn't exist in a simpler system.
It's rather ironic I think. NASA does things "rigoursly" in the name of safety, but in the end I think safety is compromised because systems are so complex. No one person can have a high level view of such as system.
Huh? I could encode flac at over 15x realtime on my old Athlon 900.
Haven't done any ruby in a while, so I don't have any code handy, but blocks are great for things like GUI callbacks. You can put the code right where it would logically fit, and you don't end up with a 1001 quitButtonOnClick() type functions cluttering your namespace.
The problem is not usually, as is often thought, bandwidth. So even fairly large static files are okay as long as your own a decent link (Say, at least 10mbp/sec upstream). Problems are usually poorly coded dynamic sites, where either the DB shits itself, or the server grinds to a halt from the cpu load.
More like 1000 times the file size...
If by pretty good you mean "Sounds like a malfunctioning japanese fairground organ..."
From what I understand there isn't "A" kilogram, but really something like 80 or 100 of them at various institutions all over the world.
Really?
Seems like every time I see a UK govt IT project in the headlines, words like "Disaster", "Overbudget", "Late", and "Useless" tend to appear with alarming frequency.
I thought the whole point of SSL is that not just anyone could get a cert...
Not Quite.
A MP in binary would look like 10000000001, where the total number of binary digits is equal to the power of two.
No it's not. It's 4ghz x 10. Most tasks are NOT parrelell in nature, and saying it's equivilant to a single 40ghz chip is incredibly misleading.
The "problem" with dongles is that it's quite possible to emulate them in software.
Shared libs aren't used much in practice, although because so much is built into the OS (Cocoa, etc) there is less need. The needed libs are part of the bundle. Causes a bit of bloat, maybe, but harddrives and RAM are cheap, and it side steps the whole dependency / DLL|RPM Hell issue.
The best approach I've seen to this is Mac OS X's "App bundles". Basically these are directories with a name that ends in .app, with a certain internal layout. To the user in the file manager, it looks and acts like a file. If you click on it it launches the app. Easy drag-and-drop installation/removal, and the program can include as many support files as it needs, without even NEEDING an installer.
That's a dangerous attitude to take. If the Post went under, then that would increase the influence of the RIGHT-WING corporate media.
Well, for that kind of stuff you really should be using a vector-based editor like Inkscape.