And for developers not used to Emacs, Eclipse and Counterclockwise is the preferred development environment. Even Emacs pros might find it easier to just start out with counterclockwise at first.
You guys troll over at Reddit too. Just the mere existence of Kotlin has gotten you and/or some of your compadres into a complete meltdown. Is this your fulltime job, or are you a part-time "Scala Defenders Brigade"? It's hilarious watching you clowns. Any criticism (real or perceived) or Scala, and you get your panties all bunched up in a knot. Scala must be in big trouble. You better redouble your efforts.
Another bitter Scala fanboy that goes trolling other language threads looking for any mention of Scala and who is very angry that Scala isn't taking off and never will.
That's the thing about the Clojure community. It doesn't have wackjob fantatics like you.
I never did see his definition of "win", but Clojure does have a great community and I consider that one of its greatest strengths.
That said, I can never see Clojure "winning" as in how Java "won". For all of Clojure's strengths, it's at best an intermediate step up from Ruby, Python, Perl... It's not that next order of magnitude leap of productivity that is necessary to "win".
The research just isn't going in that direction. The research is going into type systems and static guarantees. And I think the real productivity boosters of the future will be in very smart tooling - a conversation with your IDE I would say. Maybe Clojure could have different views (different surface syntaxes). Maybe it could be the basis of something like intentional programming. But straight Clojure with Emacs isn't going to be "winning" in the big way.
I've thought about that watching old movies from even as late as the '30s - that every single person I'm watching (scenes with 10s if not hundreds of people) are long dead.
No, no, no. That's what college professors with no real world experience tell you. In the real world, professionals use guard clauses to exit early all the time.
Yep, it's a crapshoot, but I think I'm going to pull the trigger soon on one of these anyway. Can you tell me which of the usual suspects (green-sum, hulustar, bigclothcraft, etc.... you went through?
What exactly was your problem, completely dead panel or massive backlight bleeding?
North Korea will never use nukes against South Korea. They want a reunified Korea under Kim Jong Un. And the best way to do this without killing innocent people is to do what they've attempt countless times before.
Dig a tunnel under the DMZ and send people in to capture/assassinate the key people within the government.
Wow, you really believe that is the best way? Or is that the best way in the demented minds of the N. Korean leadership?
South Korea kinda does not care, because they know North Korea wants the entire Korea, not half-korea and half burned slab of ground.
They might say that to their population, like they say that Kim Jung "Be Illing" shot a hole in one every time, but they don't really want the entire Korea, because they know they can never have the entire Korea.
That's funny because I feel the same way if I have to use Emacs. It feels like going back to the early 90s with some DOS Borland IDE.
Regular text editors just feel so clunky next to the cohesiveness of VS/Resharper or Intellij.
At some point in time, Emacs is going to have get overhauled to join the 90s, much less the 21st century.
And I understand that CL is a special case with Emacs, but it's still clunky as hell compared to what could have been really awesome environments (think Smalltalk environments), but with lots of resources pumped into the development.
When you have leftist democrats that are statists and country-club type republicans that don't really believe in limited government, and these two groups make up the majority of congress then there's really no hope until the people wake up to the tyranny that is happening.
But the people are ignorant and all the statist politicians and government officials have to say is "security" and the majority of the sheeple fall right in line - "what do I have to worry about, I'm not doing anything wrong. I dont' care if they're spying, if it's protecting the country".
I find that for majority of problems I deal with functional solutions tend to be simpler, cleaner, and more reusable.
OO on the other hand is directly at odds with reuse because you marry logic and data together into classes. If you write a method and you need to use it for a different problem, you often have to jump through hoops to do it.
On top of it OO encourages premature classification. If you create a class and you need to use that data in a different way later you have to translate it in some way. This is why you have things like wrapper and adapter patterns.
This can't be emphasized enough. I never understood why so many people thought that putting methods and data together was a good idea.
I think Rich Hickey in an interview with Stuart Halloway possibly once said that when you jam your methods in with your data you're essentially creating a mini-dsl that makes reuse impossible. I can't agree more.
Clojure is already successful for many people. What you probably meant to say is that Clojure will never be mainstream. That's probably true, but I have been subscribed to the clojure mailing list for quite a while now and actually quite surprised how much Clojure code is in production.
That said, the two big "strikes" against clojure for "mainstream" adoption are as you pointed out, it's a Lisp, and it's dynamically typed.
I like the core concepts of Clojure. That there are a small set of primitives that have a uniform interface and how Clojure is anti-OO. Clojure actually does OO better than OO languages do, but that's another story.
If I could just get a Clojure with some optional typing, a python-like syntax, and awesome tools, I'd be a happy camper.