4 ms·

Looks very nice. But how stable is the Xcode plugin API these days? BTW, what's the connection between the name "Alcatraz" and the idea of a package manager fo

by Camillo 14y ago

Looks very nice. But how stable is the Xcode plugin API these days? BTW, what's the connection between the name "Alcatraz" and the idea of a package manager for Xcode plugins? Try as I might, I can't see one. I don't know why all open source projects need an arbitrary name these days - I would have simply called it "Xcode Package Manager". I don't mean this as criticism: I am just baffled by this phenomenon, and just a little bit concerned that we're going to run out of memorable names if every single niche project needs one.

Samuel_Michon 14y ago
Alcatraz was a high-security prison associated with some high profile escape attempts, though no successful escapes have been confirmed. I suspect the creators of this package manager were trying to link the tech terms ‘walled garden’ and ‘jailbreak’ to real life penitentiaries. If so, I think ‘Shawshank’ would have been a better name, because it’s a fictitious prison and the story has a happy ending.
- mneorr 14y ago
  Shawshank sounds like an awesome name; Alcatraz was just the first one that came to my mind.
signalsignal 14y ago
Alcatraz was a prison known for tight security, so I am guessing that based on their motto "…your plugins are mine…" the project is just trying to tie all the external projects into one secured location. But I am just guessing. Others may have more cynical views, though. Here is the project list: https://github.com/mneorr/alcatraz-packages/blob/master/packages.json https://github.com/mneorr/alcatraz-packages/blob/master/pack...
terhechte 14y ago
There is no API, it's all reverse-engineered (AFAIK). I've been using the XVim plugin full time for the past year, and it's been very, very stable lately. It still crashes from time to time, but that can just as well also be XCode.
- tomlu 14y ago
  This man is correct - there is no plugin API and everything is reverse-engineered. XVim is built on an internal layer that doesn't know about Xcode, then all operations are funnelled through an interface that does know about Xcode specific things. This makes it a little easier to upgrade should they decide to refactor Xcode's internal implementation. Still, Xcode's internals haven't really changed that much since 4.2+. Source: XVim contributor, especially to its architecture
  - terhechte 14y ago
    Thanks for the reply. I really like XVim and I'm really looking forward to the current refactor branch.
    - tomlu 14y ago
      Unfortunately I'm not involved anymore, it was hard to keep up motivation since I started using the excellent AppCode. Although I do think XVim is a lot better than IDEAVim.
  - terhechte 14y ago
    I've used AppCode for a couple of months last year and tried again with 2.0 this year, but I really didn't like IdeaVim, and I didn't look like easy to extend.
  - maqr 14y ago
    I just tried XVim for the first time because of this post. This unbelievably well integrated into XCode, and the source code is very clean, especially for obj-c.
    - terhechte 14y ago
      Yeah, and the guy has been working for a long time on a huge refactor that will bring column selection, global marks, better window management, and a couple of other things. Not to mention that it may be easier to extend it. This is currently the second best vim implementation after evil-emacs, imho.

by Camillo 14y ago

Samuel_Michon 14y ago

Alcatraz was a high-security prison associated with some high profile escape attempts, though no successful escapes have been confirmed. I suspect the creators of this package manager were trying to link the tech terms ‘walled garden’ and ‘jailbreak’ to real life penitentiaries. If so, I think ‘Shawshank’ would have been a better name, because it’s a fictitious prison and the story has a happy ending.

mneorr 14y ago
Shawshank sounds like an awesome name; Alcatraz was just the first one that came to my mind.

signalsignal 14y ago

Alcatraz was a prison known for tight security, so I am guessing that based on their motto "…your plugins are mine…" the project is just trying to tie all the external projects into one secured location. But I am just guessing. Others may have more cynical views, though. Here is the project list: https://github.com/mneorr/alcatraz-packages/blob/master/packages.json https://github.com/mneorr/alcatraz-packages/blob/master/pack...

terhechte 14y ago

There is no API, it's all reverse-engineered (AFAIK). I've been using the XVim plugin full time for the past year, and it's been very, very stable lately. It still crashes from time to time, but that can just as well also be XCode.

tomlu 14y ago
This man is correct - there is no plugin API and everything is reverse-engineered. XVim is built on an internal layer that doesn't know about Xcode, then all operations are funnelled through an interface that does know about Xcode specific things. This makes it a little easier to upgrade should they decide to refactor Xcode's internal implementation. Still, Xcode's internals haven't really changed that much since 4.2+. Source: XVim contributor, especially to its architecture
- terhechte 14y ago
  Thanks for the reply. I really like XVim and I'm really looking forward to the current refactor branch.
  - tomlu 14y ago
    Unfortunately I'm not involved anymore, it was hard to keep up motivation since I started using the excellent AppCode. Although I do think XVim is a lot better than IDEAVim.
- terhechte 14y ago
  I've used AppCode for a couple of months last year and tried again with 2.0 this year, but I really didn't like IdeaVim, and I didn't look like easy to extend.
- maqr 14y ago
  I just tried XVim for the first time because of this post. This unbelievably well integrated into XCode, and the source code is very clean, especially for obj-c.
  - terhechte 14y ago
    Yeah, and the guy has been working for a long time on a huge refactor that will bring column selection, global marks, better window management, and a couple of other things. Not to mention that it may be easier to extend it. This is currently the second best vim implementation after evil-emacs, imho.