calvin_

Except no one wants to write drivers in Forth.

Have fun with libGL!

The deep irony is Windows has achieved its herculean backwards compatibility through dynamic linking.

Not because it'd be any good, but because it'd be cheaper for Microsoft.

RCS dying on the hill of DDR training blobs seems a bit ridiculous to me when the system is much better elsewhere. RYF in action!

people chose those things due to superiority, not any dogmatic reason. i.e. wordpress was there and does what you expect it to. (besides, linux displaces windows on the server, but not on the desktop for reasons.)

imagine an alternate universe where wikipedia was a ghost town devoid of information, but hey, it's open!

just because someone is a dev (even a good one) doesn't mean figuring out IRC is worth their time

disclaimer: i have 80 buffers in my irssi session, but i know why most people aren't me

just PowerPC assembly before, but mostly on a much smaller scale (RE or writing basic blocks)

they don't need BT, but rather, you can't let the VM manage its own PTEs. virtualbox lets you configure that - just turn off nested paging. vmware unfortunately doesn't do that. if you can get the VM booting in safe mode, flipping the safety options from system properties perf button might help too. (I will say ME runs fine where 98 doesn't. weird!)

VMware still supports it, it just uses an old version of Tools to do so.

that page is a bit outdated; i do know VBox has changed for at least devices like SVGA, so I think it's possible. that said, i don't use vbox, so i can't say for sure

I'm perfectly happy with Preview.app; I'm curious what's not working for you?

Most of these apps are just dipping mustards around HOTP/TOTP, so it's a standard protocol. There's an ecosystem of standard applications around it; Twilio, Microsoft, and Google all make pretty popular ones.

I think you underestimate a lot of the APIs for a platform and how they influence an app; Cocoa provides a lot for an application; for example, it can provide a lot of the structure for a document related app in terms of i.e undo/redo, window management, etc.

Windows based editors are a dying breed. The Unix and web-based editors have sucked the oxygen out of the room.

Except VDI products for enterprise already exist and are much cheaper than Mighty. AWS, Citrix, VMware, and probably others play in this space.

I use a client that does make it easy, but I shouldn't have to worry about this. Mailing lists are basically full of people who use email in an exceedingly specific way no one outside of mailing list enthuiasts do anymore. I use a graphical email client, as do my coworkers, as do our customers. We don't care about top vs. bottom replies, plain text vs. email, etc. - those who do have lost touch with the average email user.

As someone with lots of experience porting stuff to AIX, this is fairly accurate. AIX takes a malicious compliance stance to POSIX.

The worst part is that the AIX compatibility layer IBM created for i is closer to Unix normalcy than AIX itself.

I wouldn't be surprised if there's more i shops using newer software than AIX shops, nowadays. IBM's own ports of things like nginx, node, and Ruby to "AIX" were all to support i.

I know a friend who's employer was throwing out an E4A. OS/400 is also pretty interesting from an architecture perspective too.

I was never paid by IBM to do anything; this is a hobbyist endeavour.

[Here's a C# example](https://github.com/dyu/ffi-overhead/pull/10).

Nowadays, that's not an issue with Windows. On all my machines, the drivers either came with Windows or Windows downloaded them from Windows Update.

Not really - they're just Clevo rebrands with the bare minimum effort. When graphics switching was new, they were quite helpless.

If you have the SWF, you can run them in the Flash Projector, the standalone Player. What'll be problematic is if they preload resources from external locations.

Maybe in Ontario. It's uncapped out east.