On a technical level, his work is brilliant. With no budget, he puts me in a CGI space that I really can't tell is CGI, and invokes all of the feelings that are familiar to anyone who has snuck around where they really shouldn't be.

https://en.wikipedia.org/wiki/The_Oldest_View

For background, JMS knew the widescreen transition was coming so filmed everything in 16:9. As he put it at the time, it didn't really cost more, you just had to pay more attention to lighting at the wings. All CGI was done in 4:3 because it was thought to be easy to rerender in the future. Alas, the digital assets were not preserved properly and when the time came for DVD, nobody wanted to pay for more work. There may be places where they used the 16:9 masters, but anyplace where there was CGI, particularly where they were compositing over live action, basically chopped the top and bottom of the 4:3 resulting in a sub-VGA mess.

It made everyone weep.

The module init function is where you would normally create the module object (PyModule_Create) and decref it if an error occurs. The blog example is utility code that you would call within the module init function to add an enum.

Someone should really create a blog post compiler to catch these sorts of things :-)

I blended the python type system with a large low-level type system (STEP AIM low level types) and a smaller set of higher-level types (STEP ARM, similar to a database view). I already was familiar with STEP, so I needed to really grok what Python was doing under the covers because I needed to virtualize the STEP ARM and AIM access while making it look like "normal" Python.

It took me back to the old days of source diving and accumulated knowledge that you carried around in your head.

https://www.dave.org/posts/20220806_python/

Parasolid was v1 and old school C, then they got the C++ bug like many of us at the time and did ACIS as v2.

At that point, most people just go to the gossip corner of social media and spend the rest of their day being fed six hours of outrage.

I agree with you that a certain portion of images are no longer meaningful, but it's tough to say a-priori what those are. So keep them all. The real problem is that photos often have notes on the back, but digital images rarely have any metadata.

I foresaw this problem back in 2002 and have been using a time-oriented naming convention and keeping little XML files with notes. I posted a little rant about it back in the day and made some simple tooling, which has been good enough to keep some basic notes with my photos.

https://pixtag.org/

Sure, if you do a full accounting of costs you may win or lose, but fundamentally people are paying for simplicity. Because almost everyone is lazy, or too busy, or too afraid of random scammers, or whatever, and they played their cards right to become the Sears Catalog from the 19th century in the 21st century.

edit - and one thing that helped them get there is the return policy, so if you get one of those scam sellers, or they sent you wrong crap, opened crap, or just plain everyday crap, you press a couple buttons, maybe drop something off at a UPS store, and problem solved. That definitely shields them from the fallout from their endless listings from sellers like QWERTY123 and ZXCVBN789, and provides an advantage over any other online ordering that doesn't have the same massive advantage of scale.

They are a bigger fish than the mom and pop stores but that just means that it will take a little longer for the Amazon Prime monopoly cash flow to devour it.

Implementing the UI for one exact use case is not much trouble, but figuring out what that use case is difficult. And defending that use case from the line of people who want "that + this little extra thing", or the "I just need ..." is difficult. It takes a single strong-willed defender, or some sort of onerous management structure, to prevent the interface from quickly devolving back into the million options or schizming into other projects.

Simply put, it is a desirable state, but an unstable one.

It is absolutely hypnotizing.

It won't kill an entire nest late in the season, but will knock down their numbers so that they aren't as prevalent.

And you make a good point about the SIO bus - this was when every other machine had unshielded ribbon cables everywhere. Their devotion to daisy chained serial really crippled them in terms of speed, and when USB finally arrived, I initially scorned it due to the prejudice formed by my experience with the Atari peripherals! It turns out they were on the right track all along!

They have done a good job balancing the numbers so that everything requires some tradeoffs. More species/tech gives more choices and interesting variability. Some species make very efficient drives, others inefficient, more powerful but produce tons of excess heat, those folks also produce good passive cooling, others great active cooling but power hungry, etc. The ship hulls tend to match the sizes of the drives and weapon hardpoints of that race, but often work much better when outfitted with different kit (perhaps with some wasted space)

Plus the fleet management is pretty good. You fly your flagship, but you can park ships and switch your flag to different ships. So I might fly a fast little scoutship, then switch to an armor-clad behemoth surrounded my 20 of my heavy-hitting henchmen for some different missions.

https://endless-sky.github.io/