2,290 karma · joined October 9, 2008
The trade secret claims are still looking pretty good for Waymo.
I'll quibble with this bit though:
> ...toxicity festers in open source because it’s all too common for forks to ground their motivation in emnity towards other projects.
This is wishful thinking, for the most part. Communities don't break off because things are going well. The American Revolution wouldn't have forked if King George had been sympathetic to their needs.
I will say that self-driving cars help a bit in getting people to bike, though. The biggest barrier to biking in San Francisco is people's fear of getting killed by cars (the SF Bike Coalition has done surveys on this). Self-driving cars should pose less of a risk to cyclists - they don't run red lights or speed, etc.
Another potential benefit would be reducing the need for parking. The biggest obstacle to physically separated bike lanes is the space they take up - typically that requires removing parking. If self-driving taxis are super cheap, that should lead to less car ownership, and possibly less demand for parking.
That's all very speculative though.
I don't see why they should free as in beer - developers need to get paid.
As for being open source, it depends on why you think that’s important. To me, the goals of open source are:
- Make sure that you aren't building your business on top of proprietary software. This isn’t relevant for gamers.
- To increase the productivity of all software developers. This is achieved by open source engines.
The author might as well say that we shouldn't use any proprietary platforms (like, say, Hacker News).
As for tournaments, the variance is even greater, since it is closer to all or nothing. To mitigate this, pros "buy a piece" of each other. Or swap equity. If either wins they pay the other a percentage. If you do this with enough other pros, you even out your swings...
Playing 10% of your hands is very tight if you're up against other good players. At a loose table it might be very profitable though, especially if the other players aren't paying attention to how tight you are, and therefore don't give you enough credit for having a strong hand when you do play. That kind of table is pretty common at low limits.
And what's wrong with heads-up, anyway? It's not as popular as multiway, but it's a fascinating game. In a full table game, you usually only end up playing 20-25% of your hands. Heads up you play 90%+. You end up in leveling wars with your opponent more often, too ("he knows that I know that he knows I usually wouldn't play a premium pair this way").
Uber can absolutely fix known issues in its vehicles.
If you have more control, you have more liability.
Edit: Uber probably has product liability. Which is very different from liability for an employee's actions.
What's the downside?
Drivers have personal liability. Self-driving cars have corporate liability. I'd expect a big judgment if someone is killed because of a known issue.
General purpose machine translation is harder, for instance. Brute force algorithms have gotten decent, but aren't in the same ballpark as humans (though professional translation services now often work by correcting a machine translation). However, MT systems trained on a specific domain do much better (medical or legal docs, etc).
What would be the hardest task for machines that's trivial for humans? Maybe deciding if a joke is funny or not?
This investor is probably making more than the vast majority of the people building technology. It's not clear to me why society benefits from that.
High salaries encourage young people to enter the field. That's a good thing.
High housing costs are another matter...
It's a huge undertaking. There are just a ton of library calls to support. Here's the list of AS3.0 classes: http://help.adobe.com/en_US/FlashPlatform/reference/actionsc...
And a whole lot of games are still in AS2 - game developers never really embraced AS3.
It really isn't going to happen, I'm afraid.
EDIT - Maybe it's possible to compile the C++ sources for the Flash Player to WebAssembly? Then you wouldn't have to re-implement the libraries.
I don't know the state of these compilers, but there was a Mozilla post about it a while back: https://hacks.mozilla.org/2015/12/compiling-to-webassembly-i....
Adobe hasn't open sourced the Flash Player, so it would have to be them.
I'm not a machine learning guy, but when I was at Kongregate, we had a problem with credit card fraud on our virtual goods platform. It wasn't serious fraudsters, just dipshit teens with their parent's credit card.
I had labeled data: historical transactions, with chargebacks, which I fed into Weka. I included all kinds of stuff we knew about the user. A simple rule-based classifier could pick out risky transactions, with a lot of false positives.
I made a simple tool for our customer service team to review these risky transactions. They would decide whether to warn the user, temporarily block them from buying or temp ban them, or permanently ban them.
This worked pretty well for us. The risk factors were new players, players spending quickly, and users who were dicks - as measured by how often others had muted them in chat, how often they swore in chat, etc.
As an aside, saying "fuck" or "shit" in chat wasn't very predictive of fraud - often those terms aren't signs of an abusive user, since they might just be saying "fuck, I suck at this game". What was predictive was users who said "Gay", "Penis", or "Rape". People who use those terms on a game platform are largely dickheads. So the score for abusiveness became known as the "Gay, Penis, Rape Score" or "GPR" for short.
Edit: the author acknowledges the incompleteness of the data in the conclusions section. Oddly, he doesn't think that's likely to affect the mean "since the sample used herein is a large and random subset of the to-be-completed data set". That doesn't really make sense to me. How would random sampling of incomplete data improve the results?
http://regressing.deadspin.com/deadspin-police-shooting-data...