Programming thread

What's the best color programming socks to wear when playing with arduino?
Are shaved legs necessary or is HRT enough? Do the requirements change if I upgrade to raspberry pi?
What "color?" Well, they have to be more than one, of course. The classic rainbow is what most of my fellow trans-sisters of color use, but I generally prefer pink and light blue stripes since they bring out my eyes and my navel piercing, And long socks are a lot easier to put on when your legs are shaved, trust me.

The same goes for the Pi. In fact, I recommend the Pi a lot more because it's much easier to get Node running on it.
 
What's the best color programming socks to wear when playing with arduino?
Are shaved legs necessary or is HRT enough? Do the requirements change if I upgrade to raspberry pi?

pink and white or light blue and white. the faggier the better.
personally I think black is a classic color you can't go wrong with, with or without taking dick in the ass while writing code.

you can probably get by the shaved legs requirement by having a buttplug.

1608505107069.png
 
Last edited:
What do you guys think about the Win32 API? I'm learning it right now and I'm curious to know what others think of it.
 
What do you guys think about the Win32 API? I'm learning it right now and I'm curious to know what others think of it.
I don't do much with Windows nowadays. I do my coding on ubuntu like a normie and we used linux machines in university. I wouldn't be surprised if the code was spaghetti legacy microsoft garbage tho.
 
  • Informative
Reactions: BLEACHED.COM
What do you guys think about the Win32 API? I'm learning it right now and I'm curious to know what others think of it.
Think of it in what respect? I mean, it's C with all the advantages and drawbacks that implies. What exactly are you using the API for?
Typically I just dip into it when I need some threading, memory-mapping, system info, or file I/O functions - writing a GUI is generally far too much of a pain, though I do recommend at least looking at a "Hello World" example for that.
 
Think of it in what respect? I mean, it's C with all the advantages and drawbacks that implies. What exactly are you using the API for?
Typically I just dip into it when I need some threading, memory-mapping, system info, or file I/O functions - writing a GUI is generally far too much of a pain, though I do recommend at least looking at a "Hello World" example for that.
Do you enjoy working with it? I'm more used to C++ code, so the legacy C code with a shit ton of macros and the procedural style of it (vs OOP) kind of threw me off guard a little bit, but I'm slowly getting used to it. I'm implementing a GUI for a GameBoy emulator I programmed (which is not quite complete as of now).
 
  • Like
Reactions: Strange Looking Dog
Do you enjoy working with it? I'm more used to C++ code, so the legacy C code with a shit ton of macros and the procedural style of it (vs OOP) kind of threw me off guard a little bit, but I'm slowly getting used to it. I'm implementing a GUI for a GameBoy emulator I programmed (which is not quite complete as of now).
I thought most programs nowadays will use a GUI framework like Qt or GTK to abstract away all the nasty details and allow cross platform support. Don't take my word for it though because I've never written a serious GUI for anything.
Also I don't bother writing multithreaded code because I haven't written any performance critical code that would really benefit. And if I did, OpenMP pragma parallel would probably do a better job than me using fork.
 
I thought most programs nowadays will use a GUI framework like Qt or GTK to abstract away all the nasty details and allow cross platform support. Don't take my word for it though because I've never written a serious GUI for anything.
Also I don't bother writing multithreaded code because I haven't written any performance critical code that would really benefit. And if I did, OpenMP pragma parallel would probably do a better job than me using fork.
You are correct, I don't think anyone actually programs GUI with the Win32 API directly anymore. I'm simply curious to mess with it.
 
  • Like
Reactions: awoo
Do you enjoy working with it?
Working with a "classic" C API with strong legacy commitments has its upsides - it's mostly immune to faddishness and the discipline required to work in C still remains. But certain aspects, such as packing parameters into WPARAM/LPARAM have definitely aged past "anachronism" and into "barbarism", I think. I'm sure you're dealing with plenty of that if you're doing GUI.
I do find it a hassle how many "don't care" parameters you have to zero out or discard in Win32, because of course this far predates function overloading. 99+% of the time you're not going to be opening a mutex handle with some particular alternate credentials, or whatever.

It's also regrettable that SEH is usually off the table.

I'm implementing a GUI for a GameBoy emulator I programmed
Are you going through Direct2D or just going old-school and using GDI?
 
Last edited:
You are correct, I don't think anyone actually programs GUI with the Win32 API directly anymore. I'm simply curious to mess with it.
You can take a look at it and time box, but I would honestly advise against messing with low level Win32 GUI at all without a wrapper. Most of the challenge from dealing with it comes from it's, franky, retarded structure and massive inconsistencies. It's just a bunch of teeth pulling and there's very little of reusable knowledge to be learned from it in my experience.
 
  • Like
Reactions: Marvin and awoo
You can take a look at it and time box, but I would honestly advise against messing with low level Win32 GUI at all without a wrapper. Most of the challenge from dealing with it comes from it's, franky, retarded structure and massive inconsistencies. It's just a bunch of teeth pulling and there's very little of reusable knowledge to be learned from it in my experience.
I expect no less from the geniuses at Microsoft. I remember reading some blog post saying how old Office files (2003 files like .doc) implemented an entire file system within the file, but they fucked up the B tree or something and so the files were way larger than necessary. I can't find that blog post now but here's Joel Spolsky's Microsoft apologist explanation https://www.joelonsoftware.com/2008...-formats-so-complicated-and-some-workarounds/
Even after reading his article I'm convinced all four of these points are true:
  • are deliberately obfuscated
  • are the product of a demented Borg mind
  • were created by insanely bad programmers
  • and are impossible to read or create correctly.
 
Working with a "classic" C API with strong legacy commitments has its upsides - it's mostly immune to faddishness and the discipline required to work in C still remains. But certain aspects, such as packing parameters into WPARAM/LPARAM have definitely aged past "anachronism" and into "barbarism", I think. I'm sure you're dealing with plenty of that if you're doing GUI.
I do find it a hassle how many "don't care" parameters you have to zero out or discard in Win32, because of course this far predates function overloading. 99+% of the time you're not going to be opening a mutex handle with some particular alternate credentials, or whatever.

It's also regrettable that SEH is usually off the table.


Are you going through Direct2D or just going old-school and using GDI?
I am using GDI for the GUI and OpenGL for the actual game emulation. I might try something else eventually, I don't know yet.
You can take a look at it and time box, but I would honestly advise against messing with low level Win32 GUI at all without a wrapper. Most of the challenge from dealing with it comes from it's, franky, retarded structure and massive inconsistencies. It's just a bunch of teeth pulling and there's very little of reusable knowledge to be learned from it in my experience.
Thanks for the tip, I'll keep that in mind.
 
Anyone know any good starting point/examples/docs for writing pnp device drivers on windows? Language probably doesn't matter since I've dabbled in a bunch of langs and it's going to be about the complexity of a hello world, but c# or c/c++ would be preferred. I have a usb steno pedal that doesn't have 64bit drivers and doesn't register as a hid because the manufacturer is dumb.
 
Back