Comment Re:Teachers are not underpaid (Score 1) 888
How about a teacher with 20yrs experience vs an accountant with 20 yrs?
Submission + - Congress considers bill to make radio "pay to (arstechnica.com)
devjj writes: "Ars Technica is reporting that Congress is considering two bills that will remove the exemption terrestrial radio broadcasters currently enjoy that allows them to broadcast music without compensating the artists or labels for it. Songwriters are paid, but that is it. The National Association of Broadcasters is furious at the RIAA, a vocal supporter of repealing the exemptions, and has responded by agreeing that artists need better compensation. As a result, it is pointing its collective finger at the labels, asking Congress to investigate modern recording contracts.
What do you think? With the NAB up against the RIAA, what do consumers stand to gain or lose?"
What do you think? With the NAB up against the RIAA, what do consumers stand to gain or lose?"
Submission + - Intel announces Open Fibre Channel over Ethernet (open-fcoe.org)
sofar writes: "Intel has just announced and released source code for their Open-FCoE project, which creates a transport that allows native Fibre Channel frames to travel over ordinary ethernet cables to any Linux system. This is an extremely interesting development where datacenters can reduce cost and maintenance by reducing the amount of Fibre Channel equipment and cabling while still enjoying the benefits and performance of Fibre Channel equipment. The new standard for channelling fibre channel frames over ethernet is backed by Cisco, Sun, IBM, EMC, Emulex and a variety of others working in the storage field. The timing of this announce makes sense with 10 Gigabit Ethernet becoming more widespread in the datacenter."
Submission + - How to really bury a mainframe (networkworld.com)
coondoggie writes: "Some users have gone to great lengths to dispose of their mainframe but few have gone this far. On November 21, 2007, the University of Manitoba said goodbye to its beloved 47-year-old IBM 650 mainframe Betelgeuse by holding a New Orleans style jazz funeral. In case you were wondering what an IBM 650's specifications were, according to this Columbia University site, the 650's CPU was 5ft by 3ft by 6ft and weighed 1,966 lbs, and rented for $3200 per month. The power unit was 5x3x6 and weighed 2,972 pounds. The card reader/punch weighed 1,295 pounds and rented for $550/month. The memory was a rotating magnetic drum with 2000 word (10 digits and sign) capacity and random access time of 2.496 ms. For an additional $1,500/month you could add magnetic core memory of 60 words with access time of .096ms. Big Blue sold some 2,000 of the mainframes making it one of the first successfully mass-produced computers.
http://www.networkworld.com/community/node/23123"
Submission + - Microsoft's influence on upcoming ISO vote? (groklaw.net) 2
christian.einfeldt writes: "Microsoft has experienced some criticism for its handling of its bid to have OOXML accepted as an ISO standard, including the use of financial incentives to affect the Swedish national vote, which resulted in Swedent reversing its pro-Microsoft position; and failing to honor a promise to relinquish control of the OOXML specification if it gained ISO status. Now, Groklaw has published an article that raises questions about Microsoft's influence on the upcoming February vote, citing concerns with the limitation of discussions of patent issues, public accountability of the process, and even irregularities with choosing the size of the room so as to limit the delegates opposed to OOXML ISO status, as had been done in the past."
Submission + - Are you proud of your code? 6
An anonymous reader writes: I have a problem and I am hoping /. group therapy is the cure, so get on with the +5 comments, post haste!
I am downright embarrassed by the quality of my work; specifically, my code. It is buggy, slow, fragile, and a nightmare to maintain. Documentation, requirements, automated tests? Does not exist.
Do you feel the same way? If so, then what is holding you back from realizing your full potential? More importantly, what if anything are you planning to do about it?
This picture, which many of you have already seen, captures several project failure modes. It would be humorous if it weren't so depressingly true.
I enjoy programming and have from a young age (cut my teeth on BASIC on an Apple IIe). I have worked for companies large and small in a variety of languages and platforms. Sadly the one constant in my career is that I am assigned to projects that drift, seemingly aimlessly, from inception to a point where the client runs out of funding and the project is abandoned.
Like many young and idealistic university graduates I hoped to spend my life programming passionately, but ten years later I look in the mirror and see a whore. I'm just doing it for the money.
Have any developers here successfully lobbied their company to stop or cut back on 'cowboy coding' and adopt best practices? I'm not talking about the methodology-of-the-week, I'm referring to good old fashioned advice like keeping SQL out of the UI layer. For the big prize: has anyone convinced their superiors that the customer isn't always right and saying no once in awhile is the best course of action?
Thanks in advance for your helpful advice.
Submission + - Corporations face problems with employee e-mails (law.com) 4
TwistedOne151 writes: "Law.com has an article outlining how the casual attitude of many employees toward work e-mails has caused massive problems for coporations' in-house counsels."
Submission + - Is ISP Web Content Filtering Here? 1
unixluv writes: "An ISP is testing web content filtering and content substitution software, see http://lauren.vortex.com/archive/000337.html. While it seems innocent enough, is this the wave of the future? Will your ISP censor your web experience? Now consider it in the context of The MPAA asking for ISP Content Filtering on /. this week. Is the RIAA next? Will this spawn a war of web tools to circumvent ISP tools?"
Submission + - Linux is about to take over the low end of PCs (desktoplinux.com) 3
An anonymous reader writes: Desktop Linux has a recent commentary on the inevitable growth of Linux on the cheaper end of the desktop market. According to the article, the availability of under-$500 usable hardware, combined with free a operating system, free desktop office products, and free or cheap "Software as a service" online applications, opens a new market in which Microsoft cannot compete. "Microsoft will fight this trend tooth and nail. It will cut prices to the point where it'll be bleeding ink on some of its product lines. And Windows XP is going to stick around much longer than Microsoft ever wanted it to. Still, it won't be enough. By attacking from the bottom, where Microsoft can no longer successfully compete, Linux will finally cut itself a large slice of the desktop market pie."
Submission + - CSS Pocket Reference
Michael J. Ross writes: "For Web developers who appreciate the value of separating Web content from its presentation, Cascading Style Sheets (CSS) has proved a godsend, because it allows all of the styling of a Web site to be organized in CSS files separate from the site's semantic content, in HTML files (possibly dynamically generated). Yet to make this styling power possible, CSS must incorporate a long list of syntax elements, including hundreds of selectors, properties, and values. Thus it can be quite handy for the developer to have on hand a concise summary of CSS, such as the CSS Pocket Reference, authored by Eric A. Meyer.
The book was published by O'Reilly Media on 5 October 2007, under the ISBNs 0596515057 and 978-0596515058. CSS itself has evolved along with other Web technologies, and this book is now in its third edition, having been updated to reflect the ongoing changes in CSS; the book now covers CSS2 and CSS2.1. On the book's Web page, O'Reilly offers an online table of contents, as well as ways for the visitor to view and submit errata (none as of this writing) and reviews for the book. Unlike most technical publishers, O'Reilly now makes available previews of their books' contents, in the form of a table of contents with links to the first few paragraphs of each section, including tables and illustrations.
Despite the growth in the number of elements in CSS, and the attention paid to each one of them by the author of CSS Pocket Reference, the book is still small enough to fit in a pocket, at only 168 pages. The book's material is organized into 18 unnumbered sections, preceded by some notes on the book's typographical conventions, and followed by an essential index. The bulk of the material is found in the Property Reference section. Other sections explain how to add styles to HTML and XHTML pages; CSS rule structure and style precedence, including inheritance and the cascade; element classification and display roles; visual layout; rules on floating and positioning; and table layout. Subsequent sections cover CSS value types and units, and selectors, including some of the newest additions to CSS, such as the adjacent sibling selector and the language attribute selector. Just before getting into the details on properties, Eric Meyer discusses pseudo-classes and pseudo-elements, which have made it possible for Web developers to create rather robust and attractive site navigation using CSS exclusively, without any need to resort to images and JavaScript for rollover effects and other navigation eye candy.
For each element of CSS that is covered in all of the sections mentioned above, the types of information presented to the reader can vary, depending upon the category of element. But they generally include the element's possible values, a default value, what elements it can apply to, whether it is inherited, its computed value, a brief description of the element, at least one example illustrating its usage, what browsers support it, and oftentimes a note on its usage. Consequently, this new edition of the book, like its predecessors, should prove more than adequate for most CSS reference needs.
As with any computer book, there are several ways in which this one could be improved. Any reader using the book to look up a particular element, has two possible ways of doing so: They could first consult the index, and, assuming the element is listed there, go straight to the page indicated. But most readers, knowing that the elements in each section are listed alphabetically, will probably open up the book near the front or the back, and begin flipping backward or forward, respectively, hoping to spot the element of interest as quickly as possible, given its alphabetical ordering. That individual will likely immediately spot an obvious problem with the book: The pages have no running titles (the words that indicate the first element discussed on that page, and typically listed at the very top of each page). Inclusion of such running titles in the next edition of the book, would make it much faster to use.
Another valuable addition would be some sort of table listing all of the CSS elements and their level of support within the most commonly used Web browsers and, in the case of Internet Explorer, the most commonly used versions of the browser. Also, on page 48 of the book, at the beginning of the Property Reference section, it has a subhead of "Visual Media," which suggests that there are other subheads within that section, for other media types; but I was unable to find any.
All of these problems concern the publisher's choice of material. My last criticism concerns the layout of that material in the print version of the book. Because this diminutive volume has narrow pages, and they are tightly glued together in the binding, it is imperative that the publisher of such a book provide plenty of white space in the inner margins (those closest to the binding), so the reader does not have to crack open the book too much in order to read the text closest to the binding. Repeatedly opening up the book far enough to read those inmost words, will over time weaken and eventually destroy the binding. In contrast, a small reference book like this has no need for much outer margin. Sadly, O'Reilly got it backwards with this volume, with relatively wide and useless outer margins, and inadequate inner margins.
Aside from the aforementioned flaws — all of which can be remedied in the future — CSS Pocket Reference is a compact and neatly organized gem of a book, packed with information of value to busy Web programmers.
Michael J. Ross is a Web developer, writer, and freelance editor."
The book was published by O'Reilly Media on 5 October 2007, under the ISBNs 0596515057 and 978-0596515058. CSS itself has evolved along with other Web technologies, and this book is now in its third edition, having been updated to reflect the ongoing changes in CSS; the book now covers CSS2 and CSS2.1. On the book's Web page, O'Reilly offers an online table of contents, as well as ways for the visitor to view and submit errata (none as of this writing) and reviews for the book. Unlike most technical publishers, O'Reilly now makes available previews of their books' contents, in the form of a table of contents with links to the first few paragraphs of each section, including tables and illustrations.
Despite the growth in the number of elements in CSS, and the attention paid to each one of them by the author of CSS Pocket Reference, the book is still small enough to fit in a pocket, at only 168 pages. The book's material is organized into 18 unnumbered sections, preceded by some notes on the book's typographical conventions, and followed by an essential index. The bulk of the material is found in the Property Reference section. Other sections explain how to add styles to HTML and XHTML pages; CSS rule structure and style precedence, including inheritance and the cascade; element classification and display roles; visual layout; rules on floating and positioning; and table layout. Subsequent sections cover CSS value types and units, and selectors, including some of the newest additions to CSS, such as the adjacent sibling selector and the language attribute selector. Just before getting into the details on properties, Eric Meyer discusses pseudo-classes and pseudo-elements, which have made it possible for Web developers to create rather robust and attractive site navigation using CSS exclusively, without any need to resort to images and JavaScript for rollover effects and other navigation eye candy.
For each element of CSS that is covered in all of the sections mentioned above, the types of information presented to the reader can vary, depending upon the category of element. But they generally include the element's possible values, a default value, what elements it can apply to, whether it is inherited, its computed value, a brief description of the element, at least one example illustrating its usage, what browsers support it, and oftentimes a note on its usage. Consequently, this new edition of the book, like its predecessors, should prove more than adequate for most CSS reference needs.
As with any computer book, there are several ways in which this one could be improved. Any reader using the book to look up a particular element, has two possible ways of doing so: They could first consult the index, and, assuming the element is listed there, go straight to the page indicated. But most readers, knowing that the elements in each section are listed alphabetically, will probably open up the book near the front or the back, and begin flipping backward or forward, respectively, hoping to spot the element of interest as quickly as possible, given its alphabetical ordering. That individual will likely immediately spot an obvious problem with the book: The pages have no running titles (the words that indicate the first element discussed on that page, and typically listed at the very top of each page). Inclusion of such running titles in the next edition of the book, would make it much faster to use.
Another valuable addition would be some sort of table listing all of the CSS elements and their level of support within the most commonly used Web browsers and, in the case of Internet Explorer, the most commonly used versions of the browser. Also, on page 48 of the book, at the beginning of the Property Reference section, it has a subhead of "Visual Media," which suggests that there are other subheads within that section, for other media types; but I was unable to find any.
All of these problems concern the publisher's choice of material. My last criticism concerns the layout of that material in the print version of the book. Because this diminutive volume has narrow pages, and they are tightly glued together in the binding, it is imperative that the publisher of such a book provide plenty of white space in the inner margins (those closest to the binding), so the reader does not have to crack open the book too much in order to read the text closest to the binding. Repeatedly opening up the book far enough to read those inmost words, will over time weaken and eventually destroy the binding. In contrast, a small reference book like this has no need for much outer margin. Sadly, O'Reilly got it backwards with this volume, with relatively wide and useless outer margins, and inadequate inner margins.
Aside from the aforementioned flaws — all of which can be remedied in the future — CSS Pocket Reference is a compact and neatly organized gem of a book, packed with information of value to busy Web programmers.
Michael J. Ross is a Web developer, writer, and freelance editor."
Submission + - Group hopes to rename street after Douglas Adams.
interstellar_donkey writes: "After the recent brouhaha over the renaming of 4th Ave after César Chávez, a Portland group is pushing to rename a local street after the late writer Douglas Adams. The street? Why, 42nd Ave, of course. According to their website, the renaming will reflect Portlanders' commitment to the arts, respect for the environment, desire to provide technological access to all, their passion to further education to all people, and most importantly remind Portlanders DON'T PANIC. This appears to be a serious movement, with preliminary paperwork already in the works."
Submission + - DRM-Weaver: Mark Pilgrim on The Future of Reading 1
theodp writes: "Using Amazon CEO Jeff Bezos' own words against him, Mark Pilgrim offers his chilling take on The Future of Reading with a mash-up of Bezos' Open Letter to the Authors Guild, the Amazon Kindle Terms of Service, Steven Levy's Newsweek article on the Kindle, 1984, and Richard Stallman's The Right to Read."
Submission + - Is It Time for a "Kinder, Gentler HTML"? (web2journal.com) 2
jg21 writes: Web 2.0 Journal brings to our attention Yahoo! Architect and JSON inventor Douglas Crockford's latest ideas to fix HTML. Not a fan of HTML 5, which is still just an Editor's Draft and not endorsed by W3C yet, Crock puts forward ten ideas that in his view would provide extensibility without complexity, adding that the simplification of HTML he is proposing would reduce the cost of training of web developers and incorporates the best practices of AJAX development. [From the article: "The problems with HTML will not be solved by making it bigger and more complicated. I think instead we should generalize what it does well, while excising features that are problematic. HTML can be made into a general application delivery format without disrupting its original role as a document format."]
Submission + - Canada's new DMCA considered worst copyright law (theglobeandmail.com)
loconet writes: "The government of Canada is preparing to attempt to bring a new DMCA-modeled copyright law in Canada in order to comply with the WIPO treaties the country signed in 1997. These treaties were also the base of the American DMCA. The new Canadian law will be even more restrictive in nature than the American version and worse than the last Canadian copyright proposal, the defeated Bill C-60. Amongst the many restrictive clauses, in this new law — as Michael Geist explains — is the total abolishment of the concept of fair use, "No parody exception. No time shifting exception. No device shifting exception. No expanded backup provision. Nothing.". Michael Geist provides a list of 30 things that can be done to address the issue."
Submission + - Sliding Rocks Baffle Scientists (geology.com) 1
An anonymous reader writes: Scientists can't figure out why these rocks — weighing up to several pounds each — can slide across a dry lake bed. Some blame it on the wind — but it can't be that simple!
Slashdot Top Deals
Per buck you get more computing action with the small computer. -- R.W. Hamming
