This may be due to what trees are planted in cities:

https://blogs.scientificamerican.com/guest-blog/botanical-se...

No. Quite the opposite, AWS automates certificate issuance for you. You'd have to automate the process yourself if you switched to LE.

Of course, AWS only issues certificates when you're using their stuff. For everything else, use LE :)

Nitpick: You can only use ACM with ELBs/ALBs/Cloudfront Distributions.

I'd like to see the residuals from that model

My main gripe with Java is its lack of type inference and the resulting redundancy that pops up. Things like the following got tiresome quickly (I might be a newb missing out on a better way to do things like this)

  private final TreeMap<String, TreeMap<String, Record>> searchTree = new TreeMap<String, TreeMap<String, Record>>();

FWIW This will raise a warning in my dev environment as I have declared in my pom file that I use JDK 8.

Also I'd consider it better style to only specify the interface on the left hand side, something like this should work:

private final Map<String, Map<String, Record>> searchTree = new TreeMap<>();

Edit: if you use Netbeans with maven it will automatically pick up correct settings from the pom and autocomplete with a shorter version like the one I suggested.

This is a much more reasonable example than the line used in the article.

Alternative stack that gets you much of the same stuff with less:

TypeScript, React, Redux, Webpack, Immutable, Ava

- TypeScript covers much of the benefit of es6/babel/eslint/flow, Ava covers chai/mocha, and webpack can cover most of what gulp provides

Yeah ultimately what all this is trying to achieve is to make JavaScript have the basic properties and benefits of many other languages. Unlike other languages, JavaScript was developed in 10 days in 1995 and was never intended to be used as heavily as it is today, hence the gargantuan amount of packages and modules to rectify it's shortcomings.

There are many alternatives to chai/mocha. Ava, Jest and Tape.

I wouldn't consider Webpack an alternative to Gulp. Gulp is more generic. But if you use Webpack you can replace to task-runner part with a few scripts.

When using ES6 or TypeScript I'd also consider Immutable to be optional, because of "const" and "Object.assign()/Spread-Operator".

Also, React & Redux can be replaced with 1 thing, when you use a framework that bundles view components and state management.

Webpack is weird in that it's lumped with task runners/"Make"-like programs but it actually it's a configurable and hackable version of the browser asset pipeline.

Nit: not sure why you mention const. It does not provide any kind of immutability assurance.

I just use const instead of var/let all the time and it prevented me from overriding the variable later, which forced me to write my code a bit more functional then before I used it.

I know that I can still change indirect references or override valueOf() etc.

You probably know this, but for anyone else reading, the problem is that if you assign an object or array using const, the object/array members are still mutable. If you have a tree structure, you have to recursively Object.freeze the entire tree to get immutability, which AFAIK is basically what immutable.js does for you. I also use const by default, but I find that more often than not my variables are trees and lists.

there is also the possibility of talking to them about their life

The guy with the suit, house, and car is doing that too.

So? If they're that shallow to prefer the fancier suit and car over the more appropriate soul mate, let them fucking have them...

Accusing someone of being "shallow" because they have evolutionarily sensible sexual preferences is incredibly puerile. Any evolutionarily rational person would place substantial value on a partner who can provide for themselves and their offspring.

>Accusing someone of being "shallow" because they have evolutionarily sensible sexual preferences is incredibly puerile.

Being shallow is exactly that: being "evolutionarily sensible".

Unlike animals, that can be only (or mostly) "evolutionarily sensible", we have critical and self-critical faculties, and can see beyond what's "evolutionarily sensible".

And of course, billions of people don't give a rats arse about whether the person they'll fall in love with has a fast car and a fancy suit, or the body type that signals "I'll have plenty of milk for our offspring".

>Any evolutionarily rational person would place substantial value on a partner who can provide for themselves and their offspring.

If they see the world as some kind of jungle where what matters is a partner who can "provide for themselves and their offspring" then they're not just shallow, but also regressive.

You are allowed to have more than one factor in your preferences.

> And of course, billions of people don't give a rats arse about whether the person they'll fall in love with has ... the body type that signals "I'll have plenty of milk for our offspring".

Which billions of people? Females? Yeah, they're typically not looking for milk production in a mate. On the other hand, breasts are a huge component of male attraction in most cultures.

As for fancy cars, it's not the car itself; it's what it signifies. (Although personally, I would place substantial value on a mate driving fast cars! I love driving.)

In what way is it "regressive" to seek a mate who can provide for one's children?

eslint also provides static analysis for dependency resolution when using import statements instead of node require calls

eslint-plugin-import found several bugs for us when we enabled it. Can't recommend it enough. https://github.com/benmosher/eslint-plugin-import

yeah that works, your statement is fine

nice, thanks!

Potentially similar discussion https://news.ycombinator.com/item?id=11477314

For that specific problem you could use the upcoming addition to JS of SIMD for data parallelism while still in single threaded JS.