Recent submissions

Comment · 7 years ago
Comment · 8 years ago
Comment · 8 years ago
>It requires knowing your foreground and background colors at render time, which is an unnatural requirement when you want to do GPU-accelerated compositing

Most of the apple hardware supports ARB_blend_func_extended or even EXT_framebuffer_fetch, which lets you to implement subpixel blending with ease. Otherwise you just have to fall back to traditional alpha blending and render each glyph in three passes for each color channel, which is not that hard either.

Comment · 9 years ago
Comment · 10 years ago
> There's plenty of other software out there that's meant to be used with tiled windows.

There is a tiling window manager INSIDE blender used to control its window frames. It works pretty much like any other tiling manager. You immediately grasp the idea if you've ever used one.

Comment · 10 years ago
>It could've been a word processor and it would still be terrible.

Like vim or emacs?

>window panes are very much a standardized UI part which has a completely non-standard interaction design in Blender. For no reason.

It's called "tiled window management". Lots of people find it more comfortable to use than the classic overlapping windows.

Comment · 10 years ago
Comment · 10 years ago
"Draw the first letter of the alphabet please".

'a'

No. The right answer is 'A'. We will stop here because it's obvious that you don't have the necessary skills.

Comment · 10 years ago
They do, but to actually use it, to pass it anywhere, you have to either wrap it in some other object (std::function, as comex pointed out) or use a template.
Comment · 10 years ago
In C++ lambdas have limited size (about 3 machine words). If it's context is larger than that, the data may be allocated on heap (if compiler can't optimize that allocation out).
Comment · 10 years ago
>The JVM itself has a certain amount of unavoidable overhead

That is not a "certain amount of overhead" but the inherent incompatility with the modern hardware. With Java writing cache-friendly code is extremely difficult: boxing and indirections are encouraged while primitive types are cumbersome and value types are possible only through the direct byte manipulation. Memory overhead is enourmous. A simple collection like a hashmap of short strings can have up to a 75% overhead.

Comment · 10 years ago
Java.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton