That's exactly what they did. That's what SOC means. Basically instead of having to have a separate chip on the board for the radio, it's within the processor. Of course the board still needs an antenna, but this is just another step towards x86 cell phones.
Finally someone actually works in the cg industry replies. +1 to this. No one really uses fixed function stuff these days, everything is shaders and vertex and index buffers. There are no fixed function hardware units, everything in the graphics pipeline is programmable and done in shaders. Even using fixed function stuff on today's hardware forces the driver to compile a built in shader. In the interest of keeping driver size small (for mobile apps), they force the programmers to write their own shaders and throw away the fixed function stuff that would bloat the driver and slow the shader compiler.
New code doesn't use fixed function stuff these days. JWZ's point is that there is more than new code. Legacy code also matters, e.g. CAD applications. Those have little use for shaders. Frankly, your point of view sounds very game-centric to me.
Both nVidia and ATI have committed to supporting these older APIs for the foreseeable future.
Maybe not - but imagine the loss in hardware sales and ecosystem revenue if everyone ported old shitty games without re-writing them, causing batteries to die quickly and a poor user experience?
It was for the better of the industry. Boo-hoo. If it took him 3 days then hes a smart fucker. As someone with plenty of OpenGL AND OpenGL ES experience, I'd say it would have taken him just has much time to port his existing code.
And if that were the end of the story, I think we'd be able to call it a day. But everyone has this funny expectation that that old code should keep getting faster with newer GPUs, in spite of the fact that GPUs don't work the way those programs were designed to use them.
Getting modern GPU performance, or anything close to it, through the crufty old immediate-mode API code is like drawing blood from a stone. Eventually developers need to take some responsibility for the code they're maintaining and migrate to a more modern API. Even on the desktop they'll have to do this - when their customers ask for modern GPU features, they'll have to move to OpenGL 3, which doesn't have immediate-mode either.
Debugging is not fun when your program is leaking memory and you're not sure why, and existing code tools don't tell you why. Especially if you're writing drivers. Sure, stepping through python code might be fun, but not low level c/c++ code where you're in a call stack that's 20 levels deep and half the time you don't have source for the parts the code breaks or asserts on.
What about the level of excitement you get when you find a bug in an underlying Fortran library linked in by code building tools because of a random header file someone included without thinking too much?
This video kind of makes you wonder if people are really saying these things cause they mean it or if they are just being watched and have to act a certain way to reap the benefits of being a firm party supporter. Benefits like living in Pyongyang and actually having food and shelter. I feel that it's probably the latter in like 99% of cases.
My father in communist Poland wasn't able to do the research he wanted at his university at Poland cause he wasn't in the party. He cursed out his professor and called him a communist and got kicked out and had to transfer schools. Calling someone out as a communist was a slur against them because those reaping in party benefits were seen as betraying their own country.
I feel like it's a similar case in NKorea. You have to act that way cause your neighbors will tell the authorities about any signs of disloyalty and the family will disappear (into a re-education camp.) I think that's why these people on the videos when they are interviewed really chose their words carefully and make anything they say an attempt to glorify the dear leader. Their eyes give them away though. I feel like everyone is aware of it -- the conditions in their country vs the west, but they live in fear of expressing their own opinions so they just shut up and go about their lives.
Little known fact...the only reason the brace is on the same line as the function declaration is because K&R just wanted to save space in the code listings.
Um, no, K&R braces after function declaration are in the next line, because they are special.
Braces after if, for, while, switch, etc. are on the same line, and yes, it was to save space on the 80x24 screen.
Get a copy of "The C Programming Language, Second Edition". It's right in there. It's the only technical computer book I know that is still accurate after more than twenty years.
I agree it's fun to read and has some good points, but it's obvious it's meant only for really imperative-styled C that you'd expect to find in the kernel. e.g.:
> ... if you need more than 3 levels of indentation, you're screwed anyway, and should fix your program.
class A:
def foo(self):
while cond:
if othercond:
bar()
Opening braces on the same line means that you can always open a new line for editing with O and o in vi and it will be a valid line for placing code on.
I'm a computer science major and I've interned at an animation company as a technical director. We were outsourced for a certain AAA game that is coming out in 2011 (can't say what companies cause it would probably breach the NDA.) I spent a few days at the actual game company, and it sort of put me off game programming completely. Even though people had cool offices with posters and toys everywhere it was a very dull and depressing place to work. People came in at 10 and sometimes stayed till midnight. The highlight of the day was ordering dinner at 6pm. It was basically permanent crunch time. Also people don't realize that most of game creating is assets. Animations, mocap, recording dialog, scripting. There is very little actual programming unless you're working on an assets/tools team which makes engines (in my case they licensed the Unreal engine so most of the work in terms of programming was done.) Making a game nowadays is more like making a 10 hour movie...there are writers and directors that are hired. They film the action in a mocap studio and eventually animators clean up the data and level designers import it into the engine.
What is sad that all the cool hardcore C programming jobs are going oversees - unless you're a computer engineer and deal with hardware. Everyone is looking for php, ajax, python, etc, basically C-based type-less languages which anyone competent in C can pick up in a matter of days. But try to apply to those companies with C, C++ and x86 assembler on your resume, no one will get back to you.
Microsoft still requires C++ from their applicants. Nvidia and Intel both require C and C++. Google also heavily uses C/C++. I believe you're confusing "web companies" with "companies." It makes sense for web companies to use other languages, but C, C++, and assembler are things that should be on your resume.
If someone claimed to be a competent programmer, but didn't know how asm related to C, I would seriously question the merit of their statements.
Everyone is talking about how much they practice their scales in their "daily practice." If it's a chore to you and has no practical application, don't waste your time, play something you like. The only reason I know a few minor and major scales is because I like to improvise. When it comes time to solo, I know what to play because I know what notes are in the scale. If I didn't know any scales, I'd be lost. It also make a lot more sense if you practice with some backing track/chords cause then you can figure out what sounds good. This also applies to playing piano, lets say I want to play some minor sounding progression, I'd most likely play A minor because all the white keys are in the A minor scale which makes it easy to create a melody.
