We have SharePoint 2003 - in document terms it's mainly document storage (.doc.xls etc), it's a poor CMS, and has poor doc management built in. It wins because of the high integration with the office system. MOSS 2007 should improve on many areas that 2003 was lacking - including some Wiki abilities - but I have no exp. with that. If you're looking for similar office integration with OpenOffice take a look at: http://www.o3spaces.com/ - I have not tried this in production - but looks promising.
Pluses: fast, easy to use and user friendly, permission management through the web(!!), integration to Windows Active directory (with multiple sub domains) Minuses: ? flat file storage?. This is really a point of view thing. My first aim was DB storage only - but dokuwiki surprised on other ends so we took it. I don't see real performance issues because of file storage, but you lack some features you'd get if you were running a DB...
If you're looking into commercial Wiki - I was also impressed by Confluence - which would probably be my choice if I had to spend money on a Wiki today. http://www.atlassian.com/software/confluence/
Up until I read this article on Slashdot, I had never heard of Blender. Having no prior knowledge of what you're talking about, I couldn't make out what this thing is from the first few lines of the article in/.
Okay then - I clicked their website. There's nothing on the front page to the extent of: "Blender is a..."
Just a short paragraph will do - thank you. If you go to "features" page - there's nothing like that there as well. If you start reading the feature list you can see it's a 3D rendering program - but why can't they just write that?!
I see that on many Open Source projects. "Everyone" already knows what Blender is - so why bother writing a line or two at the top of the main page? Many a good project don't give information and you have to dig deep to find this simple information.
Your post says 1000 MARRIED women while the study says 1000 DVR users divided equally by sex.
This is a key point here: a. You're surveying both men and women (which might seem obvious, but not from your post) - which is important because you're trying to claim to compare men and women habits - right? You can't do that if you only survey women.
b. You're surveying a specific slice of people: those who bought DVRs - this already profiles the people you're surverying: certain income range, certain education, affiliation with technology, and so on...
What's my point? Your post suggests that you can deduce on women vs men in general (see 'hunter-gatherer' post above...) - which is wrong: the target slice in society your "studying" is a specific group with very specific characteristics, and I don't think you can project from it on the whole group. The conclusions the survey makes can only be safely applied to DVR owners.
What your post suggests is quite different than the origianl article. Dan
Just imagine the impact of your kid breaking a window now. "No TV tonight, junior..."
Or having a "dead" pixel (or line) in your "window". The cleaning-lady spends 5 bottles of windex trying to get that one off...
Hey, I can't even roll my shades up when the electricity is out, imagine sitting in the dark in your room, when there's full sunlight out there, because the LCD is opaque and there's a power outage...
DUH! Did anyone ever look at the bluetooth "server-client" protocol? This was designed by sales people to operate exactly the opposite than normal server-client schema - just for the use you're describing in the article.
In normal server-client, the client contacts the server for the requested service (HTTP,SMTP,whatever)- With bluetooth, the server knows there are clients around it, and is allowed to contact them to initialize a service (in this case - sending you a message). This is a protocol-level feature, and today is only stopped (or filtered) at application level.
Imagine you're surfing the net, and instead of you contacting a web server, web servers are contacting you asking you: "do you want to surf here?" That is how bluetooth was designed to work. It is the ultimative sales tool by design.
They can -> don't you know that given enough time any group will split into small parts and start a war with each other? Oh, so you haven't been to the middle east lately....
But you got to admit that the ER5 site does have a fascist ring about it. And that IS something to worry about. As much as I disagree with MPAA/RIAA or the movie industry - I don't intend on taking a fascist route any time soon....
1) Serious Linux companies are losing money due to SCO. SCO is basically taking business away from Linux. Sure, it's a big load of.... but in the short term SCO will make some cash, and even worse - Linux companies will lose cash, and that will weaken the competition, which is what SCO really wants. (in my opinion.)
2) I don't know if any of you noticed, but people make money out of air, epsecially hot air, this is what makes stock markets tick, and share rise: the added value of image - sometimes even more than what the real product is worth.
If you think of SCO's move in that term, the agressive move is just about that. People out there don't care that the idea is bogus, they just marvel at how brilliantly agressive the move is by itself. Apparently, that's enough to make your stock rise, which literaly means $$$ for SCO.
Now if you look at it from the PR stunt point of view, Red Hat is just jummping on the bandwagon there, not only because SCO's PR hurts Linux, but also because there is lots of money to be made there, stock market people love agressive behavior.
So poor Red Hat is not that little David standing up to Golaiath as it may first seem.
Sure, everyone pees in the pool, but not from the diving board!
With all the 'subtle' flames about GPL "justice" being served, etc. Ask yourself 1 thing: If tomorrow someone like nVidia replies with "f**k you, I'll use code as I please." - what are you going to do about it? I mean, besides falming for a few weeks, is anyone here going to open his computer and rip out that nVidia card he's using? is anyone here going to take legal action? hey, SlashDot - do a poll on this - I really want to know what readers will do. Because as much as I agree with GPL, and it think it's the way to go, I can be honest enough with myself and know that I will not stop using the two nVidia cards I currently use, at maximum I will make some noise, and thats it. This means that nVidia can do what they want, as long as they can take the public "heat", and a few zealots suing at court.... which brings me to my second, and most important point:
FSF and GNU bring a new way of looking at code, it breaks the rules of code=money, it plays on a different playing field than the software companies that want to make money, this is one of the most important revolutions FSF & GNU brought to this world, this is one of the reasons Linux is such a threat to M$, because for once M$ can't play in the monetary realm to bring Linux down. I see this as the strongest point of FSF/GNU: not playing the petty game of code=money, but there's a problem here, as you can see from the cases of nVidia and ABit: how can GNU code writers protect and enforce their own license without stepping into the realm of code=money? When you're suing over your code, you're forced back into playing the game FSF/GNU is trying to avoid - doesn't that defeat the whole purpose?
Slashdot Mirror
We have SharePoint 2003 - in document terms it's mainly document storage (.doc .xls etc), it's a poor CMS, and has poor doc management built in.
It wins because of the high integration with the office system.
MOSS 2007 should improve on many areas that 2003 was lacking - including some Wiki abilities - but I have no exp. with that.
If you're looking for similar office integration with OpenOffice take a look at: http://www.o3spaces.com/ - I have not tried this in production - but looks promising.
We also have dokuWiki as a separate service:
http://wiki.splitbrain.org/wiki:dokuwiki
Pluses: fast, easy to use and user friendly, permission management through the web(!!), integration to Windows Active directory (with multiple sub domains)
Minuses: ? flat file storage?. This is really a point of view thing. My first aim was DB storage only - but dokuwiki surprised on other ends so we took it. I don't see real performance issues because of file storage, but you lack some features you'd get if you were running a DB...
If you're looking into commercial Wiki - I was also impressed by Confluence - which would probably be my choice if I had to spend money on a Wiki today.
http://www.atlassian.com/software/confluence/
Hope this helps...
Dan
Oh... I see - so THAT'S the Nigerian Scam 8-)
whoops
My Bad
I've just noticed the first link directs to the downloads page, and that the home page IS VERY informative.
D
Up until I read this article on Slashdot, I had never heard of Blender. /.
Having no prior knowledge of what you're talking about, I couldn't make out what this thing is from the first few lines of the article in
Okay then - I clicked their website. There's nothing on the front page to the extent of:
"Blender is a..."
Just a short paragraph will do - thank you.
If you go to "features" page - there's nothing like that there as well. If you start reading the feature list you can see it's a 3D rendering program - but why can't they just write that?!
I see that on many Open Source projects. "Everyone" already knows what Blender is - so why bother writing a line or two at the top of the main page? Many a good project don't give information and you have to dig deep to find this simple information.
Dan
Your post says 1000 MARRIED women while the study says 1000 DVR users divided equally by sex.
This is a key point here:
a. You're surveying both men and women (which might seem obvious, but not from your post) - which is important because you're trying to claim to compare men and women habits - right? You can't do that if you only survey women.
b. You're surveying a specific slice of people: those who bought DVRs - this already profiles the people you're surverying: certain income range, certain education, affiliation with technology, and so on...
What's my point? Your post suggests that you can deduce on women vs men in general (see 'hunter-gatherer' post above...) - which is wrong: the target slice in society your "studying" is a specific group with very specific characteristics, and I don't think you can project from it on the whole group. The conclusions the survey makes can only be safely applied to DVR owners.
What your post suggests is quite different than the origianl article.
Dan
Just imagine the impact of your kid breaking a window now. "No TV tonight, junior..."
Or having a "dead" pixel (or line) in your "window". The cleaning-lady spends 5 bottles of windex trying to get that one off...
Hey, I can't even roll my shades up when the electricity is out, imagine sitting in the dark in your room, when there's full sunlight out there, because the LCD is opaque and there's a power outage...
Yep, I'd buy one of those, thanks.
DUH! Did anyone ever look at the bluetooth "server-client" protocol? This was designed by sales people to operate exactly the opposite than normal server-client schema - just for the use you're describing in the article.
In normal server-client, the client contacts the server for the requested service (HTTP,SMTP,whatever)- With bluetooth, the server knows there are clients around it, and is allowed to contact them to initialize a service (in this case - sending you a message). This is a protocol-level feature, and today is only stopped (or filtered) at application level.
Imagine you're surfing the net, and instead of you contacting a web server, web servers are contacting you asking you: "do you want to surf here?" That is how bluetooth was designed to work. It is the ultimative sales tool by design.
They can
-> don't you know that given enough time any group will split into small parts and start a war with each other? Oh, so you haven't been to the middle east lately....
But you got to admit that the ER5 site does have a fascist ring about it. And that IS something to worry about. As much as I disagree with MPAA/RIAA or the movie industry - I don't intend on taking a fascist route any time soon....
I think you're missing two important points here:
.... but in the short term SCO will make some cash, and even worse - Linux companies will lose cash, and that will weaken the competition, which is what SCO really wants. (in my opinion.)
1) Serious Linux companies are losing money due to SCO. SCO is basically taking business away from Linux. Sure, it's a big load of
2) I don't know if any of you noticed, but people make money out of air, epsecially hot air, this is what makes stock markets tick, and share rise: the added value of image - sometimes even more than what the real product is worth.
If you think of SCO's move in that term, the agressive move is just about that. People out there don't care that the idea is bogus, they just marvel at how brilliantly agressive the move is by itself. Apparently, that's enough to make your stock rise, which literaly means $$$ for SCO.
Now if you look at it from the PR stunt point of view, Red Hat is just jummping on the bandwagon there, not only because SCO's PR hurts Linux, but also because there is lots of money to be made there, stock market people love agressive behavior.
So poor Red Hat is not that little David standing up to Golaiath as it may first seem.
Sure, everyone pees in the pool, but not from the diving board!