TheFuzzball's comments

On: Exploring the scalable matrix extension of the App...

[TheFuzzball]

They will, just in time for everyone to have switched to pytorch!

On: A few facts about POSIX

[TheFuzzball]

The default shell on macOS has been zsh for over 4 years now, and they keep it up-to-date.

On: Apple must open iPadOS to sideloading within 6 mon...

[TheFuzzball]

The UI elements on iPadOS are necessarily larger to accommodate touch.

It's just a lot less information dense than macOS, and making it the same scale will make using it as a touch device harder.

On: Tvix – A New Implementation of Nix

[TheFuzzball]

> > A builder implementation using OCI instead of custom sandboxing code.

> Hermetic builds require some sandboxing; Using OCI containers seems like an obvious choice, but didn't exist when Nix was first created.

Presumably this would make this implementation Linux-only, since OCI isn't natively supported outside of Linux?

On: Apple explores home robotics as potential 'next bi...

[TheFuzzball]

Sonos would like a word.

[pquki4 → TheFuzzball]

I'm not holding my breath after seeing their stock price.

On: macOS Finder is still bad at network file copies

[TheFuzzball]

Window management in macOS has gotten worse over time.

There are at least 3 ways to do everything now (e.g. Classic windowing, fullscreen splits, Spaces, Stage Manager), and they're all a bit crap.

Apple needs to implement a proper window management API that lets you replace Dock.app (which controls a lot of window management suff IIRC) so that we can do it ourselves and not rely on accessibility API hacks or disabling SIP.

On: macOS Finder is still bad at network file copies

[TheFuzzball]

In a word? GPLv3.

On: JSR: The JavaScript Registry

[TheFuzzball]

I think you'd have to write a facade package with a consistent API that mapped to the node/deno/bun equivalents, since they're each quite different.

Best bet is to use the Node fs package and rely on the deno/bun compatibility layer.

More generally, Deno pushes for Web Platform APIs, and as more are proposed and implemented the runtime-specific APIs will become fewer and fewer.

[apitman → TheFuzzball]

Yeah this is basically what I'm trying to do (see response to sibling). Unfortunately I consider Node's APIs the worst of the 3. No shade on them it's just an older design. I really like Deno's approach since my code also needs to work in the browser. Writing HTTP handlers that take Request[0] and return Response[1] is a beautiful bit of symmetry with frontend code and feels like cheating.

[0]: https://developer.mozilla.org/en-US/docs/Web/API/Request

[1]: https://developer.mozilla.org/en-US/docs/Web/API/Response

[ascorbic → TheFuzzball]

If you use Node 20+ then there's a lot more compatibility with web platform APIs, so it is possible to write code that works on Node, browser and WinterCG-compatible runtimes like Deno. Obviously you'll need to avoid using Node builtins.

On: Have front end frameworks destroyed the web?

[TheFuzzball]

A toxic article full of untruths and generalisations.

> You have to teach React developers the difference between the <Link> and <a> tag, and how <a> doesn't swap nor replace your page content, it loads an entirely new page.

This is more of a complaint about JavaScript than "frameworks". Any default browser behaviour can be prevented, so when you click an `<a>` and it does the same thing as a `<button>`, a lot of devs will think "I'm done here". They need to be educated on accessibility and why it matters.

Sometimes the economics of a project make spending the time to make your advertising microsite that'll be live for 3 months not really worth making WGAC 3.0 compliant, sorry, welcome to the real world.

> But, and it's a tough pill to swallow for many… WordPress. It gets you from 0 to 97% in an instant, and the last remaining 3% is offered by some plugin, or a minimum amount of code knowledge.

facepalm

On: It’s Official, Apple Kills Web Apps in the EU

[TheFuzzball]

Bear in mind that Apple and Adobe have a very long and close history - Apple did not kill Flash to spite Adobe, they did it because 1. Flash was plagued with security problems, and 2. Flash was plagued with performance problems and the iPhone was a very low performance device.