ZILtoid1991

Likely I'll fix her blouse around the arms, other than that I think I'm mostly happy with it so far.

I'm currently developing on Windows mainly, but due to the end of life of Windows 10, I might switch my primary OS to Linux instead. However, despite Linux being called "developer friendly" I always preferred the tools available under Windows save for the command line shell of Linux.

My main gripes with Linux development is with the debuggers. On Windows, I have RemedyBG, a pretty good debugger with an easy to use GUI. On Linux, all I have is either GDB or LLDB, and a command line so far.

I looked into some of the "more mainstream" GUI options for Linux, all of them were just a separate tab for the same command line debugger in a text editor.

Please note that I'm the sole developer of my projects on the side of a full time job, so I don't have 1 month to spare to learn the in and outs of GDB, which in the days of useless AI slop articles littering the internet, might be even 1.5-2 months. I have a modern PC, any performance gains from not having a well-optimized GUI is negligible. No, I don't care about scripts. And no, unless I'm actually writing the code, the mouse is faster, not slower.

Firstly I want to get rid of my Gilette shavers since the cartridges are expensive for the handles and don't last so long, so I would like to move to some safety razor solution. At least I also reduce my plastic usage.

I'm also open for alternative shaving foam and after shave products.

It's a Windows system function that is used for creating an OpenGL rendering context, and is very cursed since you have to jump around a few hoops before you can actually use it. I barely managed to find the function signature, let alone any information on how does it work.

Context: Previously I used the CPU for rendering pixelart graphics, but then I realized I could not only render to a low-res texture that I then upscale, but also write a shader to do color lookup.

I'm under Windows, so my primary shell will be Powershell, which eats up the commas for some reason.

I'm a D developer who recently got into the whole WASM thing with it using betterC (I do plan to write my own very minimalistic runtime to allow me using classes yet again), and currently I'm looking into enhancing the language's support of WASM in one way or another, especially when it comes to two "exotic" types of WASM, externref and funcref (there's also exnref, but it's just before finalization, so I'm waiting a bit with that one).

Me and others also programming in D have experimented with LDC (D compiler with LLVM backend) attributes since those types supposed to be address space 10 and 20 pointers, but I don't know whether the issue is that LDC doesn't handle type/pointer attributes the way we expected it to thus ending up generating i32 instead, or that I specifically need to emit the types for the LLVM backend.