Psychiatrists have known for a long time that paedophiles are "born that way", that their perversion isn't really a product of their upbringing or past life experiences, just like homosexuality. It's not something they can control or repress, or avoid becoming by not looking at certain images.
Do you have any data to back that up? Or did some sarcasm just fly over my head.
Okay, so calling HyperStudio "programming" is a stretch, but it was definitely a gateway drug for it.
Playing Doom on my uncle's computer may have got me interested in computers, but using HyperStudio in elementary school was my first experience with programming and is probably what started me down that path.
I was hoping for something like ScRGB support. I've always wanted two things out of displays: higher DPI, and higher gamut. Does this deliver either?
Chris Chinnock, President of the research firm "Insight Media", is one of those who are skeptical about HP's claims. He says that while the 30-bit resolution will allow for better gradation between the color levels, the technology will not be able to increase the color gamut of a display.
Which is why I say it should be documented separately from the code. Even if it is constantly changing, these changes should be documented prior to implementation. It'd be much easier to review than looking at code - Java or C++.
Freenet is an important concept. On it you get complete freedom of speech: the ability to discuss and spread your ideas, with full anonymity and freedom from censorship. Of course, this means that you will probably come across things on it that will go against your beliefs. While nothing forces you to actually visit these freesites, you will have to come to terms that this might be cached on your computer even without you visiting them. But this is important to freedom of speech: if people where able to censor anything, the system just wouldn't work.
So why does Freenet fail? Lack of documentation. I don't mean ease of use in the interface - I mean for the protocols and network design. A system as important as Freenet -- one that people expect unfaltering anonymity and security from -- should be rigorously and meticulously documented.
But it's not. In fact, if you bring it up with the Freenet developers they will gladly tell you this is intentional -- that they use security through obscurity to guard against someone finding a way to break the system.
So -- do you trust your freedom with the competency of a handful of developers to make a good design? I don't. I want as many people looking at the system as possible. I want people to really bash on it, to try to break it. This gives me confidence, not worry, because problems will be solved sooner than later.
This would also open up the possibility of more than one client to access the network. If you have two separate clients that implement the same strict protocol and one of them messes up, it's likely to be caught far sooner than with just one. An immediate example of where this would have helped is with a bug that existed in 0.7's AES implementation for a very long time, where the data wasn't being encrypted properly.
The Freenet developers don't want multiple clients either -- again, they worry that one might break the network. This line of thought is incomprehensible to me, because as a developer I would want things that could break my network to be discovered as soon as possible so I could fix the design.
Sure, you could look at the source code. It is Open Source, after all. But what if you don't know Java? I don't particularly want to learn Java just so I can review Freenet's code. As a C++ developer I might be able to read and understand most of it, but I don't trust myself to review something so important without years of prior Java experience -- the chance that I'd miss something is just too great.
Garbage collection is surely a factor in them losing ground, but I think the main reason is simple: library support.
Java and.NET have huge well-designed frameworks behind them. You can get things done really fast. What does C have? A bunch of separate libraries all with different conventions. C++ is a little better with a more useful standard library and Boost, but it still doesn't have anywhere near the infrastructure Java and.NET have.
7-zip compressing. Multimedia encoding. VC++ has an ever so awesome/MP switch. Windows threads getting previews for all your files in explorer. Heck, even Excel 2007 will thread your calculations behind the scenes.
Games may not make significant use of multi-core yet, but some other real-world things do. Quad core definitely makes an impact on my daily usage.
It sounds like this randomness is weighted to still pay more attention to hot zones. Couldn't people with access to the same data still find the least likely places for security to be dispatched? Moreover, if they already have access they can just wait for it to calculate a plan and then go around it.
The only problem with permissions is that the very people who should use them the most are typically equally ignorant about permissions as they are horrible in coding.
How do you see that as different from what Java J2EE does? Most J2EE servers these days use pools of threads to handle requests. These threads are then utilized based on poll/select APIs so that one thread can handle many requests depending on the availability of data. Database connections are similarly pooled and reused, though any optimization on the blocking level would need to be done by the JDBC driver.
I've never used Java/J2EE before so I couldn't say.
.NET uses a per-operation callback to notify the app of I/O completion - it doesn't expose whatever internal mechanism it uses to achieve async, so the server choose the most efficient method (iocp, epoll, kqueue, how many threads, etc.). If you use SQL Server, DB queries can be done async too. If you do it right in many cases you can keep from ever blocking on I/O.
Perhaps they meant it as in "specifically designing to scale up", as opposed to a developer who just uses a thread to do some background processing.
One thing that's always saddened me is that most embarrassingly parallel problems like web and database development are still in the dark ages with this. They have so much potential, but almost nobody seems to care. To date the only frameworks I know of that allow fully asynchronous efficient processing of requests and database queries (so that you don't need to spawn a new thread/process for every request) is ASP.NET, WCF (SOAPish stuff in.NET), and some of.NET's database APIs. Does anyone know of any non-MS web technologies that allow this?
Anybody remember Vista Ultimate edition? The one that promised Ultimate Extras - regular extras that you could download through Windows Update? They released 3 things through that: an small card game, DreamScene (sucks up CPU to animate your desktop background), and Bitlocker full drive encryption. That was all just a little after RTM - nothing since then.
When they came up with the idea I thought it might be interesting, but they've shown they can't follow through. If this is at all similar I'm sure it will fail. Microsoft won't be overthrown just from this, certainly not by 2010, but I'm sure it will pave more of the Disappointment Road that Vista started.
When they say "subscription" I get kind of worried. Valve carefully calls their Steam games "subscriptions" to remove your right of resale.
Anyone who owns a cat has had the groggy middle of the night lights-off walk to the kitchen to get a drink, only to step on their cat's tail and get that nice shot of a adrenaline pumping through their arteries. Maybe it strengthens their heart, or trains their reactions to not get so damned surprised by things that their heart could stop.
Then again if things like this happen often enough to have effect, maybe they just shouldn't have a cat:)
I'll add one more: no stupid Microsoft-ish riddles.
Although I have heard one or two that were programming problems in disguise, I would argue that even in those cases your riddles are worthless to determine their skill, and anyone would be well within his sanity to respond "well, I'd look it up online. Why waste time figuring it out when the answer is done for me?".
A great programmer will love to talk shop. Have one of your existing coders talk to him.
one technique that has been used in the past, is that porn websites will have their registration page just be a proxy for a registration page on a site they want to spam. people register and they get their captchas done for free.
You mean Linux adapted something from Windows instead of the other way around? What's next, a sane proactor i/o api?
Joking aside, this is cool. You can be mad at Vista for a number of reasons, but SuperFetch is not one of them - I have noticed a decent speed improvement because of it, and look forward to having something similar in Linux. Glad to see people aren't above taking the good ideas from Windows (or wherever Microsoft stole it from, if that's the case).
Granted pretty much nobody in high school will write quality code (even if they honestly think they do, like I once did), the chance to get paid experience and a mentor to help you improve is fantastic.
Slashdot Mirror
What I want to know is: how does it compare to the existing Open Source physics libraries, such as Bullet (which was made by an ex-Havok developer)?
Do you have any data to back that up? Or did some sarcasm just fly over my head.
Okay, so calling HyperStudio "programming" is a stretch, but it was definitely a gateway drug for it.
Playing Doom on my uncle's computer may have got me interested in computers, but using HyperStudio in elementary school was my first experience with programming and is probably what started me down that path.
I was hoping for something like ScRGB support. I've always wanted two things out of displays: higher DPI, and higher gamut. Does this deliver either?
Chris Chinnock, President of the research firm "Insight Media", is one of those who are skeptical about HP's claims. He says that while the 30-bit resolution will allow for better gradation between the color levels, the technology will not be able to increase the color gamut of a display.Guess not. Oh well.
Apparently the op I was talking to in #freenet wasn't a developer, so practicing security through obscurity isn't intentional.
Which is why I say it should be documented separately from the code. Even if it is constantly changing, these changes should be documented prior to implementation. It'd be much easier to review than looking at code - Java or C++.
Freenet is an important concept. On it you get complete freedom of speech: the ability to discuss and spread your ideas, with full anonymity and freedom from censorship. Of course, this means that you will probably come across things on it that will go against your beliefs. While nothing forces you to actually visit these freesites, you will have to come to terms that this might be cached on your computer even without you visiting them. But this is important to freedom of speech: if people where able to censor anything, the system just wouldn't work.
So why does Freenet fail? Lack of documentation. I don't mean ease of use in the interface - I mean for the protocols and network design. A system as important as Freenet -- one that people expect unfaltering anonymity and security from -- should be rigorously and meticulously documented.
But it's not. In fact, if you bring it up with the Freenet developers they will gladly tell you this is intentional -- that they use security through obscurity to guard against someone finding a way to break the system.
So -- do you trust your freedom with the competency of a handful of developers to make a good design? I don't. I want as many people looking at the system as possible. I want people to really bash on it, to try to break it. This gives me confidence, not worry, because problems will be solved sooner than later.
This would also open up the possibility of more than one client to access the network. If you have two separate clients that implement the same strict protocol and one of them messes up, it's likely to be caught far sooner than with just one. An immediate example of where this would have helped is with a bug that existed in 0.7's AES implementation for a very long time, where the data wasn't being encrypted properly.
The Freenet developers don't want multiple clients either -- again, they worry that one might break the network. This line of thought is incomprehensible to me, because as a developer I would want things that could break my network to be discovered as soon as possible so I could fix the design.
Sure, you could look at the source code. It is Open Source, after all. But what if you don't know Java? I don't particularly want to learn Java just so I can review Freenet's code. As a C++ developer I might be able to read and understand most of it, but I don't trust myself to review something so important without years of prior Java experience -- the chance that I'd miss something is just too great.
Garbage collection is surely a factor in them losing ground, but I think the main reason is simple: library support.
Java and .NET have huge well-designed frameworks behind them. You can get things done really fast. What does C have? A bunch of separate libraries all with different conventions. C++ is a little better with a more useful standard library and Boost, but it still doesn't have anywhere near the infrastructure Java and .NET have.
We've had a WiiMan around for a while.
7-zip compressing. Multimedia encoding. VC++ has an ever so awesome /MP switch. Windows threads getting previews for all your files in explorer. Heck, even Excel 2007 will thread your calculations behind the scenes.
Games may not make significant use of multi-core yet, but some other real-world things do. Quad core definitely makes an impact on my daily usage.
It sounds like this randomness is weighted to still pay more attention to hot zones. Couldn't people with access to the same data still find the least likely places for security to be dispatched? Moreover, if they already have access they can just wait for it to calculate a plan and then go around it.
The only problem with permissions is that the very people who should use them the most are typically equally ignorant about permissions as they are horrible in coding.
That is basically what GPUs do already. You'll notice modern ones have something like 128 "stream processors".
I've never used Java/J2EE before so I couldn't say.
.NET uses a per-operation callback to notify the app of I/O completion - it doesn't expose whatever internal mechanism it uses to achieve async, so the server choose the most efficient method (iocp, epoll, kqueue, how many threads, etc.). If you use SQL Server, DB queries can be done async too. If you do it right in many cases you can keep from ever blocking on I/O.
Perhaps they meant it as in "specifically designing to scale up", as opposed to a developer who just uses a thread to do some background processing.
One thing that's always saddened me is that most embarrassingly parallel problems like web and database development are still in the dark ages with this. They have so much potential, but almost nobody seems to care. To date the only frameworks I know of that allow fully asynchronous efficient processing of requests and database queries (so that you don't need to spawn a new thread/process for every request) is ASP.NET, WCF (SOAPish stuff in .NET), and some of .NET's database APIs. Does anyone know of any non-MS web technologies that allow this?
'nuff said.
Anybody remember Vista Ultimate edition? The one that promised Ultimate Extras - regular extras that you could download through Windows Update? They released 3 things through that: an small card game, DreamScene (sucks up CPU to animate your desktop background), and Bitlocker full drive encryption. That was all just a little after RTM - nothing since then.
When they came up with the idea I thought it might be interesting, but they've shown they can't follow through. If this is at all similar I'm sure it will fail. Microsoft won't be overthrown just from this, certainly not by 2010, but I'm sure it will pave more of the Disappointment Road that Vista started.
When they say "subscription" I get kind of worried. Valve carefully calls their Steam games "subscriptions" to remove your right of resale.
Is this an all-new chipset, or merely two of their old ones in SLI mode on one package?
That would require them admitting they did wrong. It's much easier to claim national security is at risk.
Anyone who owns a cat has had the groggy middle of the night lights-off walk to the kitchen to get a drink, only to step on their cat's tail and get that nice shot of a adrenaline pumping through their arteries. Maybe it strengthens their heart, or trains their reactions to not get so damned surprised by things that their heart could stop.
Then again if things like this happen often enough to have effect, maybe they just shouldn't have a cat :)
I'll add one more: no stupid Microsoft-ish riddles.
Although I have heard one or two that were programming problems in disguise, I would argue that even in those cases your riddles are worthless to determine their skill, and anyone would be well within his sanity to respond "well, I'd look it up online. Why waste time figuring it out when the answer is done for me?".
A great programmer will love to talk shop. Have one of your existing coders talk to him.
one technique that has been used in the past, is that porn websites will have their registration page just be a proxy for a registration page on a site they want to spam. people register and they get their captchas done for free.
I had no idea, I had never even heard of it :/ Does it come by default with any distros?
You mean Linux adapted something from Windows instead of the other way around? What's next, a sane proactor i/o api?
Joking aside, this is cool. You can be mad at Vista for a number of reasons, but SuperFetch is not one of them - I have noticed a decent speed improvement because of it, and look forward to having something similar in Linux. Glad to see people aren't above taking the good ideas from Windows (or wherever Microsoft stole it from, if that's the case).
Granted pretty much nobody in high school will write quality code (even if they honestly think they do, like I once did), the chance to get paid experience and a mentor to help you improve is fantastic.