• 1 Post
  • 69 Comments
Joined 4 years ago
cake
Cake day: July 21st, 2021

help-circle


  • I wasn’t clear and that seems to have cause some confusion. I was talking about the Linux kernel itself, and only the Linux kernel.

    There are two sides to the Linux kernel: internal exposed to drivers and such, external syscalls exposed to the public. That’s what I was talking about.

    All bets are off with 3rd party software. That’s just a general problem in software development. It’s not specific to Linux, and it’s why vendoring libraries is recommended.

    This is why all the 3rd party software is frozen at a point-in-time with fixes backported in distros like Debian or RHEL. It fixes the problems of devs being mercurial. The distro is the SDK. It creates a stable base, and it works rather well.

    Unfortunately, most software relies on libc and a compiler. Both of which can be problems, and both of which are external to the Linux kernel. There’s not much which relies on only kernel syscalls.



    1. The user land API/ABI is stable to a fault in Linux. The kernel API/ABI is unstable.

    2. Companies are cheap. They hired web devs then tasked them with building a desktop application rather then hiring people to write native apps. They had a hammer and used it to fix every problem they had.

    3. macOS is just as affected by electron apps as a Linux is.

    4. Electron is horrible, but it does bring apps to many an OS once Chromium is ported.

    5. Open protocols or open APIs from the company would fix the non-native app problem.








  • jollyrogue@lemmy.mltoTechnology@lemmy.worldRIP Mac Pro, I guess.
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    1 month ago

    The M-series Mac Pro was always for companies which were going to rack them and use them in render farms. Normal people was never its intended market. It was more of an Xserve successor.

    Apple would need to design a different CPU for the Mac Pro, and the limited market doesn’t make it feasible. Descending the M-series CPUs from the A-series limits what the designs can do.

    There are rumors of a CPU split in the Apple lineup. iPhone, iPad, iMac, Mac Mini, MacBook get the A-series, and MacBook Pro, Mac Studio. Mac Pro get the M-series. That would make sense, and might give them some room to expand the “Pro” procs.







  • The primary ways in which the Mozilla Foundation earns money is through search partnerships, donations and grants.

    Yes. It’s the same thing with the Linux kernel and other large FOSS projects. There isn’t a perfect fit for Android, but it would be better than the way ASOP is run now.

    As for Red Hat, this comes down to subscriptions or enterprise offerings, neither which really apply to a consumer OS unless you’re willing to pay a subscription fee out of pocket.

    Consumer devices ship with proprietary software which is licensed all the time. It could be a library or an entire OS. Consumers are not the target market, like consumers aren’t the target market for RHEL.

    The prime example is Windows. It’s licensed to Dell or whomever and ships with the hardware. The license is baked in.

    Some people might be willing to pay if the price is reasonable enough. Android has support for major vendors, so using it as a base would be a boon to people doing things like media boxes and signage.

    I doubt there will be much to be earned from offering consulting or training, either, unless they make Android exceedingly confusing to use.

    It’s the opposite. Make it easy to use. Companies pay for tools which reduces developer time.

    The only companies that would pay for Android are OEMs who are already making thin margins, and effectively it’d drive the price of non-iPhones up.

    The smaller OEMs would pay for licenses, PS hours, and backend services. They don’t have the expertise or budget.

    Samsung? They’re going to keep doing what they’re doing because they have the expertise and budget to fork from upstream. It’s possible they would rally around Android, like companies have rallied around the Linux kernel.

    OEMs do this with Linux already, so it would bring Android more inline with the norms.