hueyp

Yes, he was appointed dictator before the consulship of varro / paullus, but his strategy proved unpopular. It makes sense: identity is hard and slow to change, and the romans had a strong identity around aggressiveness.

That said, in the defence of romans, they were also open to learning and integrating others ideas into their own. Scipio africanus absolutely learned from hannibal, and was able to layer aggressiveness, deception, and delay into his strategy. Every metaphor is imperfect, and cannae is absolutely an example of being blind / stubborn, but my quibble with the OP would be that romans didn't _really_ change their aggressive identity in the long term, and that identify continued to serve them well for 100's of years after hannibal.

`REQUIRED_CHILDREN` used to not be in docs -- only code. This is what I had in mind when I said partial.

I don't know which, but I think one of the `RANGE_DELETE` vs `NODE_DELETE` said it could take a list of ids but only one of them could -- it was something like this at least ... maybe path vs key? I don't remember how it was documented -- this is what I had in mind when I said wrong.

I didn't submit PR's btw -- I suck at open source :).

> if the rates are much higher compared to a marginal increase in risk

Exactly. Same thing with public records -- having a public record could very well mean you have a higher default rate but what is important is LC punishes it more than they should so its a value investment.

We invest via a model (not filters) and the whole idea behind the model isn't to find what criteria makes someone less likely to default in absolute terms, but what makes one D2 loan less likely to default than another D2 loan.

Katahdin -- the northern terminus -- is the hardest climb of the trail and is the biggest focal point regarding the discussion of overcrowding.

I wouldn't call it a software layer implosion -- most people are going to continue to use abstractions on top of these API's for game development. Unity is to Rails, etc ...

The event is the transaction.

For example of I have a 'make_user_preferred' event, I just transact the database and then add any metadata I need to the Datomic transaction.

Datomic is Event Sourcing if you create a realized version of your database on every event. It is just smart about it and keeps diffs.

Swapping out inner html has issues such as losing form data and bound events (etc...). Ignoring that you also have life cycle issues. For instance if you have a component that needs to know its render height you want a hook for calculating that height AFTER the entire DOM has updated. Otherwise you are going to force multiple layouts (bad). React provides these life cycle methods.

As far as the render method being big, the premise React is built on is that the virtual DOM is much faster than the real DOM. Test as necessary for your own comfort / use cases. I personally trust the testimonials of people smarter than me that aren't the React team also feel this is true and are making real changes to their products based on that. I also trust my own experiences that the DOM is slow :)

SelectMany is flatMap.

Could the java equivalent be?

  articles.stream().flatMap(article -> article.getTags().stream())

Or is the previous map required?