skysight-inc/HackerNews huggingface dataset:
I've built awsletter [1] as a quick PoC of the cloud-only web app some time ago. Last week (inspired by HN thread [2]) I've jumped into this project once again. In January Lambda was a big "wow" for me, but now I see some things that have to be taken into consideration:

1/ Fine-Grained Access Control is there [3], but it is performed on a pretty late stage of user-system interaction. When user assumed a role with some auth provider, then he/she can freely play with all AWS methods bundled in a well documented SDK [4].

2/ Codebase distribution means security distribution. You are authenticating user with FB/G+/Amz, then you have FGAC on DynamoDB table, then you need caller policy to call Lambda function remotely, then in Lambda function you need to check permissions one more time and the Lambda function have to have policy of what can be executed.

3/ In theory, Lambda functions are highly decoupled and testable (fn(payload, ctx)). But most of the time using Lambda makes sense in conjunction with other AWS services. Mocking Amazon's ecosystem isn't so easy.

4/ This model of computing may lead to oversized architectures, using "one more" AWS service to "close the loop", some strange solutions like watching/analyzing files in S3 buckets and so on...

I've seen a huge vendor lock-in from the beginning, I've been aware of potential security/architecture problems. These concerns are still valid for me. But at the same time, Lamba as a concept is still pretty exciting.

[1] https://github.com/jelz/awsletter

[2] https://news.ycombinator.com/item?id=9557298

[3] http://docs.aws.amazon.com/amazondynamodb/latest/developergu...

[4] http://docs.aws.amazon.com/AWSJavaScriptSDK/guide/browser-se...
Cracking Windows NTLM Hashes with Crackq
A real espresso pulled by a professional will run you €0.90 in Europe (unless you live in a the center of Paris, in which case you might get to spend as much as €1.50). There's usually one of those professionals within 50 yards of your home, possibly even on your walking route to work.

So it's not always even saving you money. Certainly compared to driving out of your way to a Starbucks and paying US (or god forbid, UK) prices. But like everything, it depends.

On the other hand, coffee brewed in your $10 stovetop espresso machine will run you $2.50 for a bag that lasts 2 weeks, and will add roughly four minutes to your morning coffee ritual.

I'm curious about these machines, but the thing that keeps me on the fence is that it would suddenly make coffee drinking expensive.
Site’s gone down, so here’s Google’s cache: http://webcache.googleusercontent.com/search?q=cache:http://...
LA the city and LA the county are not same thing.
+1 for generators. As a former PHP developer, I jumped into using generators that return promises in io.js (as well as es6 classes), and the code reads very much like PHP code, except all of the i/o is now asynchronous.
The Asm.js feature described in the article, a precondition for SIMD support to matter was actually invented in Mozilla. As far as I know they were also the first with SIMD in browser, helped by Intel.
For the same reason that CPUs don't operate on bignums. ALUs are fixed width, and you don't want to microcode every last instruction.

That said, the original vector processors from the '70s and '80s were kind of like what you describe. Not coincidentally, they died off with the RISC movement.
Step 1) Increase the resource limits as much as possible
Step 2) Distribute the load generator across multiple machines
Interesting. So French people are ok buying coffee for €90 a kilo to get this convenience? I can understand this only because traditionally, the French "Expresso" was guaranteed to be a watery, bitter, creama-less wish-wash.
Design a Contemporary Kitchen
Outdoor Kitchen “Must Haves”
A big problem with one-thread-per-connection is that you open yourself to slowloris-type DoS attacks.[1] Normal load (and even extreme load) is fine, but a few malicious clients can use up all of your threads and take down your server.

This is touched upon in the slides you linked to. On slide 62 (SMTP server) a point says, "Server spends a lot of time waiting for the next command (like many milliseconds)." A malicious client could send bytes very slowly, using up a thread for a much longer period of time. If the client has an async architecture, it can open multiple slow connections with little overhead. The asymmetry in resource usage can be quite staggering.

1. http://en.wikipedia.org/wiki/Slowloris_(software)
The fact that they're actively developing it and trying to best the open-source browsers in performance helps competition which is a good thing. Microsoft have actually continued to improve IE a lot since 9 in areas like web standards support which helps drive the web forward, particularly for technology-noobish people who don't install 3rd party browsers.
Haven't really shaved in years (the last time - maybe 5 years ago ?). I am just shaving the edges of my full beard.

For me throwaway razors last years.

But thank you for the tip !
Are pull requests the best way to do intra-company code reviews?
The oils in coffee beans are part of what give coffee its flavor. If the beans you prefer are oilier, then freshness of the bean/grounds will really make a difference in the taste. So for those beans, keeping the beans sealed up and only grinding what you need when you need it will result in more flavor.

That said, grinding takes time and requires frequent cleaning of the grinder (in my experience). So it's a question of modest/moderate flavor improvement vs inconvenience.
I would have expected at least a comment pointing out that Nespresso is a Nestlè brand.
I'm no treehugger boycotter, but I at least try to avoid the products of tentacular food multinationals as much as I could.
I'm not saying that everybody should and I won't ever disregard those who buy their products, but I think that the real origin of the food-based products is always a much neglected point when we talk about them in broader terms. A piece that poses itself as an Analysis of Nespresso should probably tackle this angle, too.
Famous Engine – JavaScript library for animations and interfaces
This was a great read, really enjoyed it.

I am a big fan of Nespresso. It saves me a lot of time, a little money, and consistently provides (for my tastebuds) better coffee than I can get within a 3 mile radius of where I live. (somewhere in los angeles).

I buy capsules 50 at a time, for .70c a capsule + 7 dollars shipping, no tax. So that comes to about 42 dollars total, or $0.84 per cup of coffee.

That enables me to consume 2 capsules per day for $1.68 per day, or $11.76 per week, and usually I drink less on weekends.

Coffee sold locally in the stores of high quality here tends to be a minimum of 10 dollars per pound, and normally to really "select" one I prefer, would cost around $13.00. I like to brew my coffee strong, and still would drink 2 cups of coffee per day, so this tends to run out for me about 6 days of my 7 day week.

So while its slightly cheaper for me to drink nespresso, its almost the same price.

But, with nespresso, I go from rolling out of bed to the kitchen, and within 30 seconds I have really good tasting coffee, no mess, and I can easily select the type of pour I want, capsule I want, etc. It is truly extremely convenient.

Furthermore they are an example of outstanding customer service. My machine had a malfunction once. Called them on first day, they over-nighted me a replacement machine while I sent my in for free repair. Got the original back a few days later. Hardly any downtime w/o a machine. Total cost: $0.00, and the machine wasn't even under warranty. Obviously they want to keep selling me coffee. I have no issue with that.

Finally, they offer recycling programs which work good, so I don't feel like I'm being a bad citizen of the earth by supporting them.

I see it as sort of a Spotify of coffee. You pay repeatedly one company for good service, and if it meets your needs, it is going to save you time and money if its something you do a lot. For those that are into coffee on a deeper level, is sort of those who are into music on a deeper level.

For me with regards to music, I am a bit of a control freak, I like to know what bit rate file I am playing, I like to back them up carefully and managing my music collection I invest time and have lots of pride about - so Spotify (While I generally like their service), is not for me.

The same can be said of Nespresso. If you love the entire process of making espresso, getting into the gear, and the execution of how its made and putting that kind of time into it and getting a specific kind of joy out of it, Nespresso would probably not be the right choice.

I guess I have enough hobbies, but I still really like well made espresso at home. Nespresso is right there in that intersection.
OpenResty does something similar. Code can be written synchronously, but all the network io for example happens in a non-blocking manner. The code still looks like synchronous, though - without call back hell. This doesn't come without issues as you need to change libraries to use OpenResty (Nginx) network primitives. Overall it is one of the nicest platforms I have worked with. A great webserver (Nginx) that can be programmed with a great language (Lua + LuaJIT).

At Nginx conf the Nginx developers where showing interest to bring Javascript to the platform. They said that they will take similar approach that OpenResty uses (aka no callback hell).
I'm always surprised by bad coffee at home given how easy it is to make medium quality coffee: buy a medium ground coffee from the supermarket that mentions somewhere Africa or South America, put in a cafetiere and wait 5 minutes.
I started out with flot after noticing the high cost of Highcharts. But now have been switching out flot with dimple.js and d3.js. The charts are much better with dimple/d3.
Consistency and pretty decent flavor is what Nespresso offers. But I do wonder about what sort of chemicals and magic they hide in the little pods...

Nestle doesn't have the best record when it comes to corporate profit vs care for humanity.
Polycarbonate Sheet Bible,Make You an Expert in 100 Minutes
What if an AI saves money, though? ( i.e. is cheaper than hiring a real person for a simple task )

" Never! Companies would never sacrifice principle and safety to save money! "

We'll see...
China's solar-panel industry
Mozilla needs money to function; this is true. But I am deeply disappointed that have resorted to this. I do not consider Chrome, Opera, Konqerour, or Safari to be real options for my use case, but I don't want to use a Firefox which spies on me. I don't know what I'm going to do about that.

Edit: reading further, there is clear effort to protect user's privacy. But I'm still uneasy.
Why is multinational bad food?
Bay Area is ripe for reurbanization and densification, but 1. Americans do not have the necessary skills for high density urban planning; 2. too much opposition to this from the current owners.
"The theft of wealth accumulation via property values and rent is far greater than the petty crimes of burglary and mugging that justify the police state."

>> "You are going to explain yourself, because this is quite backwards."

Source: http://www.npr.org/2015/05/14/406699264/historian-says-dont-...

There are lots of other sources for this type of information. Ta-Nehisi Coates has a comprehensive explanation in his Atlantic article "The Case for Reparations." Inflammatory title (also long), but well researched.

http://www.theatlantic.com/features/archive/2014/05/the-case...
Canvas is faster, as it basically is just a bitmap, while an SVG chart with a million points would correspond to at least a million DOM elements.
Thankfully the worst of those problems is the easiest to deal with. Put a call to GC.KeepAlive(this) at the end of your constructor. At least then you'll have some sanity in the case that the finalizer runs.
Expressos you get in Cafés are usually good, if a little bitter (and not comparable to what you can get in Italy).

But coffee people made at home used to be, in my own experience and opinion, an abomination. Never hot enough, never strong enough.

The truth is, everyone wants something different (decaf, strong, stronger, lighter...)

The miracle of Nespresso is that you can serve different cups to different people, at the same time, which is impossible with most other means of producing coffee at home (or very difficult, complex and expensive).
I bought a "real" coffee machine for me and my colleagues (Jura impressa F50 -- https://us.jura.com/en/homeproducts/machines/IMPRESSA-F50-Cl...) and, despite being a bit more complicated than a nespresso one, it cost less (despite buying pretty good coffee beans, freshly roasted, and despite the high cost of the machine), and the taste is IMHO better (but this is only a personal opinion).

The only cons: cleaning a bit the machine the morning, filling coffee beans time to time (the machine is almost entirely automatic otherwise, with an embedded grinder, etc.), filling water (water can be connected to a water pipe, however), and changing the water filter time to time.

Oh, and we can choose the quality/origin of the coffee, and (one more time) it is freshly roasted - yes, call me hipster, but I really like good coffee.
I don't understand these strawmans. The virtue of the asynchronous programming model is low-memory overhead as compared to threads AND low latency for IO-bound tasks in highly concurrent scenarios.

Request per-process/thread has all the same memory overhead implication it has always had. It's almost like the author is ignorant of the reason for node.js' success or why it was built in the first place.

Also, "callback hell" is just FUD. Nobody who does this for a living and knows what they're doing really has an issue with this. Promises solve the unreliability issues, and async/await solves the syntax complexity issues.

I'd like to see this same analysis for 1000 req concurrency measuring memory overhead and using async/await for code comparison. Cooperative multitasking will always be capable of lower latency when you know what you're doing, and async programming is lightyears simpler than multi-threaded programming.
They have to be repelled somewhere in order to be proven worthless.
Where I live, Nespresso makes a superior experience than I can find within a 3 mile radius. (fwiw, Los Angeles)

Yes, if I go to my absolute favorite coffee shop in town, it is superior to Nespresso.

But, in comparison to instant coffee (in my humble opinion), it is night and day, and its miles and miles ahead taste wise than coffee bean or star bucks.
> However, some users didn't like having to think about whether the source and destination were on the same mountpoint

That's actually a good thing, because it makes scripts more composable. Imagine you wrote a script that contains a buried mv somewhere in it, then you'd have to document this restriction all the way up to the end users of your script. If the mv command doesn't handle the mount-point-spanning case, then this functionality will have to be repeated in all scripts that use mv (which would be a disaster).

> the great many naive users celebrated the change

That's a very arrogant, unwarranted thing to say.
I have found that the biggest improvement in taste comes from using freshly roasted beans. Freshly grinding those beans comes a very close second. That is to say, freshly ground stale beans still taste stale. Pre-ground fresh beans still taste OK after a week (but won’t be suitable for an espresso machine.)

The biggest difference in taste comes from selecting specific beans and roasting them carefully. You may or may not find it an improvement. It seems most supermarket coffees are selected to have the same kinds of taste and I find them nearly universally bland. When I make coffee for other people I get a 50/50 split between those who immediately notice an enjoyable difference from supermarket coffee and those who don't care. Personally, I find instant coffee very unappealing but some people enjoy the taste of that too.

I think the closest comparison is wine. Nearly everybody likes wine and accepts that different grapes (beans) give different flavours. Most people agree that the very, very cheap wine often tastes like silver polish. The remainder may or may not then have a preference between a £15 bottle and a £5 bottle. Those who do then may or may not differentiate between specific qualities of those wines.

I'd suggest buying a bag or two from a speciality roaster such as www.hasbean.co.uk Get it pre-ground and see if you prefer the difference. If you do then consider getting a grinder for another leap in quality.

The same website has a brew guide for the moka pot – it’s a great way of making coffee and everybody uses it differently. You might enjoy experimenting with it.
I have a rhino grinder (http://coffeehit.co.uk/rhino-hand-grinder-1005) with my 3-cup in the morning. Freshly grinding it makes the coffee taste a little better but mainly it lets you keep coffee longer because beans keep longer than pre-ground coffee. When you get to the bottom of the bag the coffee is still as good as at the start.
this sounds interesting, can you elaborate?
I think the main argument in favor of Xen was that it would have a smaller attack surface for hackers than KVM. After all, Xen is a hypervisor-based solution, whereas with KVM you are running the full Linux kernel plus qemu as your host.

With that being said, there have been exploits in the Xen hypervisor. As more hardware integration gets added, dom0 starts to look a lot more like a traditional kernel.

Personally, I use kvm for all my virtual machines, since I don't want to run everything under dom0.
No,I am not a 10x developer.But I can get things done
What is wrong with just using these:
https://imgur.com/kXtDUnV
And then what? You just made coffee for 5 or 10 cups but you'll only drink one or two. And you won't throw away what's left, so you'll reheat it later, maybe twice, maybe more.

And maybe you'll find it a little too strong the second time, so you'll add a little hot water to dilute it.

And then you're well on the road to abomination.
FastCGI, really?

And Node has the equivalent of WSGI and Rack: Connect/Express middleware.
Yea personally I find freshly ground makes a massive difference. In fact I was just going to ask how they keep beans fresh in those pods...

Even when buying whole beans though it only lasts a week max before I can start to taste a big difference. You can usually tell as gasses are no longer released when pouring hot water over the freshly ground beans.
I'm an ex programmer now working as a high school teacher. I wont pretend that the flexibility possible in a school environment applies universally.

In regard to career advancement, I'm a realist. The primary effect of going part time is reduced pay. The secondary effect is slower career advancement. I'm OK with this.

Another way to frame this is to imagine how great your career advancement would be if you were a 7-day-a-weeker. Most people draw the line at 5 days. I decided to draw the line at 3.5. It's a personal decision that I haven't regretted for a minute.
And, Nespresso usually fixes all problems for free. After all, they are in the coffee business just as equally or more than the coffee machine business. They have absolutely satisfying customer service skills.
Same applies to all eastern European countries, Japan and China. People start prepping when they're still in middle school. Most of the winning team members are former IOI gold medalists.
Here's what's wrong: https://news.ycombinator.com/item?id=9586941
Get a full fake REST API with zero coding in less than 30 seconds (seriously)
>Cons: Larger memory footprint

The more annoying con is lack of shared memory. A single process can be much less complex when it doesn't have to worry about messaging systems and off process caching.
In Sinhala, it's "Samanalaya".
> Is there any production-level C code which relies on (int+bool, and other semantically meaningless arithmetic) working?

Yes. I have seen enterprise code making interesting tricks to covert handle values into pointers, back in the late 90's.
Ask HN: What is the most effective spam filter for Apple Mail
Marking mails as spam in Apple Mail is utterly useless. Is there a really good spam filter for Apple mail?
I have yet to see some proof that 10x developers exist. I watched some videos of pair programming, and they are the closest thing I have seen to some sort of mastery of the stack. I think they are a myth.
There are very small cafetière's available, including single-serving ones.
True, "real" modern super automatics coffee machines are a lot cheaper in the long run (cheap raw coffee) and you have to clean them only as often as a Nespresso machine. (Considering no milk processing is involved, which means care-taking in all cases). It seems like they convinced the public to install a vending machine on the customers expense. It's like Coca/Pepsi Cola convince the public to install a Cola vending machine at their homes.
The article uses the very loaded phrase "ethnic cleansing". Wikipedia says:

The crimes committed during an ethnic cleansing
are similar to those of genocide, but while
genocide includes an intent at complete or
partial destruction of the target group, ethnic
cleansing may involve murder only to the point
of mobilizing the target group out of the
territory. Hence there may be varied degrees of
mass murder in an ethnic cleansing, often
subsiding when the target group appears to be
leaving the desired territory, while during
genocide the mass murder is ubiquitous and
constant throughout the process, continuing
even while the target group tries to flee.

So, "ethnic cleansing" can involve:

crimes
similar to those of genocide
varied degrees of mass murder

Way inappropriate, way over the top. "ethnic cleansing" doesn't explicitly say Hitler, but it's pretty darn close to it. In this case the article starts with Godwin's law, rather than a discussion degenerating into using it.

Having said that, I can't believe how poorly mobile home residents are treated in this country. We had a similar situation in Wilsonville Oregon. It made financial sense to build apartments, so multiple trailer parks were closed. Despite them being "mobile homes", they're not that easy to move and frequently other parks won't accept homes that are more than a few years old.

Mobile home residents are often screwed, badly, in this country.
Is it in better hands now? What are the long term implications of this? There are promises made there that it will not affect the day-to-day running of DN, but that is rarely the case with these things. New owners can not resist flexing their muscles
where are you getting $2.50 bag of coffee? decent single origin seems to be ~$16-20 for 12 oz these days
I agree that there are already many ways to DoS the system-- for example, the age-old fork bomb. But that is not a good reason to add more flaws. People are working on ways to fix the old flaws, such as cgroups.

I don't think a ulimit would be very effective here at preventing denial-of-service. Let's say I set it to 100... I can just have my 100 children each spawn and hold on to 100 children of their own, and so on and so forth. If I just go with a bigger process ID space all these headaches go away, plus existing software works without modification.