hoon doesn't need fixing anyway, it needs a sane language with the same semantics and human-usable names for the standard library and the whole thing needs to be like 50x faster, that's the important part
-
-
This Tweet is unavailable.
-
The `:if` keyword syntax was terrible though, because `if` was just about the only keyword that made any sense. The rest were scrabble nonsense.
1 reply 0 retweets 1 like -
This is what I remember anyway. That syntax existed when I was learning hoon and it didn't improve the experience at all.
1 reply 0 retweets 3 likes -
yeah the :keyword experiment was harmful the runes aren't the main problem, the scrabble library is cgy was persuaded to add synonyms for the runes, they weren't very good, the take-home lesson was "hoon is fine"
2 replies 0 retweets 2 likes -
my Take is that scrabble needs to change for everyone hoon can stick around, with a sexpr dialect for such as prefer it the arm/leg/core/gate/wet/iron/zinc thing needs even more detailed documentation in terms of familiar concepts (this is much better than it was)
1 reply 0 retweets 1 like -
The problem with the type variance stuff (iron/zinc/lead gates) is less about documentation and more about implementation, imo. (1) too much type complexity is exposed to the ordinary programmer, (2) unfinished common language features like object (gate) type inheritance.
2 replies 0 retweets 2 likes -
Some things about hoon's type system are really nice, like the common sense forward type inference. You can do things effortlessly that are a huge pain in c++, switch on value type. Other things easy in c++ are tough. I don't know how easily fixable the latter problems are.
2 replies 0 retweets 2 likes -
actual macros can make up for a lot! not a silver bullet, but when starting from a good base (and the semantics of hoon are pretty nice), anything you can do with a "code pattern" can be stripped down to only what's different about a given use of that pattern
1 reply 0 retweets 0 likes -
I thought CGY's arguments against macros made sense in general (they result in domain specific / write-only code). But hoon kind of has the write-only code problem for other reasons....
1 reply 0 retweets 1 like
he is the last person in the world who should lecture others about write-only code
-
-
the write-only argument against macros has never really sat right with me good macros are the opposite and a culture of good coding practices isn't optional when lisping, macroexpand is always available, but I haven't needed it much
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.