101–110 of 185 posts
This is pretty nice, but why do a lot of Mac apps insist on living in the menu bar?
Making 1 click to access is faster than typing the app name in finder. Dock is usually full and used for different type of apps. Makes also constantly visible output possible with standard ui patterns.
Earlier quoted context omitted.
Absolutely this is worth packaging for KDE. Although I imagine if you don't have the motivation to make it in the first place, you likely don't have the motivation to package it.
I feel like this is so lazy bothering maintainers for it is not great.
What was the hardest thing you cut to keep it tiny? I keep adding "one more useful thing" and have to talk myself down.
Earlier quoted context omitted.
It's 1st of May here, so probably not doing it today. Looking into it a bit more when I get back from the parties. but it's basically just three files: QML for the UI, some python code to parse /proc data and a metadata file.
> It's 1st of May here Is that date significant somewhere? It was an nice sunny Friday for me.
Earlier quoted context omitted.
To save me 10 mins and $2, is this posted to GitHub somewhere?
Absolutely this is worth packaging for KDE. Although I imagine if you don't have the motivation to make it in the first place, you likely don't have the motivation to package it.
Earlier quoted context omitted.
It's 1st of May here, so probably not doing it today. Looking into it a bit more when I get back from the parties. but it's basically just three files: QML for the UI, some python code to parse /proc data and a metadata file.
> It's 1st of May here Is that date significant somewhere? It was an nice sunny Friday for me.
In North America we have Labor Day in September to distance it from the historical associations with actual organizing and police brutality.
Earlier quoted context omitted.
For some reason the app supports a separate standalone window mode as well [0]. It's not clear why the developer took the trouble to support two different modes when the menubar mode doesn't seem to add anything (like a live-updating icon for throughput). Well, I can think of one reason why it wasn't that much more trouble. François Chollet had a nice tweet [1] on why removing human cognitive friction is resulting in…
> removing human cognitive friction is resulting in needless software complexity This is kind of a hilarious statement just on the surface. Isn't removing burden from humans the whole purpose of software? How can you call the complexity "needless"?! (the actual tweet seems to go into a bit more detail around being incentivized to find good abstractions)
Doesn't work for me. Says "No USB-C ports detected", although I'm pretty sure my monitor is connected via USB-C, and the monitor also has a built-in USB hub where my USB keyboard is connected to.
There's an issue on Github for this now: https://github.com/darrylmorley/whatcable/issues/2
Seems the Intel southbridge isn't known to expose the needed info.
Good stuff, but it's telling me that my USB-C Thunderbolt cable has been plugged in upside down but the connector handled this. I was not aware that you can plug in something into USB-C upside down!
What does it mean to be ‘upside down’ if the connector handles both orientations?