It will happen to you
8d 1h ago by programming.dev/u/sus in programmer_humor@programming.dev from programming.dev
Aaand... it's Turing-complete!
You now have a moral obligation to port Doom to it
Ok I'm inferring here, but why does DSL mean more than one thing in the technology/computer field? The only one I know is Digital Subscriber Line
The one I'm familiar with is "Domain Specific Language"
I was thinking Damn Small Linux. Felt weird reading "small damn small Linux"
"small, damn small. Linux."
Sounds like an ad lol
In this case, it probably is "Domain Specific Language". If you're unfamiliar, that means it's created for a very specific context, unlike other, more general languages. That means you can keep the set of features small and save a lot of time making complex stuff work that isn't relevant to that context.
Loops are complex stuff. If you don't really need them, you're better off just keeping your language linear.
On the other hand, they're neat. Can't be that bad, can it?
Can't be that bad, can it?
Lol. Brings back so many memories of my own regrettable assumptions.
Dick sucking lips
Because every three letter acronym means more than one thing. There are only 17 576 TLA so they are going to be heavily duplicated.
You should almost always spell out acronyms on the first use.
I'm puzzled too. In DSL the "local loop" is the wiring between your house and the nearest central office or concentrator. Kind of like "last mile" but more like "last block or two". So I don't get what "adding loops" would mean.
Besides Domain Specific Language which somebody else refers to in the thread, DSL can also mean Damn Small Linux. Still no clue about adding loops.
I have created a handful of DSLs over the years and I think most of them were bad ideas. Ironically the most complex one is the one that I think was actually right. It had support for a lot of stuff like loops, functions, custom variables and even some weird shit like async execution of child commands.
I think what made it work in that case was mostly that the purpose of the DSL was completely different from the others. The system wasn't designed with a DSL in mind. The DSL was just a simpler way to provide input for something that was already there.
Exactly! Making a DSL and using it like a programming language introduces necessities that will not be considered as throughly if they where added to a "real" language.
I once wanted a DSL for a calendar program I was making (so the user could define complex events and stuff). So I made a simple programming language that could be embedded in the program, kinda like how lua is commonly used.
Your DSL isn't embedded on a Turing complete language. That was your mistake.
YAML has entered the chat.
Well, for all Turing complete languages around, you picked that one?
Using Blank Space or Malboge would be the wrong answer too.
It seemed to best fit the theme of the thread.
So... How about Conway's life for DSL?
That...
Wasn't on my enumeration of bad options :)
I wonder can you build a CI/CD framework what runs on life?
If your DSL has loops tyen it should be a Python library
Looking at you, Gradle
Gradle uses Groovy or Kotlin for its DSL, though...
So python compiled to JVM-bytecode.
https://www.jython.org/:let me introduce myself
One word: Terraform
You either put it in the DSL or people start writing generators for your DSL.