Lyngbakr

I came to say the same about JotL. They got so much right in that game with the way they introduce the rules and the spiral-bound book game board being the most prominent.

They don't cover it in the book, unfortunately. A serious omission, in my eyes.

I'm still looking around, but Owl is a frontrunner.

I had exactly the same experience (minus reading the book). Often, I'd just see the function signature and no further explanation. I do realise that it takes a lot of time and effort to build up extensive docs, but it happened enough that I put it down and started looking for another Lisp that compiles down to a binary.

Exactly. The way that Doctorow puts it in his book The Internet Con, it's actually perfectly legal to use a trademarked name, so long as it is not confusing to users/consumers. An example he gives is you couldn't open a rip off McDonalds where folks mistakenly think they're actually going to eat authentic Big Macs, but you could open a restaurant call Better Than McDonalds. This agrees with the first quote of the article:

    The most basic rule is that the Rust trademarks cannot be used in ways that appear (to a casual observer) official, affiliated, or endorsed by the Rust Project or Rust Foundation, unless you have written permission from the Rust Foundation.

Thanks for that!

    > Some popular DSLs most software developers use on a regular basis include Regular Expressions for pattern matching, AWK for text transformation or Standard Query Language for interacting with databases.

Isn't it Structured Query Language? Or are both variants used?

    > Helix, the editor? How would you pitch it?

Not the OP, but Helix is a minimal fuss modal editor with sensible defaults. My config is maybe five lines? I say "maybe" because I haven't looked at it I first wrote it. And I think I'd probably be just fine with no config.

Agreed: you don't want to create a solution to a hypothesized problem that doesn't actually exist. My point is that there are low hanging fruit if you step outside your immediate bubble, but — as you say — you'll need a guide.

    > Just fill needs that you have. Don't like how something existing works? Fix it. Think you can offer a better version of an existing idea? Go for it.

While I don't disagree with this point, what it often leads to is developers creating developer tools, which is a crowded and competitive area.

There are fields out there that are crying out for tech solutions because they are lumbering dinosaurs that haven't changed with the times. One example is the maritime industry. It's amazing how much is still done with pen and paper on a ship. True, there is often a reluctance to adopt new tech, but the younger cohort of mariners are far more eager and receptive to tech solutions than the previous generation.

My suggestion is to look for those industries and talk to folks in those fields about their pain points. The bar may be so low that you could step over it.

    OP hasn't even really used Lisp in anger, yet

This struck me, too. My current hobby project is in Go and I'm really quite enjoying it. It doesn't feel "soulless" to me at all. That said, I'm well aware that my opinion may be different if I had to write Go for a living instead of just for fun.

Did you ever try alternatives to Jupyter like Pluto.jl? I'm curious if there's the same sort of friction.

While I totally agree with the post, I think the tone of the delivery is likely to undermine the points made. From my perspective, for these guidelines to be adhered to there needs to be a broader buy in. 37signals are perhaps a prominent example of how this works. And if it's presented in a more pleasant way, rather than in the tone of a parent chastising a child, I think these principles can take root and become part of team/company culture.

    > Helix would be even worse considering it's a desktop app.

Helix is a terminal app.

Is the reason for the absence of a well-maintained dataframe library lack of demand? It looks like Gota and Dataframe-go are abandoned, while Gonum isn't particularly active. Did these wither on the vine because no one used them?

Do you have experience implementing ETL pipelines in Go? I think it'd be a better fit for us over our current language, but I'm curious to hear from people who've actually done it.

I remember Stephen King writing in his book On Writing that he once deviated from this approach (Maximum Overdrive, perhaps?) and it really didn't go well. At the time, I thought creating characters, a scenario, and setting and then seeing what happened was nuts, but it's essentially how D&D works (albeit in a group setting) and that's always fun.

    Besides, can we even attract experienced developers to a non-glamorous industry like logistics?

Perhaps it's perceived as non-glamous, but earlier in the week I met with a logistics team in another company who we're working with and the problems they address are absolutely fascinating. The complexity of the domain certainly made it intellectually appealing to me.

    > If you want to use one of Odin or Zig but don’t know which one, then I recommend spending 1-2 weeks using each and then make up your own mind.

That's fair enough, but has anyone who has done this got any thoughts? Zig seems to have a lot of admirers on HN. Is Odin on par with Zig?

Regardless of the official title, it long ago spread far beyond statistics.

R has been part of my stack professionally for around 16 years and in that time I'd estimate maybe 15% of my code had anything to do with statistics. I've used it for numerical modelling, data viz, ETL pipelines, deploying APIs, building dashboards, amongst many other topics. To reduce R to statistics is doing it a disservice.

From my childhood, there was Batfink.

https://en.wikipedia.org/wiki/Batfink

Ah, I see. Would this come at a performance cost? (My only experience with GUI editors is VSCode, which feels sluggish compared to Helix.)

I'm a happy Helix user and I'm curious what the benefit is of this over terminal-based Helix?

I had a somewhat similar experience moving from science to data science/engineering. A PhD meant I fit your description of "overqualified, but in the wrong area". Those days were hard and hugely demoralising. Until my résumé landed on the desk of someone who'd made the same career change, I was SOL.

I'd never heard of Kate and wondered if someone could explain what Kate's differentiator is versus other popular editors (e.g., Vim, Emacs, VSCode)? Is there something in particular that sets it apart or is it just a matter of taste?

While I love Clojure, I have to agree about tooling. I recently started using Gleam* and was impressed at how easy it was to get up and running with the CLI tool. I think this is an important part of getting people to adopt a language and Clojure dropped the ball a bit on this.

* https://gleam.run/

Something I really like in the Clojure data science stack that isn't mentioned is Clerk* — an interesting take on notebooks. I think it's a good gateway into Clojure for those coming from a Python or R background.

*https://clerk.vision/

You could still contribute in tiny but helpful ways. For example, fix a typo in the README, add an example to the docs on a topic you initially found confusing, etc. While these contributions seem trivial alone, together they add up to a more polished product.

If you're interested in even more on the subject, Don Canfield wrote an enjoyable deep dive on oxygen's history.†

† https://press.princeton.edu/books/hardcover/9780691145020/ox...