5 ms·
Wait, where are the Windows binaries? Oh, I see. They trying to be smart and say "cross-platform" because now it runs on more Linux distros. That's not smart,
by romanovcode 11y ago
Wait, where are the Windows binaries?
Oh, I see. They trying to be smart and say "cross-platform" because now it runs on more Linux distros. That's not smart, that's faulty marketing. And AFAIK it already was running on 90% of Linux and also on MacOS.
- alfanick 11y agoit is a big news - it really is cross-platform - OS X version was really outdated
- romanovcode 11y agoUsing it on my Mac every day and didn't even notice that it was outdated. But thanks for info.
- masklinn 11y agoThe OSX version is/was a fork of htop 0.8.2
- akerro 11y agoAnd there was no BSD version.
- floatboth 11y agoWell, it did run on FreeBSD, with a requirement to mount procfs :)
- yorwba 11y agoBSD is not Linux. htop now supports several different Unices.
- kajecounterhack 11y agoNo, it's accurate marketing. Asking for htop to be available on windows is kinda silly if you recall that htop is "top++" and depends on having a unix filesystem. "Cross-platform" is a contextual term.
- noselasd 11y agoWhy does it depend on having a unix file systems ? (note that it doesn't use /proc on e.g. freebsd)
- masklinn 11y ago> depends on having a unix filesystem. It doesn't do that. Before the multiplatform changes it did depend on having procfs (linux's I assume since BSDs had a non-identical procfs yet weren't supported), aside from the OSX fork which ripped out all the /proc access and replaced them with OSX API calls. What it does depend on is ncurses.
- kajecounterhack 11y agoAh, thanks for the correction. I had no idea it wasn't using procfs anymore, or that darwin was using something very different. TIL :)
- masklinn 11y ago> I had no idea it wasn't using procfs anymore It still uses procfs for Linux (since that's there by default), but not for the other ports. Consider Platform_getLoadAverage for instance: * linux uses /proc/loadavg[0] * freebsd and openbsd use sysctl({CTL_VM, VM_LOADAVG})[1][2] * OSX uses getloadavg(3)[3] [0] https://github.com/hishamhm/htop/blob/master/linux/Platform.c#L143 https://github.com/hishamhm/htop/blob/master/linux/Platform.... [1] https://github.com/hishamhm/htop/blob/master/freebsd/Platform.c#L123 https://github.com/hishamhm/htop/blob/master/freebsd/Platfor... [2] https://github.com/hishamhm/htop/blob/master/openbsd/Platform.c#L181 https://github.com/hishamhm/htop/blob/master/openbsd/Platfor... [3] https://github.com/hishamhm/htop/blob/master/darwin/Platform.c#L144 https://github.com/hishamhm/htop/blob/master/darwin/Platform...
- Piskvorrr 11y ago"Until it supports MY specific OS, it's not cross-platform, wah wah wah!" In this way, there is no cross-platform program at all, because there's always something that's not supported. How is Windows a measuring-stick of compatibility for UNIXlike tools? (And why would this ever be useful on Windows, which has completely different way of managing processes?)
- romanovcode 11y agoI don't even use Windows. I'm just sayin' calling something cross-platform when it doesn't support most used OS is wrong.
- Piskvorrr 11y agoI very much doubt that Windows is the "most used OS" where console applications are considered. That's just like saying "why do you call this airplane engine cross-platform when you can't even use it on a car? I don't care that it fits most airplanes, there are far more cars!" Different purposes.