Yes, let's start arresting people and putting them in jail, because they might do something criminal in the future. Arrest all teenagers that get too close to any stores, because they might just start looting the place, give speeding tickets to anyone driving a car, because they might just break the speeding limit, etc. etc.
Wow, that law is literally saying: "No restrictions shall be placed on the exercise of these rights other than all the restrictions placed on the exercise of these rights"
Did you do this as a part of your job, or was it something that you developed in your own free time?
If you did this as a part of your job, then they own the code, NOT YOU! Even if you developed it in your own free time there are still some situations where your employer can claim ownership of your work.
If you are certain that they have no right to claim ownership of your work then I suggest you get some legal help.
The best thing to do, if you want to make sure that your employer can't just take your code and claim it as their own, is to never actually bring your code in to work. Work on it at home on your own computer. Don't put it on any computer or server owned by your employer. You might just as well not even tell them about it.
Where I'm from intersections with traffic lights are considered extremely dangerous and lead to a lot of accidents, since it is so easy for people to run a red light at high speed. Roundabouts are everywhere here because they are considered much safer, they force drivers to slow down a bit and traffic flows much more naturally through them. I don't think I've ever heard of a fatal accident at a roundabout here. A lot of places that have implemented roundabouts have learned a completely different lesson than New Jersey.
You can severely limit what an application can do on windows by running it under a user with very limited priviledges, configuring your firewall properly etc. Not exactly easy for the average user tho.
Funny that Microsoft is way ahead of php and mysql on this area..Net allows you to use parameters in reqular sql queries. Just add parameters to the command object as your are building your query. You never have an excuse not to use parameterized queries.
It's only one of the oldest, most well known and easiest to defend against security issues that exist and pretty much all frameworks today have an easy and built in way to prevent sql injection. Still it's all to common to see people doing something like:
string query = "SELECT * FROM table WHERE Id = " + id;
1.8 gigahertz dual processors, a Blu-ray player and built-in ethernet and HDMI ports and a C64 emulator is not impressive, I can get better than that with any cheap modern day PC running vice. More important, are they going to feature to original blue OS or just a look-alike? Will it use SID chips for sound, so we can experience the legendary C64 sound once again? Will it have a VIC-II graphics chip? How about support for all of the old accessories (tape-drives, cartridges, joysticks etc.) ?
So far this just looks like a low-end modern day PC with a retro look.
Slashdot Mirror
Yes, let's start arresting people and putting them in jail, because they might do something criminal in the future. Arrest all teenagers that get too close to any stores, because they might just start looting the place, give speeding tickets to anyone driving a car, because they might just break the speeding limit, etc. etc.
Wow, that law is literally saying: "No restrictions shall be placed on the exercise of these rights other than all the restrictions placed on the exercise of these rights"
Did you do this as a part of your job, or was it something that you developed in your own free time? If you did this as a part of your job, then they own the code, NOT YOU! Even if you developed it in your own free time there are still some situations where your employer can claim ownership of your work. If you are certain that they have no right to claim ownership of your work then I suggest you get some legal help. The best thing to do, if you want to make sure that your employer can't just take your code and claim it as their own, is to never actually bring your code in to work. Work on it at home on your own computer. Don't put it on any computer or server owned by your employer. You might just as well not even tell them about it.
Where I'm from intersections with traffic lights are considered extremely dangerous and lead to a lot of accidents, since it is so easy for people to run a red light at high speed. Roundabouts are everywhere here because they are considered much safer, they force drivers to slow down a bit and traffic flows much more naturally through them. I don't think I've ever heard of a fatal accident at a roundabout here. A lot of places that have implemented roundabouts have learned a completely different lesson than New Jersey.
You can severely limit what an application can do on windows by running it under a user with very limited priviledges, configuring your firewall properly etc. Not exactly easy for the average user tho.
Android sort of does this. Applications have to request the permissions they need at install time and the user has to grant them.
Then use mono or some other framework that allows you to build sql queries in a sane way. The only good thing about php and mysql is that it is free.
Funny that Microsoft is way ahead of php and mysql on this area. .Net allows you to use parameters in reqular sql queries. Just add parameters to the command object as your are building your query. You never have an excuse not to use parameterized queries.
It's only one of the oldest, most well known and easiest to defend against security issues that exist and pretty much all frameworks today have an easy and built in way to prevent sql injection. Still it's all to common to see people doing something like: string query = "SELECT * FROM table WHERE Id = " + id;
1.8 gigahertz dual processors, a Blu-ray player and built-in ethernet and HDMI ports and a C64 emulator is not impressive, I can get better than that with any cheap modern day PC running vice. More important, are they going to feature to original blue OS or just a look-alike? Will it use SID chips for sound, so we can experience the legendary C64 sound once again? Will it have a VIC-II graphics chip? How about support for all of the old accessories (tape-drives, cartridges, joysticks etc.) ? So far this just looks like a low-end modern day PC with a retro look.