88 karma · joined November 30, 2011
http://www.unexpected-vortices.com/
I think the primary reason is because Markdown is prettier to read (and also secondarily because it's good enough).
There are lots of markup formats, but markdown is probably the easiest on the eyes.
> Fast compilation and nice, easy to read syntax with good default is exactly what I am looking for.
> [re metaprogramming] ... but I also think this is a pandora box.
Sounds like you might also like [Hare](https://harelang.org/). (has some work-in-progress [SDL2 bindings](https://git.sr.ht/~sircmpwn/hare-sdl2))
Fennel was created prior to Janet, by the same person. :)
Two things:
* Janet doesn't have a built-in set data structure literal. Need to use a library for that.
* Janet has mutable and immutable versions of arrays and hashmaps (the literals for the mutable variety are prefixed with `@`)
I agree. [Janet](https://janet-lang.org/) (which, coincidentally, has some superficial similarities to Clojure) has something similar at its [JanetDocs site](https://janetdocs.com/).
The Wacom One is a fine choice (its their smallest and least expensive model). Maybe artists would need a larger one, but the Wacom One is, IMO, large enough to take notes on.
Haven't tried an iPad, but that Wacom is a really excellent writing/drawing experience.
And it can also compile down to various bytecodes (like JVM), not just to other languages.
* TypeScript (Microsoft)
* Dart (Google)
* Kotlin (JetBrains, with Google too)
* Swift (Apple) (though not sure if it compiles to JS)
Haxe has actually been around since 2005 or so. I'm really liking Haxe as a general-purpose compile-to-just-about-anything language.
Here's a [comparison of Haxe and TypeScript](https://blog.onthewings.net/2015/08/05/typescript-vs-haxe/).
Also, if the project is a library or framework with a public interface, you need both API docs generated from source, and prose docs.
I don't understand --- I would think it's quite the opposite. Implementing too many unique target-language -specific features in Haxe would mean lots more compilation acrobatics to make those features work across every target language, correct?
> the main developer is working on Hashlink, which can run Haxe code on a virtual machine but can also transpile it to C for production builds
Yes, very excited about HashLink!
* stick with JS,
* learn a language that's a superset of JS (like TypeScript), or
* learn another language which compiles to JS.
If you're looking for a language that can also replace Python for you, then maybe the 3rd option above is a good bet. Something which has its own VM (or other native target), but which also can be compiled to JS. For example, Haxe, Kotlin, Nim, Go, or Dart.