You are of course correct, which means I have to look at another word (I'm rather fluent in English, but I'm not a native speaker). Um, "logical" or "mathematical" might get closer. Non-natural. Ehm.
It could just be that it is more of an ideological thing. Not everything everybody does is just for their own good. He might be outraged by all these copyright protections.
And it's an easy thing to earn a bit of money with as well. Just putting it on the web for free download might not be such a grand move either (unless you want to be listed everywhere and stop all uploads from your computer.)
And yes, I don't think the risk is that great unless you try to be big, or if you're easily picked up by automated searches.
I agree absolutely. Of course, an easy to program language can still make life easier. A well designed set of APIs can make life easier. And then you can top it off by making sure most use cases are covered. Don't forget that there is an awful lot of repetition out there. Of course, if it is all repetition then there is probably a product sitting somewhere on a shelf.
Personally I'm not so in favor of these kind of "natural" languages. Give me a language that is very abstract and well defined instead. Just make a very good IDE for it with drag and drop for designing stuff. And make sure it is easy to use and easy to configure and supply a very good API. But don't go into dynamic typing systems and such, because they twist the mind. Basically such systems force you to think abstractly, and most computer programming comes down to creating an abstract system from the solution you formed in your head.
Of course, many people will have trouble forming anything in their head, let alone solutions to computing problems (just trying to top your last remark here;).
If you're not a math student it is probably pretty hard to read in any form, not just PDF from PowerDeck. So if you're a code-head like me don't bother.
Of course they don't. They probably don't even know about it. The second that it becomes a problem though (infection, illegal content - basically anyone firing a complaint) they now have a club to hit you with.
My ISP (xs4all.nl) however has a very liberal TOS. Basically you can do with your link whatever you want (I don't think you may sell it to others, but that's about it). Companies use it for cheap web access for instance. And they've got all shell accounts, web disks, newsserver, configurable filters, SMTP functionality etc. etc. Many people only compare bandwith, but their reliability and extra services is why they (IMHO) are pretty cheap.
There don't seem to be too many of those kind of providers left.
Depends on the chip. If you include ISO 14443 processor cards then you can have crypto, combined with secure on chip storage of the key of course. You are giving away this chip, so you must make sure that the chip storage and on board crypto is sufficiently protected against attacks. E.g for passports you can have active authentication or chip authentication to verify that the chip is not cloned.
Yeah, right. And there never will be a time when the environment hurts enough, now won't there. Just because you want a power hungry expensive TV to educate your children. The children! can somebody/please/ think of the children?
I stand corrected:) Of course, if you work most of the time in a language that does not have any pointers (only refs, that can be null) you start to forget the obvious things that are part of C/C++ and the other non-managed languages.
It looks like Iran is trying to do exactly what this treaty was about, despite the lack of sharing from other countries.
Using nothing less than a top secret nuclear complex, build into a mountain. And that while they have one of the biggest oil and gas reserves of the world. Nobody believes the Iran government; the only reason the US is playing this down is because it is political suicide to complain to loud or attack. I'm considering myself a pacifist, but in the case of Iran, I'm not sure what I would do.
managed languages are meant as a convenience, not a crutch. Bad programmers shouldn't be encouraged to write their brain vomit in java any more than in C/C++.
The whole idea that security issues are only created by bad programmers is laughable. Anything that can put a lid on the number of (security) bugs is something that should be considered. Managed languages (no pointer arithmetic, bounds checking, exception handling etc.) are an important tool to accomplish that goal.
You are clearly looking down upon all those bad programmers with disdain. You know all those guys that think they can drive really well? Well, about half of them drive just above average.
The problem here anyway has nothing to do with language choice as much as an api that puts no restrictions on third party extensions. The question then has to be, how do you restrict what an extension can do when your whole platform is based on the idea that you can use extensions to completely rewrite the application's functionality.
Absolutely, there must be something that keeps those plugins in check. One way to do it is to have clear interface, an easy to read language and code reviews. It seems that this is the route that the FF devs have taken. It's a bit shaky and so you cannot trust each and every plugin.
However, it is much better than with a language where the plugins directly share the memory space (as in C/C++ and dynamically linked libs). Now *that* would really be unmanageable.
Better yet, create a special user or two, one for anonymous browsing and one for your security relevant tasks (banking etc). The first one should be automatically reset after use (I use an Ubuntu guest account for that), the other one should have an encrypted home folder. At least make sure your browser is up to date if you use farlukar's scheme.
Garbage collection does not protect against *any* security breaches. It may even introduce a few security issues (e.g. files not closed since the destructor is not called in time). The lack of pointer arithmetic and addition of bounds checking, on the other hand, certainly does protect against many security breaches. It also enables a better component based design where one component cannot change the behavior of other components. E.g. in Lobo it seems that there is an API that enables plugins. If this API is well designed it won't allow plugins to change too much outside their sandbox.
I'm very much in favor of that. I would even like to help building a Java based browser (e.g. with a OSGi based plug-in system). But the thing is that these extensions use all kinds of technologies, but not C/C++ (as far as I could see). So if the browser was managed code you would have the same issues. Managed code helps against many bugs, but not against all.
Just running webservers for the hell of it is dangerous practice, unless you make sure you don't try and do everything. Do those people really patch their servers on time? Do they rely on their fantastic 99.999 percent available ADSL or cable modem connections for connectivity? And then have people upload stuff to your server - ugh. Only to prevent my upstream of being filled up I would not allow such a thing. Having a separate virtual subdomain is an easy problem to solve regarding all the other issues they may encounter.
An alternate user would even be more preferable. You may stay with your well known browser but your files are more safe this way. Note that everything (maybe except IE) still has user privileges and browsers are hardly an unbreakable fortress. User/file separation is more easily managed. Me, I try to surf as "guest" when I'm trying out sites I find disturbing (most media containing sites are). Cookies, etc. are all destroyed after logging off.
But do these users really care about cookies? They probably just know what a cookie is, and if they find out a website doesn't work after removing the cookie, they'll probably be more frustrated than before doing the removal.
Because all these zealots blow their fuse once anything mentioning pregnancy is involved. This is (mainly) about the last stage of pregnancy though (the last ~14 weeks), so up to week 26. Even if there was anything interesting happening weeks before that stage it would not get into period that most women get an abortion. However, any sign of conciousness in early child development might fuel this debate.
"At what gestational ages are abortions performed: 52% of all abortions occur before the 9th week of pregnancy, 25% happen between the 9th & 10th week, 12% happen between the 11th and 12th week, 6% happen between the 13th & 15th week, 4% happen between the 16th & 20th week, and 1% of all abortions (16,450/yr.) happen after the 20th week of pregnancy."
And these stats are from a (US) pro-life site.
(I got interested enough to see if there was any merit discussing this regarding abortion, but after looking at these facts I decided for myself that this discussion is off-topic).
Slashdot Mirror
You are of course correct, which means I have to look at another word (I'm rather fluent in English, but I'm not a native speaker). Um, "logical" or "mathematical" might get closer. Non-natural. Ehm.
It could just be that it is more of an ideological thing. Not everything everybody does is just for their own good. He might be outraged by all these copyright protections.
And it's an easy thing to earn a bit of money with as well. Just putting it on the web for free download might not be such a grand move either (unless you want to be listed everywhere and stop all uploads from your computer.)
And yes, I don't think the risk is that great unless you try to be big, or if you're easily picked up by automated searches.
I agree absolutely. Of course, an easy to program language can still make life easier. A well designed set of APIs can make life easier. And then you can top it off by making sure most use cases are covered. Don't forget that there is an awful lot of repetition out there. Of course, if it is all repetition then there is probably a product sitting somewhere on a shelf.
Personally I'm not so in favor of these kind of "natural" languages. Give me a language that is very abstract and well defined instead. Just make a very good IDE for it with drag and drop for designing stuff. And make sure it is easy to use and easy to configure and supply a very good API. But don't go into dynamic typing systems and such, because they twist the mind. Basically such systems force you to think abstractly, and most computer programming comes down to creating an abstract system from the solution you formed in your head.
Of course, many people will have trouble forming anything in their head, let alone solutions to computing problems (just trying to top your last remark here ;).
If you're not a math student it is probably pretty hard to read in any form, not just PDF from PowerDeck. So if you're a code-head like me don't bother.
I hope you used your front end for that.
They are just waiting for the token holder to take control of the situation.
Actually, I heard that two champagne corks collided in mid aid and hit a technician in the eye.
Of course they don't. They probably don't even know about it. The second that it becomes a problem though (infection, illegal content - basically anyone firing a complaint) they now have a club to hit you with.
My ISP (xs4all.nl) however has a very liberal TOS. Basically you can do with your link whatever you want (I don't think you may sell it to others, but that's about it). Companies use it for cheap web access for instance. And they've got all shell accounts, web disks, newsserver, configurable filters, SMTP functionality etc. etc. Many people only compare bandwith, but their reliability and extra services is why they (IMHO) are pretty cheap.
There don't seem to be too many of those kind of providers left.
Replying on myself here, but the original article does not seem to include processor chip technology.
That and it should have read ISO 14443 processor chips of course, not ISO 14443 processor cards. It's Saturday morning over here - need cafeine.
Depends on the chip. If you include ISO 14443 processor cards then you can have crypto, combined with secure on chip storage of the key of course. You are giving away this chip, so you must make sure that the chip storage and on board crypto is sufficiently protected against attacks. E.g for passports you can have active authentication or chip authentication to verify that the chip is not cloned.
Yeah, right. And there never will be a time when the environment hurts enough, now won't there. Just because you want a power hungry expensive TV to educate your children. The children! can somebody /please/ think of the children?
I stand corrected :) Of course, if you work most of the time in a language that does not have any pointers (only refs, that can be null) you start to forget the obvious things that are part of C/C++ and the other non-managed languages.
I don't know you well enough to answer that question, I'm afraid.
It looks like Iran is trying to do exactly what this treaty was about, despite the lack of sharing from other countries.
Using nothing less than a top secret nuclear complex, build into a mountain. And that while they have one of the biggest oil and gas reserves of the world. Nobody believes the Iran government; the only reason the US is playing this down is because it is political suicide to complain to loud or attack. I'm considering myself a pacifist, but in the case of Iran, I'm not sure what I would do.
managed languages are meant as a convenience, not a crutch. Bad programmers shouldn't be encouraged to write their brain vomit in java any more than in C/C++.
The whole idea that security issues are only created by bad programmers is laughable. Anything that can put a lid on the number of (security) bugs is something that should be considered. Managed languages (no pointer arithmetic, bounds checking, exception handling etc.) are an important tool to accomplish that goal.
You are clearly looking down upon all those bad programmers with disdain. You know all those guys that think they can drive really well? Well, about half of them drive just above average.
The problem here anyway has nothing to do with language choice as much as an api that puts no restrictions on third party extensions. The question then has to be, how do you restrict what an extension can do when your whole platform is based on the idea that you can use extensions to completely rewrite the application's functionality.
Absolutely, there must be something that keeps those plugins in check. One way to do it is to have clear interface, an easy to read language and code reviews. It seems that this is the route that the FF devs have taken. It's a bit shaky and so you cannot trust each and every plugin.
However, it is much better than with a language where the plugins directly share the memory space (as in C/C++ and dynamically linked libs). Now *that* would really be unmanageable.
Better yet, create a special user or two, one for anonymous browsing and one for your security relevant tasks (banking etc). The first one should be automatically reset after use (I use an Ubuntu guest account for that), the other one should have an encrypted home folder. At least make sure your browser is up to date if you use farlukar's scheme.
Garbage collection does not protect against *any* security breaches. It may even introduce a few security issues (e.g. files not closed since the destructor is not called in time). The lack of pointer arithmetic and addition of bounds checking, on the other hand, certainly does protect against many security breaches. It also enables a better component based design where one component cannot change the behavior of other components. E.g. in Lobo it seems that there is an API that enables plugins. If this API is well designed it won't allow plugins to change too much outside their sandbox.
I'm very much in favor of that. I would even like to help building a Java based browser (e.g. with a OSGi based plug-in system). But the thing is that these extensions use all kinds of technologies, but not C/C++ (as far as I could see). So if the browser was managed code you would have the same issues. Managed code helps against many bugs, but not against all.
A quick Google search found this interesting article from August of this year.
80GB is small
Very small, it holds only about 2 to 10 minutes of information...
This a remarkably funny early post, so you might have spared yourself from doing that I suppose.
Just running webservers for the hell of it is dangerous practice, unless you make sure you don't try and do everything. Do those people really patch their servers on time? Do they rely on their fantastic 99.999 percent available ADSL or cable modem connections for connectivity? And then have people upload stuff to your server - ugh. Only to prevent my upstream of being filled up I would not allow such a thing. Having a separate virtual subdomain is an easy problem to solve regarding all the other issues they may encounter.
An alternate user would even be more preferable. You may stay with your well known browser but your files are more safe this way. Note that everything (maybe except IE) still has user privileges and browsers are hardly an unbreakable fortress. User/file separation is more easily managed. Me, I try to surf as "guest" when I'm trying out sites I find disturbing (most media containing sites are). Cookies, etc. are all destroyed after logging off.
But do these users really care about cookies? They probably just know what a cookie is, and if they find out a website doesn't work after removing the cookie, they'll probably be more frustrated than before doing the removal.
Because all these zealots blow their fuse once anything mentioning pregnancy is involved. This is (mainly) about the last stage of pregnancy though (the last ~14 weeks), so up to week 26. Even if there was anything interesting happening weeks before that stage it would not get into period that most women get an abortion. However, any sign of conciousness in early child development might fuel this debate.
"At what gestational ages are abortions performed:
52% of all abortions occur before the 9th week of pregnancy, 25% happen between the 9th & 10th week, 12% happen between the 11th and 12th week, 6% happen between the 13th & 15th week, 4% happen between the 16th & 20th week, and 1% of all abortions (16,450/yr.) happen after the 20th week of pregnancy."
And these stats are from a (US) pro-life site.
(I got interested enough to see if there was any merit discussing this regarding abortion, but after looking at these facts I decided for myself that this discussion is off-topic).