[–] 1 point 1 month ago

Actually, just to add to this..

Technically, it doesn't even stop them adding contributor code to a proprietary implementation if that WAS the case (which it clearly isn't). They'd just need need the contributor agreement to pass ownership of any contributions to Canonical (which is generally in a lot of the agreements anyway, to protect against developers trying to sue later).

  • source
  • parent
  • context
  • [–] [S] -1 points 1 month ago (6 children)

    Your comment reduces my article to vague claims of ignorance and a basic mention of something you admittedly only glanced on. The article is much richer in depth than your comment suggests, I encourage people here to actually read it so we can have a proper discussion. I promise you that it won't disappoint even if you don't agree fully with it.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago

    no but the dev controls it. if the dev is using the ndk and the dev is not doing the extra step of disabling/configuring it there should be in "fat" apk with each binary for each platform according to the docs. then the installer can figure out which version to use.

    the x86(/_64) version is used for Chromebooks i believe. some devs will split the apk if they configured it to reduce size so you would need to specifically go get an x86 apk version.

    the cases where a dev would disable it is if they only want to support specific instructions that might be platform specific or say a library they use doesn't support target ABIs

  • source
  • parent
  • context
  • [–] 1 point 1 month ago* (4 children)

    Like that 2800 year old Assyrian tablet?

    “Our Earth is degenerate in these later days; there are signs that the world is speedily coming to an end; bribery and corruption are common; children no longer obey their parents; every man wants to write a book and the end of the world is evidently approaching.”

    Cuz that's fake.

    Also Andy Warhol coined "15 minutes of fame" in 1968. A concept which is heavily contingent on electronic communication. So I completely disagree that the notion that youth are planning out their lives like a lottery has been said about every generation... or any generation for that matter.

    Because the lottery aspect, aka virality, is at best 30 years old.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago

    Waydroid has never worked well on any system I've tried it on. And sadly, it doesn't really work on ARM Linux installs (ironically), which is one of the places I need it.

    Lepton should work better on ARM systems since it doesn't also bundle x86_64 emulation. It leaves that to FEX, which is cleaner.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago

    not building x86 is up to the developer, the default according to the native sdk

    The default behavior of the build system is to include the binaries for each ABI in a single APK, also known as a fat APK. A fat APK is significantly larger than one containing only the binaries for a single ABI; the tradeoff is gaining wider compatibility, but at the expense of a larger APK. It is strongly recommended that you take advantage of either App Bundles or APK Splits to reduce the size of your APKs while still maintaining maximum device compatibility.

    At installation time, the package manager unpacks only the most appropriate machine code for the target device. For details, see Automatic extraction of native code at install time.

    so if you use the apk from your phone it may or may not contain an x86 compatible binary.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (2 children)

    from what i can tell, waydroid has some translation layers libndk or libhoudini. however majority of android apps require some kind of java runtime. native apps you (the ndk build system) generally create a release for arm + x86 and its up to the release pipeline to build for each platform. i don't use waydroid much outside of playing around with it for a few minutes when i get bored. however I'm curious if a lot of the issues people have with waydroid is because of taking an arm version of the apk from their phone and not grabbing a x86 one?

  • source
  • parent
  • context
  • [–] 4 points 1 month ago*

    I wonder if this is the same as when people got their sticky hands on WYSIWYG editors in the late 90s. Sure they could make some stuff by themselves, but it wasn't really viable. We might just have to get over that hill... That very tall and exhausting hill...

  • source
  • parent
  • context
  • [–] 6 points 1 month ago (1 child)

    This still happens to this day especially with startup companies that are like tech adjacent. They get one dude who built something that the company essentially hinges on but it's not really good. It works for them and when it breaks the dude is the only one that can fix it so he's treated like a rock star. I've done the same thing as what that guy did you several times.

    Several years ago I'd see this all the time with companies that were just a website or a social media company. Showing my age here but I remember one place that was like a fashion blog and they had one web dev who was treated like a rock star. he was their dev, their it guy, anything computer related. problem is he built the entire thing in dreamweaver and actually knew very little HTML or CSS or Javascript. so I was brought in on contract to fix their site that was having massive issues. I told them straight up "you need to start over from scratch" and I remember asking the guy what his stack was. that was a foreign concept to him.

  • source
  • parent
  • context
  • view more: ‹ prev next ›