![]() ![]() "Do you want to be a bloat detective? It's easy just pick any executable. Although the wordings are inexact, I believe they capture the spirit of the originals. The included quotations are not verbatim. It's easy to distribute via news and mail, and everyone can read it.Īn ASCII version of the May 12 report can be found in: I'm preparing this report in ASCII to make it widely available. If we keep doing the exact same thing, we'll keep getting the exact same results. Most of the report's warnings and predictions have come true in 5.1. We've addressed some of the problems presented in the original May report, but not enough. Make sure marketing and engineering expectations are in agreement. We'll be forced to look closely at the code, and fresh reviewers can provide fresh insights.įor the long term, let's change the way we do things so that the contents and scheduling of releases are better planned and executed. I propose massive code walk-throughs and design reviews to analyze the software. The software environment is so convoluted that at times it seems to rival the US economy for complexity and unpredictability. Nobody knows what's wrong - opinions are as common as senior engineers. If we pick a reasonable set we'll avoid emergency feature cuts at the end. Let's decide ahead of time exactly what features are in 5.1.2. ![]() What shall we do now? Let's not look for scapegoats, but learn from our mistakes and do better next time.Ī December release of 5.1.2 is too early to fix much - we'll spend much more time on the release process than fixing things. Management would not cut features early, so we were forced to make massive cuts in the final weeks of the release. The primary cause is that we attempted far too much in too little time. Disk space requirements have increased dramatically. Performance for common operations has dropped 40% from 4.0.5, we shipped with 500 priority 1 and 2 bugs, and a base Indy is much more sluggish than a Macintosh. This sequel is to satisfy all those people who have urged me to bring it up to date. Subsequently, I made it available to quite a few other people. Last May, I published my first report on software usability, which Rocky Rhodes and I presented to at Tom Jermoluk's staff meeting (with Ed, but without Tom). If you are installing Softimage on the same machine as the SPM server and you don’t know the name of your computer, enter. This legendary leaked memo has become required reading for operating system design courses: In the Server hostname box, enter the computer name or IP address of the computer that is running the SPM server. They made up for being small on the outside, by being HUGE and BLOATED in the inside: Publication date 1998 Topics Microsoft Softimage 3D, Computer graphics, Three-dimensional display systems, Computer animation Publisher Indianapolis : New Riders Collection inlibrary printdisabled internetarchivebooks Contributor Internet Archive Language English. The Indigos were another story entirely: They couldn't touch the raw graphics performance of an Iris, since the rendering was all in software, but you could actually stuff one of them in the overhead compartment on an airplane!Īnd then there was the SGI Indy. Those things are fucking heavy! It was raining outside and the office started to flood, so we had to keep taking shelves down off the wall and wedging them underneath the Iris to jack it up above the water, as it kept getting deeper and deeper. Subscribe via iTunes: itpc://Read More.When I was working at UniPress in New Jersey, we had an SGI Iris. It also offers state-of-the-art media acceleration technologies as well as access to operating system resources, input devices and displays. The goal of OpenKODE is to make it easier for developers (and carriers) to deploy rich media applications on mobile phones, by providing system abstraction so that develoeprs don’t have to worry about the underlying handset hardware or OS. OpenKODE provides functionally similar to DirectX on the desktop, except it is cross-platform, royalty-free and streamlined for handheld devices. The first podcast previews the new OpenKODE APIs. In this new series, the developers behind the industry standards for 3D, 2D, video and audio for mobile devices describe how the new technologies work and how they can be used by developers, carriers and manufacturers to create applications for mobile phone, handhelds and game consoles. The Khronos Group has launched the first episode in the Mobile Media Developer podcast series. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |