How to convert existing web extensions for Safari

Re:How to convert existing web extensions for Safari by kitsunesoba on Tuesday January 05, 2021 @03:06PM (#25650315)

Most extensions could likely be built and tested just fine on a ~$250-$350 used Mac mini. That's probably still more money than should need to be spent, but a brand new machine probably isn't necessary in this particular case.

[ Parent | on HN ]

Re:How to convert existing web extensions for Safari by caffeinewriter on Tuesday January 05, 2021 @03:13PM (#25650404)

I was thinking on that. You still need peripherals if you're using a Mac Mini, though that's no different than if you were using another desktop. Still though, if you don't use, or don't want to use a Mac as your daily driver, that's a dedicated machine just to build/publish an extension for a browser. IMO, there's a slightly stronger case for iOS apps, but requiring that for a browser extension is much harder to justify.

[ Parent | on HN ]

Re:How to convert existing web extensions for Safari by junipertea on Tuesday January 05, 2021 @06:10PM (#25652534)

It's not like you can use safari on Windows.

[ Parent | on HN ]

Re:How to convert existing web extensions for Safari by caffeinewriter on Tuesday January 05, 2021 @07:25PM (#25653278)

However, if you're the creator of a Firefox/Chrome extension, and want to utilize the WebExtension support in Safari, your deployment workflow can no longer be platform agnostic.

[ Parent | on HN ]

Re:How to convert existing web extensions for Safari by paulryanrogers on Tuesday January 05, 2021 @07:44PM (#25653427)

I've done this to build for MacOS, and it still becomes like a tax as the hardware ages out and Apple insists you have the latest OS to publish to their stores.

[ Parent | on HN ]