Programmer Humor

It was originally written as a C DLL utilized by a Visual Basic front end. The C DLL used the Win95 API, though, so it wouldn't have worked on anything but Windows 95 and onwards. I subsequently ported the entire thing to C# but still using the same API to do the actual playing of the audio (I experimented with using DirectSound instead but that was really not appropriate for an application doing its own audio mixing). Now I'm working on an iOS version and I couldn't give two fucks about Windows at this point.

Is this a LibreWolf on Mac reference, because I hate this so much about LibreWolf on Mac lol.

I mean, macOS has a lot of issues but the one hoop needed to run any unsigned app is "right-click app icon, click open".

Oh cool, let me install this software, what, it won't install because it's missing quicktime? Oh it needs directx 8 runtime? That could be a problem. Let's advance the clock, 2004, that should be fine... What do you mean you can't run .NET 1.1 applications and so that won't run?

Ironically, wine is more likely to have a path to easily run those programs under Linux, but if you had a Linux binary from that era you'd likely have a hard time getting that to run, probably harder than the microsoft scenario. So old Windows software is more likely to run under Linux than old Linux software...

I ran into old software (for Windows XP), especially games not working even with compatibility mode used for the install and opening of the app. Now if the publisher or Steam or some party puts a tad bit of effort, then yes, those games can work, although I guess a big part of that is also hardware and driver related if talking about 3D games for instance.

Oh, it should work and it will if you put all the files in the right places yourself by say installing it on wine and copying the changes to the wine system directories over, but starting in Windows 11 running the installer gets a deliberate "this program isn't meant for this version of Windows" error.

Yep.

https://vigor.sourceforge.net/

AI in vim is actually often convenient.

:set ai

Cool, now it will keep track of my indentation.

Now sometimes that gets in the way, and while you can:

:set noai

Usually it's best for me to:

:set paste

And that's my take on the utility of AI in vim. (that is what you meant right, there isn't some other AI people are thinking of right?)

If you use it to make sure your deployment is sane and that your dev system didn't have an invisible component that you assumed as a dependency, great. Containers are a great tool for simulating minimalist clean setups and not incurring surprise hidden dependencies.

If your application carries a whole container with it for the user to use and that's the only way to use the software, that's going to be annoying. 'docker style' for bloat, flatpak/snap depends on the app but sometimes the application functionality is broken by the container boundaries. Admittedly flatpak/snap is frequently acceptable, really depends on if the program has a lot of interoperability features that get broken in the flatpak/snap runtime model.

If your application only is deployable as a pod... I'm almost certainly going to want to avoid it if at all humanly possible. Pods as a self-hosted approach to do what you want, ok, fine and I own all that. If a third party pod is happening, I tend to see some part of it fall over it and no one can figure it out because the application is microserviced into oblivion and no human actually understands the whole flow... It's possible also to do this with 'traditional' application delivery, but a pod is a very high sign that no one even bothered thinking hard about how it should come together and play nice with others.

Hmm I'll email Linus