HN user

RDeckard

85 karma
Posts1
Comments103
View on HN

Delphi and Visual Basic 6 were definitely not the pinnacle of UI development.

All layout was pixel based.

I'd say that was a very reasonable trade-off at the time, when most screens were somewhere between 640x480 and 1024x768 resolutions at 72 DPI. This simplified UI design sufficiently enough that VB/Delphi provided an optimal solution that, yes in hindsight, would most accurately be described as a "local maxima" for the environment and the time.

Making windows resizable required much complex ad-hoc code

I remember there were ActiveX controls one could drop onto their form that would attempt to derive the layout based on initial positioning of controls, i.e. that a lower row of buttons should be anchored to the bottom of the window, while textboxes are took up a larger area would automagically resize with the window.

I am curious: is YouTube going to re-encode all existing content with VP9? If so, I am wondering if they do anything special to preserve as much quality as possible. Are there any techniques to do that? (For example, certain JPEG transforms such as rotation can be applied with zero quality loss.)

I was wondering the same thing. The features page claims "copy on write fork implementation" but that is not universally true. A cursory look at the code suggests that every allocation is a Win32 file mapping object (aka NT section) underneath, which the fork worker (mm_fork) remaps into the forked process. This means the memory is shared between two processes, and not in a CoW fashion. A write to the memory region from the forked process will be visible in the parent. These are not correct semantics for fork.

I am hoping I misread the code and someone can prove me wrong here, because it looks like a cool project with a lot of potential.