Don't forget that he would beat the holy hell outta his paint brushes to get the water out of them. That's gotta be in the game, for sure. I can envision an energy meter that waxes and wanes as depending how ferociously you move the brush, and points for how many people on the production crew you can spatter.
Exactly! And by the way, if you burn all your purchased songs to CD soon after you purchase them, then you don't risk losing them if your system goes ba-bye.
I agree that Chabon comes close at times to falling into the trap, yet just when you are ready to condemn him as a show-off, you come across a turn of phase that just blows you away. Some of the passages in this book are beautiful, and the characters truly come alive.
I have also read Wonder Boys, and it is quite different from K&C. It's also a much easier read, but I didn't like it as much.
I can't wait to read Summertime. I'm interested to see how he writes for a younger audience.
I will add that, like the comics of that time, there is nothing heavy about the reading despite the introduction and resolution of a remarkable pastiche of sublime themes and subplots.
While I enjoyed the book immensely, I certainly would not call it an easy read. My advice on this one is to keep a good dictionary nearby while you read.
I like to think that I have a fairly large vocabulary, but reading this book humbled me.
Why should it take a hacker conference to get AT&T to put out such a warning? I would like to think that such policies are already in place, and that employees are trained to minimize the risk of social engineering from the start.
There are things in RenderMan/non-realtime rendering programs that simply cannot be done by realtime renderers.
For one thing - programmable shading. Programs like PRMan and BMRT support programmable shaders - which are incredibly important for photo-realistic effects. They also are expensive in terms of processing, which is why realtime is going to have some problems with them.
Another thing is resolution. I don't remember what resolution the images need to be for film, but I think that it's pretty high. More pixels = more processing.
Realtime effects for games are getting to be stunning, but motion pictures are another thing entirely.
My problem isn't with non-obvious code. Such code is often necessary to squeeze performance or flexibility out of a language or system. My problem is with non-obvious code that ISN'T COMMENTED or documented in some way. If the code isn't self-documenting or easy to follow, it is the responsibility of the developer to document what is going on.
I think that the book _Code Complete_ by Steve McConnell should be required reading for everyone who calls themself a developer. Yes, the book is published by the evil Microsoft Press, but this book is truly noteworthy. It describes an approach to code-writing that is practical, efficient, and responsible. Get your hands on a copy if you can - you won't regret it.
I seriously believe that there is a vast difference between a programmer and a software engineer. And I think that as time goes on, we will see programming become more like other engineering disciplines, because customers are becoming less tolerant of late, over-budget software projects that miss the mark.
I think that many open source projects could use a bit more application of software engineering techniques, and less seat-of-the-pants coding sprees. Yes, the latter puts something out there sooner for people to bang on, but oftentimes that something is a big buggy pile o'crap. In the long run, software engineering techniques will deliver a higher-quality application that people will actually be able to use.
Ah yes, another episode of As The FUD Turns. Always amusing to watch, sometimes intriguing, but there is no real substance.
It's kind of funny to watch two technological titans call each other names like kids at the schoolyard. "We're more Open than you are", "Our technology is more advanced than yours", "My server can beat up your server", "Nyah, nyah nyah, nyah nyaaaaah nyah!".
The bottom line is that you have two groups, each vigorously defending their positions, but THEY ARE BOTH WRONG. So very wrong.
Slashdot Mirror
Don't forget that he would beat the holy hell outta his paint brushes to get the water out of them. That's gotta be in the game, for sure.
I can envision an energy meter that waxes and wanes as depending how ferociously you move the brush, and points for how many people on the production crew you can spatter.
Exactly! And by the way, if you burn all your purchased songs to CD soon after you purchase them, then you don't risk losing them if your system goes ba-bye.
I'm sure those burned CDs still work in Canada.
Oops. Correction - Summerland
I agree that Chabon comes close at times to falling into the trap, yet just when you are ready to condemn him as a show-off, you come across a turn of phase that just blows you away. Some of the passages in this book are beautiful, and the characters truly come alive.
I have also read Wonder Boys, and it is quite different from K&C. It's also a much easier read, but I didn't like it as much.
I can't wait to read Summertime. I'm interested to see how he writes for a younger audience.
I will add that, like the comics of that time, there is nothing heavy about the reading despite the introduction and resolution of a remarkable pastiche of sublime themes and subplots.
While I enjoyed the book immensely, I certainly would not call it an easy read. My advice on this one is to keep a good dictionary nearby while you read.
I like to think that I have a fairly large vocabulary, but reading this book humbled me.
This buyout (sellout?) makes the site a lot less credible in my opinion. They are simply going to use the site to sell more virus protection software.
Why should it take a hacker conference to get AT&T to put out such a warning? I would like to think that such policies are already in place, and that employees are trained to minimize the risk of social engineering from the start.
I guess that's just wishful thinking though...
There are things in RenderMan/non-realtime rendering programs that simply cannot be done by realtime renderers.
For one thing - programmable shading. Programs like PRMan and BMRT support programmable shaders - which are incredibly important for photo-realistic effects. They also are expensive in terms of processing, which is why realtime is going to have some problems with them.
Another thing is resolution. I don't remember what resolution the images need to be for film, but I think that it's pretty high. More pixels = more processing.
Realtime effects for games are getting to be stunning, but motion pictures are another thing entirely.
I have heard that Google uses Python extensively to manage its data, grab new data, etc.
As an avid fan of the Python language, I am interested in exactly how Google puts it to use. Can you clue us in?
P.S. - Keep up the good work!
My problem isn't with non-obvious code. Such code is often necessary to squeeze performance or flexibility out of a language or system. My problem is with non-obvious code that ISN'T COMMENTED or documented in some way. If the code isn't self-documenting or easy to follow, it is the responsibility of the developer to document what is going on.
I think that the book _Code Complete_ by Steve McConnell should be required reading for everyone who calls themself a developer. Yes, the book is published by the evil Microsoft Press, but this book is truly noteworthy. It describes an approach to code-writing that is practical, efficient, and responsible. Get your hands on a copy if you can - you won't regret it.
I seriously believe that there is a vast difference between a programmer and a software engineer. And I think that as time goes on, we will see programming become more like other engineering disciplines, because customers are becoming less tolerant of late, over-budget software projects that miss the mark.
I think that many open source projects could use a bit more application of software engineering techniques, and less seat-of-the-pants coding sprees. Yes, the latter puts something out there sooner for people to bang on, but oftentimes that something is a big buggy pile o'crap. In the long run, software engineering techniques will deliver a higher-quality application that people will actually be able to use.
Ah yes, another episode of As The FUD Turns. Always amusing to watch, sometimes intriguing, but there is no real substance.
It's kind of funny to watch two technological titans call each other names like kids at the schoolyard. "We're more Open than you are", "Our technology is more advanced than yours", "My server can beat up your server", "Nyah, nyah nyah, nyah nyaaaaah nyah!".
The bottom line is that you have two groups, each vigorously defending their positions, but THEY ARE BOTH WRONG. So very wrong.
It is amusing to watch, though.
C'mon guys. Open the source or shut up!