Interesting. there are some parts i like a lot here, but two things that I really dislike syntax wise. One is the lean towards a chainable syntax - this has proven to a big footgun for many devs in both java streams and typescript, making it very easy to go from O(n) to O(2n). The other part i really dislike is the first argument principle noted. If i myself define `string_and_reverse` and I can call it both through…
> making it very easy to go from O(n) to O(2n) Strictly speaking I assume everyone knows O(n) = O(2n) =O(kn) for k in R. But I see your point. I assume any decent compiler would merge the loops though
Blorp Language
61–67 of 67 posts
Re: Blorp Language
#62Interesting. there are some parts i like a lot here, but two things that I really dislike syntax wise. One is the lean towards a chainable syntax - this has proven to a big footgun for many devs in both java streams and typescript, making it very easy to go from O(n) to O(2n). The other part i really dislike is the first argument principle noted. If i myself define `string_and_reverse` and I can call it both through…
> i could definitely see this leading to some very funky looking chaining. At least for me, thing .doThis() .thenDoThat() .andFinallyThis() is much more readable than andFinallyThis( thenDoThat( doThis(thing) ) )
Re: Blorp Language
#63It looks nice. The general syntax isn't explained AFAICT? Looks somewhat Python-like but modernised (great!) - is it indentation sensitive?
There's a lot of other differences -- it's a smaller language surface than Python overall.
Re: Blorp Language
#64Why is `pure` a keyword that needs to be added, with impure being the default? This discourages programmers from marking functions as pure. I like how Nim does it, with `func` declaring a function (pure) and `proc` declaring a procedure (impure).
> Why is `pure` a keyword that needs to be added, with impure being the default? Marketing. Instead of reading the code littered with "impure" keywords, you look at the beautiful code marked as "pure".
Re: Blorp Language
#65Readable syntax with mandatory indentation is a very questionable idea. For me its easier to understand that something ends with a specific designation, not with a lack of it. Indentation should be solved by formatter and not the language. And I don't quite understand the memory model, is it something similar to Rust?
Re: Blorp Language
#66It looks nice. The general syntax isn't explained AFAICT? Looks somewhat Python-like but modernised (great!) - is it indentation sensitive?
Yes, it's python-inspired. Some notable differences are: - no return keyword - match/if are expressions - it's functional - =? is used for early returns or binding, depending on the variant of an Option or Result that is returned There's a lot of other differences -- it's a smaller language surface than Python overall.
I was trying to find if it is definitely a significant whitespace syntax, as it appears to be
Re: Blorp Language
#67It would be nice to see a "new" language that actually does something truly new and valuable. Almost all "new" languages presented on HN are basically slightly different flavours of languages that have been around for a very long time. But without the libraries/documentation/tools etc. needed to make it useful.
Look at my language: https://github.com/Panzerschrek/U-00DC-Sprache/ . It offers speed and safety without introducing too much friction.