• 2 Posts
  • 152 Comments
Joined 4 years ago
cake
Cake day: July 21st, 2021

help-circle
  • Exactly. I’ve been up for 27 hours, but I finally have a booting Gentoo install now. 😃

    Gentoo installs are not that bad these days. However, back in 2005, it would take, like, a day or so to compile the kernel on my old Pentium M Thinkpad. I would run through the install, start compiling the kernel, and go to sleep/work/whatever. I would check on it periodically to see if anything went wrong, and eventually it would get to the point where I could reboot and find out I messed something up and had to start over. That was like a week, and then I installed Ubuntu. 😂




  • 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
    ·
    2 months 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.