Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)AK
Posts
1
Comments
301
Joined
2 yr. ago

  • As much as I like to shit on Epic, but UE 5.x is pretty much innovative with each minor release. Watching the release videos of what the engine can do in realtime is always impressive. They are used as realtime backgrounds for movie sets.

  • Nah, explicit sync is the objectively better model if you want high performance. Android went for explicit sync right from the start and from what I gather also Intel and AMD prefer it. The problem is, that the graphics stacks on Linux have been using implicit sync for ages and so far no one dared to change the status quo. Nvidia was "simply" rejecting implementing an inferior mechanism in their driver. While somewhat understandable, it was still a decision on the back of their users.

  • I am not a big fan of this, because you then rely on the scanner manufacturer to produce good quality results.

    I scan everything using VueScan and that has a special mode for text documents. A single page with OCR ends up being about 25kb as PDF. It removes folding edges, sharpens the letters, etc.

    If that software gets new features, my scanning experience improves automatically, even though I still use the same scanner for 10 years now.

    With relying on the firmware, I would have long ago stopped getting updates and I either was ok with the results or I could throw away the whole device.

    Just as people here recomment to separate printing from scanning, I recomment to separate the hardware and software.

  • The problem is IMO much bigger. Every connected and/or IoT device becomes physical waste if the vendor shuts down the backing infrastructure.

    Every product (physical or digital) should be considered as a unit with the required technical infrastructure. Companies/producers should only have two choices: keep maintaining the infrastructure or publish everything necessary for individuals and/or a community to take over. This must be ready from the moment such a product enters the market and it must be part of the "will" of the company so if it goes bankrupt, the whole process can be triggered more or less automatically.

  • The bigger issue (IMO) is, that you now have a hard requirement on the startup order of your services. If another one happens to get the IP assigned automatically befor your service starts that requests it explicitly, you now have a conflict that you manually have to resolve.

    DNS is the only sane solution here.

  • Do you think being maintainer makes you some kind of all knowing being? That's not how that works. You write code and review code of others.

    If there are multiple maintainers, you may obviously not even notice what another maintainer is doing; then you wouldn't need multiple maintainers with write access if you could handle it all by yourself.

  • But everyone does keep their license. A company can not really take over in the sense that you lose your old code. They can stop developing in public but keep using your code, but so can you keep using the last public version and keep developing it. Or you can take your contribution and apply it elsewhere.

  • It's not the same model though, is it? I can buy XBox, PS an Nintendo games in a shit ton of physical or digital stores. So there are different channels. There is no equivalent on iOS. If you don't want to publish in the app store, no one will be able to install your app (developers with own certs and enterprise customers with mdm excluded).

  • ... in which case you would have seen that they delete a path referenced by an env var being set earlier.

    How likely do you think it would have been to notice, that this env var will turn up empty in your specific case?

  • I like the company and their commitment, but I would still not recommend them (I have two Tuxedo laptops myself and see others from my colleagues): all I saw were loud. Most cannot run completely without fan active, none were able to keep the fan quiet if you put even a little bit load on it. If you put REAL load on it you go deaf.

    I would really like them to be perfect, but all I've seen disappointed me, unfortunately. And I am not sure I would take that gamble again when I replace my current one.

  • Don't get me wrong: I didn't want to downplay the work or doubt the progress. Quite the contrary. I think the current state is alpha and once the first sets of apps are finished it should be beta. Then polishing until release, a few weeks of release candidate phase and then release.

    Basically I think it's too far along already to call it pre-alpha.

    (Unless the intention is to "release" it as beta with 24.04 to emphasize the missing apps... then consider what I said pointless.)