That AC isn't making more shit up... you, Mr. AC, are just too lazy to Google. A quick Google of "angry birds android ad revenue" pulled up a PAGES full of results similar to this one:
Except I can keep my KeePass master password completely separate from my DropBox password. Yes, LastPass is forcing you to change your master password, but until you do that, you are exposed. If someone gets my DropBox password then all they have access to is my encrypted KeePass file.
So long as you memorize your KeePass and DropBox passwords, and make sure they are completely unrelated to each other, you are doing better (imo) than LastPass. Additionally you can add the step (as mentioned above) of having a local auth file for KeePass (meaning you need to have a copy of that file AND know the password).
Specific to something like Flip... part of the reason Cisco killed it instead of selling it was to retain the patents and intellectual property for on-going and future products. That includes FlipShare (in fact, FlipShare is probably one of the main IPs they want to salvage in some form). Open Sourcing under those circumstances makes no sense.
I've been part of a company that did OS their products after they folded (Cobalt... Sun acquired us then when they shut us down they allowed it to go OS). It works great in some situations. Cobalt lives on in many service providers, allowing existing and new Cobalt UI users to continue to do so, while not becoming any form of competition to Sun.
It can work in specific situations, but not in most.
I went to log in to PSN today to see which security questions I had picked and answered so that I could blacklist them from other sites and... I can't get in to check it. Not helpful at all. Fix the holes and at least put it back up in a read-only mode. It has been years since I signed up for OR used PSN... so I have utterly no clue what information I had there.
And yet the people just getting into Drupal, which are the people most likely to want a book on the matter, are going to go with Drupal 7 for the most part. This is sort of my predicament... I did some stuff in Drupal 5 and am getting back into Drupal dev with 7. Had this been a book on 7 I would have jumped at it. But... its not.
And yeah, agreed to the obligatory, "but those 2 women got 'uploaded' and not killed" from the most recent "death arc"... except the very next episode they were effectively killed. They could come back in the future... except the series itself is now killed off... and almost certainly won't be resurrected.
This is something SGU did right. Characters killed other characters and those dead characters were dead. Death directly impacted the morale and capability of the remaining crew. When a crew member thought their dead child might still be alive... they weren't. When the obligatory "all these people died but now they are back!" episode happened, the dead people were dead again by the end of it.
Firefly did this same thing years earlier and in the movie. I'm sure others have done it well, but they are few and very far between.
Sadly, this is likely part of why the mainstream population couldn't bend their minds around either show for very long.
You mean... they might want you to purchase equipment to handle an entirely new function that wasn't part of the product you originally purchased, rather than spending significant effort and resources in order to give you this new functionality free? That's horrible.
Cisco and a number of other companies have directly given both specs and code to the world to aid in the adoption of IPv6. I think room for them to make money in a capitalist society is acceptable. It isn't the same as, say, buying a piece of equipment that promised an upgrade that never provided it (I'm staring at my cell phone right now). It isn't like they are going to shut down your perfectly working IPv4 home router once IPv6 products come out (I'm now staring at my OLDER cell phone). It isn't even like they lock your router from the ability to do 3rd party firmware updates (staring at my phone, my set top box, my PS3, my almost-everything-electronic).
In fact, they make it pretty darned easy for you to upgrade to a 3rd party firmware. And there are free 3rd party firmwares out there today that provide full IPv6 stacks (along with almost anything else).
"If you shrug and reboot the box after looking around for a few minutes, you may have missed the fact that a junior admin inadvertently deleted/boot and some portions of/etc and/usr/lib64 due to a runaway script they were writing. That's what was causing the segfaults and the wonky behavior. But since you rebooted the server without digging into the problem, you've made it much worse, and you'll soon boot a rescue image -- with all kinds of ponderous work awaiting you -- while a production server is down."
That argument is somehow pro-Unix?
I mean, yeah, a Windows person can screw with boot files, too. However if a Windows person were to read that paragraph it certainly wouldn't do a thing to encourage them on the solidity of *nix. It basically translates to "if you're having a problem, don't restart, you may not be able to boot again because your other admins may be incapable of writing proper scripts since every *nix system is different on its boot structure... so ALWAYS do a full check of the existence of your system binaries before rebooting."
Do Windows folks reboot too easily before examining logs, restarting services, etc? Sure. But this article extrapolates this point beyond the deep end.
The most successful way to do all this that I have seen so far, and have helped institute for a couple of companies (one was a gaming company, the other manufactured media players, almost did this for a web messaging service company but they got shy in the end), is to have a 2-pronged "data collection" approach.
1) Forums. Users come here and have a common area to bounce ideas around until they are distilled. Make it clear: your customer service reps might be reading here, but your developers do not (or at least if they do it is in private and of their own choosing).
2) A request tracker (bugzilla, request trackers, whatever works for you) that allows users to post tickets as well as to give votes on them. Make it clear: this area is ONLY for the discussion of structured suggestions -and- you will only pay attention to tickets that are well written and have at least a vote from someone other than the ticket writer.
The request tracker can either be a separate system from the customer service/technical support/whatever database or it can be set up to share the same server with permissions set properly, just depends on what is best for your organization (and how secure you feel your tracker database is). Your developers can be given access to the entire ticket if you WANT, but for some I think it makes a lot of sense to have someone (scrum master if you have one, customer service liason, whatever) re-write the ticket in a concise manner before submitting to development, possibly but not necessarily referring to the public ticket for reference.
This model does add some overlay, but another word for overlay is "filter" in this case, and that benefits the developers greatly when they are heads-down trying to implement.
PS. This model works GREAT in an agile development environment, as the tickets can easily transition to issues to be worked on, but also works well for non-software companies as long as they are open to external input.
WoW didn't invent questing, gear with buffs, world PVP, talent points, grinding, levelling, etc. Blizzard borrow from MANY games (everything from old MUDs to games like Anarchy Online, which is also still around, though with an order of magnitude fewer players). They didn't even create the basic "fluff" background and racial makeup of their world (that goes to Games Workshop with Warhammer). The game of WoW today has a huge storyline that is unique to itself, yes, but lets face it... fewer than 10% of the players really know or even care much about the individual stories.
Blizzard got extremely lucky in putting those components together (and borrowing liberally from many many other sources) and making the balance fun enough while keeping enough of the grinding aspect to addict people to the game.
My point isn't that WoW sucks, I'm a full-time player (though every single day I wish for a game that was based on Warhammer 40K instead). My point is that if Bioware/etc are able to achieve that same gameplay balance, even without inventing new paradigms and mechanics, and pair them with fluff that has at least an equal level as WoW (and Star Wars certainly has that potential)... and they have a chance for enough success to return a giant profit on the millions invested AND give players an alternative to DwarfElfOrcHumanQuest.
PS. The sad tragedy (ok, exaggeration, but it still stings:) and many others is that Games Workshop never got Warhammer off the ground years ago (Blizzard was originally working on these and when GW punted, Blizzard rebranded and changed stories) NOR have they gotten a 40K MMO off the ground, both of which would have been able to fill the niche spaces that WoW and likely SW:TOR will end up dominating. GW is the one that really trailblazed these paths but they either didn't have the cash or the balls to part with the cash to get these done.
There was also "coke" (as in the colloquial term in many places for any soda) before "coca-cola", bandages before band-aids, gelatin before jell-o, tissues before kleenex, trash cans before dumpsters, the internet before the Web, and searching online before Googling.
The point being that the article refers to the -branding- of free software as Open Source (ignoring the later splits between those communities... and the fact that 99% of us completely disregarded the socio-political arguments).
Even the term "open source" existed prior to Open Source as a brand, something that is making this/. thread even more confusing, but was FAR less common than "free software". And software that follows the common ideas of free/open has, as you point out, been around much longer. However that doesn't invalidate the article. It just points out how much better this article could have been -and- proves just how successful the Open Source nomenclature has been.
Agreed. This was the last show on SyFy I cared to watch. It wasn't great but it was better than the other shows that tried the "ship stranded away from earth/home" storyline. This was the only one of those types of spin-offs I actually enjoyed watching. Oh well.
HBO has suffered lately too, which was the other channel I really enjoyed weekly (Rome, Sopranos, etc). I pretty much don't have any story arc dramas left to watch.
What an awful example. FTP is a nearly completely static protocol with no defined presentation layer for user interaction. On the other hand HTML5 is not even a completed standard yet and is almost entirely focused around creating user interactivity with the data.
What you are missing is this... FTP doesn't correlate to HTML5. FTP correlates to HTTP. HTML5 would correlate more with the concept of the GUI to utilize FTP. Of which there are MANY completely different examples, none of which work perfectly for all situations. If you want to compare FTP to something regarding the web, then make comments about how well your web browser complies with the ability to communicate with a web server. In which case pretty much all browsers will be compliant.
Technically... neither is IE9. This article seems to fail in pointing out that it just compared a browser still in the preview phase to other browsers that are released. The board will keep changing, the difference is that within a few months of IE9 coming out there will be new Firefox and Chrome releases. The further difference here being that a year or two after IE9 coming out those same browsers (and likely Webkit/Safari, Opera, etc) will all have multiple releases.
So IE9 has essentially caught up... so what? Microsoft was dragged kicking and screaming to the point of being the "most compliant" and once it reaches that goal it will end up touting that marker well after the other browsers eclipse it.
If you've gone through the process of rooting Android versus jailbreaking iOS then you'd know there is a pretty serious difference. Both in terms of what you can do -without- going through one of these processes as well as how hard the process is to complete.
While in a flow-chart the processes look like the same block, from an end-user perspective they are significantly different.
And yes, this is the major reason why I went from an iPhone to an Android phone.
Cisco's current plan for the Linksys brand is to keep it on the "Expert" routers but put the Cisco brand on the more consumer-focused "Valet" line. Both share hardware, the main difference is packaging. This sort of kills your Squire argument, as Cisco already has the Cisco brand on the exact same hardware. It is a product marketing decision. Technogeeks like us know the Linksys line. Everyone else is much more familiar with the Cisco brand.
Yep. Simply put Apple is winning because they don't have a "range of tablet formats". The have precisely 1 at the moment. And it works exceedingly well with their mobile phone format. Anyone wanna bet that MS's tablet shares more resemblance to Win7 than WinMo? There have been dozens of Windows tablets over the past decade. None succeeded because all tried to be PCs.
I'm not an Apple fanboy. I have an old iPhone 3G (not 3Gs) that will go the way of the Do-Do in 4 months when my AT&T contract expires. I don't own an iPad. I -do- own Windows PCs. It is simply clear that MS still doesn't "get it".
Lying under oath is a criminal offense that can carry many -years- of penalty. It's called perjury. Most perjury cases only get a few months to a couple of years but in most jurisdictions it can carry up to 30 years. And guidelines are just that... guidelines. Higher courts can overturn the sentence because of them, and if it was a federal case the judge might get in hot water, but it wouldn't be an automatic dismissal in most cases. And if it is a state judge it could even work in his favor if he is elected and his constituents approve.
While the defendant got 50 months more than maximum sentencing for what he was accused of... he could have also gotten a lot MORE than 50 extra months if brought up on perjury charges. It would be a good idea for him to just take it and not complain:)
Agreed. I'm in a WiFi-only spot this week and my fiancee's T-Mobile UMA Blackberry is working like a champ for her, including SMS. Making me and my iPhone very sad.
Charcoal and Black Pepper aren't actually meat smells. Most of what you smell when you salivate about BBQ isn't meat. It is the aromatics. And most of the veggies I know still LOVE the smell of BBQ smoke as long as it's relatively clean smoke (not seared fat, etc). Especially pagan veggies since it ALSO has the aroma of a good incense charcoal.
Slashdot Mirror
That AC isn't making more shit up ... you, Mr. AC, are just too lazy to Google. A quick Google of "angry birds android ad revenue" pulled up a PAGES full of results similar to this one:
http://www.intomobile.com/2010/12/03/angry-birds-android-1-million-ad-revenue/
Is that black bomb egg on your face, or is it from a flock of blues?
Except I can keep my KeePass master password completely separate from my DropBox password. Yes, LastPass is forcing you to change your master password, but until you do that, you are exposed. If someone gets my DropBox password then all they have access to is my encrypted KeePass file.
So long as you memorize your KeePass and DropBox passwords, and make sure they are completely unrelated to each other, you are doing better (imo) than LastPass. Additionally you can add the step (as mentioned above) of having a local auth file for KeePass (meaning you need to have a copy of that file AND know the password).
Specific to something like Flip ... part of the reason Cisco killed it instead of selling it was to retain the patents and intellectual property for on-going and future products. That includes FlipShare (in fact, FlipShare is probably one of the main IPs they want to salvage in some form). Open Sourcing under those circumstances makes no sense.
I've been part of a company that did OS their products after they folded (Cobalt ... Sun acquired us then when they shut us down they allowed it to go OS). It works great in some situations. Cobalt lives on in many service providers, allowing existing and new Cobalt UI users to continue to do so, while not becoming any form of competition to Sun.
It can work in specific situations, but not in most.
I went to log in to PSN today to see which security questions I had picked and answered so that I could blacklist them from other sites and ... I can't get in to check it. Not helpful at all. Fix the holes and at least put it back up in a read-only mode. It has been years since I signed up for OR used PSN ... so I have utterly no clue what information I had there.
And yet the people just getting into Drupal, which are the people most likely to want a book on the matter, are going to go with Drupal 7 for the most part. This is sort of my predicament ... I did some stuff in Drupal 5 and am getting back into Drupal dev with 7. Had this been a book on 7 I would have jumped at it. But ... its not.
And yeah, agreed to the obligatory, "but those 2 women got 'uploaded' and not killed" from the most recent "death arc" ... except the very next episode they were effectively killed. They could come back in the future ... except the series itself is now killed off ... and almost certainly won't be resurrected.
This is something SGU did right. Characters killed other characters and those dead characters were dead. Death directly impacted the morale and capability of the remaining crew. When a crew member thought their dead child might still be alive ... they weren't. When the obligatory "all these people died but now they are back!" episode happened, the dead people were dead again by the end of it.
Firefly did this same thing years earlier and in the movie. I'm sure others have done it well, but they are few and very far between.
Sadly, this is likely part of why the mainstream population couldn't bend their minds around either show for very long.
I for one welcome our long-haired, beared, techno-guru saviors.
You mean ... they might want you to purchase equipment to handle an entirely new function that wasn't part of the product you originally purchased, rather than spending significant effort and resources in order to give you this new functionality free? That's horrible.
Cisco and a number of other companies have directly given both specs and code to the world to aid in the adoption of IPv6. I think room for them to make money in a capitalist society is acceptable. It isn't the same as, say, buying a piece of equipment that promised an upgrade that never provided it (I'm staring at my cell phone right now). It isn't like they are going to shut down your perfectly working IPv4 home router once IPv6 products come out (I'm now staring at my OLDER cell phone). It isn't even like they lock your router from the ability to do 3rd party firmware updates (staring at my phone, my set top box, my PS3, my almost-everything-electronic).
In fact, they make it pretty darned easy for you to upgrade to a 3rd party firmware. And there are free 3rd party firmwares out there today that provide full IPv6 stacks (along with almost anything else).
"If you shrug and reboot the box after looking around for a few minutes, you may have missed the fact that a junior admin inadvertently deleted /boot and some portions of /etc and /usr/lib64 due to a runaway script they were writing. That's what was causing the segfaults and the wonky behavior. But since you rebooted the server without digging into the problem, you've made it much worse, and you'll soon boot a rescue image -- with all kinds of ponderous work awaiting you -- while a production server is down."
That argument is somehow pro-Unix?
I mean, yeah, a Windows person can screw with boot files, too. However if a Windows person were to read that paragraph it certainly wouldn't do a thing to encourage them on the solidity of *nix. It basically translates to "if you're having a problem, don't restart, you may not be able to boot again because your other admins may be incapable of writing proper scripts since every *nix system is different on its boot structure ... so ALWAYS do a full check of the existence of your system binaries before rebooting."
Do Windows folks reboot too easily before examining logs, restarting services, etc? Sure. But this article extrapolates this point beyond the deep end.
The most successful way to do all this that I have seen so far, and have helped institute for a couple of companies (one was a gaming company, the other manufactured media players, almost did this for a web messaging service company but they got shy in the end), is to have a 2-pronged "data collection" approach.
1) Forums. Users come here and have a common area to bounce ideas around until they are distilled. Make it clear: your customer service reps might be reading here, but your developers do not (or at least if they do it is in private and of their own choosing).
2) A request tracker (bugzilla, request trackers, whatever works for you) that allows users to post tickets as well as to give votes on them. Make it clear: this area is ONLY for the discussion of structured suggestions -and- you will only pay attention to tickets that are well written and have at least a vote from someone other than the ticket writer.
The request tracker can either be a separate system from the customer service/technical support/whatever database or it can be set up to share the same server with permissions set properly, just depends on what is best for your organization (and how secure you feel your tracker database is). Your developers can be given access to the entire ticket if you WANT, but for some I think it makes a lot of sense to have someone (scrum master if you have one, customer service liason, whatever) re-write the ticket in a concise manner before submitting to development, possibly but not necessarily referring to the public ticket for reference.
This model does add some overlay, but another word for overlay is "filter" in this case, and that benefits the developers greatly when they are heads-down trying to implement.
PS. This model works GREAT in an agile development environment, as the tickets can easily transition to issues to be worked on, but also works well for non-software companies as long as they are open to external input.
WoW didn't invent questing, gear with buffs, world PVP, talent points, grinding, levelling, etc. Blizzard borrow from MANY games (everything from old MUDs to games like Anarchy Online, which is also still around, though with an order of magnitude fewer players). They didn't even create the basic "fluff" background and racial makeup of their world (that goes to Games Workshop with Warhammer). The game of WoW today has a huge storyline that is unique to itself, yes, but lets face it ... fewer than 10% of the players really know or even care much about the individual stories.
Blizzard got extremely lucky in putting those components together (and borrowing liberally from many many other sources) and making the balance fun enough while keeping enough of the grinding aspect to addict people to the game.
My point isn't that WoW sucks, I'm a full-time player (though every single day I wish for a game that was based on Warhammer 40K instead). My point is that if Bioware/etc are able to achieve that same gameplay balance, even without inventing new paradigms and mechanics, and pair them with fluff that has at least an equal level as WoW (and Star Wars certainly has that potential) ... and they have a chance for enough success to return a giant profit on the millions invested AND give players an alternative to DwarfElfOrcHumanQuest.
PS. The sad tragedy (ok, exaggeration, but it still stings :) and many others is that Games Workshop never got Warhammer off the ground years ago (Blizzard was originally working on these and when GW punted, Blizzard rebranded and changed stories) NOR have they gotten a 40K MMO off the ground, both of which would have been able to fill the niche spaces that WoW and likely SW:TOR will end up dominating. GW is the one that really trailblazed these paths but they either didn't have the cash or the balls to part with the cash to get these done.
There was also "coke" (as in the colloquial term in many places for any soda) before "coca-cola", bandages before band-aids, gelatin before jell-o, tissues before kleenex, trash cans before dumpsters, the internet before the Web, and searching online before Googling.
The point being that the article refers to the -branding- of free software as Open Source (ignoring the later splits between those communities ... and the fact that 99% of us completely disregarded the socio-political arguments).
Even the term "open source" existed prior to Open Source as a brand, something that is making this /. thread even more confusing, but was FAR less common than "free software". And software that follows the common ideas of free/open has, as you point out, been around much longer. However that doesn't invalidate the article. It just points out how much better this article could have been -and- proves just how successful the Open Source nomenclature has been.
Agreed. This was the last show on SyFy I cared to watch. It wasn't great but it was better than the other shows that tried the "ship stranded away from earth/home" storyline. This was the only one of those types of spin-offs I actually enjoyed watching. Oh well.
HBO has suffered lately too, which was the other channel I really enjoyed weekly (Rome, Sopranos, etc). I pretty much don't have any story arc dramas left to watch.
What an awful example. FTP is a nearly completely static protocol with no defined presentation layer for user interaction. On the other hand HTML5 is not even a completed standard yet and is almost entirely focused around creating user interactivity with the data.
What you are missing is this ... FTP doesn't correlate to HTML5. FTP correlates to HTTP. HTML5 would correlate more with the concept of the GUI to utilize FTP. Of which there are MANY completely different examples, none of which work perfectly for all situations. If you want to compare FTP to something regarding the web, then make comments about how well your web browser complies with the ability to communicate with a web server. In which case pretty much all browsers will be compliant.
Technically ... neither is IE9. This article seems to fail in pointing out that it just compared a browser still in the preview phase to other browsers that are released. The board will keep changing, the difference is that within a few months of IE9 coming out there will be new Firefox and Chrome releases. The further difference here being that a year or two after IE9 coming out those same browsers (and likely Webkit/Safari, Opera, etc) will all have multiple releases.
So IE9 has essentially caught up ... so what? Microsoft was dragged kicking and screaming to the point of being the "most compliant" and once it reaches that goal it will end up touting that marker well after the other browsers eclipse it.
Insightful? Not really.
If you've gone through the process of rooting Android versus jailbreaking iOS then you'd know there is a pretty serious difference. Both in terms of what you can do -without- going through one of these processes as well as how hard the process is to complete.
While in a flow-chart the processes look like the same block, from an end-user perspective they are significantly different.
And yes, this is the major reason why I went from an iPhone to an Android phone.
Cisco's current plan for the Linksys brand is to keep it on the "Expert" routers but put the Cisco brand on the more consumer-focused "Valet" line. Both share hardware, the main difference is packaging. This sort of kills your Squire argument, as Cisco already has the Cisco brand on the exact same hardware. It is a product marketing decision. Technogeeks like us know the Linksys line. Everyone else is much more familiar with the Cisco brand.
Disclaimer: I work for Cisco Consumer Products.
Yep. Simply put Apple is winning because they don't have a "range of tablet formats". The have precisely 1 at the moment. And it works exceedingly well with their mobile phone format. Anyone wanna bet that MS's tablet shares more resemblance to Win7 than WinMo? There have been dozens of Windows tablets over the past decade. None succeeded because all tried to be PCs.
I'm not an Apple fanboy. I have an old iPhone 3G (not 3Gs) that will go the way of the Do-Do in 4 months when my AT&T contract expires. I don't own an iPad. I -do- own Windows PCs. It is simply clear that MS still doesn't "get it".
Lying under oath is a criminal offense that can carry many -years- of penalty. It's called perjury. Most perjury cases only get a few months to a couple of years but in most jurisdictions it can carry up to 30 years. And guidelines are just that ... guidelines. Higher courts can overturn the sentence because of them, and if it was a federal case the judge might get in hot water, but it wouldn't be an automatic dismissal in most cases. And if it is a state judge it could even work in his favor if he is elected and his constituents approve.
While the defendant got 50 months more than maximum sentencing for what he was accused of ... he could have also gotten a lot MORE than 50 extra months if brought up on perjury charges. It would be a good idea for him to just take it and not complain :)
Or maybe not all iPhone4 devices have the same defect. Whodathunkit?
Agreed. I'm in a WiFi-only spot this week and my fiancee's T-Mobile UMA Blackberry is working like a champ for her, including SMS. Making me and my iPhone very sad.
Yep ... but if they ever DID figure it out we'd be that much closer to a replicator.
Charcoal and Black Pepper aren't actually meat smells. Most of what you smell when you salivate about BBQ isn't meat. It is the aromatics. And most of the veggies I know still LOVE the smell of BBQ smoke as long as it's relatively clean smoke (not seared fat, etc). Especially pagan veggies since it ALSO has the aroma of a good incense charcoal.