Untrue, there is a game (however it's not very good): http://cleancoder.com/space-war
351 karma · joined July 2, 2019
So while Maya is currently the standard, I don't believe that it's growing. It'll probably be around still in 20 years, with lots of studios having built their pipelines and tooling around it, with lots of people being trained in it, and because it's at the moment still better than Blender in some aspects like rigging and animation (afaik).
So I guess try separating your compensations from the original work and create a workflow that automatically applies them
PNG kinda sucks for high resolution stuff because decoding is extremely slow. The way PNG does lossless compression also only really works with flat graphic design, anything with gradients or texture blows up the file size.
I'm currently dual booting Windows & CachyOS with Niri and installation was incredibly smooth, including setting up secure boot or playing Windows games.
But now with the new Meta Ray-Bans featuring a light field display and with new media like gaussian splats we're on the verge of being able to make full usage of all the data those cameras were able capture, beyond the demos of "what if you could fix your focus after shooting" of back then.
Beyond high tech, there's a big market for novelty kinda-bad cameras like Polaroids or Instax. The first Lytro has the perfect form factor for that and was already bulky enough that slapping a printer on it wouldn't have hurt.
It says there's no standing, not be because the law is _unenforced_, but because plaintiff hasn't suffered any perjury _from enforcement_ (which is ofc bc the law isn't enforced, but that's besides the point).
---
And - maybe this is a stretch, but you also have to consider that the competing product (Servo) is written in Rust, while Ladybird is C++.
From what you read on hn, I think Rusts community being very liberal sort of resulted in memory safety being perceived as a culture war thing by some; ("authoritarian big compiler is forcing you to not free this memory" vs "the handmade c programmer with his artisanal allocations"). So Ladybird not being written in a safe language might be part of the appeal.
And I know that Ladybird is supposed to adopt Swift, but I don't think any single LOC has been written yet?
What I find annoying about the pattern is that it hinders API exploration through intellisense ("okay, it seems I need a XY, how do I get one of them"), because the TryFrom (sort of) obscures all the types that would be valid. This problem isn't exclusive to Rust though, very OO APIs that only have a base class in the signature, but really expect some concrete implementation are similarly annoying.
Of course you can look up "who implements X"; it's just an inconvenient extra step.
And there is merit to APIs designed like this - stuff like Axum in Rust would be much more significantly more annoying to use if you had to convert everything by hand. Though often this kind of design feels like a band aid for the lack of union types in the language.
There are a couple other projects that bridge S3 and LFS, though I had the most success with this setup.
This makes zero sense, right? Even if this was applicable, why would it need a standard? There is no interoperability between game servers of different games
SEPA flows typically have a more rough UX, maybe this would put off a lot of customers?
They could also just piggy back off of SEPA and just do the bog standard thing of asking the customer to transfer x amount of money with the reference abcxyz. If the customer then uses instant transfer in their banking app, they get to immediately confirm the purchase.
In case of Steam they could totally also just give immediate access and then revoke it if the payment doesn't happen within 36 hours.
what damage is it causing?
The thing I'm running into right now is that I should really learn the revset language, so that I don't have to constantly copy paste ids from jj log