I've been hacking properly for 14 years or so - starting with ARM assembler that is, not counting BASIC for good reason. Since then Java, C, perl and ML to name a few on everything from huge servers to embedded boards.
Multiple cores are great, and to be honest, you can get plenty of concurrency issues using multiple threads on single core CPUs. Bring it on.
Try living in a 100% oxygen atmosphere for a week because "it's a vital ingredient for animal life".
Too much CO2 is bad, just like too much of any damn thing.
Let's just say that the US emits more spam total, and you don't know enough Indians to bring up the signal:noise ratio. If you're working somewhere like a university, you just cannot block email by country.
Mods are on crack today. Typically, programmer time costs a lot - to the extent that it's often cheaper to throw hardware at a problem than to spend 10x as long doing it "properly" in C. If you've ever written multi-threaded code, you will really really appreciate Java over C.
If you're just an armchair critic who has never had to write serious multi-threaded code, it's very easy to say "do it in C". I'm coding in C now for an embedded platform, but if it was a desktop PC, you can bet I would choose to write in Java. Trade-off of a longer dev cycle is just not worth it for the performance increase. If you can even find anyone who can write good multi-threaded code in C.
Kerkhoffs' Principle: The security of a cryptosystem must not depend on keeping the cryptographic algorithm secret. -- Journal of Military Science, 1883
gnupg is definitely OK in this regard - as is any decent AES / hybrid AES/RSA or similar system.
You just need a tap or SPAN port on your main Internet connection, plus a separate workstation with a reasonably good graphics card to run the visualisation.
I thought this would be just the thing for our reception area, but sadly my boss vetoed it. (I thought management were meant to like shiny.)
"Separation of duties" is the new jargon for "I think you're a bonehead who doesn't document their work, but I don't want to come right out and say that."
The flaws pointed out rest on asserting that the sampling is not representative, and that is impossible to tell without knowing a lot more about the data set.
My bad in that I was referring to the media - we just got the "it's rubbish" line from government and pundits. However, none of the flaws claimed in wikipedia have been substantiated - they are still very much open to question, and plenty of statisticians think it was a robust study.
In what universe is wikipedia a better source of information than the BBC and the Guardian? (not fucking Pravda, nor Al-Jazeera)
But just for shits and giggles: "The Lancet surveys have been supported by many epidemiologists[5] and statisticians, as well as the September 2007 ORB survey." - your quoted source.
This was a peer reviewed paper and personally I believe the real figure *is* within their 95% confidence interval - between 400,000 and 950,000). And I have two degree in maths, thanks for asking.
Got any flaws in the methodology, apart from "obviously nonfactual"? If it's so fucking obvious, please let us all know.
Slashdot Mirror
And possibly a monkey with a gun.
Multiple cores are great, and to be honest, you can get plenty of concurrency issues using multiple threads on single core CPUs. Bring it on.
do you have to write $lots of perl by any chance?
I write a couple of articles here and there and once you calculate income per hour it's less than minimum wage.
I know; I remember when I used an old value of pi in a complex analysis problem. Man, I was so embarrassed.
http://www.basicinstructions.net/
http://www.mnftiu.cc/mnftiu.cc/war.html
It's in the big blue room.
Try living in a 100% oxygen atmosphere for a week because "it's a vital ingredient for animal life". Too much CO2 is bad, just like too much of any damn thing.
Yeah, and I was told that I'd have to get used to wearing a suit for "real life". Guess what? That was bollocks too.
1. Java, 2. C, 3. C++, 4. PHP, 5. VB. ("The ratings are based on the number of skilled engineers world-wide, courses and third party vendors.")
Let's just say that the US emits more spam total, and you don't know enough Indians to bring up the signal:noise ratio. If you're working somewhere like a university, you just cannot block email by country.
Really.
How many times have you been screwed over by a vendor who thinks they know best? (Symantec / L0phtcrack anyone?)
http://en.wikipedia.org/wiki/Thar_Desert - mostly lying within Rajasthan.
If you're just an armchair critic who has never had to write serious multi-threaded code, it's very easy to say "do it in C". I'm coding in C now for an embedded platform, but if it was a desktop PC, you can bet I would choose to write in Java. Trade-off of a longer dev cycle is just not worth it for the performance increase. If you can even find anyone who can write good multi-threaded code in C.
On the contrary, the one thing that keeps me coming back is the friendly, smiling faces of Customs and Border Patrol.
... but if things go badly, we could end up in prison, married to the guy with the most cigarettes.
And writing 'veterinary anaesthetist' for partner's occupation gets painful very quickly :)
gnupg is definitely OK in this regard - as is any decent AES / hybrid AES/RSA or similar system.
I always have a backpack though, so wouldn't be visible on me.
No EFS (file encryption) if I remember rightly. To the other poster, the lack of IIS is a good thing.
You just need a tap or SPAN port on your main Internet connection, plus a separate workstation with a reasonably good graphics card to run the visualisation.
I thought this would be just the thing for our reception area, but sadly my boss vetoed it. (I thought management were meant to like shiny.)
Hope this helps!
One job, there was a page-long FAQ about how to bring down the Ingres DB. Compare and contrast with "/etc/init.d/postgresql stop".
The flaws pointed out rest on asserting that the sampling is not representative, and that is impossible to tell without knowing a lot more about the data set.
My bad in that I was referring to the media - we just got the "it's rubbish" line from government and pundits. However, none of the flaws claimed in wikipedia have been substantiated - they are still very much open to question, and plenty of statisticians think it was a robust study.
But just for shits and giggles: "The Lancet surveys have been supported by many epidemiologists[5] and statisticians, as well as the September 2007 ORB survey." - your quoted source.
This was a peer reviewed paper and personally I believe the real figure *is* within their 95% confidence interval - between 400,000 and 950,000). And I have two degree in maths, thanks for asking.
Got any flaws in the methodology, apart from "obviously nonfactual"? If it's so fucking obvious, please let us all know.