| DISABLE AUTO REFRESH
 
ALEX HANDY'S BLOG

Alex Handy, Senior Editor of SD Times, is a veteran technology journalist. He began his career at a local newspaper, and has since then held editorships at MacHome Journal, Computer Gaming World, and Game Developer Magazine.

His work has appeared in Wired, the Atlanta Journal Constitution, the Austin American Statesman, Gizmodo.com, Computer Games Magazine, Information Security Magazine, MacAddict, GameSpot, the East Bay Express and Gamasutra.com.

Alex lives in the San Francisco Bay Area, where he serves full time as BZ Media's resident conference tourist.

 

Google gets smacked

by Alex Handy 05/07/2012 03:01 PM EST

After all of that noise and tumult, the Oracle versus Google lawsuit is reaching the end of its first phase. First phase, I say, because Google is already asking to have a mistrial declared. The jury had been unable to bring a unanimous verdict to the court on all counts, but today, they brought in a major win decision for Oracle.

The jury found that Google violated Oracle's copyright by copying the Java API calls in Android. And, hoooo boy, we could debate for months on the validity of this decision. But at its core, it shows us that all those crazy years of licenses, Java development and TCK's meant basically nothing until right now when a court has actually had to consider all those lawyer-infused pages of licensing agreements and JCP legalese.

In the end, I predict this whole thing will result in money changing hands and no real damage to Android in the long term. But this could also be seen as a chilling realisation for companies around the world that you now must absolutely use only the proper distributed version of a language, or else you could be sued.

Google has issued a statement: "We appreciate the jury's efforts, and know that fair use and infringement are two sides of the same coin. The core issue is whether the APIs here are copyrightable, and that's for the court to decide. We expect to prevail on this issue and Oracle's other claims."

And, as has been the case throughout this trial, Groklaw has covered the whole sordid affair more thoroughly and completely than anyone else could ever hope to accomplish.

Hacker News, as well, has good commentary, which boils down to the following: Google is accused of copying the range checking code for their implementation of a Timsort in Android. Timsort is a standard sorting algorithm, and it's actually one of the default sorting methods in Python. Are we really surprised a jury composed of non-developers didn't quite understand that an algorithm's implementation across different applications is likely to be quite similar. Kind of like how a hamburger is always going to have two buns and meat between them?

The sum total of the jury's decision rests on the fact that the code for range checking in Timsort in both the JDK and in Android is the same:

From OpenJDK:

private static void rangeCheck(int arrayLen, int fromIndex, int toIndex) {

        if (fromIndex > toIndex)

            throw new IllegalArgumentException("fromIndex(" + fromIndex +
                       ") > toIndex(" + toIndex+")");

        if (fromIndex < 0)
            throw new ArrayIndexOutOfBoundsException(fromIndex);

        if (toIndex > arrayLen)
            throw new ArrayIndexOutOfBoundsException(toIndex);

    }

From Google:

private static void rangeCheck(int arrayLen, int fromIndex, int toIndex) {

        if (fromIndex > toIndex)
            throw new IllegalArgumentException("fromIndex(" + fromIndex +
                       ") > toIndex(" + toIndex+")");

        if (fromIndex < 0)
            throw new ArrayIndexOutOfBoundsException(fromIndex);

        if (toIndex > arrayLen)
            throw new ArrayIndexOutOfBoundsException(toIndex);

    }

}

Yeah, they're the same, but if the whole case over infringement and copyright violation comes down to less than 10 lines of code, in amongst millions of other dissimilar lines, it's tough to swallow. I sincerely doubt this lawsuit is truly over.

Currently rated 1.3 by 6 people

  • Currently 1.333333/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/2004

Tags: , ,

java

Here's the nitty gritty on the update from Oracle:

The Java SE 7 Update 4 JDK includes the next-generation Garbage Collection algorithm, Garbage First (G1). G1 provides predictable garbage collection even for very large applications.

Java SE7 Update 4 contains numerous performance enhancements to the JVM.

With the release of Java SE 7 Update 4, all of the performance enhancements available in Oracle JRockit have been merged into Oracle Java HotSpot and OpenJDK, the open source Java SE implementation.

Java SE 7 Update 4 will be the first consumer release of the Java 7 JRE, scheduled to be made available as the default version on Java.com starting on May 1, 2012.

JavaFX 2.1

JavaFX 2.1 introduces playback support for digital media stored in the MPEG-4 multimedia container format containing H.264/AVC video and Advanced Audio Coding (AAC) audio.

New WebView support for JavaScript to Java method calls, which allows a user to render HTML/JavaScript and allow JavaScript (in WebView) make calls to Java APIs to offload specific operations to Java.

The JavaFX 2.1 release adds enhanced font rendering for modern LCD displays with Windows-style LCD sub-pixel rendering.

Additional user interface enhancements in JavaFX 2.1 include: controls for combo box, stacked chart and application-wide menu bar.

JavaFX 2.1 is available now for Windows and Mac OS X. A developer preview for Linux is also available.

Currently rated 1.5 by 14 people

  • Currently 1.5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1999

Tags: , , , ,

Oracle | java

Semicolon, as drama

by Alex Handy 04/16/2012 05:40 PM EST

There are few areas of study in which a semicolon can become a point of contention. Clearly, in the world of the written word, the colon and its half-bred ilk are widely regarded as essential; tools of the trade. So, too, is the case in the software development world; an omitted punctuation mark usually means broken code, or an incomplete loop. In JavaScript, however, semicolons as statement terminators are optional.

But it would seem that this ambiguity around the mark's use in that language is quite a hot-button issue. This began as a bug report and comment war in the GitHub repository for Bootstrap. It escalated (but had been brewing for months) until the creator of JavaScript chimed in. Now everyone has an opinion. It's gone so far as to have spawned a vanity domain name and a new programming language, comprised entirely of, you guessed it; semicolons!

Of course, this has also been called "the most boring technical debate ever," by one Hacker News commenter. Even if it is, as a writer, it's always fascinating to see minutia discussed on the level of punctuation.

Currently rated 1.5 by 4 people

  • Currently 1.5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1992

Tags: , , ,

javascript

OpenStack Foundation takes shape

by Alex Handy 04/12/2012 02:01 PM EST

The OpenStack Foundation has, essentially, arrived. Today, Mark Collier, the vice president of OpenStack at RackSpace posted a blog updating the project's progress towards the creation of a non-profit foundation, along the lines of the Eclipse Foundation, or the Apache Software Foundation. From Mark's update, it sounds like the only remaining barrier between where things are now and the legal formation of the Foundation is the lawyers. They're writing the final legal documents as we speak, in order to pass them to the community for a final perusal.

In the meantime, however, the primary tenets of the Foundation, it's processes and goals have all been laid out, where else? On a <a href="http://wiki.openstack.org/Governance/Foundation">Wiki</a>, of course! Collier said in his blog posting that the Foundation is literally modelled on existing software foundations, so there shouldn't be any surprises in the final legal mumbo-jumbo. The vagaries of how this particular Foundation will work are, at this point, less relevant than the names of the companies that have signed on to participate.

Those names include AT&T, Canonical, HP, IBM, Rackspace, Red Hat, SUSE, Cisco, and Dell, among many others. That's definitely a powerful list of donors and contributors, right out of the gate.

But big companies aren't the only big names in this big new foundation. The mailing list for the OpenStack Foundation has been vibrant and lively, and has included wisdom from many luminaries in open source. Therein, Jim Jagielski, founding member of the Apache Foundation, gave these words of wisdom on March 13, when the list was discussing branding and marketing:

If you get the open source part right, with a vibrant, healthy community, then very little marketing/branding is needed to commercialize it.

If, instead, one focuses on the commercialization aspects, then the open source part will suffer and no amount of "branding" will make it better... It would be like putting lipstick on a pig. Which is good, I guess, if you sell pig lipstick....

Hopefully, the OpenStack Foundation will get the open source part right. On the goals front, Colliers laid out the following three principles:

  • An open development process that is driven by technical meritocracy
  • Making significant investments in community building and driving awareness and adoption
  • Encouraging the development of a healthy and profitable ecosystem of companies powered by OpenStack

And, of course, there is a general mission statement for the Foundation, as well.

The Foundation Mission: The OpenStack Foundation is an independent body providing shared resources to help achieve the OpenStack Mission by Protecting, Empowering, and Promoting OpenStack software and the community around it, including users, developers and the entire ecosystem.

And, this is all occurring just in time for the OpenStack conference in San Francisco, next week. I'll be there, too, taking a gander at all the pieces of this datacenter operating system puzzle.

Currently rated 1.5 by 17 people

  • Currently 1.529412/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1990

Tags: , , , , , ,

openstack

Jack Tramiel, the founder of Commodore, passed away yesterday, April 8, at the age of 83. As the man who brought the VIC-20, Commodore 64 and and Atari ST to market, Tramiel's business savvy helped to bring computing to the masses. The Commodore 64, alone, did more to expand the audience for home computers than just about any of the systems introduced in the 1980's.

In December of 2007, I had the pleasure of meeting Jack at the 25th anniversary party for the C64 at the Computer History Museum in Mountain View, California. It was a spectacular evening, which is fully documented in photographs here.

I wrote a piece that evening which for some reason I didn't manage to get onto the Web. Tramiel talked about his life and work that evening. I attempted to collect as much of his talk into this piece, at the time. Here, then, is entire article about the Commodore 64 25th Anniversary.

Tramiel kicked off the evening by speaking to New York Times journalist John Markoff. During their chat on stage, Tramiel recalled the triumphs of his life. Tramiel was born in Poland in 1928, and was sent to the Auschwitz concentration camp during World War II. When he was liberated by the Americans in 1945, Tramiel emigrated to the United States. Once there, he joined the army.

“When I came to the US I definitely felt I owed something to this country. I believe always in paying back. I lived in the east side of New York City for the first three months, and almost felt like I was back in Poland with the smell of the herring and the onions. I felt that I had to learn what this country was all about, so I joined the army, and served the country. That took me to Fort Dix,” said Tramiel.

At Fort Dix, Tramiel learned how to repair typewriters. That skill would support him when he returned to civilian life in New York. Eventually, after working two jobs and continuing to fix typewriters, Tramiel quit to start his own business across the street from Forham University. That school sent their typewriters to Tramiel for repairs. Before long, he was manufacturing his own machines.

The name of the company, right from the start, was Commodore. Tramiel said he got the name from his time in the army. “I wanted to call my company General, but there's so many Generals in the U.S. General Electric, General Motors. Then I went to Admiral, but that was taken too. So I wind up in Berlin, Germany with my wife and we were in a cab, and the cab made a short stop and in front of it was an Texas Instruments. Soon, TI decided that it wanted to be the one in control of the expanding market for handheld digital calculators, and the company slowed down chip shipments to Tramiel.

Thus, Commodore's future, Tramiel decided, would be held in owning and controlling its own chip supply. Commodore had previously purchased processors from MOS Technologies, Tramiel found himself talking to that company in the late 70's.

“I called them. We met. They were in very bad financial shape. They needed help. I decided to buy this company and turn it over to become strictly a Commodore supplier, except for companies like Apple to which we would supply some,” said Tramiel.

Along with the purchase of MOS, Commodore inherited a young developer named Chuck Peddle, who wanted to build a personal computer, a relatively odd-ball idea for 1976. Eventually, Peddle produced the Commodore PET, also known as the personal electronic transactor.

At the time, said Tramiel, he had no idea how many PETs to build. “We were told why don't you go up to Arthur D. Little, and they will tell you what this market can stand. The first thing [Arthur D. Little] told me was cost that it would cost $5 million and take one year. Then I found out that the same company had told IBM not to buy Xerox. I decided 'nope, gonna go another way.' We went and we advertised the PET in the Wall Street Journal: 3 full pages. A couple weeks later we had $3 million in sales, and we knew we had a winner,” said Tramiel.

The PET gave way to the VIC-20, the first personal computer to sell one million units. But that was nothing compared to Commodore's next product.

In August of 1982, the Commodore 64 peaked its head out from the shelves of Sears and Montgomery Wards around the country. From the time of its release to the time of its discontinuation in 1995, Tramiel estimated that his company sold around 30 million units. “I remember we sold 480,000 to 500,000 computers a month. That slowed down when I left in 1984. I understand we sold between 22 million and 30 million units,” said Tramiel.

Of course games were, perhaps, the C64's greatest contribution to the world of computer history. With classics such as Ultima III, Boulder Dash, Commando, The Last Ninja, and Lode Runner all made the system a huge success around the world. The system's unrivalled ability to produce 16-color graphics and three-channel sound made it the first major platform for graphics and sound demos, which continue today. Now known as the demo scene, graphic and visual programmers made the C64 into a media presentation system long before the MP3 and the Divx codec.

Tramiel said he was aware of all this creativity his product unleashed. “People came over to me at shows and told me how successful they are, and I was very proud of it,” he said. Perhaps the single greatest strength of the C64 was its price tag. When it was introduced in Las Vegas in early 1982, most show-goers found it impossible to think that this computer with 64KB of RAM could be sold for $595. The secret was Tramiel's decision the buy MOS Technologies, and his philosophy of business: “I believe that if you can afford it, you should always sell a product for no more than 100% of the price it costs to produce it.”

Tramiel's peers was also in attendance to commemorate the 25th anniversary of the C64. Al Alcorn, employee number one at Atari, said that, when he was with that company (long before Tramiel purchased its Consumer Division and appropriated the name), Commodore was seen as untouchable. “We came up with the Atari computer to stop Steve (Wozniak) from stealing our employees (at Apple). We wanted to avoid competing with Commodore because of that price,” said Acorn.

Steve Wozniak, co-founder of Apple Computer, said that his own company's machines were often seen as too expensive after the C64 arrived. “After a while, every time I went to shows they had their C64's! This was at one show after another after another after another. Of course, they wanted an Apple, but they couldn't afford one,” said Wozniak.

But Tramiel and Wozniak share more than their storied pasts in the personal computer business. Tramiel related a little known tale during the proceedings at the behest of Markoff. Tramiel, like Wozniak, had a near-death experience on a plane in the 1980's.

“At Commodore we had a plane called the PET Jet. [Tramiel's wife] Helen and I and 6 other members of Commodore went from New York to California,” said Tramiel, “but we made a stop to pick up dealers in Chicago. On the way from Chicago to San Jose, the plane started smoking. There were no brakes, no radio. The smoke got very black. I heard a signal of some kind, and we landed in Des Moines Iowa. We exited the plane, and after a few minutes, the plane blew up.”

Currently rated 2.1 by 17 people

  • Currently 2.058824/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1988

Tags: , , , , ,

history

Cheating is good for you

by Alex Handy 04/09/2012 01:31 PM EST

Got Cheat Sheets? There's never shame in using a cheat sheet, especially in a world where languages, frameworks and standards are changing, appearing, and being forked every single day. Here, then, is a nice list of links to useful cheat sheets.

HTML5, CSS3, and JQuery.

Core Java Concurrency.

A slew of C# cheat sheets.

Python, many versions.

Nice graphical Vim cheat sheet.

Bash shell.

And, for fairness, Emacs.

Currently rated 1.5 by 14 people

  • Currently 1.5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1987

Tags: , , , ,

links

Eclipse Community Award winners

by Alex Handy 03/27/2012 03:38 PM EST

With EclipseCon taking place this week in Virginia, there's an awful lot of neat projects to explore and talk about in the popular tools integration platform. Perhaps the easiest way to take a stroll through the Eclipse ecosystem's latest developments is to look at the winners of the Eclipse Community Awards.

Winner of the Most Open Project award was the Eclipse Communication Framework. Mustafa K. Isik, a contributor to the ECF project, attributed the win to the work of Scott Lewis, the projects lead. "IMHO, this is first and foremost [Scott's] achievement. [Scott has] always set the tone and course for openness and acted accordingly, serving as an example for us all," wrote Isik in a posting to the ECF mailing list.

The Most Innovative New Feature award went to Eclipse Code Recommenders. That project is currently at version 0.5, but is pushing quickly towards creating a revolutionary new method of code completion. Code Recommenders is all about teaching developers how to use essential APIs directly in the IDE, in the code. The project uses extended javadocs, smart bug detectors, stacktrace search engines and intelligent code completion to give developers highly relevant suggestions.

Outside of Eclipse, the Community awards also recognised projects and products based on Eclipse. This year's winners clearly show that Eclipse users appreciate better debugging and rapid prototyping tools.

Best Developer Tool honrs went to the Chronon Time Travelling Debugger. This tool that comes with the Chronon test system for Java applications allows for some very interesting debugging possibilities. Chronon calls itself "DVR for Java," meaning applications can be run and recorded, then played back to find root causes for bugs. The debugger actually lives inside of Eclipse, and it was this integration that won the award.

Best modeling product was MaintainJ, which is praised for its ability to turn complex Java applications into more comprehensible models. And the award for best application went to the Justinmind Prototyper, which allows developers to quickly design Web application experiments.

Currently rated 1.8 by 52 people

  • Currently 1.75/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1983

Tags: , , , , , , ,

eclipse

25 years of GCC

by Alex Handy 03/22/2012 12:27 PM EST

GCC 4.7 was released today. It's a fairly standard point release with some bug fixes, and a handful of new features. But the most significant aspect of this release is that it marks the 25th anniversary of the GCC project itself.

To that end, Richard Guenther, who works in toolchain development at Suse Labs, and spends his days working on GCC, sent an email to the GCC development newsgroup to mark this historic occasion. Here it is, reprinted, for your reading pleasure.

Today the GCC development team celebrates the 25th anniversary of the GNU Compiler Collection.

When Richard Stallman announced the first public release of GCC in 1987, few could have imagined the broad impact that it has had. It has prototyped many language features that later were adopted as part of their respective standards -- everything from "long long" type to transactional memory. It deployed an architecture-neutral automatic vectorization facility, OpenMP, and Polyhedral loop nest optimization. It has provided the toolchain infrastructure for the GNU/Linux ecosystem used everywhere from Google and Facebook to financial markets and stock exchanges. We salute and thank the hundreds of developers who have contributed over the years to make GCC one of the most long-lasting and successful free software projects in the history of this industry.

As a special present we have prepared the release of GCC 4.7.0 which continues the series of free software high-quality industry-standard compilers.

GCC 4.7.0 is a major release, containing substantial new functionality not available in GCC 4.6.x or previous GCC releases.

GCC 4.7 features support for software transactional memory on selected architectures. The C++ compiler supports a bigger subset of the new ISO C++11 standard such as support for atomics and the C++11 memory model, non-static data member initializers, user-defined literals, alias-declarations, delegating constructors, explicit override and extended friend syntax. The C compiler adds support for more features from the new ISO C11 standard. GCC now supports version 3.1 of the OpenMP specification for C, C++ and Fortran.

The link-time optimization (LTO) framework has seen improvements with regards to scalability, stability and resource needs. Inlining and interprocedural constant propagation have been improved.

GCC 4.7 now supports various new GNU extensions to the DWARF debugging information format, like entry value and call site information, a typed DWARF stack and a more compact macro representation.

Extending the widest support for hardware architectures in the industry, GCC 4.7 gains support for Adapteva's Epiphany processor, National Semiconductor's CR16, and TI's C6X as well as Tilera's TILE-Gx and TILEPro families of processors. The x86 family support has been extended by the Intel Haswell and AMD Piledriver architectures. ARM has gained support for the Cortex-A7 family.

See http://gcc.gnu.org/gcc-4.7/changes.html for more information about changes in GCC 4.7.

Currently rated 1.5 by 51 people

  • Currently 1.54902/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1981

Tags: , , , , ,

gcc

JIRA 5 goes all a-REST

by Alex Handy 02/23/2012 07:29 PM EST

You may have noticed that JIRA 5 shipped yesterday. As a success story in the software world, you can't do much better than Atlassian. As a center-point for the day-to-day bug squishing expeditions of enterprise developers, JIRA has pushed Atlassian's success numbers to a 9 digit revenue figure this past year.

What's the secret to their success? A relentless focus on saving you 5 minutes here and there, rather than on saving your whole team hours and hours after weeks of painful integrations. Bug tracking systems are an odd beast that way. As stated, they're the primary method of interface on projects for many developers and Q/A folks in the business world. And yet Bugzilla remains a popular, no-frills tool. While ClearCase and massive HP tools are still around, the lighter weight, better integrating alternative of JIRA quietly took over the marketplace.

That theme of being the center-point (guh, don't make me say "portal") of software development work and interaction is what's really driven Atlassian in JIRA 5. They've taken a lot of inspiration from Facebook and Twitter, but then, everyone else has too, right?

Everyone's got that social stream of information thing going on these days, right? The special sauce of JIRA 5 is actually quite modest at first glance. They've added name-completion to postings. That means when you post "Obviously Steve introduced this bug last night while coding 16 hour straight," Steve's actual name on the JIRA boards is spliced in there, like an @name in Twitter. Thus, Steve is immediately alerted whenever someone mentions his name in the bug tracker.

Atlassian has also extended this idea to bugs themselves. Each issue that is mentioned in JIRA comments is alerted to that chatter. A link to the mention of said issue will appear on the issue page.

Behind this, Atlassian revamped its back end to allow for RESTful calls to just about any bit of the system. Those bug mentions are accompanied by RESTful addresses, so you can feed actions, events, and data into and out of each entry.

JIRA 5 isn't a revolution. What JIRA 5 is, however, is a time saver. And this release includes dozens of little time savers, such as the ability to retain information in the issue submission form, so you can quickly submit 20 similar issues without retyping the same information over and over.

But given Atlassian's growth as a company, and JIRA's popularity, I don't think a revolutionary product is needed. JIRA works, and people love it.

What JIRA has needed for a long time, however, is a better enterprise pricing plan. For years, the JIRA price list has looked more like a pricing scheme for a round of golf at an expensive club, rather than a piece of enterprise software. That's a good thing, but there are, of course, enterprises that cannot even comprehend paying $2000 for an enterprise software solution.

Another problem for these enterprises has been the lack of 24/7 phone support. Until now, it's been 24/5 for JIRA users. But that all changed yesterday.

The enterprise pricing options for JIRA are now 500 users at either $8000 or $12,000, with the price upgrade including the full enterprise support and training package. It's 2000 users for $16,000 and 10,000 users for $20,000. This is a one-time fee, with 50% charged per year afterwards.

That's a totally reasonable price in the enterprise world. Compared to an HP or IBM engagement, that's actually peanuts. I think it's pretty clear that Atlassian, of all the companies in the software tools market, is doing it right.

Currently rated 1.6 by 29 people

  • Currently 1.62069/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1967

Tags: , , , , ,

applications

Ryan Dahl steps down

by Alex Handy 02/01/2012 04:58 PM EST

Ryan Dahl, creator of Node.js, has stepped down from his position as gatekeeper of the project. Clearly, the project has grown to a point where the project's creator can finally step back and take a break from working on bug fixes and daily commits. Here's the email he sent to the Node.js developer mailing list:

Now that the rewrite on top of libuv is largely complete, I am ceding my position as gatekeeper to Isaac Schlueter. Our energy will now be largely focused over the next few months on improving the third party module system experience including a website for browsing modules, a new addon build system, and binary installations from npm. Isaac is in the unique position to bridge the gap between core and external modules to ensure a pleasant experience. After three years of working on Node, this frees me up to work on research projects. I am still an employee at Joyent and will advise from the sidelines but I won't be involved in the day-to-day bug fixes. Isaac has final say over what makes it into the releases. Appeals for new features, changes, and bug fixes should now be directed at him.

Currently rated 1.3 by 3 people

  • Currently 1.333333/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Share this link: http://www.sdtimes.com/blog/1955

Tags:

node.js

 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
MAY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Creation
To write better software, cultivate your ability to be creative.
05/19/2012 07:40 PM EST

Slick...but who needs it?
compilr.com is a well-designed site and the folks behind it seem to have their heart in the right place. But...who needs it?
05/16/2012 12:45 PM EST

How to be a better software developer
Want to be a better developer? You won't get there by mastering an interesting language or learning a new set of APIs.
05/14/2012 12:18 PM EST

Wooing Galatea
Do yourself a favor and check out Galatea 2.2, a wonderful book by novelist Richard Powers.
05/12/2012 07:05 PM EST

The world as story
An artificial-intelligence system at Carnegie Mellon seeks to understand the world by making statements about it.
05/10/2012 06:39 AM EST

The Rise of the Brogrammer, or the Rise of the Sexist Programmer?
Women in Silicon Valley get vocal about sexist ads and campaigns that contribute to a tense work environment.
05/09/2012 03:14 PM EST

 

Events calendar tab
5/23/2012 to 5/24/2012
Chicago
IEG

6/3/2012 to 6/7/2012
Orlando
IBM Rational

6/10/2012 to 6/15/2012
Las Vegas
SQE

6/10/2012 to 6/15/2012
Las Vegas
SQE

6/11/2012 to 6/14/2012
Bellevue, Wash.
AMD