CPU-X: CPU-Z for Linux
thetumultuousunicornofdarkness.github.io
thetumultuousunicornofdarkness.github.io
On a side note, and not wanting to criticize the people that spend their time working on something like this, that UI is the main reason why I still use Windows and macOS. Light grey on a white background, dark grey on a that blue background, a black AMD logo on a dark grey background, the padding around the text inside boxes...
I feel bad saying this when it's a free tool, but it's a shame that open source projects struggle so much with UI stuff.
Take a look at modern KDE and specially GNOME software, they are pretty well made regarding UI/UX best practices and GNOME even has a great HIG that they follow strictly on their stuff, you can't even say that regarding Microsoft own software anymore.
Add the Jetbrains search anywhere function if you really just innovate.
No more Hamburger menus.
In fact, Linux generally offers many more affordances for adjusting the appearance of the UI, especially in comparison to Windows and Mac. If you don't like way your system looks, you can change your UI theme settings, where corresponding options on the proprietary OSes are much more limited.
My friends keep telling me android is better because it offers so much more customization, and I keep telling them I don't want to customize, I just want it to be nice by default, and to me iOS is, so that is a selling point for me.
That's why software development and distribution are two different concepts in the Linux world. The core software is fully customizable, but people who want preconfigured out-of-the-box experiences can choose a distro that is largely defined by its configuration choices.
From their wiki: https://camo.githubusercontent.com/04c2219de0884fc8e6bf4d264...
The comment about the colors was based on the screenshots they have on the website, but based on your and other comments here, I can see that it's based on the theme we use use. That's why the AMD logo probably shouldn't be black with a transparent background as then it's hard to see the logo if you're using a dark theme.
Is this a huuuuge deal? Nope. But the programs are just not as polished as they could be.
CPU-Z also does not have padding around the text, it just has a different font, but in the screenshot at techpowerup[0] you can see that, e.g., the "y" in "MBytes" down right is touching (clipped) by the container box and the instruction flags also touch the left side of the box.
It is just that the font in CPU-Z is much smaller than the font used in the screenshots.
It's actually not bad imo.
For example, here you have commas and letters like "y" touching the borders of their box. On CPU-Z there's a padding around the text. Black AMD logo with transparent background? That won't work very well with a dark background.
Small things, inconsistencies, etc, are more common (but not exclusive) with open source/linux stuff. That's what I was trying to point out.
Welcome to Windows.
https://github.com/i-nex/I-Nex
$ man dmidecodethe daemon separates userspace from root domain, and ensures that the code running with root privileges is very small and easily auditable
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.
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.