skysight-inc/HackerNews huggingface dataset:
Science is about what is, not what we should do. Politics is about what we should do.

The minute you cross that line, the minute you start advocating for an outcome, you are an activist, not a scientist. You are now playing in the political arena. Messaging becomes important. Fundraising. Making sure the right people get elected. Preventing the wrong people from getting elected.

As a layman who likes watching smart people argue, I'd said for some time that the climate debate is the worst public debate today, mainly because it's dragging the name "science" through the muck of politics.

Now I'm hearing from both sides that politicians (gasp!) want to get involved. Well, what the hell did you expect? Do you really think it's reasonable one day to be yucking it up with politicians from party X and then expect folks from party Y to just leave you alone because science?

Real scientists can't be advocates. It's a conflict of interests. This, along with open science being a requirement for public funding, has become abundantly clear over the last few years. Science itself it awesome. It's mankind's only future. The actual practice of science over the last decade or so has been full of fail.

If you'd like to hear the other side, here's a great Reason article. http://reason.com/archives/2016/07/15/the-lefts-insidious-wa...

The bottom line is that if we want to make good public policy, we need scientists to honestly evaluate the science, not engage in political muck-raking, venture into economics of the year 2100, posit that big companies are misleading the common rubes through purposely-slanted studies, or anything else. Just science.
Corresponding [Reddit discussion](https://www.reddit.com/r/MachineLearning/comments/4tsi2n/uda...) and [Medium post](https://medium.com/self-driving-cars/udacitys-self-driving-c...)
A safe Rust abstraction layer for native Node.js modules
I'd be curious to know what kind of image recognition software the author used to detect relevant images and if it came with a significant performance hit.
Computers are not apriori better - you can always develop a stupid or buggy algorithm that fails often. But Tesla is working to PROVE (using real-world data) that autopilot is better than a human driver, and IMPROVE it constantly until it is ten times better.
sounds like diazepam
Show HN: Lua Digest -- Regular Lua Newsletter
Yeah, possibly. It depends on the industry. Like you couldn't directly compare Intel to ARM because their strategic groups are too divergent, even though they ostensibly do the same thing.

But within the same strategic groupings, it might become more appropriate to say "outsourcing or more/less integration is/isn't a good choice for this industry due to xyz". So at some point you might expect to see (for example) the manufacturer who mines their own metal's revenue to increase if there's ever a global shortage, compared to competitors who rely on other companies. So as in, the mining car company might have lower production numbers per employee than competitors due to a larger staff, but if vertical integration makes sense in that industry, you'd expect revenue per employee to demonstrate that over time.

In this case, if Tesla have lower production numbers per staff due to less outsourcing then that's just necessity, due to the fact that it's a tentative young company which sells a highly niche product. It'll work out over time if they can establish themselves in the industry.

But basically yeah you're correct, it doesn't make sense to look at a single metric in isolation, without taking a wider view.
I just had a crazy brain fart, what if bitTorrent and bitcoin had a child?
How many mobile phone accounts will be hijacked this summer?
Because we have to reinvent the message bus every fifth year, so we have to de-invent it in between.
This is how the US debt collection system works according to an article I read a couple of years ago...
See my other comment a bit up in the thread. ZFS does data checksumming which relies on the ram not lying to you.
> I'm okay with calling that a microservice, since it's infrastructure code that needs to be deployed and maintained as part of the app. But it's really only a line of BASH.

I'm under the impression that most people wouldn't call that a microsevice. Moreover, isn't that solution completely dependent on the implementation of the code that is writing those certain files, without making this dependence explicit - and pretty difficult to test automatically?
The title is misleading, as is the press release. The ECB does not issue banking licenses, nor is it involved in active regulation of individual banks.

If someone had issued NUMBER26 GmbH a banking license, then as a company situated in Germany, that someone would have been the BaFin, the German banking supervisory authority.

Neither N26 nor BaFin list such a license yet, but I guess it's still early.
Since when was "Arduino" a language??

Its C++, just hidden.
Part of BT is down again
What are the worst things about it?
Not only that, but I believe a bad checksum can also cause a cascade to "fix the data", causing further corruption.
Sure they can be replaced peacefully, in theory. Governments do occasionally fire civil servants for loyalty reasons, though it's controversial, since those positions aren't supposed to wield political power. Think of Bush's prosecutor purges.

Though I agree that Popper doesn't focus enough on degrees of change or feasibility of change (if the only parties essentially agree on everything, is government really replaced?)
Microservices also enable you to scale individual parts of your application. If you need better performance for, say, image compression then it's much easier to add resources to a service that lives in its own process space (or its own server, or rack of servers, or data centre..) than it is to improve the performance of a specific library in a larger application.
Here, the application's notion of whitespace was more comprehensive that the standard library's.
Atletico Madrid telah membuat tawaran
The ECC myth?
There are three issues here that I can think of.

First is the obvious one that your loaded question alludes to: a resistance to change because that costs so companies won't do it until it would give them a relatively easy advantage (that lasts more than a week) over their competitors.

Second: creating new infrastructure can be a lot easier than upgrading. You don't have to worry about supporting existing devices and userbase.

Third: In developing nations infrastructure projects like that are often in significant part funded by internal government funds and external aid rather than there being an expectation that commercial entities will foot the entire bill.
How to fix flying
> For load balancer health checks, I prefer ones that hit the controller and expect a 200, and nothing more

A very sound strategy, IMO. I subscribe to this KISS practice. If response/status != 200, issue an alert and/or call a deeper health check routine.
> HN comments usually seem pre-dominantly pro or anti copyright depending on context (e.g. "big company fails to comply with GPL" would result in mainly pro copyright comments while "bittorrent site gets shut down" would mainly result in anti copyright ones).

I wouldn't use the GPL as a copyrights poster-boy since it subverts the 'normal' use of copyrights (restriction of distribution by 3rd parties) - the FSF calls it 'copyleft' for that very reason. My feeling is that being pro-GPL and being pro-bittorrent is consistent with the "information wants to be free" mindset - no cognitive dissonance necessary. The day HN becomes pro-Mickey-Mouse laws then you would have an argument.
Just another average guide to deep learning. Nothing new here other than some guy trying to become a thought leader.
It's been like that for a while now, and similar to yesterday's issue.

http://downdetector.co.uk/problems/bt-british-telecom

And seems to be related to the same issue
Yes it did. I start using a lot (as a student) Visual Studio and Windows 7 after a year with Linux. By this time products were good. I got a Windows Phone 7 and developed some app on it.

After that Microsoft release Win8 with its insane UI that make me loose time compared to previous versions and it was mandatory to develop for WP8. Then it release WP8 with no upgrade for existing phones. It purposely "uglify" VS 2012 removing all color and using CAPS menu which I found more difficult to use.

Things got even worst with Win10 where they actually didn't listen to feedack and release an OS with start menu not really usage. And forced people to migrate by changing their whole system!
Also bugs, bugs and bugs with both the system, new version of Visual Studio. And on the phone side they kill the entire Nokia line-up and still no manage to release a usable version of Win10 for phone in on year. The insider builds each broke more stuff than they fix even to the point you cannot even deploy an app.

I franckly tired of this cr*p. Promises not kept. And the fact Microsoft had cards to do great stuff but self destroy them. Many times. I'm still using VS and C# because that's awesome but I will not change my system for Win10. That's why the .net core stuff is interesting.
I'd agree philosophically that this is the right way to do it, but that's not what most people are speaking about when they say "microservices". They usually mean small independent servers communicating via RPC, each of which only does one thing. I'd say that this is pretty much the opposite of what you describe, since now each task needs the overhead of serialization, deserialization, marshalling, error-checking, process monitoring, etc.
Or any memory safe language. Heck, you could implement image decoding by doing an RPC to a sandbox with a shared memory segment that decoded the image to a device bitmap using Java or C# or JavaScript or pretty much anything.

Java specifically doesn't have this issue because its image decoders (except for JPG) are written in Java itself.

So whilst for the types of library that Apple OS' use, rewrites in Rust would avoid any odd IPC issues and be the most obvious drop-in replacement, you would pay the cost of rewriting the libraries as I guess there are no mature Collada or OpenEXR libraries in Rust. I do see a TIFF library though it says it doesn't support interlaced images.
Thm: There are no uninteresting theorems.

Proof: Assume there are uninteresting theorems. Let T be the shortest such theorem (under some fixed encoding). Having the special property of being the shortest uninteresting theorem makes T interesting. qed.
I was hopping for more from Rust :|
Rio, the Olympics, and Broken Promises
The real takeaway from this is that the author uses Hackathon Starter (https://github.com/sahat/hackathon-starter).

I have used it for multiple projects and it gives a huge head start compared to starting from zero. Signing up, logging in, resetting the password, uploading, etc all seem like easy work but when you pile them all up you can easily spend a week just getting to the point where you are within minutes of cloning the starter repository.

However the failure of GoChat is not relevant to Pokemon Go. While GoChat might have done something very wrong comparing 1mil users to an app with tens of millions of concurrent users is invalid. Pokemon Go would be a NoGo running on a single Node.js machine without any sort of balancing.
PVS-Studio: Recheck Blender open source project
> A shift to technologies safer than human-driven cars would dramatically reduce human suffering and should be welcomed.

Car-for-car I'd easily wager that manually-driven cars have been involved in far more accidents than the one or two Tesla accidents that have occurred over the same time period (not to dilute the terrible result of the most recent accident).

The problem is that a typical person doesn't care. Car accidents where a human is at fault are "normal." We live in a society where speeding, aggressive driving and/or DUI are routinely practiced. From personal experience: even when you dial the convenience factor to 11 (Uber/Lyft) people are still adamant that they are OK to drive. The driver is blamed, not the fact that the driver is doing something that evolution has never had to solve.

Additionally, the non-technical crowd are very used to machines breaking and doing the wrong thing. So when you come along with a story about how a machine killed a person in, what is very strictly, a motor vehicle accident everyone's built-in beliefs about machines are merely reinforced. Few step back and consider how embarrassingly incompetent humans are at driving, and how a machine that doesn't yet have the sensors required to properly perform the task still runs circles around our very rich set of senses.
I have been doing it since the early 90's.

It is called unit, module, package, library.

No need to put some network layer, with its own set of problems, between method/function calls.
How to Reformat Reality
As acquisition nears, Jabong pivots from an inventory-based to marketplace model
> but in comparison it will never fail as often as human do.

Maybe eventually, but what I'm interested in is right now, does the tesla autopilot fail more often than a human driving in similar conditions. My suspicion is that it does.
Regex: ruining your life since 1956.
Tiobe seem to alter their methodology fairly often which afaik also has the effect of altering historical rankings.
In other words if you look at the TIOBE rankings on the wayback machine for a particular year in the past they can differ greatly from the rankings for that year given on the site today.
For example, I think that VB was affected greatly by this
If you draw a circle 50 miles in diameter around LA, SF, NYC, Boston, and DC: basically anywhere outside of those circles in the mainland US is pretty reasonable. It's not just the rust belt, really. You can live in Miami, Seattle or Chicago and do just fine.
But that is the thing.

It just means that instead of using the language features and creating clean interfaces across modules, they were witting spaghetti code.

With microservices they get to write spaghetti REST calls with the added fun of distributed computing failures.
It doesn't use cert pinning so using mitmproxy to intercept traffic is possible. So far I've found:

It sends couple of POST to https://play.googleapis.com/log.

Seems like it is sending some kind of google maps counters (GMM_COUNTERS, GMM_PRIMES).
Although, many of them do not handle non-ASCII Unicode whitespace characters (which is what the StackOverflow regex was going for).
Pff that's nothing. I could build a fake app, in less than 1 hour, for $100 and get about 5 million downloads in 1 day.

Step 1. Find some opensource app code

Step 2. Call it Pokemon Go 2!

Step 3. Upload it to Appstore & link it to dropbox

Step 4. Spend $100 on African "talent" to give fake 5 star reviews & positive comments in app store.

Step 5. Hit F5 repeatedly at Appstore to watch the download counter increase to 5 million in 24 hours.

Step 6. Profit ?!?!

Step 7. Post story in /r/nosleep because too much guilt fooling 5 Million people.
The idea of putting into different collections up front is pretty smart. To generalise it into a broader lesson, I guess you could say it makes sense to make a one-time effort up front to save complexity down the line.
Should link to: https://blog.mozilla.org/futurereleases/2016/07/20/reducing-...
Building projects of one's own design is significantly different from freelancing. A freelancer finds people who will [hopefully] pay money for services. Building a product means finding a product that people will pay for. It's a lot easier to build something people won't pay for than a product they will pay for.

One way to look at it is that a freelancer sells the work before performing it. A product still has to be sold after all the work is done.

Anyway, I went out on my own when the economy tanked and my employer was sinking. I was just another rat fleeing the ship.

Good luck.
I believe thats already been done
http://global.yamaha-motor.com/showroom/event/2015tokyomotor...
> We've shown over the past 40 years that we value developer productivity much more than user resources

Of course: we're developers, and we can't multiply. When we use the user's time, we picture using one user, not one million (or, more reasonably, a couple thousands). So it rarely occurs to us that the users' resources are vastly more important than our own productivity.

To a lesser extent, this can be true for custom software as well.
I really value your contribution, thanks for sharing.

I give the proponents/consultants credit for proposing a practical and incremental solution to these people instead of just insulting them or saying "you're doing it wrong".

That being said, the issue I have with microservices is the fact that the below is repeatedly used as a core technical argument :

> They had built the whose system using the classic, box-box-cylinder architecture. There were hundreds of little top tier 'services', but in practice, they all shared the same database, had to be deployed pretty much at the same time, and version upgrades had to go in lockstep. Every so often, database changes were necessary, and the world would grind to a halt for months to make the system still work after the migration: It was awful.

This is not a feature of "monoliths", this is a feature of shortsighted design (at the beginning) and cowboy design (at the end).

Let's be clear : apart for load balancing for performance critical areas (which only exist in 20% of the applications, and only cover 1% of a typical such application - or 60% if you are Google, Facebook, or Amazon or the rest of the top 10), there's nothing that microservices do better than in-memory libraries. Also, centralizing everything as opposed to having processes run on various servers creates the issue of the single point of a failure. Whole new classes of similar issues appear. It basically is buying troubles.

Adding microservices will never be a neutral operation, and incurs a real cost. This cost is the cost of distributed objects which has been known for over 20 years and has been well-documented by our fathers.

Once the above has been dismantled, it then comes to : "yes but teams can develop in different languages", "yes but dependency management becomes easier". But once again, when it comes these interoperability considerations, a solution also exists and has been created about 15 years ago. This solution is called .NET (30+ languages compiling to a single Intermediate Language, COM components, first-class library support, etc...). Even the "yes but I need to communicate with non .NET in-memory applications" is very maturely addressed by the framework. (it was one of the first-use cases addressed)

I also read in this thread : "the ability of teams to control their own destiny and not be blocked by other teams". With libraries teams can choose the version that works best for them, and a well-design in-house library would provide the extension points (Dependency Injection, Dynamic Binding...) that would allow the clients (the other teams) to specialize the behavior.

So in a gist, my main reproach for this, is that if people put the same effort they put in learning microservices to learning system and component design, they wouldn't even be a need to talk about the former. My regret is that people will always choose the hype and the new. But hey, that's how the game works.
C.E.O.s Meet in Secret Over the Sorry State of Public Companies
France orders Microsoft to stop collecting excessive user data
AFAICT (based on years of poking around various projects, and based on the data they provide on my own projects), the data provided by GitHub are largely broken.

Making analyses and comments on these data is futile, as I have already argued directly (and with vigour on my side) with several Redmonk employees in the past. This didn't end well, since I'm pretty passionate about these things in particular, and "the truth" in general (vs. "opinions").

I'm sure real scientists could do some interesting work on this subject, but Redmonk's methodology is anything but scientific, and in consequence, their results are just content marketing, not something that you should base business or engineering decisions upon.
A new wave of startups that rewards the individuals generating value
… and earned $0.
There's quite a bit of variability in what people mean when they say "microservice" I've read quite a few articles over the last few years that describe things as I just did.

However, you are correct. Most people are unable to get the cruft out of their head, so when they talk about microservices, they mean something like "exactly the way we used to do things, only with a few differences"

I was talking to a team last year that wanted to do microservices. They had a framework, a lot of tools, and were busy doing research, most of which consisted of reading fanboy posts and walking through happy-path tutorials.

When I started listening to what they were talking about in terms of an architecture? Wow! Too much to go into here, but one of the things was a "microservice" that at the beginning of the pipeline cleaned all the data.

Think about that. One "service" which was responsible for knowing every data type, performing all safety checks, and ensuring that all of the other services could run correctly. All in one place. You screw that one up? The whole thing is broken. You couldn't ask for tighter coupling.

And this, they thought, was better than a monolithic app.

I'm a big fan, but micoservices are going to make a huge mess in the industry that it will take decades to clean up. That's because most people doing them will think of them just as you suggested.

(Having said that, the ones who don't are going to run over everybody else in terms of productivity. Good for them and the orgs they work for)
I agree with you that it's not a bad thing - I think it's the main benefit of microservices for most larger organizations, the ability for different teams to control their own destiny and not be blocked on each other.

But there's now a whole bunch of new developers out there who are just starting out and read all about these microservices, and think that it's the way to write web backends, and that if you don't do it that way, you just don't know what you're doing. Even if you're a two person team - you must use microservices if you want to scale out in the future apparently. It's just unfortunate the amount of cargo culting going on.
I fully agree with this. If a system cannot be extended by some external team using only external extension points, all claims of modularity and architecture are idle talk.

I tend to use MEF (on .NET) and OSGi (on the JVM) not because I actually need extensibility, but because I want to enforce certain architectural constraints.
That is a misleading summary. (And out of context your link to Apple’s support document is also a bit misleading.)

OS X Security Update 2016-004 applies to v10.9.5, v10.10.5, and v10.11+ https://support.apple.com/en-us/HT201222
There are apks avaialable outside of app store and here in my office in India almost all of my colleagues are onto capturing pokemons
They still need to sell cars for the next couple of years. When they've mentioned autonomy and removing the steering-wheel (some) people get upset because they want a car they can drive themselves.

So if they tout the idea of people not owning cars too much that is will only antagonize people in the short term.

If the ownership model changes they can easily adapt. I think they are very aware of the car ownership statistics and how cars being shared is a fundamentally better model in most cases.
Both great.

AWS is great to the tune of $15,000
https://aws.amazon.com/activate/

GCE is great to the tune of $100,000
https://cloud.google.com/developers/startups/

I'd recommend doing both options. Burn through your credits on both platforms first, then make a decision about which one you like best... or choose none of the above!