I don't disagree with you per se, but I think we can look at it another way: See assignments as statements of fact. The sky is blue. Himmelen er blå.
aka himmelen er blå. A statement of fact.
Also, "blir" becomes yet another keyword. More keywords, more to remember. Not that this has been a real consideration or worry in Brunost so far. The design so far is very much "What I felt was okay that day".
This makes sense in functional languages where variables can't change, but not in imperative languages like Brunost. When a fact changes halfway the story, it wasn't much of a fact. Himmelen er blå, inntil den blir rosa.
If there is a market for that, then I would build a new language from the ground up that is... better designed.
Brunost is just me throwing syntax at the wall to make a "nynorsk programming language". Less about careful design and more about getting something to work.
If I were to make a language intended for an important production system, it would be a compiled language that (probably) would go the Gleam route and compile to JS and some other language, while also being typesafe, having a package manager and so forth.
I don't know how far I want to take this language, but if there is a market for an actual nordic/norwegian language then it shouldn't be Brunost.
I would want something that compiles down to something, not interpreted, typesafe, with a proper package manager, etc.
My initial goal was always to take it far enough to do file I/O and sockets, so I could make a Brunost website in Brunost.
If there is interest in the language from the POV of education and so forth I'd be happy to tailor it away from goofs and gafs and into something a little more usable, but I don't want the language to become a full-on production language.
Well, I got a 2 in nynorsk, so I expected to have some mistakes going into this. Not sure I can handle also being graded by it.
I have replaced endreleg with "open", and the immutable variable with "open" in later versions (done after the article).
So now the "endreleg" is less of an annoyance, both because it no longer exists and because it has the same number of characters as the immutable keyword.
> I have renamed the "endreleg" since the article release to "låst" and "open".
I like that - much shorter and also the two keywords are the same length, which is always nice when you're making a list. I have to say I would prefer 'åpen', though, just to make extra trouble for people who don't have a keyboard with Correct letters on it. :D
A further thought on `alltid` - you could add the keyword `aldri`, which makes it a runtime error for the variable to take that value. Maybe add ranges as well, for easy bounds checking, e.g.
```
en peker er aldri = null
en indeks er aldri > 5
```
I have actually changed this since the post's release.
I got annoyed that "fast" and "endreleg" have different numbers of characters (regardless of whether endreleg is nynorsk. I got a 2 in Nynorsk in school, so........)
> Isn't it obvious that "nazi bullshit" isn't welcome? Like a no-brainer?
Unfortunately, not in this day and age.
> Why does a programming language feel the need to say this?
It's less about "the language saying it" and more about the standards of the community that surrounds the language.
For a language to thrive, it needs a community of people contributing to it. If it doesn't, it'll eventually die unused. As such, there's more than "just the language"; it is also a community-building effort.
> Also, the phrase "nazi bullshit" is severely...
IMHO, you're reading too much into the word "bullshit".
Maybe I should throw that into the language somewhere.
reply