They want someone to have written the plugin/extension they're looking for. It makes sense that developers would trade stock platform-widgets in exchange for an editor with greater cross platform reach because users of these tools benefit from network effects of these tools having wider reach.
You might be able to make the case that using stock widgets matters for non-developer tools (and I would only partially agree there), but for developer tools when people say they want "native" they are more likely to mean they want the performance that more often comes with natively compiled languages without a VM. The problems that people have with the dominant players that have gained traction is the performance. They are the ones that have become dominant.
Just look at the market share of developer tools and IDEs/editors that don't use stock platform widgets. I'll adopt whatever definition you want "native" to mean for the discussion - and under your definition of native, I would say it's pretty clear that users of text editors and developer tools don't care much at all about "native"(your definition of using the platform provided widgets). (Shortcuts on iOS is trying, but it's not on the Mac yet, and it gets pretty clunky if you start doing overly complicated automation bits with it.)
I don't think we have a "modern" replacement yet - certainly not in the Apple ecosystem, and I'm not sure anywhere else. I actually think it's a shame that AppleScript has been kicked to the curb. You arguably can't script the AppleScript-intensive BBEdit to the same level that you could, say, Emacs or Vim, but imagine the possibilities of a suite of apps from different makers that all had complete scripting dictionaries that could all be woven together with a deep system-wide scripting language. Applications can provide "dictionaries" of commands that, when implemented well, provide GUI applications with the kind of "snap together for amazing effect" you get with shell scripts and a host of well-written CLI tools. TextMate never had AppleScript integration, AFAIK.Īlso, I'm not convinced we should ignore those "archaic" technologies, at least in the abstract.
0 kommentar(er)
