

Emergency thermal shut-off is a very common function in various pieces of computer hardware. And if throttling doesn’t help it should indeed shut down, rather than cause damage.


Emergency thermal shut-off is a very common function in various pieces of computer hardware. And if throttling doesn’t help it should indeed shut down, rather than cause damage.


Yes there is also device managment for them. Our company uses Jamf. Not sure how it compares to AD group policies in power but some restrictions, settings and updates get pushed on the regular.


So much.
I have installed various pieces of third party software to fix some of them, but still, those are things I dislike about macOS.


No, instead I’m forced to use macOS at work.
And Microsoft Teams, which is terrible, but somehow still better than Cisco Webex.


Not that many it seems… Ignoring extremely pricey ones, I could find the Lenovo ThinkVision E65 LFD for what converts to 1200 USD in a local shop. And even that is not really price competitive.


HDMI has never been an open standard (to the best of my understanding anyway). You’ve always needed to be an adopter or a member of HDMI forum to get the latest (or future) specs. So it’s not like they’ve just rejected a new idea.
Okay not publishing the spec is still the same, but something else is new nonetheless.
AMD is an adopter*, they have the spec and they implemented a driver for 2.1 intended to be open sourced in Linux. But they were still blocked from publishing it. For HDMI 1.4 that wasn’t an issue yet from what I’ve found (though it’s always hard to search for non-existence). Open source implementations of HDMI 1.4, even in hardware description languages, seem to exist.
*you can search for “ADVANCED MICRO DEVICES” here to confirm for yourself
That was actually preinstalled by IT at my workplace! It’s a pretty nice little archiver. Seconded.
To make the desktop experience bearable: AltTab, Forklift, Rectangle, Ukelele, MonitorControl, Amphetamine, Firefox, Thunderbird, qView and duti to set the latter three up as the defaults.
As a package manager I’m pretty happy with nix-darwin, now I get all the CLI tools there, and what isn’t packaged, like wireshark for example, I get through my nix-controlled homebrew.
Coming from a Linux userland you might want to replace some coreutil packages with their GNU variants. I ran into one case where the GNU grep was much faster than the BSD version preinstalled in macOS for example.
What I haven’t found a good solution to yet is Filesystem support. Both NTFS and ext4 are missing. I currently have a Linux VM just for that. I think Paragon sells a driver, have been meaning to look into it more, but haven’t.
Edit: To be fair to macOS the App called Preview is a pretty good PDF reader in my view.
PS: If you ever need to use dd on macOS, be aware that there are /dev/rdisk handles instead of /dev/disk for the un-buffered access. Its significantly faster for dd shoveling.
PPS: You will probably have to turn off what they call “natural” scroll. macOS inverts the default for some reason.
when I look at Gnome I don’t doubt for a second where I want to be
Yeah me neither, from the other side, lol


I’m also not familiar with how these things work. But it looks like the problematic commit was reverted:


All these naysaysers in the comments here… It’s obvious you have to keep the development pipeline moving. Just because we have one free codec at the stage of hardware support now does not mean the world can stop. There are always multiple codecs out there at various stages of adoption, that’s just normal.


Wow what a betrayal, poor guy. He works for an open source release for a year and they just rip it away from him. Fuck Alex Austin.


Ahh right! Thanks for correcting me. Now that you mention it I remember too. It also makes sense, a year is roughly 365.2425 days long. Add 0.25 (one out of four), subtract 0.01 (one out of hundred), add another 0.0025 (2.5 out of thousand which is 1 out of 400)


Leap years are each fourth year, except each hundredth year, except each thousandth fourhundredth year.
1896 leap year
1900 not leap year
1904 leap year
…
1996 leap year
2000 leap year
2004 leap year
…
2096 leap year
2100 not leap year
2104 leap year
Then you just arrange the 10 year window in different positions to overlap 1 to 3 leap years to reveal the three outcomes of the bug.
- / - - - / - - - /
- - / - - - / - - -
- - 0 - - - / - - -
- is a normal year, / is a leap year, 0 is an exceptional non-leap year.


Sure, here’s one example for each case:
1 day off: 3650 days before 1907-01-01 is 1897-01-02
2 days off: 3650 days before 2027-01-01 is 2017-01-03
3 days off: 3650 days before 2025-01-01 is 2015-01-04


The python version seems buggy as fuck. Depending on which year you run it it’s off by 1-3 days


Not sure about the enconding
Right click on video -> Stats for Nerds


Did you misread? They wrote “the only reason left to boot from a DVD”, so the use case you replied with has nothing to do with the topic.


Just recently there was a guy on the NANOG List ranting about Anubis being the wrong approach and people should just cache properly then their servers would handle thousands of users and the bots wouldn’t matter. Anyone who puts git online has no-one to blame but themselves, e-commerce should just be made cacheable etc. Seemed a bit idealistic, a bit detached from the current reality.
lol
lmao