News for hackers. Stuff that matters.
Re:A History of Clojure [pdf] by fooster on Thursday June 04, 2020 @06:07PM (#23422552)
Yes, yes in the future at some undefined point java will be better.

Meanwhile go works very well today. And you don't need to be saddled with the JVM and the very bloated java ecosystem.

Re:A History of Clojure [pdf] by nojito on Thursday June 04, 2020 @06:42PM (#23422849)
>very bloated java ecosystem

Why waste time reinventing what java has already solved?

Re:A History of Clojure [pdf] by armitron on Thursday June 04, 2020 @06:53PM (#23422933)
Life is too short to waste on Java? Yes, some of us really find Java that bad.

Plenty of other languages have solved the same problems in much better ways (as demonstrated by this very discussion re: asynchronicity). I'll pick Go over Java, Erlang over Go and wouldn't pick Java (incl languages running on top of) for anything today.

Re:A History of Clojure [pdf] by bcrosby95 on Thursday June 04, 2020 @07:40PM (#23423332)
I usually find immutability to be more important than this particular detail. Because of this my preference is usually Elixir/Erlang, followed closely by Clojure (for the potential interop with a huge ecosystem), with languages like Go and Java fairly close to eachother but pretty far down list.

I would love it if Clojure on BEAM were more mainstream.

Re:A History of Clojure [pdf] by didibus on Saturday June 06, 2020 @03:52AM (#23437510)
Re:A History of Clojure [pdf] by nojito on Thursday June 04, 2020 @07:16PM (#23423124)
Why not?

The java ecosystem has solved so many problems already.

Don’t you want to just focus on the business problems?

Re:A History of Clojure [pdf] by lostcolony on Thursday June 04, 2020 @10:13PM (#23424328)
The business problem still can include things like "concurrency", which is just -painful- in Java, especially if I/O bound.

I much prefer languages that make easy stuff harder, but hard stuff easier, than languages like Java that make easy stuff easier, and hard stuff harder.

Re:A History of Clojure [pdf] by waheoo on Friday June 05, 2020 @12:00AM (#23424960)
Java doesnt solve business problems.

It solves enterprise ones.

Or at least claims to.

Re:A History of Clojure [pdf] by dkersten on Sunday June 07, 2020 @01:34PM (#23449018)
The Java ecosystem has solved many business problems, for me and plenty of other people I personally know, both in small startups and in large companies. Just because you are personally prejudiced against Java for some reason, doesn't mean that its not a good ecosystem, because it is. I don't like Java the language (and certainly not the crazy frameworks), although it has improved, but the ecosystem, especially from Clojure, is fantastic.
Re:A History of Clojure [pdf] by pjmlp on Friday June 05, 2020 @09:54AM (#23428536)
Enterprises do business last time I checked.
Re:A History of Clojure [pdf] by armitron on Thursday June 04, 2020 @07:23PM (#23423195)
I don't solve business problems, I solve my own problems and try to have fun along the way.
Re:A History of Clojure [pdf] by raspasov on Friday June 05, 2020 @01:13PM (#23430911)
You are confusing Java with the JVM.
Re:A History of Clojure [pdf] by armitron on Friday June 05, 2020 @03:12PM (#23432599)
No I'm not, there is no escaping Java when you work with Clojure, since you'll be using Java libraries and working with Java APIs all the time.
Re:A History of Clojure [pdf] by dkersten on Sunday June 07, 2020 @01:35PM (#23449024)
Depends on what you're doing.
Re:A History of Clojure [pdf] by didibus on Friday June 05, 2020 @01:05AM (#23425251)
Regarding Java, sure. But in the context of Clojure, it's here right now as well, no need to wait for anything.

I also don't really understand the "bloat" comment. What do you refer too? Are you referring to the fact the JVM supports too many features?

Re:A History of Clojure [pdf] by pron on Thursday June 04, 2020 @07:34PM (#23423278)
Sure, sometimes a simple, crude runtime will do, but if you need really good performance and low-overhead deep observability, you might want to be saddled with something that's more state-of-the-art.