The brunost programming language could be very useful for norwegian government agencies. It is common to use norwegian names for variables and functions at the Norwegian Labour and Welfare Administration (NAV in Norwegian). A subset of typescript where the reserved words are written in nynorsk, would help prevent misunderstanding.
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 understand how having 65–100 keywords localized makes any difference. People can use these kinds of mixed registers for specific niches and it seems seamless to everyone.
Not directly related but still interesting. The fellow who came up with the ide for the Architectural Uprisings we have seen around the world, is still anonymous.
My favorite pasttime for the last 12 years, besides reading hacker news, is to make music on my phone, ipad or on my piano. Will I stop making music now that Suno is here? No frigging way. Because I still like to make music. I won’t stop talking either, just because some AI is better at doing conversation about research. If I make enough money on my latest, I will spend more time making music.
tl;dr: the final product is just a receipt of the effort, the sleepless nights, the self-doubt and personal transformation that goes into creating art. They have found a way to automate creating this receipt, without the personal transformation that an artist goes through, a process which leads her to learn more about herself and her place in the world.
An artist will find a way to leverage generative slop into this genuine process, but the by-the-bucket gruel generated in seconds from a prompt will always be a simulacrum of the real thing, despite how good it might sound.
I am pivoting from sterile software engineering where only product and revenue are the guiding metrics, to others where artistry and this personal drive for self-expression will always be valued, despite the attempts at diluting the field for a quick buck by talentless hacks.
The world will always care about Art. It is the most human of instincts.
Is there some documentation for this? The code is probably the simplest (Not So) Large Language Model implementation possible, but it is not straight forward to understand for developers not familiar with multi-head attention, ReLU FFN, LayerNorm and learned positional embeddings.
This projects shares similarities with Minix. Minix is still used at universities as an educational tool for teaching operating system design. Minix is the operating system that taught Linus Torvalds how to design (monolithic) operating systems. Similarly having students adding capabilities to GuppyLM is a good way to learn LLM design.
Absolutely. If you loaded this into an agentic coding harness with a decent model, I can practically guarantee it would be able to help you figure out what's going on.
> there is no more need for writing high level docs?
Absolutely not. That would be like exploring a cave without a flashlight, knowing that you could just feel your way around in the dark instead.
Code is not always self-documenting, and can often tell you how it was written, but not why.
> If you loaded this into an agentic coding harness with a decent model, I can practically guarantee it would be able to help you figure out what's going on.
My non-coder but technically savvy boss has been doing this lately to great success. It's nice because I spend less time on it since the model has taken my place for the most part.
There are so many blogs and tutorials about this stuff in particular, I wouldn't worry about it being outside the training data distribution for modern LLMs. If you have a scarce topic in some obscure language I'd be more careful when learning from LLMs.
They do. Think of it like a very intelligent but somewhat unreliable engineer you can hire to look at your code. They have no context about the codebase beyond what’s written in the source code, or any docs you give them.
What I meant was the docs might provide explanations about the problems the codebase solves, design decisions, the abstractions chosen, etc that wouldn’t live in a particular source file. Any discussion someone has with an LLM about the codebase will lack this context in the explanations given if docs don’t exist.
Yes, architects still very much needs to draw by hand. Imagining working as an architect on a single family house. Being able to listen to the client and make drawings by hand in meetings is the best way to communicate architectural ideas. Drawing on paper before continuing on a computer, also makes it easier for an architect to design something other than square boxes.
Just likte this demonstrates the stupidity of infinite scrolling, here is a site that demonstrates how easy it is to manipulate everybody to click click on things that gives us rewards:
Semantic web is for computers to read data from your website. WebMCP is for interacting with your website.
Using URIs as identifiers and RDF as interchange format, makes it possible for LLM's and computers to understand well what something really means. It makes it well suited for making sure LLM's and computers understand scientific data and are able to aggregate it.
reply