Live data from Hacker News

An app for M1 Macs that plays the sound of a fan as CPU usage goes up

fanfan.rambo.codes

431–440 of 454 posts

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#431
post #291

Earlier quoted context omitted.

"PC" was "personal computer" years before the IBM PC. Just look at old computer magazines. The whole reason the phrase "IBM PC" existed was to differentiate it from the other PCs that already existed. "IBM" was the adjective. "PC" was the noun. Because of its success in offices, "IBM PC" became just "PC" the same way other words like "omnibus" became just "bus" because it's simpler to say.

As I recall, the most widely used term early on was "microcomputer", to distinguish the small home computers from the larger "minicomputers" (e.g. the DEC PDP-11 of blessed memory). The term "personal computer" was also in use, but the use of "PC" was not common until after the introduction of the IBM model 5150 (whose actual product name was the "IBM Personal Computer"). Since then, you might refer to any of a varie…

I was there too if you need anecdotal evidence, my Dad worked in marketing for Apple - notable for being the ad manager for the 1984 ad campaign and you're wrong. I mean that ad was an attack on IBM PC's. The answer is on wikipedia too, https://en.wikipedia.org/wiki/Personal_computer

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#432
post #292

Earlier quoted context omitted.

This will never be the same as Electron due to differences in the various rendering engines (e.g, Webkit2/WKWebView/WebView2 all have subtle differences), and this isn't accounting for version differences. The reason people ship Electron is because Electron is literally the same thing wherever you shove it. You can search on this very forum for comments from the dev who migrated Slack from per-platform-WebViews to El…

That’s what I meant by evergreen webviews. I think you missed the point of what I was saying. There are not evergreen webviews cureently. They currently only update webviews on major OS releases. with windows 11 they will ship an evergreen webview for use by Teams and will abandon trident as well. it’s currently a react/electron app that will run in the OS webview on Windows instead of in Electron. This is precisely…

>I think you missed the point of what I was saying.

I don't believe I have, and I believe you're missing the point - much like everyone who says that platform-specific WebViews are the solution to Electron.

Go actually read the comments from the devs who migrated away from WKWebView. What you are describing will not solve what they sought to get away from.

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#433
post #297

Earlier quoted context omitted.

Look, I think you're missing the point: - First, the marginal value of 1MIP has plummeted in the past 40 years to near nothing. When my dad programmed on the 1401, another .01DMIPS would be worth ~$100,000 (1960s dollars, or $86 million 2021 dollars/DMIP). Now another 100000DMIPS is worth almost nothing (Maybe $0.006/DMIP today). So there's really no debate about declining marginal utility of computation vs. time. -…

I am definitely missing your point. I was originally responding to your comment that the marginal utility of doubling performance is diminishing. I don’t believe it is. I never said the marginal utility of a DMIP or whatever isn’t decreasing, which I don’t think is relevant, since processor performance increases exponentially, not linearly. I also never said that it will be possible to keep on improving performance a…

> I was originally responding to your comment that the marginal utility of doubling performance is diminishing. I

Your ambiguity in your responses is why I've been both addressing the marginal value of DMIP and marginal value of log(DMIP).

> since processor performance increases exponentially, not linearly.

It doesn't look very exponential right now. Looking at consumer-focused processors, we've gone from 176k DMIPS in a package in 2011, to 298k DMIPS in 2014, 320k DMIPS in 2016, 412k in 2018, and now we've finally got a substantive boost again to about 850k in 2021, though these are golden parts that aren't really available.

> The rate of improvement is what is diminishing, not the value of the improvement.

It's both --- the improvement is getting much more expensive, and the value is going down.

> Fabs are still motivated by demand from their customers and competition.

The vast majority of fabs have stopped being anywhere near the leading edge, because costs are too high for the benefits. At >100nm, there were about 30 manufacturers close to the leading edge; then at 45nm we had about 15 manufacturers who were close to the leading edge. Now it's Samsung, TSMC, and Intel-- 3, that's it. And even Intel is starting to question whether it's worth it versus than pooling effort together with others to amortize the massive capital costs. Most parts and applications are staying further and further from the leading edge, because the areal density benefits to cost are smaller and the tape out costs are ever higher, and because the vast majority of applications and semiconductor units do not need the performance.

Whereas 30 years ago, almost anything that could shrink, did, because of areal density benefits and because almost all applications desired improved performance.

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#434

Earlier quoted context omitted.

You can only use one external monitor

And that's only on the laptops. Two monitors are supported on the Mac Mini.

hdmi port doesnt work on many m1 mac minis, is this counting the two usbc or hdmi plus 1?

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#435
I prefer to read a graph, also another one for memory, another one for GPU, another one for network out, and another one for network in. This is in Ubuntu 20.04 with Gnome whatever.

Honestly, this fan sound seems to give much less information than what I am used to.

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#436

Earlier quoted context omitted.

So why does linux ux feel slower?

On the exact same hardware linux always felt much faster to me, I remember doing stuff like resizeing finder windows vs KDE's dolphin, finder would be all janky and laggy and KDE wouldn't miss a frame

Yeah, my go-to for speeding up Macs is to throw Linux on them.

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#437

Earlier quoted context omitted.

So why does linux ux feel slower?

X-Windows: …A mistake carried out to perfection. X-Windows: …Dissatisfaction guaranteed. X-Windows: …Don’t get frustrated without it. X-Windows: …Even your dog won’t like it. X-Windows: …Flaky and built to stay that way. X-Windows: …Complex non-solutions to simple non-problems. X-Windows: …Flawed beyond belief. X-Windows: …Form follows malfunction. X-Windows: …Garbage at your fingertips. X-Windows: …Ignorance is our…

Almost all major distributions use Wayland as of today.

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#438

Earlier quoted context omitted.

To my knowledge, .nomedia files are created on Android to prevent the folder from being scanned for media. I don't think it's due to "anything besides", but Android in particular. I haven't tried configuring the Android Syncthing app to exclude .nomedia files, but it may be possible.

Then it's not .nomedia but some Mac specific file. I can't recall what it is since I stopped using syncthing on my Mac haha. I rarely use it unless I kinda have to.

IIRC, MacOS is well known for leaving .DS_Store droppings absolutely everywhere. If you ever shared a pen drive with a MacOS user, it would come back full of .DS_Store junk all over it. It might be that one you're recalling.

Re: An app for M1 Macs that plays the sound of a fan as CPU usage goes up

#440
post #412

Earlier quoted context omitted.

No, that would be OS-provided GUI components (or sometimes manual reimplementation), similar to how most win32 apps had the same right-click menu behavior.

The unique thing about this is that it takes a widget from the app, and expands it out while blurring the rest of the screen. So it’s not just an OS gui component.

Blurring happens inside the UI server process. Here is a related technique in macOS: https://avaidyam.github.io/2018/02/17/CAPluginLayer_CABackdr...

Basically, it's like an iframe — you declare what contents this portion of screen should have, and the render server composes it onto the screen. The render server is shared between all apps (just like in X11), so it can compose different apps with dependent effects (like blur). Apps don't have direct access to the render server's context, just like a webpage doesn't have any way to extract data from a foreign iframe.

Post reply on HN