Slowpoking

[soonts]

   Watched some presentations from Build 2013 conference.

IMO the most interesting so far is this one: "Native Code Performance and Memory: The Elephant in the CPU".

Also, this "Innovations in High Performance 2D Graphics with DirectX" could be useful to troll non-windows users.

Comments

[thedeemon]

Just watched the second one. Boring.
"We need to draw a hundred of icons and this is a Really Hard Problem because we're fucking retarded".

[soonts]

You are ignorant of tablets, with their low power CPUs and 200-300 DPI screens. So yes, drawing 100 color vector icons could be a hard problem.
Besides, only 15% of the presentation is about icons.

[thedeemon]

I don't think those tablets can change their DPI dynamically and unpredictably. So turning those vector icons into prerendered bitmaps once is a no-brainer, and I don't believe drawing those vector curves can be faster than blitting a bitmap.

Rest of the talk is not so dumb, but still too obvious and boring.

[soonts]

>I don't think those tablets can change their DPI dynamically and unpredictably.
Yes, they can.
You move your application's window to external display = your DPI changes:
http://blogs.windows.com/windows/b/extremewindows/archive/2013/07/15/windows-8-1-dpi-scaling-enhancements.aspx

> I don't believe drawing those vector curves can be faster than blitting a bitmap
I think you are wrong.
Drawing a polygon on the GPU is much faster than blitting a bitmap from system RAM into video RAM.

>so dumb, but still too obvious and boring
It’s not a rocket science, indeed.
However, the thing is, using GPU for rendering 2D graphics and text leads to huge performance gain.
Due to various reasons, it's very hard to implement on any non-Microsoft platform.