With all of the chatter about the merits and viability of the tax credit, I'm surprised at the lack of comment on the preamble. Regardless whether the proposed legislation makes it, as a resident of NYS, I'm really encouraged to hear that the Assembly "Gets It" when it comes to *using* OSS. That's not "proposed" -- they've already made OSS a significant part of how they get things done. This is a *huge* win in mindset, and will have positive effects (even indirect ones) beyond any small tax credit.
I haven't looked carefully at the rest of the platforms that Yahoo provides, but I believe that at least Yahoo Messenger (when connecting with Pidgin anyway) also sends the same auth credentials in plain text. Not that the overall problem is insignificant (*any* time auth credentials are sent, in any context, they should be encrypted), but worrying only about IMAP is naive in this case. (What about POP? What about all the Y! web platforms?)
As an engineer / architect who has had to deal with some frustrating management (most of it indirect, fortunately), I've found these two blogs to be both enlightening and useful for feeding to managers. Rands especially, as a developer who moved into management with a purpose, has some very insightful commentary. He's also recently published a book, which I'm planning on giving to some of my favorite managers (who despite their sincere desire to treat us well, sometimes have a hard time understanding the geeks they herd.)
Unfortunately, you don't care enough to understand the situation. There's nothing to fix. 64-bit userland would only benefit a very very few apps (that needed more than 4GB of RAM), and would significantly slow down the rest of them. (I was actively subscribed to the debian-sparc mailing list for several years. Do some research, and talk to the sparc linux maintainers.)
I expect that this will come out in one of the promised followup articles on OSNews.
Slashdot Mirror
With all of the chatter about the merits and viability of the tax credit, I'm surprised at the lack of comment on the preamble. Regardless whether the proposed legislation makes it, as a resident of NYS, I'm really encouraged to hear that the Assembly "Gets It" when it comes to *using* OSS. That's not "proposed" -- they've already made OSS a significant part of how they get things done. This is a *huge* win in mindset, and will have positive effects (even indirect ones) beyond any small tax credit.
--
It must be bunnies.
I haven't looked carefully at the rest of the platforms that Yahoo provides, but I believe that at least Yahoo Messenger (when connecting with Pidgin anyway) also sends the same auth credentials in plain text. Not that the overall problem is insignificant (*any* time auth credentials are sent, in any context, they should be encrypted), but worrying only about IMAP is naive in this case. (What about POP? What about all the Y! web platforms?)
As an engineer / architect who has had to deal with some frustrating management (most of it indirect, fortunately), I've found these two blogs to be both enlightening and useful for feeding to managers. Rands especially, as a developer who moved into management with a purpose, has some very insightful commentary. He's also recently published a book, which I'm planning on giving to some of my favorite managers (who despite their sincere desire to treat us well, sometimes have a hard time understanding the geeks they herd.)
f tware-Engineering/dp/159059844X)
Rands on Management: http://www.randsinrepose.com/cat_management.html
Rands's Book: http://managinghumans.com/ (Direct to Amazon: http://www.amazon.com/Managing-Humans-Humorous-So
Joel on Software: http://www.joelonsoftware.com/
Good luck! It's great to hear about people who care enough to want to do it right.
Unfortunately, you don't care enough to understand the situation. There's nothing to fix. 64-bit userland would only benefit a very very few apps (that needed more than 4GB of RAM), and would significantly slow down the rest of them. (I was actively subscribed to the debian-sparc mailing list for several years. Do some research, and talk to the sparc linux maintainers.)
I expect that this will come out in one of the promised followup articles on OSNews.
If it's been released into the public domain, why does it need to be "Open Sourced"?
Why doesn't sucks.com just sell {companyname}.sucks.com for a nominal fee to serious people who want to bitch? Could the WIPO touch that?
For that matter, why aren't there more places that sell single names or sub-namespaces? I don't really need a whole primary domain to myself...