←back to thread

CPU-X: CPU-Z for Linux

(thetumultuousunicornofdarkness.github.io)
170 points nateb2022 | 2 comments | 07 Jul 25 13:52 UTC | HN request time: 0.003s | source
Show context
mmh0000 ◴[07 Jul 25 16:59 UTC] No.44492320[source]▶
[flagged]
replies(5): >>44492393 #>>44492464 #>>44492651 #>>44492668 #>>44496566 #
jcelerier ◴[07 Jul 25 17:05 UTC] No.44492393[source]▶
When I type all that (if I type them correctly, I do a lot of mistakes so I need simple icons to click sometimes), it really doesn't look like CPU-Z in my terminal, I wonder what I'm doing wrong?
replies(1): >>44492522 #
1. Brian_K_White ◴[07 Jul 25 17:18 UTC] No.44492522[source]▶
Those commands do provide the information. They never claimed it exactly matches the graphical layout.

And I don't think they are even claiming that a graphical presentation of the same info is necessarily wrong or pointless, they are simply saying, that's a lot of c++ for merely wrapping the text in some gui widgets.

It's a fair observation.

I can imagine generating say an html rendition that looks almost the same in a few k of shell. Maybe there's more to it and it wouldn't be so simple, but that is what it looks like.

replies(1): >>44492585 #
2. jcelerier ◴[07 Jul 25 17:23 UTC] No.44492585[source]▶
> Those commands do provide the information. They never claimed it exactly matches the graphical layout.

but that's the thing, the target audience for "CPU-Z for Linux" is not people who want the information (because if you do it's of course trivial to google and find out about /proc/cpuinfo), it's people who want to use a software which is as close as possible to the original CPU-Z (so HTML layout definitely does not cut it either).

> I can imagine generating say an html rendition that looks almost the same in a few k of shell.

considering that the source code assumes that dmidecode won't be present (it embeds it) I doubt you'd reimplement the whole dmidecode in only a few k lines of shell. And that's just a small part of what CPU-X does.