boiler

Java isn't much better either, why all this boiler plate, and still concurrency nightmares.

You have to heat and cool boilers and steam turbos slowly or else differential expansion can rip them apart.

However, for a simple example like a + b, it's still quite a bit of boiler plate; we can certainly do better!

In Java the boilerplate was a creation of the language, but in javascript it's a creation of the community!

This is great because it saves all the boilerplate above and nicely abstracts away most of the null checks while preserving safety.

Functional objects, case classes and implicits could help you model your business domain better, write thread safe code, and get rid of much of the boiler plate.

Idling the diesel for 15 minutes a week is not quite as exciting as slamming it open full throttle for 12 hours while you heat up the main boiler or whatever.

You mentioning Java actually reminds me, what I find bizarre about the recent trend in javascript is that they're creating the boiler plate on purpose.

Below is a boiler-plate message I got from a lame tech recruiter, followed by my snarky response.------------------My associate forward me your contact info.

For example, whenever I need to perform multiple async calls with callbacks I've always got to write a bit of repetitive error-prone boiler plate to wait for and combine their results.

It's the only one where I don't lose my train of thought trying to remember to remember the idiosyncratic way someone ordered the parameters to an API call, or because I'm stuck writing a few dozen lines of boiler-plate.

They are put into agreements typically as boiler plate "I agree for a period of 'x' I will not work for a company that competes with employer or start my own." So if you were hired in California and went to work for a competing company in California, it would be safe to say if there was a non-compete" clause in the original contract the courts would not enforce it.