I just wanted to share a (hopefully soon-to-be) Linux success story.
A coworker came by asking me if I had any experience with Linux servers.
I was expecting a technical question, or a request for assistance, so I conservatively answered that I know a moderate amount.
Instead of the expected tech-support, he tells me that the Windows file server he runs in our lab is starting to die. He's going to replace the system with a new one, and wanted to know if Linux could behave like a Windows file server.
I told that samba would do what he needed. He said that was great because Linux was cheaper and that was it.
It's nice to be able to help our company save money.
Linux Binder
A coworker came by asking me if I had any experience with Linux servers.
I was expecting a technical question, or a request for assistance, so I conservatively answered that I know a moderate amount.
Instead of the expected tech-support, he tells me that the Windows file server he runs in our lab is starting to die. He's going to replace the system with a new one, and wanted to know if Linux could behave like a Windows file server.
I told that samba would do what he needed. He said that was great because Linux was cheaper and that was it.
It's nice to be able to help our company save money.
Linux Binder
And I just can't see interpreted bycode being more efficient than compiled-to-the-processor
code. I just can't.
Why don't they just run one of those java to native compilers. If they're not keeping to any spec where you can share the bytecode anyway, what's th epoint?
Why don't they just run one of those java to native compilers. If they're not keeping to any spec where you can share the bytecode anyway, what's th epoint?
Pity... I used wave on rare occasions. I think it could have gone somewhere if they had promoted it a little differently.
Why don't they just run one of those java to native compilers. If
they're not keeping to any spec where you can share the bytecode
anyway, what's th epoint?
Actually, that could be kind of cool -- the app is distributed as bytecode, but compiles to native code when the app is installed to the mobile device.
Kind of like distributing source code except with less room for things to go wrong.
Hey, look at it this way: at least they didn't decide to develop apps in FORTH.
Buncha obsolete wankers and their outdated embedded systems :)
Buncha obsolete wankers and their outdated embedded systems :)
Google Go would probably have some advantages as an embedded systems language...
It was supposed to be the Next Big Thing but I don't think anyone ever figured
out what it was useful for.
That's the thing, they were pushing a product w/o a need. Features that nobody
thinks they can use now. Thing is though, I used wave a bit and it really
did have serious potential. It re-worked they way people could have used e-mail
to communicate. It re-defined e-mail. Add a person into an existing conversation
and they get the ability to read/view the convo from the begining, including
any attatchments.
VERY useful features for biz; esp. when working on a project and add'l people are brought in to work on it, either from outside (consulting) or inside the corporation.
VERY useful features for biz; esp. when working on a project and add'l people are brought in to work on it, either from outside (consulting) or inside the corporation.
Well, the biggest problem with Wave, perhaps, is that it's centrally managed.
If businesses had their own Wave engine, where all their data remained at their facility, it might be more compelling.
Well, they did publish the protocol, and a bunch of code. If it had taken
off there would have been a lot of software able to host it. I had observed
that if it became huge, we would have built Wave support into Citadel. Even
the folks at Lotuss and Microsoft could have played.
I can see a problem with add-somebody-to-a-conversation-later features.
I realize its the same thing as adding somebody to a reply all chain, but if that became the standard way of doing things, it make make it so much of a habit that people would add the wrong person not having seeing the bad comment made in their direction.
I realize its the same thing as adding somebody to a reply all chain, but if that became the standard way of doing things, it make make it so much of a habit that people would add the wrong person not having seeing the bad comment made in their direction.
Aug 8 2010 11:02pm from fleeb @uncnsrd
Of course, that problem exists now.
Right, except that with Google Wave, all of the attachments that were part of a "wave became accessible to new participants of the wave. Oh, and you
could also have public and private waves, and wavelets. I got a little confused as to what constituted a wave versus a wavelet but the whole thing was just cool.
There was one point where I shared a video with people, when Wave first started coming out. And instead of having to eat up bandwidth and take up more storage space in my webmail account by forwarding the same file to new people as they entered the convo, they were able to view the video (and all comments from the beginning) just by joining the wave. That just had a coolness factor of like a Googolplex!
That's great, but it seems that Wave doesn't do that any better than any traditional
message board, or even a blog. The added functionality of seeing everyone
update the conversation in real time has coolness factor, but does it really
add any value?
You actually were able to "replay" the entire conversation from the beginning,
and watch as people joined & contributed to the conversation.
Not only valueless, but it may actually be a liability. I would compare it
to the problems that began to surface when it became common to send word processing
documents as email attachments, and unwittingly created situations where the
entire undo history was viewable. ooooops.