Comment Re:Enough rope (Score 3, Informative) 387
PySide is quite powerful as well, and can be used for both desktop and mobile development.
PySide is quite powerful as well, and can be used for both desktop and mobile development.
While I really like C, I think it doesn't remotely qualify as "doesn't have to be compiled for a particular processor".
If I decided to do this, I would need to operate my LAN like every node was bare on the internet.
You should be doing that anyway if you actually care about security.
I've got fileservers with guest access (for, you know... houseguests), web services, my invoicing system, and a whole slew of other personal services.
Sounds like if any single of your devices (or your guest's devices) are compromised, your entire network is compromised. The problem already exists, opening up your network would only expose it further.
[...]
Now, what stops a company from taking your code and making massive changes to it and shipping that code for mad moneys? What forces them to give back their changes that might make that code better?
Nothing. Giving stuff away for free means you don't expect anything in return. Not all forms of FLOSS are GPL-like.
What did you and the community gain by contributing to that company's revenue? What if I just took your code and put it on a CD and started selling it with no credit to you and no link or reference to the source code? Wouldn't that rub you the wrong way? Just a little?
Some people just don't care about all that. All they care about is creating a good software for people to use. Period.
Well, what if that company then claimed that your code was an unlicensed version of their code and moved to have it remove?
The same can ocurr if the code had a BSD banner on top of it - a license doesn't keep companies from making up lies.
But who would buy GPL software, when it's generally free? I don't think there's any interest in forking GPL software and reselling in Antigua, and if any big corporation (ie: MS) decides to move there and do something like that, it would hurt their image way too much.
You can point finger wherever you want, but if your product failed to sell it's still 100% your fault. (this may no apply to smaller businesses, indie devs, etc, but heck, it's MS we're talking about).
Arch is bleeding edge, and way more than Fedora. I've never seen broken installers or any important packages broken. Most issues in general, are upstream packages, but nothing as important as the installer.
Really? What kind of wild changes have there been in recent linux kernels? In particular, what kind of API breakages have there been?
I've used Arch for years, which uses rolling release as well.
I've noticed that rolling release doesn't tend to carry the breakage that dist-upgrade carries, because changes are gradual to the system, one at a time, and don't need to be tested in some arbitrarily defined time, which means they usually get tested more thoroughly too.
It's cheap mp3 players that dominated that market. iPods sold so much because they were the latest fasion, but their sales are nowhere close to cheap mp3s. Zune attempted to be a second iPod, and there's no place for two iPods.
It's not just open source: the truth is, windows doesn't have a bug tracker, so you can't see really old bugs.
Windows 7 won't allow users to open/delete/move/do-anything-else on files with some particular characters in their filename. This bug has existed since DOS, so it's actually around two decades old.
Reboots aren't as necessary in Linux.
Sure, if you want to run the same kernel for the rest of your life, that's true.
For some definitions of "hack".
Really, if the site was still up with the security hole, it's not the student's fault: he's not the one who was giving out information.
He didn't run any scanning software, if you'd at least read the summary you'd realize he found an application-level hole while developing a client application.
I use keepassx for infrecuent sites. But it's not so useful for other thing: sites I visit every day from different PCs, logining into the OS, hard drive decryption, etc. You can't carry keepassx around, and that's a problem.
Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.