I was scrolling through Reddit and found something on porting Chrome extensions to Safari.
(I have not tried this as it involves downloading Xcode. I am not sure if it’s worth having a 10GB app on my MBP just to eliminate the need for a Chromium browser. At the moment, I’ll keep Helium around for when I need a Chrome extension; or, for when I cannot vibe code the equivalent. BTW, I did that new Safari extension vibe coding thingy and it worked perfectly. Mine copies a URL and strips the tracking gunk that comes after the suffix.)
But, for those who may be nerdy and geeky enough to want to do it: Guidelines on using Chrome Extension on Safari on Mac
There’s no such thing as “vibe coding”. Otherwise taking a cab would pass as “vibe driving”.
I’m just using a commonly accepted term for whatever it should be called. (“Natural language guess-coding?”)
2 Likes
I didn’t say the term doesn’t exist. Your linked article even explains why there’s no such thing described by it:
The term was coined by Andrej Karpathy, the former director of AI at Tesla and a founding engineer at OpenAI, to describe how artificial intelligence can enable someone to create a new app while being able to “forget that the code even exists”.
Collins Dictionary:
If you don’t write code, let alone forget that it even exists, you’re by definition not coding. You’re commissioning a work to someone or something else to code for you.
Imagine you want to build house, without knowing how to build a house. You talk to someone who does. After discussing your ideas and some back and forth and a little bit of cash, someone builds a house for you. You didn’t “vibe build” it.
1 Like
Just a reminder, my original post and the article I linked to had nothing much to do with ‘vibe coding’ as it is popularly understood; I just mentioned the Safari natural language extension-creation thing as an aside as to why I likely won’t bother with downloading Xcode so as to convert Chrome extensions to work in Safari. To me, trying the Safari custom-extension creation function or using Chrome, or a Chrome-clone, is easier than going the whole Xcode route.
I just thought that some in here might like the idea that Chrome extensions might be made to work in Safari.
1 Like