Another good option is JQuery. I've used that a lot, and never had compatibility difficulties between IE/FF/Opera/Chrome except:
A couple Javascript string/array functions missing from IE or FF (I have a compat.js I use, which adds the three functions I have issue with to the string and array prototypes), IE cannot index strings (i.e. x="cat";alert(x[2]); is an error in IE, works in others), and IE barfs if there is a comma after the last element in a object definition (i.e. {a:"a",b:"b",c:"c",})
I'll non-AC second this one. Using Visual Studio 2010 Express, it's very easy to make something with this. Using Mono and LibGDIPlus, I've only had one issues getting apps to run in Linux or FreeBSD. That issue was - I didn't change the project settings to target the.NET 2.0API. Once I did that, everything worked fine.
If it can be done HTML+Javascript is also not a bad option - I use JQuery for that kind of thing.
And I've used Python + QT (mentioned by the GP), which works well, and is pretty easy, but not as easy as C#/VS2010.
Telomerase activation shouldn't give you cancer. First of all, your telomeres won't be a problem untill you are in the 700-800 year range (if I remember my undergrad genetics courses correctly). At least, outside of the white blood cell lineages, those will probably go for most people in the first 100 years - they could probably use some telomerase. OK, so lets say you would normally get cancer by the time you were 150, thankfully, your white blood cells stop functioning so well around age 90 and you die of pneumonia instead. Now, lets assume the other causes of aging are fixed, so, that's pretty much the standard.
Insert telomerase. You now live to 150, and die of cancer. Did the telomerase give you cancer? No, it just allowed you to live long enough for the factors that did give you cancer to take hold.
You do have cells in your body producing telomerase - the gamete producing lineage. You can trace telomerase back to the development of successful linear DNA from that lineage - without break. No cancer. Telomerase is a DNA stabilizing agent, not a mutagen.
Not really - mice, unlike humans, normally have telomerase functioning throughout their entire lifespans. Telomere shortening is not an issue for them.
Actually, if I remember my undergrad genetics correctly, unless you know people living to around 800 years old, it's not an issue for people either.
However, I'd rather keep the white pages, and ditch the yellow pages. I actually use the former, the latter is just annoying and makes it difficult to find what I want interspersed with all the crappy adds.
Then again, with Google and anywho, I've not opened either in years. They both end up simply going from the doorstep to the recycle box.
No, because traditionally a salt is kept with the passwords. Salts are useful against Rainbow Tables, yes, but they are not useful towards brute force attacks, WHICH IS WHAT THE DISCUSSION HERE IS ABOUT. you can just grab the salt and add it into the password, the time is increased by a small linear factor.
All of your suggestions only increase the brute-force cracking time by a linear factor.
They are useless. Adding another character or two to the minimum password length, requiring more distinct character or requiring more character classes will all have a significantly higher affect on brute force attacks, with much less effort, and less CPU time for legitimate password entries.
Agreed - the only thing brute force shows is the importance of good passwords.
Aren't most hashing algorithms linear in time based on the input? In that case, all such algorithms would only vary by a constant factor, not really a difference in terms of security worthiness anyway.
Correct me if I'm wrong, but isn't the main point of a hashing algorithm to make it unlikely that two different messages would have the same hash (in particular to make it difficult to coerce this effect and have the second message with a matching hash also be in some way intelligible)?
Aside from the other reply, in the 80s/90s when they shook their iron fist at clones.
No non-app store apps on iDevices, forcing the use of iTunes to use them effectively, etc. would be another set of examples.
In the latter set, you can get around them, if you are willing to void your warantee, but that shouldn't be necessary. Also, it seems that they were not too early with the Pods/Pads (mostly due to lack of reasonable competition when they were released, I suspect), but they may have been too early with the Phone.
True, but in China, that kind of stuff is the every day/every location rule that the public accepts, not the monthly/yearly by few locations that the public does not as readily accept as in places like you described.
Yes, there ARE other places that are as bad, but China is the poster child right now.
There are two places where someone can gain that power.
He who controls the servers. and He who controls the clients.
If one party controls a high portion one side, and no one party controls the opposing side, the opposing side has to adapt to the side under a monopoly. If one side is controlled by one party, and the opposing side is controlled by a conflicting party, then they either need to come to a compromise (where both win and the consumers, usually, lose) or one/both of them will be wrestled out by third parties who can work with the other side.
Basically, if the decline of the desktop/laptop comes into play and Apple gets the iGadgets (Phone, Pod, Pad, etc.), into a high level of dominance, or Apple continues it's popularity upswing too far, then Apple will have the client side under it's belt, and suddenly, it has a very strong control of the internet - If Apple prevents Flash players on it's clients for HTML5, Flash is gone, if Apple prevents HTML5 on it's client for ProprietaryAppleWebMarkupLanguage, HTML5 is gone, if Apple says AmazingAwesomeNewTech isn't allowed, AmazingAwesomeNewTech is gone, etc.
Mind you, I don't think it's remotely reasonable that Apple will get this kind of power, they have a habit of shaking their iron fists a little too soon. Still, surprises sometimes happen.
True, but a better generalization: They saw something there, better than where they came from.
This is probably the way Mars will be colonized. It will be done by a country like China, where those risks seem nice compare to being under the heel of the oppressive government.
Or that they are unaware that they already have one, or that they just are too trusting when someone says it's failed. Given that the users are demonstrating a lack of knowledge about reliability about AV software, the latter says more about the user than the installed AV.
That that Java is used in a larger scope really only suggests it's better marketed. Java *might* be available on a few more platforms, but I'm not sure about even that - I've gotten Mono running better on FreeBSD than Java, I know it works well on Linux too. Both work on Linux, both work on HPUX, and a few more platforms as well.
The exception I can think of is that there are more phones that will run Java than.NET.
I don't know about memory issues, my systems all have at least 1GB (XP, Linux), or 2GB (Win 7, FreeBSD) of memory, and both Visual Studios 2010 and Eclipse run well on all compatible platforms.
Or is open source just too tribal and fragmented to coordinate on something so big and cross-disciplinary?
I'm tempted to respond to this with "Hammer, mean head-of-nail", except that we have projects like Linux, FreeBSD, KDE, Gnome. Even though they are competing, they are big and seem to be quite cross-disciplinary. Likewise there's GCC, which could be considered the same (and lacking serious FOSS competition).
More likely, nobody has felt the need, given what is currently available.
Slashdot Mirror
You have a drag-and-drop GUI design tool - visual. A studio is a work room for a class of task - it is effectively an electronic studio.
Another good option is JQuery. I've used that a lot, and never had compatibility difficulties between IE/FF/Opera/Chrome except:
A couple Javascript string/array functions missing from IE or FF (I have a compat.js I use, which adds the three functions I have issue with to the string and array prototypes), IE cannot index strings (i.e. x="cat";alert(x[2]); is an error in IE, works in others), and IE barfs if there is a comma after the last element in a object definition (i.e. {a:"a",b:"b",c:"c",})
I'll non-AC second this one. Using Visual Studio 2010 Express, it's very easy to make something with this. Using Mono and LibGDIPlus, I've only had one issues getting apps to run in Linux or FreeBSD. That issue was - I didn't change the project settings to target the .NET 2.0API. Once I did that, everything worked fine.
If it can be done HTML+Javascript is also not a bad option - I use JQuery for that kind of thing.
And I've used Python + QT (mentioned by the GP), which works well, and is pretty easy, but not as easy as C#/VS2010.
Telomerase activation shouldn't give you cancer. First of all, your telomeres won't be a problem untill you are in the 700-800 year range (if I remember my undergrad genetics courses correctly). At least, outside of the white blood cell lineages, those will probably go for most people in the first 100 years - they could probably use some telomerase. OK, so lets say you would normally get cancer by the time you were 150, thankfully, your white blood cells stop functioning so well around age 90 and you die of pneumonia instead. Now, lets assume the other causes of aging are fixed, so, that's pretty much the standard.
Insert telomerase. You now live to 150, and die of cancer. Did the telomerase give you cancer? No, it just allowed you to live long enough for the factors that did give you cancer to take hold.
You do have cells in your body producing telomerase - the gamete producing lineage. You can trace telomerase back to the development of successful linear DNA from that lineage - without break. No cancer. Telomerase is a DNA stabilizing agent, not a mutagen.
Not really - mice, unlike humans, normally have telomerase functioning throughout their entire lifespans. Telomere shortening is not an issue for them.
Actually, if I remember my undergrad genetics correctly, unless you know people living to around 800 years old, it's not an issue for people either.
In TFS: it's available in most cases.
However, I'd rather keep the white pages, and ditch the yellow pages. I actually use the former, the latter is just annoying and makes it difficult to find what I want interspersed with all the crappy adds.
Then again, with Google and anywho, I've not opened either in years. They both end up simply going from the doorstep to the recycle box.
No, because traditionally a salt is kept with the passwords. Salts are useful against Rainbow Tables, yes, but they are not useful towards brute force attacks, WHICH IS WHAT THE DISCUSSION HERE IS ABOUT. you can just grab the salt and add it into the password, the time is increased by a small linear factor.
All of your suggestions only increase the brute-force cracking time by a linear factor.
They are useless. Adding another character or two to the minimum password length, requiring more distinct character or requiring more character classes will all have a significantly higher affect on brute force attacks, with much less effort, and less CPU time for legitimate password entries.
Agreed - the only thing brute force shows is the importance of good passwords.
Aren't most hashing algorithms linear in time based on the input? In that case, all such algorithms would only vary by a constant factor, not really a difference in terms of security worthiness anyway.
Correct me if I'm wrong, but isn't the main point of a hashing algorithm to make it unlikely that two different messages would have the same hash (in particular to make it difficult to coerce this effect and have the second message with a matching hash also be in some way intelligible)?
Aside from the other reply, in the 80s/90s when they shook their iron fist at clones.
No non-app store apps on iDevices, forcing the use of iTunes to use them effectively, etc. would be another set of examples.
In the latter set, you can get around them, if you are willing to void your warantee, but that shouldn't be necessary. Also, it seems that they were not too early with the Pods/Pads (mostly due to lack of reasonable competition when they were released, I suspect), but they may have been too early with the Phone.
No. The real value of pi is strawberry rhubarb. All other values are just cheap imitations.
Reading comprehension much? I never said they were the worst, I said they were the poster child.
And don't be an ASSumption TARD, I never said they were my enemy.
True, but in China, that kind of stuff is the every day/every location rule that the public accepts, not the monthly/yearly by few locations that the public does not as readily accept as in places like you described.
Yes, there ARE other places that are as bad, but China is the poster child right now.
There are two places where someone can gain that power.
He who controls the servers.
and
He who controls the clients.
If one party controls a high portion one side, and no one party controls the opposing side, the opposing side has to adapt to the side under a monopoly. If one side is controlled by one party, and the opposing side is controlled by a conflicting party, then they either need to come to a compromise (where both win and the consumers, usually, lose) or one/both of them will be wrestled out by third parties who can work with the other side.
Basically, if the decline of the desktop/laptop comes into play and Apple gets the iGadgets (Phone, Pod, Pad, etc.), into a high level of dominance, or Apple continues it's popularity upswing too far, then Apple will have the client side under it's belt, and suddenly, it has a very strong control of the internet - If Apple prevents Flash players on it's clients for HTML5, Flash is gone, if Apple prevents HTML5 on it's client for ProprietaryAppleWebMarkupLanguage, HTML5 is gone, if Apple says AmazingAwesomeNewTech isn't allowed, AmazingAwesomeNewTech is gone, etc.
Mind you, I don't think it's remotely reasonable that Apple will get this kind of power, they have a habit of shaking their iron fists a little too soon. Still, surprises sometimes happen.
True, but a better generalization: They saw something there, better than where they came from.
This is probably the way Mars will be colonized. It will be done by a country like China, where those risks seem nice compare to being under the heel of the oppressive government.
There was a huge news rush several years back. Slashdot is just trying to catch up.
Or that they are unaware that they already have one, or that they just are too trusting when someone says it's failed. Given that the users are demonstrating a lack of knowledge about reliability about AV software, the latter says more about the user than the installed AV.
maybe, but how many companies have "Cowboy Neil" in their sales figures?
I know. That picture makes me want to go to the grocery store and buy some of the pre-made pilsbury or tollhouse cookies...
Damn you slashdot! I'm trying to NOT look like the steriotypical obese geek, thank you very much! mm.... coookies...
Did you have LibGDIPlus running? I've not had a problem with any .NET app written in 2.0.
That that Java is used in a larger scope really only suggests it's better marketed. Java *might* be available on a few more platforms, but I'm not sure about even that - I've gotten Mono running better on FreeBSD than Java, I know it works well on Linux too. Both work on Linux, both work on HPUX, and a few more platforms as well.
The exception I can think of is that there are more phones that will run Java than .NET.
What exactly would Java be better at than .NET?
not really.
Go to the project properties, one of the menu items therein has a target .NET runtime, set that to 2.0. Click [ctrl]+[s], and you are good to go.
I've had no trouble with threaded debugging in Visual Studio 2010 / C#
I don't know about memory issues, my systems all have at least 1GB (XP, Linux), or 2GB (Win 7, FreeBSD) of memory, and both Visual Studios 2010 and Eclipse run well on all compatible platforms.
I'm tempted to respond to this with "Hammer, mean head-of-nail", except that we have projects like Linux, FreeBSD, KDE, Gnome. Even though they are competing, they are big and seem to be quite cross-disciplinary. Likewise there's GCC, which could be considered the same (and lacking serious FOSS competition).
More likely, nobody has felt the need, given what is currently available.