This is the book of the blog Python Module of the Week, so you can get a look at the content there.
Hugh Pickens writes "PC Magazine reports that the licensing company overseeing the HDMI specification has confirmed that existing Mini DisplayPort-to-HDMI adapters which are designed by several cable makers and sold by several PC OEMs, are apparently illegal and could be recalled. According to Charlene Wan, director of marketing for HDMI LLC, any cable that does not include HDMI connectors on both ends violates the specification. 'The HDMI specification defines an HDMI cable as having ONLY HDMI connectors on the ends,' says Wan. 'Anything else is not a licensed use of the specification and therefore, not allowed.' That apparently includes Apple's mini-DisplayPort-to-HDMI adapters, which are sold by Belkin on Apple's Web site. However a representative for Belkin denies that the cable it sells on Apple's Web site is illegal. 'Essentially, the product you mention in your post is not out of compliance because it is just an adaptor and not a cable,' the representative wrote in an email. 'We do not sell a cable with a male Mini-DP and male HDMI port, which is what falls out of compliance with the spec. HDMI does recognize a product that has a Mini-DP connector and HDMI receptacle with an internal active circuitry as it falls into the definition of a source device.' There may also be a glimmer of hope, in that HDMI Org understands that there is a need for this type of cable: 'We do recognise that there may be a market need for a cable solution rather than a dongle solution. However, at this time, there is no way to produce these cable products in a licensed manner.'"
Thank you...and thanks to your governments for opening the back road through Rendija again. I bailed to Albuquerque Sunday night; not much to do now but follow the news and hope I have a house when we go back.
And the Pentium one was obviously a joke on the FDIV bug...
Reading that page in context, he's delivering a talk entitled "An Earthshaking Announcement". That doesn't necessarily mean he's making an earthshaking announcement.
Thank you for sparing me that
:) We've had "slashdot is dead" thread drift ever since the "what's this slashdot BS, I miss chips & dips" babble died down.
levell writes "Alex Brown, Convenor of the Ballot Resolution Meeting on OOXML, has written a blog post saying that Microsoft is failing the standards test. Mr. Brown notes: 'In its pre-release form Office 2010 supports not the approved Strict variant of OOXML, but the very format the global community rejected in September 2007, and subsequently marked as not for use in new documents — the Transitional variant. Microsoft are behaving as if the JTC 1 standardisation process never happened, and using technologies (like VML) in a new product which even the text of the Standard itself describes as "deprecated" and "included... for legacy reasons only"...' He also says that defects are being fixed very slowly and that 'Looking at the text, I reckon it is more like 95% that remains to be done, as it is still lousy with defects.' It's an insightful look at what has happened with OOXML since ISO approved it from someone who was not opposed to its becoming a standard."
I think it works better if you don't divide by six...
Directing people to a third-party service which doesn't provide source counts as a "proprietary solution" to me. I understand more and more where Debian's apparent fanaticism about "freedom" comes from, slippery slope and all that.
arkowitz writes "I happened to have access to five days worth of firewall logs from a US state government agency. I wrote a parser to grab unique IPs out, and sent several million of them to a company called Quova, who gave me back full location info on every 40th one. I then used Green Phosphor's Glasshouse visualization tool to have a look at the count of inbound packets, grouped by country of origin and hour. And it's freaking crazy looking. So I made the video of it and I'm asking the Slashdot community: What the heck is going on?"
Agreed, in spades. Wasting ten (or more) minutes of the seventy on violence-against-women "jokes" seriously undermines an otherwise solid argument. NSFW tag is one thing, what about a trigger warning?
Note the name of the Wikimedia counsel...I have to wonder if it's that Mike Godwin.
The X-15 used rocket engines (carried its own oxidizer). This is a jet, using oxygen from the air.
An anonymous reader writes 'At my company, our mis-implementation of Agile includes the employment of some of our most highly-paid, principal engineers as ScrumMasters. This has effectively resulted in a loss of those engineering functions as these engineers now dedicate their time to ScrumMastery. Furthermore, the ScrumMasters either cannot or do not separate their roles as Team Leads with those of ScrumMastery and — worse — seem to be completely unaware that this poor implementation of Agile development is harmful to our velocity. To date, I have chalked this up to poor leadership, a general lack of understanding of Agile, and an inability to change from traditional roles left over from the waterfall development mode. In addition, I have contended that, for a given Scrum Team, the role of ScrumMaster should be filled by someone of lower impact, such as an intern brought in specifically for that purpose. But I would like to put the questions to Slashdotters as to whether they have seen these same transitional difficulties, what the results have been at their respective companies, or whether they just plain disagree with my assertion that principal engineers should not be relegated to the roles of ScrumMasters.'