This seems like a common issue in Linux, particularly for people using it as a desktop environment. What would be the preferred method to limit access? Dedicated user/group with filesystem perms, cgroups, ACLs, chrooting, security modules (AppArmor/SELinux)?
I think you're exaggerating the severity of shortcomings Steam currently has. While you may have trouble finding specific games and disagree with their approach to bubbling suggestions to the top, I'm still overwhelmingly satisfied with what they do provide.
-On-demand game
-Support for a plethora of indie titles
-Emphasis on multiplayer/friends and communities
-Novel monetization approaches (DOTA)
-Strong push for cross-platform support with Valve heading the charge
-Investment in bridging the PC/console divide
I understand where you're coming from but while you may have a strong aversion to the direction they're going with some of the console-related adjustments, I really don't see the extent of detractions from their core product you vehemently push.
Settle down captain cynicism. Maybe we did have an era where games rested mostly on their reputation and that of the studio that produced them, but I think we've far from lost that. Sure the market may be flooded with the F2Ps for the masses but I think that's expected to come along with the the accessibility of digital distribution.
I stepped away from PC gaming for about years, and came back feeling just as at home as I ever have. The difference nowadays is that those small indie games have earned an opportunity to become the behemoths that their predecessors were. The games I get drawn into now still include the platformers but now those platformers have to stand among the smaller titles that have earned their keep solely on enjoyment and playability. I still play games like Half-Life and Civilization, they just happened to be mixed into Minecraft, FTL, and Plants vs. Zombies - games that may have never seen the light of day if conceived 10 years ago.
It's good to see stuff like this hit the front page. It helps space out the onslaught of disappointing stories slashdot breaks regarding the incompetence/malice of leadership in this country.
Seeing a cruising ice comet hit the sun with a CME following is pretty damn cool too.
I don't know why you've made a blanketed assumption about the OSS community. While I realize that maintaining the linux kernel may be the pinnacle representation of the OSS community, it's far from your only option. I have some colleagues that are active maintainer's of some python libraries and the boorish nature of the linux management style doesn't seem to be a factor among their contributors.
If you had a project as pervasive as the linux kernel which you have fostered for a long time and has the expectations that it does, you'd probably hold it pretty close to the chest as well. He has taken on the responsibility of seeing it through, primarily putting him in the driver's seat. If his candor doesn't suit you, the nature of the OSS community is that you have other options. It's his decision if his degree of 'unprofessionalism' happens to be running off young talent.
I've heard that they essentially operate as a bank, but technically aren't classified as one. This means they can get away with shady banking practices without being held to the standards that legitimate banks operate under.
Where is all the tech stuff? I want to know what systems were swapped out, what was used in place or what was swapped, what the steps were (did they set up unit tests first followed by architecture changes and scalability testing), what new coding practices they employed etcetera.
I'll sum up this horn-tootin session: "LinkedIn had to change to grow, and they did".
Maybe we should make it a habit of giving the owner some warning before slashdotting them. I know that if I ever get any concept development project up and running, I'm pretty excited to show my friends and tend to make it accessible before it's optimized enough to handle that king of onslaught.
Slashdot Mirror
http://askubuntu.com/a/376386
This seems like a common issue in Linux, particularly for people using it as a desktop environment. What would be the preferred method to limit access? Dedicated user/group with filesystem perms, cgroups, ACLs, chrooting, security modules (AppArmor/SELinux)?
I think you're exaggerating the severity of shortcomings Steam currently has. While you may have trouble finding specific games and disagree with their approach to bubbling suggestions to the top, I'm still overwhelmingly satisfied with what they do provide. -On-demand game -Support for a plethora of indie titles -Emphasis on multiplayer/friends and communities -Novel monetization approaches (DOTA) -Strong push for cross-platform support with Valve heading the charge -Investment in bridging the PC/console divide I understand where you're coming from but while you may have a strong aversion to the direction they're going with some of the console-related adjustments, I really don't see the extent of detractions from their core product you vehemently push.
Leroy jenkins got his whole team annihilated. #neverforget
Nailed it
The pragmatic programmer and code complete
http://codegolf.stackexchange....
So, would you say they have faith in it being the correct model? ;)
/endtroll
Settle down captain cynicism. Maybe we did have an era where games rested mostly on their reputation and that of the studio that produced them, but I think we've far from lost that. Sure the market may be flooded with the F2Ps for the masses but I think that's expected to come along with the the accessibility of digital distribution. I stepped away from PC gaming for about years, and came back feeling just as at home as I ever have. The difference nowadays is that those small indie games have earned an opportunity to become the behemoths that their predecessors were. The games I get drawn into now still include the platformers but now those platformers have to stand among the smaller titles that have earned their keep solely on enjoyment and playability. I still play games like Half-Life and Civilization, they just happened to be mixed into Minecraft, FTL, and Plants vs. Zombies - games that may have never seen the light of day if conceived 10 years ago.
I tend to apply this mentality to all 'breaking news'
If he gets us all thoroughly stoned, we may forget what we were up in arms about. That conniving bastard!
It's good to see stuff like this hit the front page. It helps space out the onslaught of disappointing stories slashdot breaks regarding the incompetence/malice of leadership in this country. Seeing a cruising ice comet hit the sun with a CME following is pretty damn cool too.
They kind of did. http://www.itworld.com/software/358908/install-netflix-ubuntu-1304 At least it works pretty well for me over here on mint.
But...but...we just want them to play with us.
This actually works pretty well for me: http://www.iheartubuntu.com/2012/11/ppa-for-netflix-desktop-app.html
At least 3 times
I don't know why you've made a blanketed assumption about the OSS community. While I realize that maintaining the linux kernel may be the pinnacle representation of the OSS community, it's far from your only option. I have some colleagues that are active maintainer's of some python libraries and the boorish nature of the linux management style doesn't seem to be a factor among their contributors. If you had a project as pervasive as the linux kernel which you have fostered for a long time and has the expectations that it does, you'd probably hold it pretty close to the chest as well. He has taken on the responsibility of seeing it through, primarily putting him in the driver's seat. If his candor doesn't suit you, the nature of the OSS community is that you have other options. It's his decision if his degree of 'unprofessionalism' happens to be running off young talent.
http://www.youtube.com/watch?v=Gv7Y0W0xmYQ
I've heard that they essentially operate as a bank, but technically aren't classified as one. This means they can get away with shady banking practices without being held to the standards that legitimate banks operate under.
I'd like to see what a fine-toothed comb turns up after running through the legalities of PayPal's business practices.
Why are there wheels? So they could call it a bike? Maybe you just ride it around like a regular bike for a while before REMEMBERING YOU COULD FLY.
Where is all the tech stuff? I want to know what systems were swapped out, what was used in place or what was swapped, what the steps were (did they set up unit tests first followed by architecture changes and scalability testing), what new coding practices they employed etcetera. I'll sum up this horn-tootin session: "LinkedIn had to change to grow, and they did".
kind*, I'm not sure whether or not slashdot holds the title of 'king of onslaught'.
Maybe we should make it a habit of giving the owner some warning before slashdotting them. I know that if I ever get any concept development project up and running, I'm pretty excited to show my friends and tend to make it accessible before it's optimized enough to handle that king of onslaught.
Was able to get a month's worth of FUD out of the way with that single quote.