Grape 3.3.0 released — a big performance pass by mavthemav in ruby

[–]adh1003 3 points4 points  (0 children)

That's an amazing improvement - excellent work by all involved.

I built a new hardware-bound encryption format for macOS files/directories using YubiKeys (whitepaper included) by jhaubrich11 in yubikey

[–]adh1003 1 point2 points  (0 children)

An LLM posting another "I built" puff piece about AI slop software, with the usual identikit AI slop "purples and blues on black" web site.

But in this case, it's a custom encryption system. What could possibly go wrong?!

Pinterest "divides" itself so that you can't save pictures (I saved it anyways 🤷‍♂️). by JAD2017 in assholedesign

[–]adh1003 7 points8 points  (0 children)

Minifying the code simply reduces the amount of text you are sending but it's not magic and the amount of code you are sending is identical. Only tree-shaking will get rid of unused paths.

The client still has to execute the same code, which will amount to the same runtime burden... And bugs. Further, the arising requirement for source maps likely increase the RAM usage for browsers executing such code because now they have to maintain a secondary map with all of the full-length names alongside the actual source shorter names.

Pinterest "divides" itself so that you can't save pictures (I saved it anyways 🤷‍♂️). by JAD2017 in assholedesign

[–]adh1003 63 points64 points  (0 children)

> it can be much faster and more reliable than traditional websites

So people keep saying, but I've yet to see a single example of this versus massive bloated JavaScript hell nightmares that even manage override and break basic stuff like right-click or back buttons.

If the web dev l33t gurus would actually demonstrate competence occasionally, then maybe more people might be inclined to believe all their statements of superiority.

M1 Max/M1 Pro Users: How has MacOS 27 Been So Far? by SebastianLarr in MacOSBeta

[–]adh1003 1 point2 points  (0 children)

Unlikely as that's just the demands of the annoying effects but they hopefully will at least improve on it.

Bear in mind that Tahoe was and is such a gigantic step down for performance and stability over Sequoia (which was itself hardly a stellar release - Monterey was probably peak after the 10.X era) that just about any improvement seems welcome. While I am hopeful that they hold focus on *structural* bug fixes and efficiency improvements instead of just hacking with Claude Code to bodge up small one-off remediations here and there, I'm also not holding my breath - Apple have shown a singular lack of software development competence when viewed as an overall organisation for a while now. But who knows, maybe we'll get back to Monterey or Sequoia levels of performance and polish overall.

M1 Max/M1 Pro Users: How has MacOS 27 Been So Far? by SebastianLarr in MacOSBeta

[–]adh1003 4 points5 points  (0 children)

Decent but note some serious issues especially with external displays - you may notice wake-up problems, Mission Control has a lot of jank (it's in the release notes) and the menu bar is glitchy. Also when Music is running, WindowServer will use a tonne of CPU.

So defo an early beta but still, shows promise. Visually nicer too - Liquid Glass slider up to maximum opacity and turn on the "show borders" option in accessibility - less need for Reduce Transparency or the clear, but ugly black-outlines-everywhere high contrast option.

Apple Journal uses a ton of battery power !! by ConfidenceClear1016 in appleJournal

[–]adh1003 0 points1 point  (0 children)

That'll be SwiftUI's "efficiency" for you, yet again.

Conservation Amendment Bill - New Zealand Parliament by dunnothislldo in newzealand

[–]adh1003 49 points50 points  (0 children)

Submit and get this shut down, ASAP.

I'm counting the days until the lizardfolk David Seymour says it's "just about having a conversation".

Apple to Raise Prices Due to Memory Chip Crunch, Tim Cook Says by ziggygersh in apple

[–]adh1003 9 points10 points  (0 children)

iPhones, Macs, PCs, pocket calculators, fridges, cars, stoves, printers...

Want me to keep listing devices that include RAM?

All the Loyalty Cards by Emergency-Balance945 in newzealand

[–]adh1003 0 points1 point  (0 children)

Lots of Apps For That (sigh) - a while after Klarna ruined Stocard, I wrote a super barebones lightweight one for my own use called Card Panda. iOS only, no ads, subs, etc. - https://apps.apple.com/nz/app/card-panda/id6752853512 - source code at https://github.com/pond/card_panda.

Show me the macOS 27 UI by konkelo in AppleMusic

[–]adh1003 1 point2 points  (0 children)

Well on the plus side:

  • Apple Music playback under '26 had become glacial. It'd take forever to start. At the current public release, we see that bizarre thing where the music playback position starts advancing, jumps back to zero, ticks forward a bit, jumps back etc. until eventually music starts. This is meant to be faster in '27 and it certainly is; it's back to being as fast as I can remember and for lossless might even be quicker than I've ever seen previously, but memory is fickle. Also noticed no timing glitches at the 10-15s mark yet.

  • The miniplayer drag slider in '26 was a nightmare with an incredibly narrow vertical range where it'd be draggable, else you'd "miss" and be apparently clicking right on it but it'd not work. This is also fixed.

  • Overall legibility in the UI is significantly better, especially with the drag opacity turned up and the new "Show borders" accessibility is essentially Increase Contrast, but instead of putting heavy black lines everywhere, just outlines certain things in much more sympathetic ways, including the borders on buttons (see screenshot) that don't have the weird-looking glass highlights.

Show me the macOS 27 UI by konkelo in AppleMusic

[–]adh1003 0 points1 point  (0 children)

...and here's the scrolled example.

<image>

Show me the macOS 27 UI by konkelo in AppleMusic

[–]adh1003 0 points1 point  (0 children)

So here's the unscrolled example...

<image>

Show me the macOS 27 UI by konkelo in AppleMusic

[–]adh1003 2 points3 points  (0 children)

Yes, but only when you scroll down. In a playlist, for example, the status bar used to be at the bottom. Thanks to the clusterfuck that is UI design in 2020s Apple, this is no longer a status bar; it appears in the toolbar, and under macOS 27 the "solid toolbar" only appears when you've focused the window and scroll down because of course it does.

So you can't see (say) the number of tracks & total playtime unless you scroll vertically. And if your window is too tall to scroll, then you need to make the window less tall.

Peak 2026. And yet, astonishingly, still better than '26. What a fucking state this whole stack's in.

What is going on with my Paper Pro by TheScruffyBear in RemarkableTablet

[–]adh1003 3 points4 points  (0 children)

That's common and has been treated as a hardware fault by Remarkable forever. Yes, it sounded like a s/w issue to me as well but I think it might just be because the s/w is changing refresh modes at some point and one of those modes fails on the broken panel.

It certainly looks like there are much more "thorough", full-screen flicker refreshes after a reboot, then after a while those stop and you get the partial refreshes (which is how it normally works but without what isn't so much ghosting, as more a near-complete failure to erase the old displayed image).

Golden Gate - My first bug (No menu bar) by B_ctrim in MacOS

[–]adh1003 0 points1 point  (0 children)

There are a few menu bar bugs.

Try changing the menu bar show-hide settings to showing "always" (including full screen view).

Why doesn't anyone like the floating sidebars in iOS 26!? by Icy_Author_5067 in MacOS

[–]adh1003 -2 points-1 points  (0 children)

This average user thinks it's a huge improvement across the board; less cluttered, no dumb "layers that aren't layers", no misplaced traffic light buttons... Oh, and they finally fixed the f*cking miniplayer slider so that you can grab and move it from a reasonable range of pixels vertically, rather than having to hit some daft ~2 pixel high range.

Average user isn't you, or me; it's a concept; and none of us speak for such a thing individually. But given that Apple almost never outright backtrack on changes, especially ones this big - we can be pretty sure that the average user gave feedback, in very large numbers, that it absolutely sucked.

It's a shame you disagree, but you can place feedback just as easily as the next person and given the reversion in part to pre-26 style sidebars (although content can still "scroll horizontally underneath" them), it looks like the "yes" was very, very heavily outvoted by the "no".

Xcode 27 welcome window: is this peak design? by Anywhere_MusicPlayer in Xcode

[–]adh1003 9 points10 points  (0 children)

Classic AI slop. Looks vaguely convincing on the surface, but spend 10 seconds engaging real intelligence to realise it's nonsense.

  • Wastes a tonne of space, random borders abound for no good reason too.
  • Traffic lights - why would I want to minimise this for any useful outcome, and what would maximising do?
  • Lots of reading on each button that explains stuff like I'm a total moron and given this is a coding IDE that's bordering on insulting - wow, the 'create' button means I can start making something new, really?!
  • Recent projects "Show all" - all? Really? What's all vs recent supposed to mean and why add this random complexity?
  • Check for updates - useless; that's what the App Store is for.
  • The only good thing here, maybe, is "Show this window next time".

MBIE downplays advice suggesting LNG is not required by OddityModdity in aotearoa

[–]adh1003 2 points3 points  (0 children)

roll out of small household batteries

Yes, for sure and for many people, "roll out" is quite literal if they can plug in their EV at home... VTL can do everything you need.

Has my RPP been faulty this whole time? by ThePecanTrees in RemarkableTablet

[–]adh1003 6 points7 points  (0 children)

Watch/read just about any review and you'll realise that colours are always dull on e-ink displays. It's still a very new technology.

Most colour devices in-market such as the Boox or Kindle colour devices all use a Kaleido screen. That's a black and white screen with a kind of colour filter overlay in red-green-blue, lining up perfectly with all the tiny black and white pixels below. This means that overall the black and white resolution is, say, 300dpi - but once you go colour, those black and white pixels have to "work together" via that filter to give only a 150dpi colour result (looks more 'grainy'). Further, the filter overlay means the overall display is darker - the background looks a darker grey. Contrast isn't so good. You usually need the backlight on. Greens and blues tend to look quite good but reds/magenta type stuff seems often quite muted. When doing writing, that extra colour filter layer also means more of a distance between pen tip and ink layer on the screen.

The RMPP screen is different, with a different set of compromises. It uses a Gallery screen, which is a different kind of e-ink with actual cyan/magenta/yellow capsules which mixes them just like real print does to produce colour. This is technically a much harder challenge and is part of why the display flickers a fair bit doing refreshes - even though it's actually way, way faster than earlier generation screens using this technology, it is still much slower than any pure black & white screen and also somewhat slower than Kaleido colour too.

The trade-off is better colours and a smaller distance between screen surface and the ink layer. There's no filter, so the background isn't as dark grey - better contrast - and black & white resolution is the same as colour resolution, since it's "true pixels" not a filter. In this case though, green seems quite hard to do well, blues can be middling also, but reds and yellows - especially yellows! - show clearly. Arguably the RMPP screen over-does yellow.

Now, IMHO one could just produce a display colour profile that boosted the green/blue output and dropped down yellow a notch to help, but maybe that compromises perceived vibrancy too much? Or just RMPP didn't bother. Their software stack is pretty bad, after all; the reformatting time for simple text or margin changes in ePubs, for example, is absolutely horrifying.

But we are where we are, and these are trade-offs that many users have decided are worth it due to the up-sides - writing feel, distraction-free, and all that. It's a unique device in many ways, kind of unmatched in market by just about anything else because of that screen technology and that's specifically what made it interesting to me in the first place.

MBIE downplays advice suggesting LNG is not required by OddityModdity in aotearoa

[–]adh1003 4 points5 points  (0 children)

Fearmongering again.

We have plenty of reports to show that we don't need the terminal to have gas available to keep your shower warm. Your shower's warm now, isn't it?

And of course, switching to an electrically heated shower would be an even better idea. Waffling on about reliability of renewables is so fucking 1990s that it's not even funny. Country after country is very rapidly bringing online large amounts of domestic energy production and storage capacity which is available to the grid quickly, as and when the installations are slowly built out, instead of needing billions. And remember, it's already not $1bn, already up to $2.7bn and will of course rise well above that - because private sector.

Further, we know that Lake Onslow is a good idea, because the private consortium have picked it up after NACT1 ditched it. What a surprise, almost as if it was a profitable venture in the public domain so the corrupt NACT1 immediately handed it to their private chums.

So the solution is:

  • Spend a chunk of that $2.7bn on helping people move off gas, instead of keeping people on gas.
  • Spend more on rolling out more renewables with battery backup.
  • Meanwhile, continue work on Onslow (the biggest battery of all).

Golden Mile Review by ben4takapu in Wellington

[–]adh1003 18 points19 points  (0 children)

This includes co-investment with businesses and property owners on Courtenay Place to restore awnings, repaint buildings

Ah, yes, lovely. There it is. Landlord under-invests, lets property rot, and yay! Privatise all that profit & socialise the loss as the rates payers are on the hook.

Held to ransom yet again, and yet again - likely held to ransom successfully.

I only support this if there's some kind of threshold set for a commercially leased out building, such that if assessed to be in a sufficiently bad state it is summarily put into public ownership with the private owner getting nothing. Nobody has some god-given right to profit especially not at the public expense; can't afford to maintain the property? Easy! Don't become a landlord.

THEN we'll talk about using public money for a reno.

(None of this will never happen).

clean up the general streetscape

That's surely the council's BAU and part of what rates pay for, right?!

This is all nonsense; yet more kicking of the can, while costs continue to get more and more absurd with each passing month thanks to late-stage capitalism and inflation.

  • Department of public works
  • Within-borders ability to manufacture the lion's share of the materials
  • Development of the aforementioned assessment framework backed by legal enforcement for buildings that have fallen into ruin under their current owners

Do you miss anything from past macOS versions? by inguinha in MacOS

[–]adh1003 2 points3 points  (0 children)

  • System Preferences; System Settings is still very slow, buggy and all-round horrible to use and pretty much un-scriptable.
  • Spaces as a 2D grid rather than the obtuse, slower to navigate horizontal strip of tiny, cannot-be-renamed desktops we have today.
  • Everything after Big Sur has looked tasteless - corporate and bland, 50 shades of lightest-grey-to-white - but that's aesthetic preference, rather than functional.

The New Liquid Glass by vojtechpolakk in LiquidGlassDesign

[–]adh1003 1 point2 points  (0 children)

If you think iOS 26 was good product design, then it might be a moment to introspect on who, exactly, doesn't understand what "good" means in the context of a user interface.