I'm in the process of finding where to put $100,000 of 4090s for training non-llm models.

It looks like "my garage" is cheaper by far even when I include installing an HVAC system and 3 phase power when I look at yearly costs for a spot with 20kW's of power.

Very Nice.

A rare mention of Intentional Programming aka IP (https://en.wikipedia.org/wiki/Intentional_programming) on HN. I first came to know of this from an article by Charles Simonyi titled "The Death of Computer Languages, The Birth of Intentional Programming" on MSDN. But alas, the promise never came to pass. The only other place i know of which covers it is a chapter in the book Generative Programming Methods, Tools, and Applications by Krysztof Czarnecki et al. IP is rather hard to understand (i still don't get it completely) and afaik there are no publicly available tools/IDEs to learn/play with it.

I don't believe Jetbrains MPS is a IP programming editor, it is meant for designing DSLs. IP has aspects of a DSL but is not the same.

Finally a huge upvote for mentioning Markus Voelter who is THE Expert in DSL design/implementation/usage. Checkout his articles/essays and the free ebook "Domain Engineering: Designing, Implementing and Using Domain-Specific Languages" from his above mentioned site.

Thank you! I've never fancied myself a good writer; I feel like, on a personal level, I can identify the beauty in things. However, I tend to have a hard time putting it to paper in a way that I feel conveys how I feel. But I'm working on it!

I'm a practical man, for me it's just n_loc difference and more useful imlicitness (and the listed downsides). Not sure if I can understand this "creation" part, even as a former Perl-ist. I think you can turn any language into Perl, it just happens that their core beliefs are incompatible with its ways.

For example, I can easily imagine something like this:

  import 'use-perl'

  while (await ls_lr('./*.txt')) {
    while (await read_lines($filename)) {
      print($ln, $line)

But it's not idiomatic as it uses awful implicit iterators and hideous globals. This conflict is purely dogmatic and doesn't need special syntax, for the most part.

My reason to break up with Perl was the lack of garbage collection and then later the lack of types and then later 6.

I don’t think investing in it is wise when you can invest in something more relevant. Although there’s barely anything that covers the subj as much as Perl, which is a shame on us all. A programming language that requires an import or two to dig through a file is degenerate. Old languages understood well what a programmer needs.

This is good insight. Limits are often built into programming languages. Java is all about the limits. TS's selling point is literally the limits. As well as every opinionated language.

I wonder if AI will make limitless languages easier to work with and maintain.

The case for Perl is just that it has no limits. You will never run out of tool if you go with Perl. That is what, I believe, makes the investment worthwhile.

Why Perl gets such a bad rap, then? I'll tell you.

I've used Perl for almost 30 years now, and I've never found any limits in the tool. This means every limit I found was _mine_. Many programmers feel bad when they find their own limits, but it doesn't have to be the case.

You should be OK with finding your own limits, and be willing to overcome them, and strive to become a Perl power user, just like the founder, Larry Wall.

If you choose this, to grow and improve and be better, and better, and better, then Perl is the best option.

It's up to you.