• 185 Posts
  • 1.57K Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle
  • Oh yeah, and I just realized I’ve been a dum idjit and completely forgotten to mention the slightly hacky way you can enlarge some UI fonts that might help y’all @feoh@lemmy.ml & @Libb@jlai.lu.

    You may be familiar with this already, but by editing some system preference keys “manually”, you can crank up the default font sizes that apps, the OS, and some native UI elements use beyond what System Settings lets you do – both allowing for bigger font sizes in apps and the OS itself (but which can lead to UI bugs), and allowing changing eg. label or tooltip font sizes separately. This can only work for native apps, but even then sometimes it only sort of works at best and especially SwiftUI seems to just completely ignore these (because of course it fucking does).

    You can either use Tinkertool which also allows you to export and import the current state of all the configs that Tinkertool manages, and that’s pretty handy when you’re fiddling with your configs. It does eg. limit the system font size to max 24 for whatever reason though, so if you want to go over that limit you can hop in the Terminal and use defaults to add/change the preferences:

    (All of these take an int value)

    • NSFixedPitchFontSize
    • NSSystemFontSize
    • NSMessageFontSize
    • NSLabelFontSize
    • NSToolTipsFontSize
    • NSTitleBarFontSize
    • NSPaletteFontSize

    So for example to set the system font size to 15, you’d use defaults write -g NSSystemFontSize -int 15
    If you want to restore the default value I think it’s enough to just delete the key(s) you’ve changed: eg. defaults delete -g NSSystemFontSize.

    Caveat emptor, though: this is of course completely unsupported and you’ll probably run into UI funk depending on which sizes you change and by how much. For example NSLabelFontSize defaults to 10, and I’ve increased it to 12 which mostly works but some labels can get truncated if the label’s container doesn’t scale with the label font size which many apps assume will never change. It’s definitely not an ideal solution or even a good one by any means because UIs do kinda start borking once you change these too much, but might be worth a shot anyhow?


  • The low-friction you mention is probably one the thing most non-Apple users don’t get as, when it works (which is not always the case but often is), a Mac is like butter smooth and help so much getting things done. Linux is not there yet but when I started considered and testing it I was was surprised how usable it was already and, at least, in exchange of that tad more of frictions we do get back that control we have lost to Apple. And that’s a compromise I willing to live with — and so are my older eyes that can’t read ant-sized texts anymore ;)

    Yeah, even though the older I get the more I appreciate how macOS for the most part “just works” while still being a UN*X system at heart, I’m just so fed up with how each release is more opaque and less documented than the last, with more services that collect your data and send it to Apple even if you opt out. Also, because fixing bugs and incremental development isn’t sexy and marketing needs something cool, each OS release comes with an oodle of half-finished and buggy whizz-bang features that ultimately never really get polished, and end up sort of quietly abandoned and left to gather dust once Apple’s dev teams move on to working on the big OS release’s whizz-bangs, which often sort of overlap with previous whizz-bangs without actually leveraging them. So for example, instead of incremental improvements to Spaces and Mission Control – the two window management systems we already had – we got Stage Manager which initially didn’t even work with Spaces, and which nobody seems to have found a good use for yet, all the while multimonitor support somehow manages to get worse with every release, color calibration support was completely fucked much to the chagrin of visual arts folks, that audio balance drift bug is 10 years old, visual accessibility’s gotten worse, and so on and so on.

    It never was great, imho. For some time, I even considered using Windows in place of macOS (since it worked better to make text larger), I even invested in one of Microsoft laptop but I ended up giving it away as I just could not stand all the incoherence within Windows itself (it is such a sad state of affair). Also, I’m not a fan of their telemetry.

    The one issue I have not decided on so far, in regard to a full switch, is the phone.

    Hah, yeah, as much as I gripe about problems with macOS and Apple’s data collection habits or the occasional jank in Linux, using Windows feels so painful and intrusive that it should probably be covered under the Geneva Conventions, although part of that definitely just comes from the fact that I haven’t owned a Windows system since Win8 was a thing so my Windows encounters are pretty sporadic. It’s honestly surprising that the accessibility story is actually better in Windows, I really wasn’t expecting that.

    I’m in the same boat as far as phones go. Android’s UX somehow manages to irritate the everliving fuck out of me, so even a “degoogled” Android version is a non-starter for me, but there aren’t too many choices out there anymore (yay consolidation.) Sailfish OS is one that springs to mind, but as a project it feels more undead than really alive, and it’s closed source too.


  • I think this current Macbook is probably going to be my last Apple machine. I’ve been using both Macs and various Linux and BSD setups for the past ~25 years and I’ve appreciated having a low-friction, low-hassle UNIX OS with great UX. I’ve been exclusively running macOS for a few years now, and with each successive macOS version I just feel more and more that not only does the quality go down (even the fucking main development language, Swift, is buggy and poorly planned), but I also have less and less control over what’s actually running on my machine. For example, even if you toggle Siri off it’ll still do something with your data (fuck knows what) and actually disabling it requires first disabling SIP, and there’s also seemingly no way to opt out of Apple’s frankly creepy “trial” system which nobody really knows much about in the first place – they’re apparently running some sort of ML-related experiments on users via triald, but good fucking luck finding out much more than that.

    Even the accessibility situation is deteriorating, especially for accessibility clients (so things like screen readers etc) – the API is ancient, extremely poorly documented, and a huge pain in the ass to actually use from Swift. And don’t get me started on the terrible state of Apple’s developer documentation in general…




  • People don’t give precise percentages though when surveyed. They might round to typical fractions like 1/4, 1/3, or they might round to 10 or 20 percent.

    Nobody is saying “hmm, I estimate that it would be approximately 37 percent”.

    Of course the wisdom of the crowd does wonders for smoothing those coarse estimates, but still, if the crowd is +/- 10 of the real percentage value, I’d say they’re pretty much on the money.

    Oh yes absolutely, people would definitely just “eyeball” their estimate and the percentages we see in the graphs are population (well, sample) level averages, but I’d still say that the differences between these average estimates and actual reality are by and large much worse that “on the money”. To illustrate, if the estimate for some country was eg. 30% and the real proportion 40%, the relative error – off by a factor of 1.33 – would be smaller than if the estimate is 12% and the real value 2% – off by a factor of 6 – even though both have a 10 point error.

    So eg Poles’ and Argentinians’ estimates are both 12 percentage points off, but because Poland’s immigrant population is smaller that means that they overestimated its real size by 650% and so their estimate was 7.5x higher, but Argentinians were “only” off by 460% / 5.6x. 'Strayans were off by 7 points, but their relative error was only around 23%, which is still almost a 1/4 error and their estimate looks like it was the best out of these. The average global error was 100%, so on average people think there’s 2x as many immigrants as there actually are, and characterizing that as “pretty much on the money” is, well, maybe a bit generous





  • Thank you ❤️

    Yeah the colors are all there, the buildings in that area have a sort of copper-like cladding on them so they’re pretty funky just by themselves, and people really seem to like wild room lighting. I actually just realized I never did an sRGB conversion of this so I don’t know how it looks on most monitors.

    Here’s the original unedited version:

    Just looks a bit more subdued compared to how vividly orange everything there is when using the Mark I Eyeballs












  • hydroptic@sopuli.xyzOPtoScience Memes@mander.xyzThis feels wrong. I love it.
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    6 days ago

    Far as I understand it (which is not very far), i is a scalar even if you take it to be the complex number 0 + i. Just by itself i is the imaginary unit that’s defined as i = sqrt(-1) (edit: or, well, the solution to x² + 1 = 0, but same difference), and nothing in that definition says it’s a vector quantity.

    Even though complex numbers do extend real numbers into a 2D plane doesn’t mean they’re automatically vectors, and – again, as far as I’ve understood things – they’re still treated as single entities, ie. scalars. i by itself isn’t a complex number I think, though.

    The joke is that i² = -1 by definition, so i² + 1² = 0²

    Edit: eg. nothing on the imaginary number wiki page implies that the imaginary unit is not a scalar value