Ok... i'm up late, and i'm ANGRY... >;( which means i'm complaining about something that has bothered me for weeks now.

In GitLab's redesign, they decided to add a 'margin' to the actual content, and as a result, that means the scrollbar is offset with it!!!

Listen, i like the scrollbar, esp on huge issues/pull requests/commits(!), i just like to scrub through stuff with it... but since it's offset by a couple pixels... guess what! now i can't grab the scrollbar by moving my mouse to the right side of the window! No... instead i keep accidentally 'selecting' all the text on the page or something silly and have to readjust myself... every time.

What a tragic design!! Do not do something like this even if you can't help it!

My favorite logo in all of the computing sphere for me happens to be the XCB logo.

I have absolutely no clue what the hell it signifies. I'm not sure why it's a cat. I don't know why they made him so innocent and cute. I don't know why he is blue. But most certainly, I have absolutely no idea why the hell his paws are _like that_.

But, this is an asynchronous X11 library (think: xlib). Make of that as you will. It apparently _needs_ this logo.

One little funny thing that's been on my mind is redoing the canvas system for the new engine, which is not really the best... The current one is basically an immediate draw, meaning.. no state can be held... you just, draw draw draw draw, but this is contradictory to the fact that all game objects in a typical game session have retained state anyway (how do you think collision works??), thus allowing them to retain their existence a little more consistently.

I'm not exactly aiming to create a scene graph however, and I don't really want nesting or anything fancy (doesn't make much sense), though it would also be nice if you could move layers and the relative content within them move as well... apply effects, so... a scene graph, kinda.. :) Perhaps a nested approach could be separate from the drawing context in general, though, and just be a literal thing that's handled externally.

Anyhow, I cooked up a (very lazy) image showing how it'd work.