javaistheworst

In the longer term, I would expect both of rthem to be afraid of the many smaller local players in each country when they start to up their game in terms of hosting. People are starting to become wary of putting all your data in one cloud - whether it is a Google or amazon shaped one.

Not mentioned but important is coding - if you are a quant in an IB these days, you will be expected to do some level of coding - often C++, Python, and maybe some Excel VBA to plug things in for the desk to play with, while IT production-ise the rest intop the RMS and trading apps.

The speed with which the news is published, retracted, updated, edited, syndicated, these days is having interesting effects on other industries.

One example is the algo trading systems going off strat due to a news posting, which may then get revised a short while later, but by then it can be too late, the portfolio is already affected.

Another industry affected is the research, advisory and consulting houses. Clients pay them for a reasonably constructed set of arguments and viewpoints, but fast news means the client can in some occasions validate or invalidate those paid for opinions in almost real-time, potentially lowering the value.

One day, maybe we will have a slow news movement.

A similar model for London, especially in the city and along the river, would be a constant - the old adage about never being more than a few feet from a rat are spot on. Bear in mind, the officially reported numbers are often a fraction of the real population. Rats are fairly intelligent creatures and are adept are remaining mostly hidden, even in the well populated areas.

A friend who makes a very decent income as a pest controller has very interesting stories to tell about the size of the rat population he encounters, the shift in their diet over the years (more fat and junk food remains), and worryingly, their increasing resistance to the wide range of controls in use today.

We are using Erlang and trying out Elixir on one of our projects, and so far it is working out very well - a big chunk of that comes down to the way concurrency is handled especially in the context of letting things fail, accepting they will fail, and designing with that in mind. A similar attempt with Go was perhaps not so successful with the need to bear in mind how Go models errors and failure within code, which ended up cluttering up the code quite considerably.

Excellent - will have a play with this tonight. Docs look pretty good too, only thing that stands out right now which I want to dig into a bit more is one of the special forms, specifically the dot one - looks like something that would be tricky to see in an eyeball scan of code, but probably worrying prematurely.

Most people in our large open plan office now wear large noise cancelling headphones in an attempt to drown out the gossip by the coffee machine, the colleague behind making a phone call with details far too personal to be sharing/scaring with us, the drone of many printers and photocopiers, inane ringtones, someone laughing far too loudly, and the person who eats with their mouth open and smacks their lips. But otherwise, yeah, go open offices.

Walking around Northern British towns on a Friday evening can provide a glimpse of those early hominoid alcohol consuming ancestors.

So anyone who posts anything critical about Java the language is now a troll? Must be fun in your world!

It would be cheap and easy to label this view as almost a perfect example of Stockholm syndrome, but I would suggest you may need to be a little more objective and critical of your tools. The master works with a variety of tools exactly because they have strengths and weaknesses. Java has some extreme weaknesses in verbosity, almost to the point of programming language diarrhea. It envelopes a development culture that gave us things like: InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneMaximizeButtonWindowNotFocusedState.

I have created a new account, but I don't recall mentioning it was a throwaway - sounds like someone has a bad case of the assumptions!

No really, Java the language is bad. Terrible in fact.

The fact I need an IDE to make it workable (just) highlights this point. J2EE was terrible too, because it showed where things can go, if you let the Java astronaut architects lead.

Some of my most profitable projects were helping to rescue systems by migrating to to an alternative language on the JVM, or off it completely.

The worst part is the damage Java inflicted upon a generation of developers.

I have a problem, I think I will use Java, and Eclipse, and Maven, and all the rest. Now I have twenty thousand problems!

Edit - if you disagree, then say so. Bit spineless to downvote without a valid point to back it up!