282 karma · joined August 7, 2013
That said I agree they should have picked Go instead /s.
Are security devices optional features for cars (and I am not talking about collection cars or similar niche items) ? They are not in first-world countries.
I have not read Taleb's latest book, I am silly enough to have found some interesting bits in Antifragile so I am certainly missing something. Ignoring the sarcasm, how is this idea ridiculous?
I am certainly worried of today leaders wielding more power than ever without having any concrete idea of the outcome of an actual war. And it will only get worse.
I had to implemented a specialized geocoder/administrative boundaries referential last year. Mapzen was really compelling, the documentation about how they handled hierarchical data was clear and interesting but execution was lacking. I am French, handling European data was important and I quickly hit several pain points:
- Their github repository organization was a mess. A lot of small ones without a clear map of which did what. - The vagrant setup to experiment locally was unmaintained - I found a basic unicode normalization issue in the geocoder several hours after playing with it. - Manipulating their dataset via git-lfs was a massive pain - Their geocoder was nicely presented but relations to administrative levels was done with neightbourhood search to administrative area centroids, instead of (even approximated) geometries. - The data was not as comprehensive and up to date as OSM one, at least in France. For instance, France second level administrative areas (Régions) were redesigned at the beginning of 2016. They were defined in OSM but progress seemed fairly slow in Mapzen.
Now, I appreciate Mapzen was a very ambitious project and handling cartographic data at this scope and scale is a difficult job, but as pure data consumer, it was not comparable to OSM.
I eventually used OSM data and while their documentation/tools are quite a mess too, wiki style, it is workable. Datasets are large but there are a lot of way to retrieve them efficiently. Their non-protobuf binary format hits a sweet spot between size efficiency and ease of processing. And at least in Europe, the data is fairly good, at least for my requirements.
The solution is not tipping, the solution is applying the law and closing loopholes.
[1] http://www.lemonde.fr/economie/article/2017/08/26/en-colere-...
The US is a superpower that maintains its geopolitical order with the help of its military. Like any dominating nation before it, no argument there. But please stop justifying all this with good intents or universal values. The US does what it does to improve the life of its citizens, period (or at least a subset of its citizens).
"To date, the mechanism of action of paracetamol is not completely understood."
and:
"It is the most commonly used medication for pain and fever in both the United States and Europe."
"Not completely understood" is not the same as "we have no idea why it works", but still I find it telling for such a popular product.
I feel like you are addressing teams of several hundreds of developers. Unless they commit large binary files each day this is hardly an issue for smaller several tens people teams.
> even after stringent code reviews, bad code gets checked in and break multiple projects not just your team's project.
Revert such code immediately once detected by the CI. Which is harder to do if the changes and their adjustments are spread across dozen of repositories. Also, please compare the easiness of setting up CI for a hundred of repositories compared to a single one with tens thousand of files.
> your IDE (IntelliJ in my case) stops working because your project has million of files. Require creative tweaks to only include modules you are working on.
Monorepo does not mean you have to load everything in a single workspace. It means everything gets committed at once. If your tools cannot handle so many files or cannot be configured to work on subsets, blame your tools.
Yes, monorepo present some challenges but handling hundred of repositories is no better. Having done both, I prefer the former.
And yes not everyone is Google, with thousand of developpers and billion lines of code.
Sorry, 50k is not massive, let's talk about a couple of millions.
I do not think relying so much on nuclear energy was a bad move but it should have been a transitional thing (to renewable energy, fusion, anything else?). And it requires good forward thinking, commitment and the kind of leader we have not had for decades.
Finally, the EPR looks more and more like a big mistake. Smaller designs might have been more successful and offered more agility in time of crisis.
> I don’t really get how, in the case of an HTTP conversation (or flow) which is connectionless, all the packets in the conversation get marked the same.
What do you mean? HTTP is stateless, not connection-less. This is probably related to:
> Although HTTP is a connectionless protocol this change of IP address did seem to freak some services out.
Maybe what you saw is a single request being split into multiple packets taking different routes then different source address from what you said. I have no idea how such setup could work in practice.