A big, ever bloating cake that is all flavors to everyone, that allows you to extend it with pie and ice cream and allows you to skin it so it looks like a steak.
So because an employer says you can't, you think it doesn't happen? What if I applied that to the other side of the argument? Because GPL says Microsoft can't leverage the code they way they are suspected of doing, it didn't happen?
I'm not saying I'm old enough to remember, but wasn't there a Mole Men of the Moon enemy our slightly gay, tight wearing, dual-life-leading, Krytonian Ersatz Messiah had to fight?
This is actually a pretty accurate post when considered from the point of view of capitalism's proponents. They bypass the moral discussion (with respect to individual freedom, personal autonomy, mutual voluntary association, etc)
Telling.
Many anti-Capitalists would, if they had their way, remove THE CHOICE of capitalism and free-market, thus obviating the messy moral issues.
Of course, it is that removal of CHOICE that is the greatest moral threat.
Can you imagine what would happen if other markets went the way of OSS and FSF ideals? You'd get a few finished products and a lot of half-baked, half-finished products. You'll have to supply your own containers when shopping for soup at the market, and provide your botulism test because the kitchen hadn't gotten around to it yet. You go to buy a car, but someone decided to break with convention and try a new brake design. He's delivered the car in a.5 Alpha and makes a small note that the brake fluid/master cylinder/wheel interface isn't ready yet.
I prefer capitalism, even the messed up version we have here in the U.S. to what most anti-capitalists have in mind. At least it lets me choose my morals.
As a Federal Employee, I am glad to say that we have flying cars, we just aren't allowed to tell anyone about...
Uhmmm, on a separate note, in the CS we haven't been allowed to use cell phones period while driving a government vehicle. So, this order is kind of superfulous. If you check out the old government vehicle and return it dirty, low on fluids, with a scratch, you can count on a lot of hassle. Get in an accident? You're CS career is toast. And don't get a ticket or have someone call the GSA to complain about your driving in a government vehicle. They track those things.
If you go default on SharePoint, then it is very easy to find what you want in the SharePoint contentdb. It's in SQL and very accessable. It's very easy to pull it out of SP and shove it into something else, including XML. You can go raw, not recommended, but very doable and discoverable, you can go through the object model, very easy, or you can go through the web services. So, I have a real problem with the term "Lock In".
If you have a SQL programmer or a.net programmer or a programmer that can do web services, you don't have lock in.
Yes, SharePoint integrates with office. Surprise! But, you aren't locked in.
No, SharePoint doesn't trap anything.
SharePoint out-of-the-box, is o.k. To make it USEFUL, you extend it with features. Features can be purchased or developed. One such add on is StoragePoint that allows all the BLOB storage to be moved to the file system, other DB's, other CMS, etc.
The common answer to the lack of a feature in an OSS project is, "Well, write it yourself." If you need a feature in SharePoint that isn't available OOTB, or COTS, you can...surprise, write it yourself.
You, apparently, didn't buy the key to the book. The actual story that is revealed is a knee slapping, edge of seat read that will make you laugh, cry, slap your mamma. Oh, and it has all the stuff you really wanted. Next time you buy a book on cryptography, turn it 90 degrees, read back to front, right to left, every other character on odd pages that aren't prime, every fourth letter on even pages that don't end in zero. Once you've collected the letters, use the ISBN as a skip guide to pull letters off of the prime numbered and even pages ending in zero, this is your key to the rest of the text.
The Aconynm Elimination Mandate (AEM) was signed by the President's APP, and will be over seen by the OMB. The PTG is the TLA category to be followed by the FLA groups.
The GOP oppoosition to the AEM headed by the OMB states that if the AEM is successful, millions of OGD (Official Government Documents) will be rendered unreadable.
The AG, who previously pledged to improve responses to public-records requests, has not responded yet.
The above from TFS reads like it was written by the guy that wrote:
Now, a clever man would put the poison into his own goblet, because he would know that only a great fool would reach for what he was given. I am not a great fool, so I can clearly not choose the wine in front of you. But you must have known I was not a great fool, you would have counted on it, so I can clearly not choose the wine in front of me.
So, clearly, while the post is "off topic", it obviously can't be because the expression "what" is a clear explanation of the writers intent to express his utter incredulity upon reading the TFS.
No, I'm saying that to bring this up as some great sensationalist, "look at what they just did" kind of thing, this really should have been brought up 3 YEARS AGO!!!
The article makes it seem like it hasn't been in Windows since Windows NT and that Windows 7 is the first time it's reappeared. Seriously, Vista has it.
Is this a case of "It's after midnight, must post another slam on Microsoft, even if we have twist and stretch like taffy to make the case"?
It wouldn't be so bad but the body of the submission is incredibly slanted, almost more than some of the replies.
Re-read the poster I was responding to. I didn't say "fire". I said that if the boss tries to enforce a new process that moves from email to SharePoint, and call it mandatory, some yahoo is *IS* going to file a complaint, and in my little killer branch of Government, thats enough to put the kabosh on any innovation. And, yes, I'm CS not a contractor.
I'm not too familiar with OS X platforms that work or don't with SharePoint. The problem with some Linux installs, and we have a few, are that dependencies aren't well documented. Your best bet is to use the.net plug in for FF.
The other problem is that a lot of companies are told about all the wonderful things that SharePoint does, except, most of the integrators doing the selling are telling you about things that have to added on to the system.
SharePoint workflow sucks donkey balls. Don't sell it to your users, its out-of-the-box and not worth the time they put into. Go with Nintex or K2 for SharePoint workflow.
Also, we have had a major issue with an integrator and then asked them to set up Performance Point, Google Earth, and CorasWorks. They have yet to get it working right. I really wish I could tell you their name so you could avoid them, but I can't. But, I do know the USMC and USAF have similar farms that are well integrated and working fine. We got screwed by the "partner" we went with.
I've gone to a lot of code camps, seminars, and other functions, and anectdotal evidences seems to indicate that most companies that have problems with SharePoint is because they went with a crappy integrator, or they handed the install manuals to someone in their IT department and said, "Go" without sending them to training.
MOSS: Microsoft Office SharePoint Services (This is the for pay SharePoint with extra features. WSS: Windows SharePoint Services (This is included in Windows Server 2k3 and 2k8.
Well, if it's so fucking great, why can't you get people to use it?
Inertia...oops, I put that in the title.
Opera
I have a feeling the only browser you used that choked on SharePoint was Opera. You definitely didn't try FF.
Firefox handles SharePoint wonderfully. But, remember, SharePoint makes use of JavaScript, so if you are blocking JavaScript, you have a problem.
In my office, we have a mix of FireFox 2 - 3.x, and IE 6 through 8 (IE 6 is thanks to EDS and NMCI for being behind the curve).
The only time FireFox chokes on SharePoint is because of a non-SharePoint problem, we make heavy use of card based certs and log on, and FireFox doesn't like passing card based authentication, but, there is a U.S. Navy developed open source FF plug in for that. Works fine, lasts long time. In fact, for you open source types, FF plug ins are great way to add functionality to SharePoint sites and make it work even more wonderfully with SharePoint unaware applications.
Most of SharePoint is exposed by web services, and most of the SharePoint feature systems can be modified by some DOM stuff.
I never told a user to STFU. Maybe you are having issues with your company? If your IT folks regularly tell you to STFU, then 1) they aren't worth anything, or 2) you are in need cranalanalectomy.
Slashdot Mirror
My life will be forever autumn, now you're not here.
A big, ever bloating cake that is all flavors to everyone, that allows you to extend it with pie and ice cream and allows you to skin it so it looks like a steak.
A lot of people take home office supplies because they think the company should be thanking them.
So because an employer says you can't, you think it doesn't happen? What if I applied that to the other side of the argument? Because GPL says Microsoft can't leverage the code they way they are suspected of doing, it didn't happen?
Just wondering. Hence, the question. Are you feeling guilty? Did you steal code from work? You seem to have taken the question a little personal.
How many developers took code they wrote for their company and used it in a GPL project afterwards?
I prefer "Rocketship Galileo". Any geek hobbyist can build a rocket, take a Browning, and fight Nazi's on the moon.
I'm not saying I'm old enough to remember, but wasn't there a Mole Men of the Moon enemy our slightly gay, tight wearing, dual-life-leading, Krytonian Ersatz Messiah had to fight?
(Batman rules!)
Telling.
Many anti-Capitalists would, if they had their way, remove THE CHOICE of capitalism and free-market, thus obviating the messy moral issues.
Of course, it is that removal of CHOICE that is the greatest moral threat.
Can you imagine what would happen if other markets went the way of OSS and FSF ideals? You'd get a few finished products and a lot of half-baked, half-finished products. You'll have to supply your own containers when shopping for soup at the market, and provide your botulism test because the kitchen hadn't gotten around to it yet. You go to buy a car, but someone decided to break with convention and try a new brake design. He's delivered the car in a .5 Alpha and makes a small note that the brake fluid/master cylinder/wheel interface isn't ready yet.
I prefer capitalism, even the messed up version we have here in the U.S. to what most anti-capitalists have in mind. At least it lets me choose my morals.
As a Federal Employee, I am glad to say that we have flying cars, we just aren't allowed to tell anyone about...
Uhmmm, on a separate note, in the CS we haven't been allowed to use cell phones period while driving a government vehicle. So, this order is kind of superfulous. If you check out the old government vehicle and return it dirty, low on fluids, with a scratch, you can count on a lot of hassle. Get in an accident? You're CS career is toast. And don't get a ticket or have someone call the GSA to complain about your driving in a government vehicle. They track those things.
So you went from ME to Vista? Sap!
No. Vendor lock in is where you build your infrastructure with a vendor and then have to use their solutions in order to use your infrastructure.
If you go default on SharePoint, then it is very easy to find what you want in the SharePoint contentdb. It's in SQL and very accessable. It's very easy to pull it out of SP and shove it into something else, including XML. You can go raw, not recommended, but very doable and discoverable, you can go through the object model, very easy, or you can go through the web services. So, I have a real problem with the term "Lock In".
If you have a SQL programmer or a .net programmer or a programmer that can do web services, you don't have lock in.
Yes, SharePoint integrates with office. Surprise! But, you aren't locked in. No, SharePoint doesn't trap anything. SharePoint out-of-the-box, is o.k. To make it USEFUL, you extend it with features. Features can be purchased or developed. One such add on is StoragePoint that allows all the BLOB storage to be moved to the file system, other DB's, other CMS, etc.
The common answer to the lack of a feature in an OSS project is, "Well, write it yourself." If you need a feature in SharePoint that isn't available OOTB, or COTS, you can...surprise, write it yourself.
I tested this plug-in:
I don't know about making it less secure, but it sure causes a bunch of "recovered" tabs and multiple errors.
Not Ready for Prime Time!
You, apparently, didn't buy the key to the book. The actual story that is revealed is a knee slapping, edge of seat read that will make you laugh, cry, slap your mamma. Oh, and it has all the stuff you really wanted. Next time you buy a book on cryptography, turn it 90 degrees, read back to front, right to left, every other character on odd pages that aren't prime, every fourth letter on even pages that don't end in zero. Once you've collected the letters, use the ISBN as a skip guide to pull letters off of the prime numbered and even pages ending in zero, this is your key to the rest of the text.
I prefer iPinot
The Aconynm Elimination Mandate (AEM) was signed by the President's APP, and will be over seen by the OMB. The PTG is the TLA category to be followed by the FLA groups. The GOP oppoosition to the AEM headed by the OMB states that if the AEM is successful, millions of OGD (Official Government Documents) will be rendered unreadable.
The above from TFS reads like it was written by the guy that wrote:
So, clearly, while the post is "off topic", it obviously can't be because the expression "what" is a clear explanation of the writers intent to express his utter incredulity upon reading the TFS.
No, I'm saying that to bring this up as some great sensationalist, "look at what they just did" kind of thing, this really should have been brought up 3 YEARS AGO!!!
The article makes it seem like it hasn't been in Windows since Windows NT and that Windows 7 is the first time it's reappeared. Seriously, Vista has it.
Is this a case of "It's after midnight, must post another slam on Microsoft, even if we have twist and stretch like taffy to make the case"?
It wouldn't be so bad but the body of the submission is incredibly slanted, almost more than some of the replies.
Re-read the poster I was responding to. I didn't say "fire". I said that if the boss tries to enforce a new process that moves from email to SharePoint, and call it mandatory, some yahoo is *IS* going to file a complaint, and in my little killer branch of Government, thats enough to put the kabosh on any innovation. And, yes, I'm CS not a contractor.
I'm not too familiar with OS X platforms that work or don't with SharePoint. The problem with some Linux installs, and we have a few, are that dependencies aren't well documented. Your best bet is to use the .net plug in for FF.
The other problem is that a lot of companies are told about all the wonderful things that SharePoint does, except, most of the integrators doing the selling are telling you about things that have to added on to the system.
SharePoint workflow sucks donkey balls. Don't sell it to your users, its out-of-the-box and not worth the time they put into. Go with Nintex or K2 for SharePoint workflow.
Also, we have had a major issue with an integrator and then asked them to set up Performance Point, Google Earth, and CorasWorks. They have yet to get it working right. I really wish I could tell you their name so you could avoid them, but I can't. But, I do know the USMC and USAF have similar farms that are well integrated and working fine. We got screwed by the "partner" we went with.
I've gone to a lot of code camps, seminars, and other functions, and anectdotal evidences seems to indicate that most companies that have problems with SharePoint is because they went with a crappy integrator, or they handed the install manuals to someone in their IT department and said, "Go" without sending them to training.
MOSS: Microsoft Office SharePoint Services (This is the for pay SharePoint with extra features. WSS: Windows SharePoint Services (This is included in Windows Server 2k3 and 2k8.
Inertia...oops, I put that in the title.
I have a feeling the only browser you used that choked on SharePoint was Opera. You definitely didn't try FF.
Firefox handles SharePoint wonderfully. But, remember, SharePoint makes use of JavaScript, so if you are blocking JavaScript, you have a problem.
In my office, we have a mix of FireFox 2 - 3.x, and IE 6 through 8 (IE 6 is thanks to EDS and NMCI for being behind the curve).
The only time FireFox chokes on SharePoint is because of a non-SharePoint problem, we make heavy use of card based certs and log on, and FireFox doesn't like passing card based authentication, but, there is a U.S. Navy developed open source FF plug in for that. Works fine, lasts long time. In fact, for you open source types, FF plug ins are great way to add functionality to SharePoint sites and make it work even more wonderfully with SharePoint unaware applications.
Most of SharePoint is exposed by web services, and most of the SharePoint feature systems can be modified by some DOM stuff.
I never told a user to STFU. Maybe you are having issues with your company? If your IT folks regularly tell you to STFU, then 1) they aren't worth anything, or 2) you are in need cranalanalectomy.