Now that I'm out of the corporate tyranny and have my own company, I use lisp for everything. There's certain satisfaction in writing config files and persisting data directly in s-expressions. Any json requirements are triggered by exports to foreign systems.

▲ atcol 4 hours ago | parent | next [-]

Which Lisp, out of interest?

▲

iLemming 37 minutes ago | parent [-]

Does it really matter? There's a point in every Lisper's life, a threshold after which the question becomes immaterial - you'd stop thinking about intricacies of whatever Lisp and focus on the platform specifics instead. Any given day I might program in three-four different Lisp dialects, e.g. Clojure/Clourescript, Fennel, Elisp, Janet, etc. and it practically feels like I'm using the same PL. While switching between TS and JS (same family) never feels even close - there's always some mental burden.

	▲	arikrahman 33 minutes ago \| parent [-]
		Even the Lisps have Lisps. Like Clojure with ClojureScript, CLR, ClojureDart, Jank... etc.

▲ Blikkentrekker 3 hours ago | parent | prev [-]

That JSON prohibits trailing commata makes it an absolute pain to work with in practice.

I also like how in Haskell:

   something =
     { element
     , element1
     , element2
     , element3
     }

Is an actually idiomatic way to deal with the lack of trailing commata.

	▲	shawn_w a minute ago \| parent \| next [-]
		You see that style in SQL too.
	▲	kazinator 2 hours ago \| parent \| prev \| next [-]
		I did something like that in C++ circa 1998, before seeing it anywhere else: `MyClass::MyClass(foo bar, int arg1, int arg2) : Base(bar) , member1(arg1) , member2(arg2) { }`
	▲	Ferret7446 12 minutes ago \| parent \| prev [-]
		Not really? A linter/formatter takes care of it.