Quite the opposite - CMS are a set of systems where vendor lock-in is virtually impossible to archive. Simply put, one major part of content management is content access, often en-masse for large quantities of content, and automated for use with other pieces of software that need that content. They all provide APIs for accessing and dealing with the content, and if not APIs, at least easy to handle outputs.
Sharepoint is a piece of collaboration based software that Microsoft developed. People can jointly work on documents or data stored on the server, and manage the security within their own niches. The design is primarily to give groups or projects their own space, and then give a lot of control over what happens there to the group leader.
While CMS features were mentioned by another user, they are almost an afterthought or byproduct of the other features, rather than the main purpose of this software. It also happens to SUCK for content management, and it's recommended you get another back end content server to store your Sharepoint managed or created data long term.
Choice is a point it already had with Sharepoint. I work a lot with content management systems (sadly), many reports (particularly Gartner) suggest using SharePoint as a front end and something else as the back end for your content storage - and strongly recommend AGAINST using Sharepoint for a content server/storage role. I know where I work (and several other places) use Oracle Universal Content Server to store the data, and SharePoint only when working on it (you could probably integrate just as easily with Drupal or some other content storage system). Getting the content out of these is often easy. In Oracle Universal Content Server, I can use the archiving tool to generate an archive, and then write a simple script in most scripting languages to toss the files into a directory structure that is more end-user friendly, or parse the data for use in importing into another content server.
If you don't know how to use your product, then don't complain about it lacking a feature that it actually has.
Most, yes, but there were a couple leaks (I believe with docs?) that didn't revolve around this.
Anyway, since I've actually been encouraged to do the research, my point can stand without relying on comparison to their security in more long-running products...
Actually, looking over the articles, I believe there are only three distinct flaws reported in this set, but my google search seemed to indicate there are more.
Every 6 months to a year it seems there is yet another goof up that lets users access other users email (gmail) or data (google docs).
While this is still better than the track record on many MS products, it still leads me to suspect the security of Google. Face it, they are good at distributing information, not hiding it... Now, unless *EVERY* Google security hole is already in IE, new holes will be added.
Half of my proprietary software is from Circa 99-03, and I haven't needed to upgrade.
The *only* "upgrade" that I had to do (really a downgrade), was my new notebook couldn't be take an XP install, so I had to use Vista because the vendor doesn't supply XP drivers, and ATI doesn't want to release drivers to notebook users.
I see where you are coming from, but I'll offer that bloat isn't necessarily *bad*. Personally, I've thought of Linux as somewhat to rather bloated for 5 or 6 years.
It just means there are a lot of available features. Many of which people need.
Bloat isn't a problem. In software, it's in a lot of places because that's what you need many (but not all) cases that target a wide audience. The problems come in two flavors. 1) the inability for an individual to turn off the bits he or she doesn't need, and 2) lack of documentation to make ascertaining which bits can be turned off for a particular use a relatively trivial task.
And, pray tell, how is/buying/ this device having it provided for them.
They aren't asking others to provide it for them, they aren't asking that the government assign one for every child. The device is simply available to all who want to purchase it. Much like a computer at at a computer store, or food at a grocery store.
Seriously to the GP: Do you grow your own food, make your own building materials, build every component of all of your devices and then assemble them?
What makes the human race so impressive, so powerful is that we help each other, we work together. We accomplish more as a team than as individuals.
Also, if you think of it,/this is a self reliance device/. Now, you can have a resource (not given to you, but bought, from your [hopefully] earned money) to solve your problem. You don't have to go around asking strangers "have you seen this kid", etc.
You can't watch your child every moment of every day (not if you have a job). This is a nice advance for helping yourself in doing an at-minimum decent job at raising your kids.
Yes, but the child may not know the parent can find them.
The child could be lost a lot longer before the parents are worried (the child is not lost to the parents, but the child doesn't know that), therefore actually *enhancing* the educational experience for the child.
Seriously, aside from the price, it isn't invasive, and it does help the parents do their jobs.
PC-BSD/is/ FreeBSD with some extra userland tools added on. I'm not sure it's worth calling another BSD. The rest at least have significant differences at lower levels of the OS, and not just a few extra packages installed.
And where, pray tell, did you get THAT load of tripe? I'm a BSD fan and all, but to think that NT will switch to a BSD base, is absurd, Android less so, but still ridiculous, and Mac I can't see switching from it's Mach/FreeBSD hybrid that works so well for it.
I couldn't get 5.x to install. 6.x and 7.x have been very stable fore me under high load. That being said, from what I hear the problem requires an 8+ CPU system and most/all of the CPUs under high load. I've only got single and dual core systems.
Two things: the irradiation you are talking about is done after harvest, right? (Not that this farmer isn't being silly, the amount of radiation will be mostly harmless, and since the main reproductive and sustenance parts of garlic are under ground, his crop will have some shielding).
And DC being expendable? Usually you use the term "expendable" for a valuable resource that can be lost permanently for a short term advantage. That statement makes the assumption that we get some kind of value out of the folks in DC...
Slashdot Mirror
Anyway, at least it's not a cup...
I mean one that's placed lower.
I think I'd rather suffer the gas.
we use Sharepoint with non-ms products, it's just not offered out of the box. It's not hard to get set up though.
Quite the opposite - CMS are a set of systems where vendor lock-in is virtually impossible to archive. Simply put, one major part of content management is content access, often en-masse for large quantities of content, and automated for use with other pieces of software that need that content. They all provide APIs for accessing and dealing with the content, and if not APIs, at least easy to handle outputs.
Sharepoint is a piece of collaboration based software that Microsoft developed. People can jointly work on documents or data stored on the server, and manage the security within their own niches. The design is primarily to give groups or projects their own space, and then give a lot of control over what happens there to the group leader.
While CMS features were mentioned by another user, they are almost an afterthought or byproduct of the other features, rather than the main purpose of this software. It also happens to SUCK for content management, and it's recommended you get another back end content server to store your Sharepoint managed or created data long term.
FUD.
Choice is a point it already had with Sharepoint. I work a lot with content management systems (sadly), many reports (particularly Gartner) suggest using SharePoint as a front end and something else as the back end for your content storage - and strongly recommend AGAINST using Sharepoint for a content server/storage role. I know where I work (and several other places) use Oracle Universal Content Server to store the data, and SharePoint only when working on it (you could probably integrate just as easily with Drupal or some other content storage system). Getting the content out of these is often easy. In Oracle Universal Content Server, I can use the archiving tool to generate an archive, and then write a simple script in most scripting languages to toss the files into a directory structure that is more end-user friendly, or parse the data for use in importing into another content server.
If you don't know how to use your product, then don't complain about it lacking a feature that it actually has.
Actually, those are Chrome security flaws that I posted (one crash, two remote code execution), not google apps flaws.
Most, yes, but there were a couple leaks (I believe with docs?) that didn't revolve around this.
Anyway, since I've actually been encouraged to do the research, my point can stand without relying on comparison to their security in more long-running products...
flaw flaw flaw. flaw.
Actually, looking over the articles, I believe there are only three distinct flaws reported in this set, but my google search seemed to indicate there are more.
Just considering the companies track record since it seems to apply well with cross-product security. But if you want chrome security flaws. Ok.
Every 6 months to a year it seems there is yet another goof up that lets users access other users email (gmail) or data (google docs).
While this is still better than the track record on many MS products, it still leads me to suspect the security of Google. Face it, they are good at distributing information, not hiding it... Now, unless *EVERY* Google security hole is already in IE, new holes will be added.
Sure it tidies up the browser. In the same way a fresh coat of cow shit will tidy up the inside of your house.
I love you.
Half of my proprietary software is from Circa 99-03, and I haven't needed to upgrade.
The *only* "upgrade" that I had to do (really a downgrade), was my new notebook couldn't be take an XP install, so I had to use Vista because the vendor doesn't supply XP drivers, and ATI doesn't want to release drivers to notebook users.
I see where you are coming from, but I'll offer that bloat isn't necessarily *bad*. Personally, I've thought of Linux as somewhat to rather bloated for 5 or 6 years.
It just means there are a lot of available features. Many of which people need.
Bloat isn't a problem. In software, it's in a lot of places because that's what you need many (but not all) cases that target a wide audience. The problems come in two flavors. 1) the inability for an individual to turn off the bits he or she doesn't need, and 2) lack of documentation to make ascertaining which bits can be turned off for a particular use a relatively trivial task.
The electrical components can get smaller without shrinking the phone. Just more empty space, or mayb e a larger battery. Possibly even a faster CPU.
I want a cell phone that can run my chosen desktop with my chosen word processing software, web browser and a few other productivity apps.
Let me guess, the user name will be your card number, and the PIN will be it's relationship status?
And, pray tell, how is /buying/ this device having it provided for them.
They aren't asking others to provide it for them, they aren't asking that the government assign one for every child. The device is simply available to all who want to purchase it. Much like a computer at at a computer store, or food at a grocery store.
Not just widges - food!
Seriously to the GP: Do you grow your own food, make your own building materials, build every component of all of your devices and then assemble them?
What makes the human race so impressive, so powerful is that we help each other, we work together. We accomplish more as a team than as individuals.
Also, if you think of it, /this is a self reliance device/. Now, you can have a resource (not given to you, but bought, from your [hopefully] earned money) to solve your problem. You don't have to go around asking strangers "have you seen this kid", etc.
You can't watch your child every moment of every day (not if you have a job). This is a nice advance for helping yourself in doing an at-minimum decent job at raising your kids.
Yes, but the child may not know the parent can find them.
The child could be lost a lot longer before the parents are worried (the child is not lost to the parents, but the child doesn't know that), therefore actually *enhancing* the educational experience for the child.
Seriously, aside from the price, it isn't invasive, and it does help the parents do their jobs.
PC-BSD /is/ FreeBSD with some extra userland tools added on. I'm not sure it's worth calling another BSD. The rest at least have significant differences at lower levels of the OS, and not just a few extra packages installed.
And where, pray tell, did you get THAT load of tripe? I'm a BSD fan and all, but to think that NT will switch to a BSD base, is absurd, Android less so, but still ridiculous, and Mac I can't see switching from it's Mach/FreeBSD hybrid that works so well for it.
I couldn't get 5.x to install. 6.x and 7.x have been very stable fore me under high load. That being said, from what I hear the problem requires an 8+ CPU system and most/all of the CPUs under high load. I've only got single and dual core systems.
It'd have been $100k if they gave him the appropriate machine (serial number #F4200NUM1701)
I think it would have been worth making that the first model, and skipping that number in normal production...
Two things: the irradiation you are talking about is done after harvest, right? (Not that this farmer isn't being silly, the amount of radiation will be mostly harmless, and since the main reproductive and sustenance parts of garlic are under ground, his crop will have some shielding).
And DC being expendable? Usually you use the term "expendable" for a valuable resource that can be lost permanently for a short term advantage. That statement makes the assumption that we get some kind of value out of the folks in DC...
Except there ARE NK resistant cancers. While this would work on most, it's still not a silver-bullet.
Correct, but if the cancer isn't recognized by the NK cells as foreign, then they won't be effective.