• 0 Posts
  • 49 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


  • I’m very torn on disco. Season 2 is probably the best (due in no small part that it sets up SNW), but the rest are a chore to watch. Most of them have some neat ideas, but they’re badly executed more often than not. They also were too heavy handed with each season arcs serialization, most episodes don’t stand on their own, and the writing and consistency is just bad. I just finished the final season, and I’m glad they’re done with it so they can put more money on good Trek like SNW - hopefully they don’t screw it up eventually.





  • Apparently it’s not that the software is broken, it’s that the software being installed breaks Windows Update. There are reports from people that uninstalling StartAllBack, updating the OS, then reinstalling it back (renaming the install executable first) works fine.

    As much as being affected by this is frustrating to me (though this is all happening still on the dev channel, so for me it’ll be a problem for the future), I understand Microsoft’s rationale here. They can’t be expected to support every third-party tool that can break the OS, and it’s known that both ExplorerPatcher and StartAllBack relies on many hacks using undocumented APIs to work.

    In the last few decades that I’ve been using Windows, I never felt compelled to use shell replacements or customizations - the default experience always worked fine for me with a few tweaks. So, if anything I’m more frustrated at Microsoft that I’m forced to use StartAllBack, because MS went and removed options from the shell that existed forever and always took for granted, and then some.



  • This sounds like dev sour grapes but what the company was asking them to do seems better from the customer pov and for cyber security I’m general.

    As a developer myself (though not on the level of these guys): sorry, but just, no.

    The key point is this:

    […] we did not issue CVEs for experimental features and instead would patch the relevant code and release it as part of a standard release.

    Emphasis mine. In software, features marked as “experimental” usually are not meant to be used in a production environment, and if they are, it’s in a “do it at your own risk” understanding. Software features in an experimental state are expected to be less tested and have bugs - it’s essentially a “beta” feature. It has a security bug? Though - you weren’t supposed to be using it in a security-sensitive environment in the first place, it sounds perfectly reasonable to me that it should be addressed in a normal release as opposed to an out-of-band one.

    We can argue if forking the project is or isn’t extreme, but the devs absolutely have good reason to be pissed. This is typical management making decisions without understanding technical nuances and - from what is being told by the devs - not talking it through before doing it.






  • I mean, it was groundbreaking for its time and it redefined the genre and a lot of moviemaking in general, but it really didn’t age well as far as moviemaking goes. Yeah, it has severe pacing issues, is undeservedly way too long and it got way too trippy and abstract by the end. Frankly a whole lot of it feels like Kubrick masturbating over how great he is, with a lot of scenes being way too long and serving no real or useful purpose on on the movie.

    I could say pretty much the same about Solaris too (the original Tarkovsky version which cinephiles always rave about, not Soderbergh"s, which I actually prefer), and if rumors are true, apparently Kubrick took a lot of ideas from it.

    And I say all that as an avid sci-fi fan. The books from Arthur C. Clarke are more enjoyable.





  • Just FYI, Barrier has been abandoned / unsupported for awhile. Although the last release mostly works, don’t expect future support.

    Its successor is https://github.com/input-leap/input-leap, and although there have been some coy maintainance on it, they have yet to provide an installable release, due to “reasons”.

    I use Synergy myself, which is the ancestor of both of the above. Although it started as open source, it has been turned into a commercial product a long time ago, which is why I’m not providing the link here. It’s still maintained, for better or for worse, but in the latest release-to-be they revamped the UI and for some reason I couldn’t get it to work at all on my setup - it seems to rely on some auto configuration / autodetection gimmickry which simply is not working here. To make matters worse, the new UI is essentially an electron app, which means it has become a lot more bloated. And then there’s also the telemetry thing. I’ve been using the old 1.1 legacy version, holding out hope that input-leap eventually lifts off.