5 ms·
Very similar to the c++ vs c debate. C++ has tons of arguably useful features. But these features also in a way distract from the task at hand - solving a prob
by strictfp 10y ago
Very similar to the c++ vs c debate.
C++ has tons of arguably useful features. But these features also in a way distract from the task at hand - solving a problem. You risk ending up discussing the meta problem too much - how to write and organize code.
C on the other hand is very basic, requires a lot of boilerplate and encourages re-implementation. But you are (subjectively) more likely to produce pragmatic code which will solve your problem.
Scala is the kitchen zink of languages, i could elaborate but I don't even know where to begin.
Go is very simplistic and architected to solve some recent problems. It's easy to write high concurrency, low latency apps with minimal startup costs. Perfect for microservices. And it explicitly avoids certain complicating features such as generics, while still catering for its use cases by supporting code generation and compile-time constant computation.
Go is the rise of New Jersey Style. All developers tormented by c++,ORMs,Java EE,Soap et al join ranks to show the world that "Worse Is Better".
A funny thing is that go is very similar in style to early Java, and I believe that Gosling et al did have the same mindset as Thompson and Pike. But somehow Java got overrun by the enterprise guys, and I don't know where they came from. Does anybody here know maybe?
- eweise 10y agoJava was a way For Sun to sell more servers so they pushed it as application server technology.
- strictfp 10y agoBut do you know who designed the server tech? Was it old mainframe people?
- fauigerzigerk 10y agoFor what it's worth, the initial EJB spec was written by IBM, so I guess the answer to your question could be yes. "The EJB specification was originally developed in 1997 by IBM and later adopted by Sun Microsystems" https://en.wikipedia.org/wiki/Enterprise_JavaBeans https://en.wikipedia.org/wiki/Enterprise_JavaBeans
- strictfp 10y agoThank you for the link. I looked up Java EE, which according to wikipedia mostly originated from WebLogic. The founders didn't seem that enterprisey though: http://otechmag.com/magazine/2015/summer/michel-schildmeijer.html http://otechmag.com/magazine/2015/summer/michel-schildmeijer... So IBM does sound likely.
- strictfp 10y agoThe anwers to this question is also interresting: https://www.quora.com/What-were-the-original-principles-behind-Enterprise-Java-Beans https://www.quora.com/What-were-the-original-principles-behi... . Hints that https://en.wikipedia.org/wiki/CICS https://en.wikipedia.org/wiki/CICS was the product inspiring EJB.
- deleted 10y ago[deleted]
- psiclops 10y ago> "Worse is Better" I wouldn't say that it is inherently worse to have a simple feature set. Sometimes less is more [0] [0] https://commandcenter.blogspot.de/2012/06/less-is-exponentially-more.html https://commandcenter.blogspot.de/2012/06/less-is-exponentia...
- strictfp 10y agoI was refering to https://en.m.wikipedia.org/wiki/Worse_is_better https://en.m.wikipedia.org/wiki/Worse_is_better , which does essentially say 'less is more'.
- deleted 10y ago[deleted]
- tomcam 10y ago<grumble>the hell's wrong with Jersey?</grumble>
- strictfp 10y agoNothing! I like Jersey style.