Re: Alternatives languages on the JVM: which one or is there no alternative?
On 14.12.2013 18:47, Arved Sandstrom wrote:
I have fairly typical online subscriptions and professional reading
habits: DDJ, CodeProject, InfoQ, ACM TechNews, ODN, The ServerSide,
LinkedIn groups, to name a few that are reasonably general. I've noted
the same thing - how the hell does anyone keep track of all this stuff?
Hire someone doing the reading for you... ;-)
Agile was supposed to supplant waterfall and spiral and all that, but
now apparently agile often fails at scale, so lean is the way to go.
Build system A for language X is obviously obsolete because it's already
6 months old, so someone had to invent build system B. There may be ten
thousand *.js libraries out there now, and God only knows what they all do.
:-)
I've evidently really missed the boat by not being up to speed on
asynchronous event-driven functional reactive programming. I've also
noticed that after the few years that I generally ignored NoSQL that now
there's a backlash that is talking up relational again - good to know,
RDBMS's worked just fine for me all along.
I, too, am convinced that many underestimate the value of mature RDBMS
systems. I'd love to know how many people go through hoops and loops to
retrofit transactional behavior on a NoSQL DB because it looked cool
when the project started out. "Concurrency we'll do later." Well...
There's plenty of innovation and disruption alright. So much so that
we're no further ahead in solving core problems than, say, 20 or 30
years ago.
It's disturbing to see how often the same problem is solved over and
over again. Just look at the number of text editors...
The core problem with UML or other modeling languages is not the
constructs they make available, it's the fact that many people feel the
need to express every detail of their design using UML etc. I'm not
interested in seeing a class diagram that shows every private field for
every class, nor sequence diagrams for mundane interactions. The
graphics should express key information, not all information.
Exactly! Well put.
1. Not always a person's fault. One's employer frequently indulges in
title inflation. I'm familiar with quite a few local software
consultancies where practically everyone is a "senior consultant" - no
matter that you're just a junior coder for hire who's got 2 years
experience...
You get to charge more for a senior... In part it's also a cultural
thing. A few weeks back I saw a request for a senior which required two
years of experience - and it was not in the western hemisphere.
Cheers
robert