While some people here on slashdot don't want to try something new unless someone else has already done something big with it, it's great to see that there are some in "the community" who are still interested in pushing the bounds on what is currently done.
While I personally may not be looking to move to another platform, it's great to know that there are resources out there for new stuff.
Personally, I only want books on stuff that's already well documented. And none of these new super-duper languages that one can learn quickly. If it isn't written in assembly, it isn't worth using. Why would you use anything else? It will only slow things down. In my day......
Seriously though, it's great to see that people are still able to take ideas and run with them, even if there is not a foreseable "big use" for it. When PHP was first introduced, it was met with a "why bother?" attitude. As long as there was PERL, why anything new?
I'm happy to see a book that is not a "for dummies" or "for idiots" or "for l33t hax0rs" but rather is by a programmer for programmers.
A single book that covers the topic from soup to nuts is a great idea. Maybe fairly ambitious, but if it covers the topic well, then kudos to the author(s).
Sure, there are many, many options, if you are willing to ignore the rules.......
Everything is available for a price.
On the other hand, I might suggest searching for a solution that does not ignore the rules. Rules for communication systems are (for the most part) fairly sane. The avoid pesky things such as cross talk, interference, etc. But hey, this is Slash, who really cares about that kind of thing;)
Bad Name. Has anyone seen Matrix Revolutions? At this point, does "revolution" bring any positive image to those of us who spend that much time in front of a screen?
For me, the term "Revolution(s)" now conjures a root of that word... Revolt.... or more specifically... revolting.
Getting sued will likely have very little to do with the viability of legal action.
Any potential legal action will likely be more of an attempt to intimidate, or for the plaintif to flex their muscles. Given that recent rash of lawsuits against torrent sites, I'm going to assume that those who may sue will watch the site to find out what sort of traffic it will generate, what sort of usage the site will get. If the site is not getting any traffic anyhow, the odds of getting sued are pretty low.
Announcing the planned features of a product set is basically useless. By the time the product will hit the shelves (or vitual shelves), the product will have gone through enough changes that showing any features at this point is a waste of time.
Hey, guess what, I've got this new thing comming out, it does some cool stuff, you should buy it.
Microsoft does this... anyone ever applied a "service pack"? Only we kick and scream over it.
Of course, we expect that when Microsoft removes a "feature" for "security reasons" it really has to do with the fact that the feature was not adding anything to the bottom line, or buggy.
I view security somewhat as an analogy to homes.
If I live in my home, and I am the only person who lives in my home, I can have all of the doors keyed the same, and use the master key, and have the master key on me at all times. If my house is broken into, it is all my stuff. This is the same as running as root all the time.
Now, I may have things that I'd prefer not to get stolen, then I'd have a safe. Now, I wouldn't have a house safe that is key operated that uses the same key as my front door. I just wouldn't. I might store a spare house key in my safe so that I know how many house keys are out there, etc, but I would not have my safe using the same key as my front door. This would be similar to having my own computer system, but not running as root. Instead I would use a non-privileged user account for most of my day to day operations and only use "root" or "administrator" in the case where I specifically need those privileges.
Now, in a multi-person environment, things change. Let's use an apartment (or hotel, if you please) as the word picture this time. If I managed an apartment, I might have a master key for the entire building. My life would be a heck of a lot easier if all I ever carried was the master key. I could go into whatever apartment I wanted as I pleased. I would only ever have to worry about losing that one key. This is the same as running as root on a multi-user system. I have access to everything. Back to the apartment model. If the apartment manager is getting groceries one day, and someone steals his ONE key, the whole apartment is now wide open to the person who possesses the key. A smart apartment owner might instead have a safe where he stores that key. The only key he would carry would be the key to open his apartment, and that key would not open his safe. If his key were now stolen, there would be a lot less risk to the other people in the building. Similar in a multi-user computer situation.
As a user (or a tenant), I'd rather have an admin (or manager) who is security conscious enough to take basic precautions.
As an admin (or manager), I'd rather take some simple precautions as come cya.
For a one person system, root or not root.... not a large difference.... that being said, not following "good practices" is a bad practice.
Slashdot Mirror
Until a year later when you have a single 2U server hanging in a 42U cabinet....
Anyone wanna buy a 42U Dell Rack?
Shipping cost is murder though.
Thanks for posting the review.
While some people here on slashdot don't want to try something new unless someone else has already done something big with it, it's great to see that there are some in "the community" who are still interested in pushing the bounds on what is currently done.
While I personally may not be looking to move to another platform, it's great to know that there are resources out there for new stuff.
Personally, I only want books on stuff that's already well documented. And none of these new super-duper languages that one can learn quickly. If it isn't written in assembly, it isn't worth using. Why would you use anything else? It will only slow things down. In my day......
Seriously though, it's great to see that people are still able to take ideas and run with them, even if there is not a foreseable "big use" for it. When PHP was first introduced, it was met with a "why bother?" attitude. As long as there was PERL, why anything new?
I'm happy to see a book that is not a "for dummies" or "for idiots" or "for l33t hax0rs" but rather is by a programmer for programmers.
A single book that covers the topic from soup to nuts is a great idea. Maybe fairly ambitious, but if it covers the topic well, then kudos to the author(s).
Everything is available for a price.
On the other hand, I might suggest searching for a solution that does not ignore the rules. Rules for communication systems are (for the most part) fairly sane. The avoid pesky things such as cross talk, interference, etc. But hey, this is Slash, who really cares about that kind of thing ;)
For me, the term "Revolution(s)" now conjures a root of that word... Revolt .... or more specifically ... revolting.
Any potential legal action will likely be more of an attempt to intimidate, or for the plaintif to flex their muscles. Given that recent rash of lawsuits against torrent sites, I'm going to assume that those who may sue will watch the site to find out what sort of traffic it will generate, what sort of usage the site will get. If the site is not getting any traffic anyhow, the odds of getting sued are pretty low.
Hey, guess what, I've got this new thing comming out, it does some cool stuff, you should buy it.
Of course, we expect that when Microsoft removes a "feature" for "security reasons" it really has to do with the fact that the feature was not adding anything to the bottom line, or buggy.
In more news, Bill Gates still has too much money, George W. Bush is still president and Bill Clinton was not seen in a gay bar.
I view security somewhat as an analogy to homes. If I live in my home, and I am the only person who lives in my home, I can have all of the doors keyed the same, and use the master key, and have the master key on me at all times. If my house is broken into, it is all my stuff. This is the same as running as root all the time. Now, I may have things that I'd prefer not to get stolen, then I'd have a safe. Now, I wouldn't have a house safe that is key operated that uses the same key as my front door. I just wouldn't. I might store a spare house key in my safe so that I know how many house keys are out there, etc, but I would not have my safe using the same key as my front door. This would be similar to having my own computer system, but not running as root. Instead I would use a non-privileged user account for most of my day to day operations and only use "root" or "administrator" in the case where I specifically need those privileges. Now, in a multi-person environment, things change. Let's use an apartment (or hotel, if you please) as the word picture this time. If I managed an apartment, I might have a master key for the entire building. My life would be a heck of a lot easier if all I ever carried was the master key. I could go into whatever apartment I wanted as I pleased. I would only ever have to worry about losing that one key. This is the same as running as root on a multi-user system. I have access to everything. Back to the apartment model. If the apartment manager is getting groceries one day, and someone steals his ONE key, the whole apartment is now wide open to the person who possesses the key. A smart apartment owner might instead have a safe where he stores that key. The only key he would carry would be the key to open his apartment, and that key would not open his safe. If his key were now stolen, there would be a lot less risk to the other people in the building. Similar in a multi-user computer situation. As a user (or a tenant), I'd rather have an admin (or manager) who is security conscious enough to take basic precautions. As an admin (or manager), I'd rather take some simple precautions as come cya. For a one person system, root or not root.... not a large difference.... that being said, not following "good practices" is a bad practice.