I've been vegan for a couple of decades now and during that period I've had that time to observe meat eating people get all upset about veganism at various dinner parties during even though I don't advertise it or even talk about it.

What I've concluded is there's just NO WAY the world is going to do the right thing until the entire Amazon rainforest (and forests in general) have been converted to food production for food animals, dusty fattening lots for slaughter stretch to the horizon and all fresh water sources are drained.

So sensitive is the subject of what one consumes!

Maybe once climate disasters become more common and the price of meat becomes far too expensive for value menus will we start to change course. But I doubt it, we'll probably build meat factories in space before that.

In the meantime, those precious ag jobs are probably more threatened by automation than impossible burgers.

Yeah I adopted it after exploring other languages after learning to program in Turbo Pascal 5. Bit later I started using it for mail and news (Gnus) and other things.

It’s a life time tool that grows with you.

Forths such as FlashForth https://www.flashforth.com/index.html on the Arduino support multiple tasks .. in addition to including a compiler and interactive REPL

What's the reasons for that?

Easier tax fraud mostly to keep your illicitly gained money away from the taxman.

Plus conservative population that is skeptical about new tech and strongly keeps outdated ways of working and doing business (visible in any company there). Letters are common as well and digitalization is pretty weak.

Like what's the last tech product you remember that came out of Austria?

> Clojure libraries target microservices with a precision that ..

I’m not sure what that means exactly, but no one is using Rails only for building out micro services. They’re using Rails to go from nothing to a production ready web application, with all the incidental complexity taken care of, in a very short time.

It’s been a few years since I was involved with Clojure ecosystem - what is the Clojure experience equivalent to say, the original Rails demo from back in 2005? The last I tried, all the parts seemed to be there, but much painful assembly/“composing” was required and not all the parts fitted which ended up producing a lot of awkward complexity needing desperate decomplecting.

This might be what happens when the community seems to follow “composable libraries over frameworks”. You still have to do the composing, and it’s not obvious how to do that.

This is the one thing I found that prevented me from getting far with Clojure. I love the language and the concepts...but there's no stable well-documented go to tool that I can use to hit the ground running. Instead, I spent so much time looking at blog posts and random videos trying to cobble together some sort of system of various libraries to form the basic functionality of a web framework just to get to a point where I could actually start working on the meat of the application. Luminus is extremely helpful but I'd also end up having to learn about the individual pieces and found it hard to add libraries after I started my project.

The pervasive "compostable library" mindset also completely ignores the other benefits of having a standardized framework such as Rails that people can rally around: 1. Standardized documentation 2. Being able to create community that can provide support when you're having issues 3. Easily google-able solutions to common issues 4. A standard that can be iterated upon. I feel like Clojure libraries do this somewhat already so they can work with each other so what's the harm on standardizing these interfaces?

I reckon nobody opposes your fine idea, simply that when a template is transformed enough to be a useful web app starting point, it's often too opinionated to be generally applicable! But maybe the next time I start a few web apps I will think about how I can keep it a clean template as long as possible -- might go somewhere cool.

Perhaps that stance has changed over time. In Clojure, there's the clojure.string namespace just functions wrapping java.lang.String methods https://clojuredocs.org/clojure.string

This is much more than "just wrapping". It allows strings to be used more readily with existing Clojure abstractions and/or allows idiomatic use without the need for being on guard to avoid reflection.

Notably, Alex didn't write this library and only has a minor contribution to it.

There's two cases where you'll see pragmatic wrapping:

1. Higher order usage. When functions would really benefit from being used in a higher order way, passed around as values, you'll see some of the Java methods wrapped so they can more easily be used as such, since you can't use Java methods in a higher order way. This would count as "can do it better", and it's the case for clojure.string.

2. For portability with Clojurescript. This is a more recent thing, but as Clojurescript usage grows, and code reuse between backed and frontend more common, there are certain basic methods Java interop was totally fine with that now benefits from being wrapped. This is the case for clojure.math.

I think the problem is that if you want to write code portable between clj and cljs, you’re gonna need a lightweight abstraction. With that said, I’m still not sure how exactly the maintainers feel about portable code, having written a portable http library.

Common Lisp has it too, via https://stmx.org/ I believe it supports the Intel TSX stuff if present and falls back to a software implementation if not present.

Should have put it into fundamental STEM education

It won't work. Most of them would go to software industry after graduated.

I use an 8 foot, iron digging bar ahead of the post hole digger.