• 36 Posts
  • 3.35K Comments
Joined 5 years ago
cake
Cake day: May 31st, 2020

help-circle


  • The SSN is likely to appear in multiple tables, because they will reference a central table that ties it all together. This central table will likely only contain the SSN, the birth date (from what others have been saying), as well as potentially first and last name. In this table, the entries have to be unique.
    But then you might have another table, like a table listing all the physical exams, which has the SSN to be able to link it to the person’s name, but ultimately just adds more information to this one person. It does not duplicate the SSN in a way that would be bad.






  • (Other than things like locked down smart phone bootloaders, but that’s got nothing to do with the FOSS part of this discussion.)

    See, I disagree on that. If I know something I could (help to) build will only ever be used by a few folks and can never help most people, then my motivation is significantly lowered. Well, unless I’m truly just scratching my own itch, but even then I might choose to not scratch my itch, because I’d rather quit using the platform, if possible.

    And then, yeah, what the other person said about financing.

    For Android, there are various small efforts in terms of forks, with the biggest being LineageOS. There are even some commercial efforts, like /e/OS. I think, Huawei also wanted to do a fork or something. No idea what happened with that.
    But yeah, none of these efforts are hard forks, which can change more than superficial stuff. And it’s not for a lack of desire, but because it’s just such a ridiculous uphill battle to try to get anything noteworthy changed. Many times, LineageOS (and its predecessor CyanogenMod) had some cool features, which they later had to scrap, because they needed to follow what Google was doing and their features wouldn’t work with that anymore. If they would’ve seen any chance of a hard fork working out, they probably would’ve tried to go that route.



  • Well, any software needs to include a license of some form, if you want it to be usable by others. But if it’s not an open-source or libre license, then it’s a proprietary license. That’s not necessarily a bad thing. At that point, it depends on what’s actually written into the license. But it’s also not a good thing, as you miss out on various open-source benefits due to there being no proven legal compatibility with open-source licenses. Well, and if I remember correctly, FUTO’s license actively prohibits reuse of the code anyways.



  • Ephera@lemmy.mltoFunny@sh.itjust.worksbarrel roll
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    Well, I’m hoping, they also talked about whether she wants a public proposal. If she told him to ask her with a megaphone, whether she wants tea, then she’s hopefully sure enough. Well, and it’s not either like she’ll have to empty that cup of tea right then and there. There’s still plenty ways to back out, if she starts doubting herself.



  • I also like to use log statements or error messages as a way to describe what’s happening.

    Comments are only visible in the exact spot where they’re written, whereas decent names or log statements become visible in a second place, which makes them more valuable, but also increases the chance of them being kept up-to-date.





  • Android, Chromium.

    The problem is that:

    1. Google puts in more development power than anyone else. Any forks we’ve seen so far are only really soft forks, as in they only apply a few patches on top of what Google puts out, rather than taking the project in a new direction, because you’d be behind pretty quickly.
    2. These projects establish platforms that have shitty decisions baked in. For example, the Android dev tooling has Google ads/tracking as one of the built-in UI components, which is why even if you patch the OS, the apps will still be shitty. To actually change this stuff, you’d need a majority of users to switch to your fork and stay there for a few years.
    3. Partially, it’s only financially viable for Google to develop these projects, because they have those Android ads or benefit from a web with less tracking protection. This makes it extremely unlikely for any other organization to be able to splurge a similar amount of money, which brings us back to a fork just being unlikely.

    And so long as a fork is unlikely, Google can do shitfuckery quite similar to proprietary projects.


  • Die Verwendung der Vision Pro wird somit immer zu einen “Big Deal”. Man greift nicht einfach zu dem Headset, wie man zu einem Notebook oder einem Smartphone greift. Man muss sich für das Gerät richtiggehend Zeit nehmen.

    Ja, so ungefähr hatte ich mir das auch vorgestellt. Bei den normalen VR-Brillen machen die Leute das ja tatsächlich, indem sie dann eine Stunde lang Beatsaber spielen und dann ist wieder gut. Aber ja, keine Ahnung, was man mit so einer Vision Pro tatsächlich eine Stunde lang macht. Damit wirklich etwas arbeiten ist ja nur begrenzt geil. Vielleicht einen Film anschauen. Also alleine. Ist es dafür 4000€ geil? Kann ich mir nicht vorstellen…