dvcc

Based on the overview alone (of course I can't read the entire report that fast!), this is exactly what I expect a spy agency would be doing -- if they were not then I would be disappointed.

What exactly in the admittedly shortened list am I supposed to be upset about? It makes no distinction between US citizens and overseas parties. If these actions are being done domestically against US citizens, with no just cause sure I will get upset, but that has yet to be seen.

As usual it seems Wikileaks publishes a sensationalist story around one of their leaks, claiming dozens of zero-day releases where most were already patched. Hell, they included the i0nic jailbreak as one of the 0-day exploits (https://wikileaks.org/ciav7p1/cms/page_13205587.html).

I'll let journalists parse through the full report before coming to any conclusion as of yet. I just find it hard to get excited about any Wikileaks release that has yet to be vetted.

It's probably not a favorable idea here, but luck probably plays a large part in converting from X to Y a month. Of course, perseverance over a two-year period increases your chances, so it still has a ton of value.

So I had some doubts about the numbers at first, but a rough quick calculation 12,000 / (1.3 billion (people) * .5 (age 25-54)) ≈ 0.002% of the available population a day creating a startup (1 in every 50,000) which does not seem too far-fetched, but still seems a bit high to be honest.

At first, I considered it more clever than anything. Using data to reduce ticketable-offenses for their drivers (in an undeniably unethical way). However, my view quickly soured when I read:

> If those clues were not enough to confirm a user’s identity, Uber employees would search social media profiles and other available information online.

For some reason, I make a mental distinction between some automated system blocking access and having employees research potential customers online for a ride-share app. The bad PR week for Uber continues.

Do people really find language-specific books helpful in better understanding a programming language long-term? Without ever implementing something, I don't think my memory would hang on to some language feature for long.

I think its a bit weird to think that Twitch needs to act as the parent of a thirty-five year old man. It's his own judgement in the end.

As an aside, sitting for 24 hours would not kill an otherwise healthy man, there was probably some underlying condition.

Just a slight warning, not everyone wants to read this at work most likely. I am not quite sure why I expected anything else though.

I don't think its really all that magical when looked at as a giant component. In the context of the react-redux lib, its really similar to just having one large top level component that contains your entire state and all methods you would want to commit (but instead its called a store and actions). Everything is still unidirectional in that it has to go through that main redux provider and then gets passed back down to all the children, without the need to pass around every single possible method to each child.

So even if you have two "smart" components they are still just children of that main redux provider and therefore it makes sense that they can impact each other. The same way children can call methods that change a parents state on normal react components.

That pricing seems insane :o. Even on the lite setup, each conversation would need to have $2 in value, on the standard plan it would need $2.50 in value (I know there is an increase in features but an increase in price per conversation as well?). Although I am not quite sure what a conversation consists of -- it could be a chat between two people over any timespan, in which case it really isn't terrible?

For those wondering Chrome v53 was released about 6 months ago. That's quite amazing.

My mistake, I didn't mean to marginalize the 1% decrease, but I don't think even its biggest proponents expected demonetization to help short-term.

I think you read a bit too much into that title, it's just saying that the cash shortage is having an impact. It quite often mentions that it's nothing crazy within it, but uses the anecdotes to humanize a story; otherwise, it pretty clearly mentions that 'the pain is hidden for the most part' and underlines that the projected growth only dropped around ~1%.

Wow, as a member of a blue-collar family this is downright insulting. The gross generalization of an entire social class is anything but healthy.

Funny enough, I just finished reading the article and comments from the story on what it's like to be poor at an Ivy League (https://news.ycombinator.com/item?id=13480802). Personally, I thought that I never really felt disparate enough where I actually stuck out to my peers, and that the thoughts everyone had were more akin to class anxiety. It seems that the thoughts are not always unfounded I guess. Oh well.

I'm always amazed at the employee counts for Twitter, Snapchat, etc. 1,500 people just seems astounding for a chat application; understandably, there will be other departments than engineering, but I'm still left amazed.

By the looks of it, I could just throw at it some response that is massive and it would still attempt to grab it?

If this is really being just run as a proxy setup, the jsonbrowse-proxy might not need the isomorphic-fetch lib, in which case you can just use the embedded node-fetch instead, which has max response size and timeout options available.

I'll take the counter-point on this one. I picked it up after it was mentioned in the YC's Summer Reading List; however, I found it to be a tire to finish.

The reasons and explanations given seem to touch around a technical, but not too technical approach to algorithms. Getting stuck in a place that probably just leaves both audiences a bit unhappy. For instance, there is a chapter that mentions that the optimal stopping point is ~37%. There is never any mention about how the 37% number is found. Of course, I could look it up but I could just as well look up the optimal stopping problem.

Aside from that, the examples come across as contrived and inapplicable. Sure merge sorting your socks sounds great, but I still will never do it!

The 'let' should have made me re-think the problem.

I think everyone will need a bit more context around what you do know prior to answering the question. Front-end development has somewhat quieted down from the crazy pace of the past few years -- or maybe I just settled into a stack and have given up, who knows!

But a lot of the major players (e.g, Webpack/React/Angular[!2]/TypeScript/etc) have all been around for more than a year, so context is important.

Doesn't this have more to do with Babel and less to do with Webpack? I think this originates with how Babel treats ES6 Modules differently from CommonJS, and if you were to instead do:

  const foo = require('./bar').foo

it would keep the name the same?

EDIT: https://github.com/jamietre/babel-plugin-transform-es2015-mo...

There is a better explanation with a partial solution.

It seems to me that optimizing for the 80% is exactly what they did.

The easiest buttons to get to are those at the bottom, and coincidentally they are the most common. I am guessing that is why AirDrop the ~1% case is hoisted to the top. Also, most likely, people do not use more than three to four apps to share information (Messages/Mail + 2). Giving a list of 10+ seems a little but too absurd if that is the case and makes it hard to select them. The UI seems to be pretty sufficient and even allow users themselves to optimize to their own 80% case.

I don't know to me their current UI seems to be the better option.

I don't know, I don't think my main problem was with the CLI rather how hard it was to just get something small going. In contrast, node takes all of 5 seconds to setup a small library, install dependencies, clearly list required engine, etc. Is it perfect, no way; however, it isn't very complicated either.

I don't think I'm totally alone with that sentiment either. .NET Core was a project that had pretty high expectations from the beginning, a cross-platform, sane and simpler .NET development platform (C#/F# too!).

The CLI is new to .NET Core, and .NET Framework/.NET Core are practically different platforms. Despite that, I don't get why I should struggle that much trying to get a simple empty project going.

Admittedly, I would be much better off using VS to create the project/install packages/etc but I thought I no longer needed to, hell they were providing yeoman generators for .NET Core (but they weren't always updated at the same time as a new release)!

I just took a brief look at the tutorial and it would still get me caught up on the same issues. The class library created by `dotnet new -t lib` had a different target framework than most tutorials, and short of just copying and pasting in a whole new project.json file (which changes the target framework and imports two more) I am out of luck. It's pretty confusing and tiring!

.NET Core really needs to figure out how to become somewhat accessible. I (.NET <= 4.6 developer as my day job) recently tried to setup a new project after it hit 1.0 and I was extremely disappointed.

The first step was to create a new project, okay cool. `dotnet new MyProject` -- oh wait I want it to be a class library. Let's see `dotnet --help`, hmm I don't see an option (at least not when I tried). Oh `dotnet new MyProject -t lib`, of course!

Okay lets add xUnit and xUnit-runner. There is no simple command line utilty that I saw to add them, so I have to manually edit the project.json file (wait isn't this supposed to be csproj again?). Oh wait there are weird compatibility issues between all the .NET Core versions, I have to manually go look it up on the xUnit page (https://xunit.github.io/docs/getting-started-dotnet-core.htm...). Okay I have the correct version listed, let's run my first test.

Error... Oh the created class library is targeting netstandard15, which I thought was all I needed? I need to add netcore50. Some other unexplained error occurred and I gave up for the time being. Yea maybe I could have sat through it an persevered, but why should I? Why should it all be so complicated and require two different frameworks just to get a small class library and a test project going.

Was I using it wrong? Most likely, but oh well. It was frustrating enough for me to just not continue with it. .NET Core fatigue feels more real than JavaScript fatigue.

Awesome game, my basic strategy revolved around capturing as much as possible, as fast as possible regardless of troop counts. Then just trying to confuse them by going on as many fronts as possible.

That thought requires the users to actually use new and unique passwords on every reset. If the attacker knows that your password is "Password1!!!!", it's pretty easy to guess that the next time it asks you for a password it will be "Password1!!!!!". We're all computationally lazy after all.

I feel like the notifications that X device was recently used to login from Y IP/location solve that problem in a much easier way.

In the same spirit, can we please do away with the idea of expiring passwords -- and then enforcing that we can't even re-use our last X number of passwords. It just causes locked out accounts, written down passwords or adding on one more of whatever character was at the end.

I don't think anyone thinks its economical long-term over beans/maker, just that it is cheaper than going to a store to get coffee. The convenience of having a serviceable cup of espresso in less than 30 seconds (no warm up time!) all for under a dollar makes it worth it.

As for the environment, they do have a recycling program for Nespresso pods with drop-off stations in a bunch of places. It is Nestle though so they might just be taking the recycled pods and putting them in the trash.

Apparently 12 servers were seized by French authorities. This is huge and completely surprising. I felt like What.cd would just always be here but I guess everyone felt the same about Oink as well.

They just had their nine year anniversary too, ten was so close!