The State of Hy
fox.devport.no
fox.devport.no
A real fun language, one which matured a lot within the year. Keep up the good work!
Genuine curiosity as to why. I've heard arguments against using it because of speed and type-issues, but you're using a derived language that doesn't change either of those things. I've never heard anyone just blatantly dislike the language itself.
Hy gets rid of both the significant whitespace, and the syntax too. Yet, allows me to have bidirectional interop, so people using my modules are none the wiser, as long as I make a little effort to remain python compatible (macros used only internally, and not exposed in the API, and using valid python names for functions and other stuff).
EDIT: Thanks for the perspective.
As for "getting rid of the syntax", I think that's a bit disingenuous. Much like Clojure, Hy cheats by collapsing nesting:
(for (i (range 1 10)
j (range 1 10))
...)
{1 2 3 4} ==> {1: 2, 3: 4}
I mean, this isn't just getting rid of syntax. It's getting rid of structure. As a purist, my stance is that you either keep the structure (`{(1 2) (3 4)}` or you add syntax (`{1 2, 3 4}`, and unlike Clojure, make the comma significant). What you don't do is tuck syntactic information in the parity of the rank of an argument.I've made a g+ community about it, who's interested - welcome: https://plus.google.com/communities/112523471857971507059
Keep it up guys! =)
Does anyone know how they do sandboxing in there? Judging from the source (https://github.com/hylang/tryhy/blob/master/main.hy) repl.eval is called on each expression. I'm guessing it just uses App Engine's default python sandboxing.
This is off-topic, but, what? The concept of an annual State of X report is nothing new, and I don't see how it ties to "hipster attitude" in any way.
That word means less and less every day. Sure, who cares, but it's just lazy to throw it around any time you want to be edgy.
and paultag wrote snitch https://github.com/paultag/snitch
There are people using Hy in production, but that code isn't out. A good way to see Hy in action is looking at our tests/native_tests section. http://github.com/hylang/hy