HN user

uvtc

88 karma

John Gabriele

http://www.unexpected-vortices.com/

Posts0
Comments87
View on HN
No posts found.

It's nice that most of Janes the literals match Clojure

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 `@`)

The "pen display" is the type where it's a monitor with the transparent trackpad overlaid on it. That, I think, is what you want. I tried the other type, where you write on the tablet but you look at the screen elsewhere, and it was not fun.

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.

Janet is small, simple, efficient, and practical. For me it has nice syntax and sensible semantics. Great little package manager too. Very happy with and excited about Janet so far.

Would be nice if that tiny image on the top left of the homepage were clickable so I could see the screenshot full-size.

I'm not sure there's a catch, so much as there's just a number of comparable but corporate-backed alternatives that are seeing some popularity right now:

* TypeScript (Microsoft)

* Dart (Google)

* Kotlin (JetBrains, with Google too)

* Swift (Apple) (though not sure if it compiles to JS)

Goodbye, Flash 7 years ago

I believe with Haxe you can use OpenFL to get what you're looking for. FWIU, that provides a nice migration path from Flash.

Haxe feels much more promising than most alternatives. If I do web stuff again I'll be diving in here. There is some good library support. I am a little concerned by its relative youth, will it last?

Haxe has actually been around since 2005 or so. I'm really liking Haxe as a general-purpose compile-to-just-about-anything language.

Given that GitLab/GitHub/etc (and, often, online package repositories) automatically display markdown files as rendered html, a directory of markdown files is a fine way to document your project. The docs can, at any point, optionally be processed into html that goes into a separate website (lots of folks have written tools for this. My own is [Rippledoc](https://gitlab.com/uvtc/rippledoc)).

Also, if the project is a library or framework with a public interface, you need both API docs generated from source, and prose docs.

Nim 0.19 8 years ago

I think the one downside of Haxe (which is also is strength) is that it doesn’t only support compiling to C/C++, but to every major language possible (Java, C#, PHP, Javascript), so the language ends up being too complex.

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!

If you're already using JavaScript for the web, I think there's three main options for that domain:

* 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.

Nim 0.19 8 years ago

Nim appears to be quite similar to Haxe, though Haxe compiles to numerous additional targets. Aside from that, and the syntax, what are the main differences between Nim and Haxe?