Yes, but one of the genders is ready to kick your podiums over, throw coffee into your routers, and strangle various exhibitor functionaires with Cat6 after they set fire to your expensive literature.
Where does the commitment demanded by manufacturers become too high for a small shop?
I see so many camera models moving thru big box retailers, that it seems that few really have a long market life, except for the big DSLRs and the 4/3rds, and so forth. Consumer cameras seem to go poof, and they perhaps break as much as the pro models. Just looking at the Olympus new models announced at CES, it seems as though the churn for 2013 was almost half their product line. I really think that cameras models have a shorter sales life these days.
The designs of cameras have a lifecycle that approaches several months, some don't even make it thru the end of the year. This is a problem for both consumers, and repair people. I've waited for ages for parts for some of my cameras (and laptops, etc) to arrive even at the factory.
Each camera has test jigs and version-specific firmware to deal with. The complexities don't lend themselves to a productive third-party repair venue. Ask any Apple authorized repair shop how weird repairs can be.
Should third-parties get parts? Do they know how to use them? Do they use safe static discharge devices? Do the have the test software and parts needed to ensure the customer (me) gets the job done without charging scandalous amounts of labor with re-tries?
It's not an easy metaphor. The farrier and horse are one things, horse shoes another, and veterinary medicine still another-- all as the nature of the horse changes every several calendar quarters.
I feel for the plight of this repair guy, yet I also understand that consumer demands have made for short shelf-lives of the product, let alone backup repair inventory and the skills needed to do a reasonable job of the repair.
Yes, you did. So, I'm the non-person behind my people corporation. Just the stockholder, president, cook, and bottle washer. And my assets are magically protected from litigation. This is how it works today. Is there a different system? Perhaps, but the investments in corporations makes them difficult to touch. Do the right thing? Morality? These aren't necessarily strong concepts to corporations, but they should be.
I can see a "skunksworks" division, the prototype-farm, or something similar. Either no support, or heavy premium. It could be easily isolated and even VLAN partitioned off their main grid.
The skunkswork potential of AWS has made Amazon a small fortune, and I have no idea whether it's caused plausible destabilization of the AWS services offering. But it has a very nice "cool" factor. Rackspace, while "cool" in some ways, is a more hardened model. I can see why it would be reasonable to keep science projects off their grid.... with a small investment.
Your subject line question is best answered by others that have jumped into the OpenStack framework with products and support whose name isn't Rackspace.
Although Rackspace is seemingly closing their turf to competition, any reasonable customer outcry will have them doing a 180, and with good reason. They want to flip the bird at Citrix, fine-- Citrix can make a fine target. But it's not a closed framework, only the realization that overly broad support could distract them by costing them lots of $$ to reasonably support difficult stuff. I think it's a reasonable stop on RackSpace's part, although they could have been wiser about how they went about it.
I take encouragement that iOS is a combo of Windows CE and older Blackberry functionality that was done well. Schmidt was on Apple's board when they were conceiving iOS, and he took what he discovered and grafted it onto Android. These have all been incremental repackaging of stuff. BB/RIM has a weak engineering team, but good ideas, hobbled by not making vast ecosystems out of content, apps (especially games), and so forth. They focused on business. In a way, that much hasn't changed, but they're trying to break open the cartels behind iTunes and G+Stuff.
Someone will come along and one-up the one-uppers. It's only a matter of time. Whether it's a Boot2Gecko/Mozilla, Ubuntu in the flesh, Chinese hack of Android, it'll be something. Windows 8 faces a lot of animosity, so it's a "dark horse" in my mind.
All this will pass. Everyone will try to get you to buy new hardware, change your sub & carrier, do subscription models, and so forth. New combos will be found. Maybe BB will survive and flourish. The OP seems like he/she's asking a baited question.
Yes you can do anything you want with your source. I don't care what you do with your source.
If, however, you publish it, you still own the copyright,which you acknowlege. I can view your material and go, gee, interesting, eh?
I cannot scrape it and use it, becauseYOU still have the copyright, and all rights reserved by the copyright, one of which is DON'T COPY THE THE STUFF. Just publishing it on a screen grants NOTHING. If I use the code under the circumstances you describe, you can successfully sue me, because of the NATIVE COPYRIGHT YOU SPECIFICALLY HOLD until you grant another use case.
Your choice? Knock yourself out. My choices are indeed legally limited in using your code.
It's yours as originator, unless others use it as an example, not to copy it, UNLESS YOU TELL THEM IT'S OK. That advice to them, CC, CopyLeft, etc., allows them to use it. Without that, you can sue them for infringement.
Infringement occurs, if he owns it, and you use it. Therefore, it's nothing but a coder's masturbation to post such things-- without a stated license or intent. I'm not a thief, and likely, you aren't either. But you can't use that code unless you 1) want to take your chances or 2) want your code to be forever of dubious source.
Make up your own license. Use CC, copyleft, whatever. But otherwise, you're just spewing your ego, not making a contribution to anything, because its ownership is tenuous. This is the real world, not someone's fantasy. Farting code, no matter the scent, is still farting.
You can also call it by it's narcissistic name: sloth, don't-give-a-shit, don't bother me with trifles and crap I don't understand, and so forth.
Public domain may not be the default status of a published work, at least in the USA. This means that code is essentially untouchable in its whole form. Without a declaration, the originator owns it, IMHO.
Of course they act to benefit themselves, but they have actual controls, although there are any number of citations to show that they have let a lot slide. Part of the reason for that: derivatives and other forms of obscured trades made a mess of things, and the entire US banking system was on the slide, not just one part of it-- the whole thing.
So they forced mergers, and they still do. Lots of banks were upside down in securities whose worth was unknown, not just questioned. It took a long time to unravel what derivates were asset-based, the worth of those assets, and the assets ratios and acid test-findings of various banks, big, small, and any sized.
Lots of people got off with no prosecution, especially compared to the S&L scandal of a couple of decades ago.
But the Fed can print money during deflationary cycles. So long as inflation is in complete check (and it was, as the derivatives and foreclosures and bad assets were discovered) to prop up the economy by offering low/no-interest loans, buying up bonds, and doing their job to keep it in balance.
Yeah, there's a lot amiss. But nothing compared to what RBS did. It wasn't just the US banks that were diddling with derivatives, Deutsche Bank, various Swiss banks, lots of them were caught in the cookie jar. A lot of the damage has been stanched. We still have a way to goes.
But the Fed members aren't lining their pockets in the way you're thinking. A lot of surviving banks have made staggering paper profits. They screwed a lot of people. But in the end, in 2013, we're still ticking and the bombshells haven't even dropped regarding what's going to happen to RBS, et al.
Often you can find plumbing or heating/cooling plenums to run the cable through; just make sure the cable meets local codes for where you're running it. Plenum cables abound. Crimp tools are cheap. And you won't trip over the cables or have them chewed by a neurotic dog.
The cable companies want this revenue for themselves. And make no mistake: multiple concurrent streams will start to crater their infrastructure. The more you buy from non-CDN networks, the more dicey it will get. They'll try to upgrade you to an advanced tier of service, then show you what kind of "deal" they can offer you instead.
We've seen this sort of thing plenty of times before. Video on demand is kind of ok, but it's compressed like crazy. If you think compresses kinda-nice HD is going to suck the air out of the NOC, wait until you see what 4K (ultra-high-def) will take.
None of these has really garnered much marketshare, despite Paypal's evils. Although an interesting payments model, its customer service is an oxymoron. When you've got auction funds tied up from eBay, or there's a question to your business model, they shoot their clientele first, look for blood, and allow questions to be asked later.
If the US banking laws were real (I know, another oxymoron), Paypal would have the teeth of a hundred US DAs in their leg, gnawing viciously. But they're seemingly exempt, as are all the big financial houses.
Can you code? We need logic like yours in the new NRA IT initiative! Your knowledge of history, combined with your keen insight will have new recruits lining up to sign on!
An epic rant you have there, but there's a lot to agree with. All three of these have been known to buy a good idea, just to put it into the trash can, in an attempt to chill out a market segment that they want to control. Sometimes a few good features might find themselves into the codestreams of a project, more often than not, it's: go away kid, ya bother me. Here's some candy, now get outta here.
Is it anticompetitive? In certainty, and it's business-as-usual and a seemingly accepted tactic that skirts Taft-Harley and other law handily.
Yes, but one of the genders is ready to kick your podiums over, throw coffee into your routers, and strangle various exhibitor functionaires with Cat6 after they set fire to your expensive literature.
>> "Insightful"?
No.
Crickets.
There, fixed it for you.
Where does the commitment demanded by manufacturers become too high for a small shop?
I see so many camera models moving thru big box retailers, that it seems that few really have a long market life, except for the big DSLRs and the 4/3rds, and so forth. Consumer cameras seem to go poof, and they perhaps break as much as the pro models. Just looking at the Olympus new models announced at CES, it seems as though the churn for 2013 was almost half their product line. I really think that cameras models have a shorter sales life these days.
The designs of cameras have a lifecycle that approaches several months, some don't even make it thru the end of the year. This is a problem for both consumers, and repair people. I've waited for ages for parts for some of my cameras (and laptops, etc) to arrive even at the factory.
Each camera has test jigs and version-specific firmware to deal with. The complexities don't lend themselves to a productive third-party repair venue. Ask any Apple authorized repair shop how weird repairs can be.
Should third-parties get parts? Do they know how to use them? Do they use safe static discharge devices? Do the have the test software and parts needed to ensure the customer (me) gets the job done without charging scandalous amounts of labor with re-tries?
It's not an easy metaphor. The farrier and horse are one things, horse shoes another, and veterinary medicine still another-- all as the nature of the horse changes every several calendar quarters.
I feel for the plight of this repair guy, yet I also understand that consumer demands have made for short shelf-lives of the product, let alone backup repair inventory and the skills needed to do a reasonable job of the repair.
Yes, you did. So, I'm the non-person behind my people corporation. Just the stockholder, president, cook, and bottle washer. And my assets are magically protected from litigation. This is how it works today. Is there a different system? Perhaps, but the investments in corporations makes them difficult to touch. Do the right thing? Morality? These aren't necessarily strong concepts to corporations, but they should be.
Fraud is still fraud.
IANAL, but the protections vary from state to state, litgation to litigation, criminal and civil.
Which is sadly the reason to incorporate, or do an LLC/LLP, etc., and join the madness of shielding yourselve personal assets from the trolls.
Sad to have to recommend it, but litigation, whether you're right or wrong, is expensive. Welcome to the game. You start out by losing.
I can see a "skunksworks" division, the prototype-farm, or something similar. Either no support, or heavy premium. It could be easily isolated and even VLAN partitioned off their main grid.
The skunkswork potential of AWS has made Amazon a small fortune, and I have no idea whether it's caused plausible destabilization of the AWS services offering. But it has a very nice "cool" factor. Rackspace, while "cool" in some ways, is a more hardened model. I can see why it would be reasonable to keep science projects off their grid.... with a small investment.
Your subject line question is best answered by others that have jumped into the OpenStack framework with products and support whose name isn't Rackspace.
Although Rackspace is seemingly closing their turf to competition, any reasonable customer outcry will have them doing a 180, and with good reason. They want to flip the bird at Citrix, fine-- Citrix can make a fine target. But it's not a closed framework, only the realization that overly broad support could distract them by costing them lots of $$ to reasonably support difficult stuff. I think it's a reasonable stop on RackSpace's part, although they could have been wiser about how they went about it.
It was a payload destined for the NYTimes, but somehow, it was re-routed.
You can whatif yourself into a deep, deep bog. There are unknown variables, and the answer to the question must rely on them.
You can put a big divisor on this, however, with the fact that a nuclear winter trumps most cards, dystopic science fiction scenarios notwithstanding.
I take encouragement that iOS is a combo of Windows CE and older Blackberry functionality that was done well. Schmidt was on Apple's board when they were conceiving iOS, and he took what he discovered and grafted it onto Android. These have all been incremental repackaging of stuff. BB/RIM has a weak engineering team, but good ideas, hobbled by not making vast ecosystems out of content, apps (especially games), and so forth. They focused on business. In a way, that much hasn't changed, but they're trying to break open the cartels behind iTunes and G+Stuff.
Someone will come along and one-up the one-uppers. It's only a matter of time. Whether it's a Boot2Gecko/Mozilla, Ubuntu in the flesh, Chinese hack of Android, it'll be something. Windows 8 faces a lot of animosity, so it's a "dark horse" in my mind.
All this will pass. Everyone will try to get you to buy new hardware, change your sub & carrier, do subscription models, and so forth. New combos will be found. Maybe BB will survive and flourish. The OP seems like he/she's asking a baited question.
I express my opinion, because I can't legally render legal advice. IANAL.
What you state, in my belief, is entirely true. Please explain this to the downstream poster. I give up.
Yes you can do anything you want with your source. I don't care what you do with your source.
If, however, you publish it, you still own the copyright,which you acknowlege. I can view your material and go, gee, interesting, eh?
I cannot scrape it and use it, becauseYOU still have the copyright, and all rights reserved by the copyright, one of which is DON'T COPY THE THE STUFF. Just publishing it on a screen grants NOTHING. If I use the code under the circumstances you describe, you can successfully sue me, because of the NATIVE COPYRIGHT YOU SPECIFICALLY HOLD until you grant another use case.
Your choice? Knock yourself out. My choices are indeed legally limited in using your code.
Sorry, but you're wrong.
It's yours as originator, unless others use it as an example, not to copy it, UNLESS YOU TELL THEM IT'S OK. That advice to them, CC, CopyLeft, etc., allows them to use it. Without that, you can sue them for infringement.
Infringement occurs, if he owns it, and you use it. Therefore, it's nothing but a coder's masturbation to post such things-- without a stated license or intent. I'm not a thief, and likely, you aren't either. But you can't use that code unless you 1) want to take your chances or 2) want your code to be forever of dubious source.
Make up your own license. Use CC, copyleft, whatever. But otherwise, you're just spewing your ego, not making a contribution to anything, because its ownership is tenuous. This is the real world, not someone's fantasy. Farting code, no matter the scent, is still farting.
You can also call it by it's narcissistic name: sloth, don't-give-a-shit, don't bother me with trifles and crap I don't understand, and so forth.
Public domain may not be the default status of a published work, at least in the USA. This means that code is essentially untouchable in its whole form. Without a declaration, the originator owns it, IMHO.
>Can we be sure..... ?
Of course they act to benefit themselves, but they have actual controls, although there are any number of citations to show that they have let a lot slide. Part of the reason for that: derivatives and other forms of obscured trades made a mess of things, and the entire US banking system was on the slide, not just one part of it-- the whole thing.
So they forced mergers, and they still do. Lots of banks were upside down in securities whose worth was unknown, not just questioned. It took a long time to unravel what derivates were asset-based, the worth of those assets, and the assets ratios and acid test-findings of various banks, big, small, and any sized.
Lots of people got off with no prosecution, especially compared to the S&L scandal of a couple of decades ago.
But the Fed can print money during deflationary cycles. So long as inflation is in complete check (and it was, as the derivatives and foreclosures and bad assets were discovered) to prop up the economy by offering low/no-interest loans, buying up bonds, and doing their job to keep it in balance.
Yeah, there's a lot amiss. But nothing compared to what RBS did. It wasn't just the US banks that were diddling with derivatives, Deutsche Bank, various Swiss banks, lots of them were caught in the cookie jar. A lot of the damage has been stanched. We still have a way to goes.
But the Fed members aren't lining their pockets in the way you're thinking. A lot of surviving banks have made staggering paper profits. They screwed a lot of people. But in the end, in 2013, we're still ticking and the bombshells haven't even dropped regarding what's going to happen to RBS, et al.
Often you can find plumbing or heating/cooling plenums to run the cable through; just make sure the cable meets local codes for where you're running it. Plenum cables abound. Crimp tools are cheap. And you won't trip over the cables or have them chewed by a neurotic dog.
The cable companies want this revenue for themselves. And make no mistake: multiple concurrent streams will start to crater their infrastructure. The more you buy from non-CDN networks, the more dicey it will get. They'll try to upgrade you to an advanced tier of service, then show you what kind of "deal" they can offer you instead.
We've seen this sort of thing plenty of times before. Video on demand is kind of ok, but it's compressed like crazy. If you think compresses kinda-nice HD is going to suck the air out of the NOC, wait until you see what 4K (ultra-high-def) will take.
None of these has really garnered much marketshare, despite Paypal's evils. Although an interesting payments model, its customer service is an oxymoron. When you've got auction funds tied up from eBay, or there's a question to your business model, they shoot their clientele first, look for blood, and allow questions to be asked later.
If the US banking laws were real (I know, another oxymoron), Paypal would have the teeth of a hundred US DAs in their leg, gnawing viciously. But they're seemingly exempt, as are all the big financial houses.
I say: if you're going to extend a meme, give it a decent shot.
Can you code? We need logic like yours in the new NRA IT initiative! Your knowledge of history, combined with your keen insight will have new recruits lining up to sign on!
An epic rant you have there, but there's a lot to agree with. All three of these have been known to buy a good idea, just to put it into the trash can, in an attempt to chill out a market segment that they want to control. Sometimes a few good features might find themselves into the codestreams of a project, more often than not, it's: go away kid, ya bother me. Here's some candy, now get outta here.
Is it anticompetitive? In certainty, and it's business-as-usual and a seemingly accepted tactic that skirts Taft-Harley and other law handily.
Remember your PR#6 to boot the floppy from Applesoft in ROM. Cloads were for cheapskates ;)