linguafranca

It's nice to see the Clojure/ClojureScript community growing. But the fact remains that these tools still don't enjoy the maturity of their more mainstream counterparts.

So if you use any ClojureScript libraries in production, expect to run into strange issues and submit bug reports that are not responded to for months on end. Nothing against their authors, it's just the nature of writing niche tools.

This is one of the reasons I very strongly support the Neovim project. They are taking an incredibly sensible and pragmatic approach to modernizing Vim.

Yes, there will be controversies. There always are. But even collaborative open source projects need strong-willed leadership, or they cannot grow properly.

> I, personally, used ex-mode only a couple of times, so even if I will use neovim I don't think I would care. But that just doesn't sound like a right think to do.

So he shouldn't remove it because of some strongly held principle of a random person on the internet? Even though that person in practice doesn't have any problem with it? That sounds backwards.

"Elixir compiles directly into BEAM byte code."

from http://elixir-lang.org/crash-course.html

Elixir reminds me a lot of Clojure.

- It's a language that sits on top of another language's bytecode (Erlang vs JVM)

- It has its own task runner and dependency manager (mix vs lein)

- It has homoiconicity and macros!

- One of its main features is amazing concurrency support.

But Elixir has been in development for a much shorter time than Clojure. Yet it's approaching the same level of maturity of Clojure very quickly.

I'm eager to see where is Elixir is adopted. I hope to see it gain some traction in the web development world.

Only slightly related, but I often solve hard(ish) programming problems while I'm in that state between asleep and awake throughout the night. Take that, cliche!

Sorry, am I missing something here? What's the context? Is Apple accused of some recent scam? Is this because of them forcing U2 into our accounts?

> Because Lua is a strictly less useful language than elisp.

The word "useful" is too subjective to be useful here.

> - It doesn't have macros.

There's MetaLua for those who truly think they need macros. But in reality they're just a convenience.

> - It doesn't have integers.

Lua 5.3 is getting them.

> - It doesn't have arrays.

It has tables that function perfectly well as arrays.

> - It doesn't have lists.

Singly-linked-lists can easily be created using tables.

> - It doesn't have dynamic binding.

Thankfully!

> Also, its 1-based array-like hash tables are just ecchy.

This is purely an imaginary problem. Personally, I prefer 1-baed indices.

> I like Lua; it's cool for what it is (and in fact I'm currently writing some hobby code in it), but it's not Lisp (and in fact my current hobby code is Lisp in Lua…).

So, your favorite language is Lisp? Great. Except, favoritism and bias aren't really compatible with truly constructive criticism.

Good point. But it's not unheard of to write a transpiler from Language X to Lua. See the VimL compiler in NeoVim[1].

[1]: https://github.com/neovim/neovim/wiki/FAQ#lua-and-vimscript-...

The history behind AppleScript involved being able to write it in any language, not just English. But that was a terrible idea and Apple knows that.

English (more specifically, JavaScript) is the Lingua Franca for the majority of programming, and we've all come to accept that, for better or worse, in good times and in bad, in sickness and in health.

I think you're misreading the document, I don't think you actually have to instantiate an NSTask in order to compare whether another application is running. You would just do something like this:

  Mail = Application('Mail')
  if (Mail.isRunning) { ... }

The goal here seems very vague and not well defined. And the fact that all its members are high-profile companies worries me that their involvement will merely been a facade for publicity more than anything truly constructive.

Why isn't Lua even a choice? It's small, portable, easily embeddable, lightning fast, supports high-level functional programming idioms, and is extremely flexible in creating and enforcing policies (via metaprogramming).