Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Dyalog appears to be more popular with conferences and more products, but it costs $1k ish for a commercial license and nobody else can run your code without a license and server licenses aren't cheap. It also pretty much needs a special keyboard and a key mapping. J is free for pretty much everything and uses standard characters (although I really like the APL characters). I think they're both nice.


sort by: page size:

I think the open source version of J is more mature and has a larger community. It also has a lot of support packages that are not available for open source APL. If you are trying to write real-life projects, J seems to be a better option at this time.

That's fair, I haven't tried D yet but I've heard good things about it. One thing Go's really good at is web services, and from what I've seen D seems to be a bit lacking here. But in general D seems more versatile than Go.

The beginner friendly is important. I use code-d because it provides a better out of the box experience, providing dub build and run tasks. In DLS I either only get the building task or have to set them up myself.

I like K better than Q too, but J[1] clicks with me more.

J has JDB[2] and Jd[3] for things somewhat similar to qdb with Jd being the commercial offering similar to qdb rather than JDB.

I would probably choose APL over Q if that were a choice. In J you can always make your definitions (verbs, nouns, etc...) plain words if you like the way Q reads.

  [1] jsoftware.com
  [2] http://code.jsoftware.com/wiki/JDB
  [3] http://www.jsoftware.com/jdhelp/overview.html

I'm fairly familiar with both V and D (even made some minor contributions to the V compiler), and I can't think of a single notable feature that isn't also available in D. V has a more modern and straightforward syntax, but that's the only major advantage imo. In terms of what you can _do_, I'm pretty sure D is almost strictly more powerful.

V can produce JavaScript, and it has an interpreter, but those are pretty experimental features. V has built in markup templates (like Mustache but worse), basic built in JSON reflection (D's CTFE can implement this), and built in portable inline SQL (for some reason), but that might be less desirable than targeting one specific ORM with its entire feature set. V also has a built in Sokol shader compiler, and can run `.vsh` files in a special script mode that works very slightly differently than normal V, but those aren't exactly killer features compared to D imo.


LiveCode is much better, cross-platform, supports mobile and is free for non-commercial development.

Cleaner, better documented, better interface, highly competitive performance, faster compiles, active development community, emscripten, better tooling/IDE integration. License is not viral.

It's better if you are writing new code for the web and want to use a different language, but Doppio is better if you need compatibility with existing JVM code. The goals are different.

1) Basically the same as `tig`. 2) Seemingly not open source.

Better than JRE based ones. They eat far more memory and are slow and often buggy.

I second ag too. Not because it's faster, but because it is developer-oriented so it has sane defaults for searching into code.

I'm trying to decide if this is better than Zulip. They're both open source, backed by someone trusted, and I can run it on my own server.

I'd recommend Goji to most users. The one I wrote has better performance, but also less features.

I've used all three at one point and they are pretty similar and will get more similar in the future. For public repositories all are free. In my opinion now in 2018 there's no clear winner, just personal preferences.

It’s not unique, check Python.

They are simply two very popular development environments so you will get more tools.


I think that no one of them. They both are too complicated for average developers.

Both are very, very easy to use.

Both have a very, very cheap option.

I'd say that all things being equal, you should spin up a server on each of them and see which one is easier to work with for you.

Personally, I use DO.


Tbh for me it’s the better plug-in UX and the built in debugger. Of course I use IJ for real stuff.

jq seems to have a lot more functionality than this, but its DSL is slightly different. This one might be easier to use if it matches with your mental model more easily.
next

Legal | privacy