Open source Nuclear Reactor
Open Source assault Rifle (No it doesn't have software, but if you open the spec/blueprints....)
Open Source Assault Vehicle
Open source Wiretapping software for phones
Open source spamming/junk mail circumvention software (Nobody LIKES spam)
Basically6 anything that might pose a danger to society by the nature of the project itself. Anything the general public should not have based off of other laws, Should, not be allowed to be made. Most of these devices have serious regulatory concerns outside their open sourced-ness, and thus should be regulated. However, depending on the nature of the unmanned aircraft, I think it should be safe to leave an open spec. Just as long as it's not designed to takeover manned aircraft (disable them, whatever), or have them packed with explosives to drive them into buildings..... if the bad part is in the SPEC, then the project should be axed out of existence by EXISTING regulations...
Of course regular autonomous planes for aerial photos are OK. Provided distance laws are upkept (must fly above XXXX ft) are kept when flying - Also helps keep things private. These planes obviously shouldn't be for spying through my bedroom window.:)
You can only go as fast as the site you connect to.... Which speed test are you using? many speed tests get overloaded after time, and you can't get your maximum speed....Where do you live? Where is the server located? How many hops to the server? I work for a Major High speed ISP (technical Support), and our customers recieve pretty close to the 5 MBit barrier that they are allowed when they go to speed test sites relatively close to us (7 hops to our preferred external speedtest). However if they go to a speed test on the other side of the continent, they get around 1MBit. This is normal, and I have educated many users on this.
Put it in Highway terms. The car you bought and licensed in Germany may be able to reach 200 MPH on the Autobhan, but if you're caught in traffic, visiting a busy town or if the speed limit in England is slower than in Germany, you're stuck going slower. Nothing your ISP can do will speed you up to a slower external site.
please provide more info (ie: your state, and the site of your speed test) when making claims that your speed test gives you less-than-desirable speeds. and remember - it's a Theoretical maximum - you'll never hit it. It should come close though.
Yes, C++ has faults which make it EASIER to cause a crash, but it is the coder who has to ensure that it doesn't. making sure your app has as simple a design as possible, always check for ANY AND ALL invalid data (Create objects with their own validation functions), and ensure both your design and code are well documented.
Tricky bits of code, involving memory management, should be avoided as this is the cause for most errors in C++. If possible, limit all memory management code to constructors/destructors and VERY specific resize code. Document inheritances, and avoid tricky multiple inheritance situations.
Furthermore, you should ALWAYS have a development cycle that contains a long testing phase, with the ability to test your extremes, as well as testing as close to real world situations as you can - Real users will crash your software much faster than any programmer with knowledge of the internals.
Always use strong error handling, and code using try/catch blocks for exception handling - if you're going to have an error, handle it gracefully.
Once you have a solid program base from this process, you can start worrying about crash resolution strategies that may increase the complexity of your code - overseer processes and the like. When in doubt, go back to basics and build simpler code. If you don't confuse the coder, it's harder to confuse a computer to cause a crash.
Consolidate all your widgets to one monitor and use the other for your work. this lets you focus on work with one screen, while having your widget-fix on the other screen. Keep your XMMS (Or other MP3 Jukebox program) over there as well. One clutter screen and one clean screen is the best way to work for me.
Use that second display for copy/pasting from one application to another, without having to scroll around a tiny window. Likewise, you could also have one screen for coding and debug output and the other for runtime programming. Of course, I haven't done this in Linux, but it is something i've done in MS Visual Studio... The concept should work there...
Punishing the average user for their ignorance of wireless security is even more stupid than using an insecure wireless connection for shopping online. Most people for whom I've set up wireless networks don't understand what WPA or WEP is, or why they would want to stop people from using their internet access.
Who is this targeted at anyways? I agree I would like BUSINESSES that deal with MY money to have strict security applied to their network (And I'm not against government regulations on that one...), but to require ALL computer users (Home users included) to secure their wireless, is asking too much...
Slashdot Mirror
Open source Nuclear Reactor Open Source assault Rifle (No it doesn't have software, but if you open the spec/blueprints....) Open Source Assault Vehicle Open source Wiretapping software for phones Open source spamming/junk mail circumvention software (Nobody LIKES spam) Basically6 anything that might pose a danger to society by the nature of the project itself. Anything the general public should not have based off of other laws, Should, not be allowed to be made. Most of these devices have serious regulatory concerns outside their open sourced-ness, and thus should be regulated. However, depending on the nature of the unmanned aircraft, I think it should be safe to leave an open spec. Just as long as it's not designed to takeover manned aircraft (disable them, whatever), or have them packed with explosives to drive them into buildings..... if the bad part is in the SPEC, then the project should be axed out of existence by EXISTING regulations... Of course regular autonomous planes for aerial photos are OK. Provided distance laws are upkept (must fly above XXXX ft) are kept when flying - Also helps keep things private. These planes obviously shouldn't be for spying through my bedroom window. :)
You can only go as fast as the site you connect to.... Which speed test are you using? many speed tests get overloaded after time, and you can't get your maximum speed....Where do you live? Where is the server located? How many hops to the server? I work for a Major High speed ISP (technical Support), and our customers recieve pretty close to the 5 MBit barrier that they are allowed when they go to speed test sites relatively close to us (7 hops to our preferred external speedtest). However if they go to a speed test on the other side of the continent, they get around 1MBit. This is normal, and I have educated many users on this.
Put it in Highway terms. The car you bought and licensed in Germany may be able to reach 200 MPH on the Autobhan, but if you're caught in traffic, visiting a busy town or if the speed limit in England is slower than in Germany, you're stuck going slower. Nothing your ISP can do will speed you up to a slower external site.
please provide more info (ie: your state, and the site of your speed test) when making claims that your speed test gives you less-than-desirable speeds. and remember - it's a Theoretical maximum - you'll never hit it. It should come close though.
Yes, C++ has faults which make it EASIER to cause a crash, but it is the coder who has to ensure that it doesn't. making sure your app has as simple a design as possible, always check for ANY AND ALL invalid data (Create objects with their own validation functions), and ensure both your design and code are well documented. Tricky bits of code, involving memory management, should be avoided as this is the cause for most errors in C++. If possible, limit all memory management code to constructors/destructors and VERY specific resize code. Document inheritances, and avoid tricky multiple inheritance situations. Furthermore, you should ALWAYS have a development cycle that contains a long testing phase, with the ability to test your extremes, as well as testing as close to real world situations as you can - Real users will crash your software much faster than any programmer with knowledge of the internals. Always use strong error handling, and code using try/catch blocks for exception handling - if you're going to have an error, handle it gracefully. Once you have a solid program base from this process, you can start worrying about crash resolution strategies that may increase the complexity of your code - overseer processes and the like. When in doubt, go back to basics and build simpler code. If you don't confuse the coder, it's harder to confuse a computer to cause a crash.
Consolidate all your widgets to one monitor and use the other for your work. this lets you focus on work with one screen, while having your widget-fix on the other screen. Keep your XMMS (Or other MP3 Jukebox program) over there as well. One clutter screen and one clean screen is the best way to work for me.
Use that second display for copy/pasting from one application to another, without having to scroll around a tiny window. Likewise, you could also have one screen for coding and debug output and the other for runtime programming. Of course, I haven't done this in Linux, but it is something i've done in MS Visual Studio... The concept should work there...
Punishing the average user for their ignorance of wireless security is even more stupid than using an insecure wireless connection for shopping online. Most people for whom I've set up wireless networks don't understand what WPA or WEP is, or why they would want to stop people from using their internet access. Who is this targeted at anyways? I agree I would like BUSINESSES that deal with MY money to have strict security applied to their network (And I'm not against government regulations on that one...), but to require ALL computer users (Home users included) to secure their wireless, is asking too much...