Live data from Hacker News

Blorp Language

blorp-lang.org

41–50 of 67 posts

Re: Blorp Language

#41
post #15

Why 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).

Roc defaults functions to being pure, and functions that can run side effects are inferred to have a different type by the compiler based on usage. By convention, their names should also end in `!` (e.g. `transform` for the name of a pure function and `transform!` if it does side effects), and the compiler warns you if you don't follow that convention.

https://github.com/roc-lang/roc/blob/b2503210da6b58a4ce1254d...

Re: Blorp Language

#42
"${name}: ${features.join(", ")}"

This is in the very first example you see on the site. If it's a mistake, that's not encouraging. If this is actually how the language works, that's even less encouraging -- the syntax highlighter doesn't even get it right!

Re: Blorp Language

#43
post #42

"${name}: ${features.join(", ")}" This is in the very first example you see on the site. If it's a mistake, that's not encouraging. If this is actually how the language works, that's even less encouraging -- the syntax highlighter doesn't even get it right!

The whole thing is 400k lines vibecoded over 3 weeks, I don't think there's been a lot of effort put into it yet.

Re: Blorp Language

#44
post #15

Why 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

#45
post #29
post #20

Readable 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?

That's more of a compiler limitation that became cultural for a while. Most languages (both natural and artificial) use delimited structures sparingly and rely more on other cues. It sometimes appears spontaneously (e.g. "∫ dx f(x)" is logically fine, but feels wrong) but in general it's rare. The move away from indentation in programing came as a rebellion against the too-constraining fixed column languages, in the…

In my experience there are many problems with significant whitespaces, things like copying pieces of code require much more work, when indentation actually changes the logic you can not ask your tool to do it automatically - because there is no single right way to do it. Tabs vs spaces can also be a problem.

Re: Blorp Language

#46
post #21

I applaud the effort, but every time there's a new hobbyist programming language on HN, almost always it's something I've already seen in countless other hobbyist languages, just a slight variation of it based on the author's personal tastes. It doesn't tell me why I should adopt it over language X. What I'd like to see is exploration of novel practical ideas that would make certain types of projects much faster to w…

I would recommend building a macro system and/or library for an existing language - that most closely aligns with your goals.

It seems like your goal is to make things more declarative / readable.

Creating a language is a pretty large undertaking, and unless you need to do it to achieve your goals, I wouldn't recommend it - unless you really just want to see what it's all about and make one.

Re: Blorp Language

#47
post #29
post #20

Readable 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?

That's more of a compiler limitation that became cultural for a while. Most languages (both natural and artificial) use delimited structures sparingly and rely more on other cues. It sometimes appears spontaneously (e.g. "∫ dx f(x)" is logically fine, but feels wrong) but in general it's rare. The move away from indentation in programing came as a rebellion against the too-constraining fixed column languages, in the…

No, significant whitespace today is still terrible, coming from Haskell, Python and Go (newlines that break expressions unreasonably)

Re: Blorp Language

#48
post #29
post #20

Readable 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?

That's more of a compiler limitation that became cultural for a while. Most languages (both natural and artificial) use delimited structures sparingly and rely more on other cues. It sometimes appears spontaneously (e.g. "∫ dx f(x)" is logically fine, but feels wrong) but in general it's rare. The move away from indentation in programing came as a rebellion against the too-constraining fixed column languages, in the…

Apparently the truth hurts.

I can't believe that the claim "python-style syntax is perfectly reasonable" deserves to be down-voted into the basement.

Post reply on HN