agriculture | asatru | copywrongs | humor | musings | politics | technology | index haxton.org  
   
MacRaven Logo
MacRaven
Dave Haxton's Weblog

Musings, Reflections, Rants and Comments from a Hoosier Heathen husband, father, grandfather, farmer and software engineer. There's really only one of me ...


Contact Me   


RSS Feed   


July
Sun Mon Tue Wed Thu Fri Sat
   
24 25 26
27 28 29 30 31    



The Blogroll
A Mindful Life The Accidental Smallholder Asahel's Search Austro-Athenian Empire Brad Spangler DiRT Dispatches Garden of Thought Hardscrabble Creek The High Seat Knit Together Laudator Temporis Acti Little Heathen Fox Lorrie's Livejournal Masson's Blog Mutualist Blog MyAppleMenu nobody asked, BUT NoNAIS Notes on Religion Numenous Thoughts OrangeGuru Overlawyered Prophet or Madman rogueclassicism Secular Blasphemy Sugar Mountain Farm TMN Thud Factor Wildhunt Blog within the crainium

Page Loaded at

Eastern Standard Time

Support Denmark!

No NAIS!

MLL


lunar phases
 


Click for Thorntown, Indiana Forecast

       

home :: Technology :: How_Microsoft_D...opers.html

Tue, 06 May 2008
How Microsoft Dropped the Ball With Developers

And all the developers said "Amen!"

As part of an Ars Technica series on how one developer migrated from Windows to OS X (and why), this second article concentrates on how Microsoft bungled the transition from XP to Vista. The author looks at some unfortunate decisions Microsoft made that have made Windows an unpleasant development platform. "So Windows is just a disaster to write programs for. It's miserable. It's quite nice if you want to use the same techniques you learned 15 years ago and not bother to change how you do, well, anything, but for anyone else it's all pain... And it's not just third parties who suffer. It causes trouble for Microsoft, too. The code isn't just inconsistent and ugly on the outside; it's that way on the inside, too. There's a lot of software for Windows, a lot of business-critical software, that's not maintained any more. And that software is usually buggy. It passes bad parameters to API calls, uses memory that it has released, assumes that files live in particular hard-coded locations, all sorts of things that it shouldn't do."

(link) [Slashdot]

Tue, 06 May 2008 06:46 /Technology | 0 writebacks | permanent link