skysight-inc/HackerNews huggingface dataset:
Not really true. Yesterday I was trying to debug resource-loading issues. In any normal programming language, you can just strace it and you'll see where the program is doing I/O and you can figure out where it's trying to load files from. But if everything is in a jar, you don't see any OS-level I/O happening when Java tries to load something, so you have to invent all-new tools just to figure things out. When you switch to Java you throw away 40 years of UNIX for a bunch of private methods implemented by summer interns at Sun 20 years ago. The third-party libraries are fine, but the core is not.

Also type erasure.
Gradiente will start smartphone line IPHONE in Brazil
While this looks cool, what the obsession with making new Graphite dashboards recently? Everyone seems to be making one.
Since Scala is also a JVM language, from scalability perspective can someone expand on what it offers that Java, or any other JVM language, doesn't.

I'm not asking about language semantics since I believe that to be a personal preference, rather scalability and performance.
Or strace -p whatever, or gdb -p whatever.

Shockingly, attaching to running processes has been a feature of UNIX for decades.
This is actually kind of a big deal. Have you sent this info to any tech blogs?
http://dev.pocoo.org/~mitsuhiko/didntknow.pdf

"Custom Ducks" and "Cached Properties" terrify me a bit. Not Pythonic (as in, not easily readable).

But on the whole, I take that back. I was looking through your talks and realized that was the only place I got that feeling, and also found http://dev.pocoo.org/~mitsuhiko/badideas.pdf which takes a stand against magic.

Edit: I still think arguments would be better (more explicit/readable) than globals (request, etc.) in Flask, but it's your module and I know you've considered the reasons to make it that way. And globals don't exactly qualify as magic.
My mom cooked from scratch. She fried chicken, put lots of butter in the mashed potatoes, put butter in vegetables, always had gravy, etc. But "it was ok because they're low-sodium low-cholesterol heart-healthy home-cooked recipes".

Just cooking from scratch by itself doesn't solve the problem. You have to ensure you're using healthy ingredients.
This confused me for a minute but I think I get it now -- it's referring to a response with zero length, not a response of two quote characters right?
I was under the impression that they were rejecting fart apps and flashlight apps and the like.
Manufacturing and supply chain is one of the most complicated processes that occurs at businesses, by and large. We're talking about logistics to get your stuff to the warehouse, storing said inventory, monitoring inventory levels to know when to order, manufacturing goods that take time, then storing the finished goods until they can be shipped, and finally, sending them on their way. I've seen companies from all walks of life, and manufacturing goods is by far the most complicated process I've ever had to dive into.

People think it's easy because it's simple on the small scale. There's nothing I know of that's harder to scale than manufacturing operations.
'Big Pit' National Coal Museum Now Powered by Solar Panels
Several downvotes as this is some bizarro statement?

Is it because we as geeks we haven't seen the very same thing play out several times already?

Or because people in HN genuinely believe that Instagram really INTENDED to sell people's photos without their permission or money?

HN has really hit rock bottom...
Not to mention, they presumably need to get paid.
The hardest thing about legalese: trying to convey intent and write something specific at the same time. The intent may be in the category of “don’t be evil”, but the user never knows. And while it is easy to say “well, just stop using the service”, the impact of networks is that it makes it less realistic to use another service. Just another signal that we live in a “Caveat User” world…
Judges and juries can see through blatant abuses and rule that the contract did not cover that use.

I've seen this observation mentioned a few times on HN and it seems quite right. The letter of the law may say this or that, but ultimately it comes down to some form of the giggle test. You have to imagine a judge saying, "You didn't really think that's what the law|contract meant, did you?"

For example, people trying to avoid penalties for unauthorized distribution of copyrighted material by claiming they own the copyright on certain large integers or are merely passing _numbers_ around, not movies or songs.

With the boilerplate TOS there may be all sorts of things that one could imagine are allowed but I'm pretty sure Instagram's (i.e. Facebook's) lawyers thought that the original phrasing would not be sufficient to clearly allow them to do what they wanted to do, so it was changed.
The Virtual Memory Toucher
Could be it was because facebook wanted to focus and capture other important stuff like - facebook comment plugin , facebook like button, facebook share plugin ...

They always knew that replicating craiglist can be done any day later.
No, I mean the right Armin. See the other reply though. I only got that feeling once when looking through his talks, and I otherwise take that sentiment back.
I won't go so far as to call this unethical, but this is basic social engineering. You're tricking somebody into violating the normal "flow" of external communications into the company. This may end up hurting that person if, say, they are identified as the reason that some random person schmoozed their way onto the phone with a busy higher-up.
Ha! They missed one :-)
Hi, OP here. We love feedback on our posts, so happy to hear your thoughts on conflicting conclusions - either here or at contact@survata.com. Thanks.
Deploy your Heroku application through Beanstalk
Yes, exactly like that.

CNN and other media outlets report that Facebook reverted their TOS update and went back to using the previous one. 'The site posted a brief message on users' home pages that said it was returning to its previous "Terms of Use" policy "while we resolve the issues that people have raised."

http://tech.slashdot.org/story/09/02/18/1310239/facebook-rev...

New to the interwebs?
My data is just fine, thank you.

>There is nothing positive about guns; your group illusion of "self-protection" is quickly diminish by the fact that legal guns many times end up in the hands of the criminals, provoking accidents or in hands of mentally unqualified people... so even 1 death is enough.

The idea that "even 1 death is enough" to take away a basic human right is just plain idiotic. How many times have assaults and murders been deterred by a gun? That doesn't show up in homicide statistics, does it?
I had the same argument over here: http://news.ycombinator.com/item?id=4938204

Would you consider Windows as a monopoly? There are alternatives.. If your answer is 'No', the EU seems to disagree with you (and might on the FB case, we'll see). If your answer is 'Yes', where's the difference?
This is the worst thing they found in facebook's term of use? Really?
These companies do all of the above deliberately until there is no viable competition left. This is a situation they competely created over several years.

It's not surprising people are upset when the mass trial period ends and there are no competitors left to move to.
Simple Social Media "Share" Buttons
I don't agree with equating cross cutting concerns with the purpose of "roles" in DCI. These are not mutually exclusive ideas. DCI is seems almost exclusively concerned with changes in domain state. That is, organizing the interactions between actors in the domain model into contexts which, generally speaking, result in changes in state.

I find, DCI doesn't say much with regards to how you query that state or present it to the user. I don't need a context or role to query data. Concerns do seem to provide some really nice ways to "DRY" things up on that end.

Certainly you can use concerns to deal with interaction/role type issues, but then they really aren't all that "cross-cutting" they tend to be specific to a particular use case or scenario. In which case I think there are better options. DCI is one, domain services are another. But hey, if Concerns work as your golden hammer by all means. I have some doubts.

I don't see this as a DCI vs. Concerns argument. However, if you want to argue it isn't possible to do DCI well in Ruby (extend sucks, yadda, yadda, yadda) go right ahead.
Some people can eat anything and naturally regulate their caloric intake.

Other people can eat whole foods (meat, vegetables, fruits, etc.) and keep a stable weight.

Others have an appetite that isn't well linked to their caloric intake and try to use external markers to guide what they should eat.

As long as it works, go for it.
Looking at it more, it seems pretty easy, but perhaps consider that your audience might only have a cursory knowledge of their Graphite implementation. Maybe point to a couple of the important fields in dashboards.js, like graphite_url and the bits inside metrics?
>Is there any evidence that building 100 megabit pipes to non dense metro areas is actually profitable exercise for ISP's right now?

That's not at all what your parent is saying.

>I'm not sure the majority of Americans would even opt in to this service as they might not have a need for anything more than a basic cable modem connection at $20/month.

Lack of the option (due to few competitors) is the point, not whether or not it would be useful to a majority of Americans.

Additionally, "640K is more memory than anyone will ever need" - Bill Gates
This is for authentication when you're not logged in. But that aside, yes, I'd would too prefer named cards. I don't think of my cards by their numbers quite as much as their issuers.
FTA:

1.7.1 How to read this specification

This specification should be read like all other specifications. First, it should be read cover-to-cover, multiple times. Then, it should be read backwards at least once. Then it should be read by picking random sections from the contents list and following all the cross-references.
Version x.0 in open source software implies "this is ready for production"

I've never really had this impression before. Do you think people would have been holding off on using a library like this because it was at 0.14 before? I'm curious where this impression comes from.
That would work, unless you were determined to avoid Apple (I'm not)
In all likelihood, the conclusion will be #3. If government agencies feel compelled to do such studies beforehand from now on, then change has occurred in the right direction.
One can only imagine the level class action lawsuit if they were to find them detrimental to peoples health.
Wunderlist 2 Goes Native On All Platforms
If the model gets big, it's an indication that it is doing too much work. You want every class in your system to have a single well-defined role--if the classes are getting huge it might mean that there's code duplication or it might mean that the class is taking on too much work.

In this context, DHH is pointing out that rather than duplicating the code for tagging and the code for managing visibility and the code for managing a Dropbox account on each class that needs these things you can use a Concern to abstract out each of those groups of functionality and then apply them case-by-case with one line of code. It's a pretty neat trick and used appropriately it looks like it would really help keep the model layer trimmed down to its bare essentials.
Yes, I'm not sure that Kickstarter's missed deadline rate is any higher than anywhere else. Humans almost universally underestimate complex tasks, a phenomenon so widely known there is a particular phrase for it: the Planning Fallacy (http://en.wikipedia.org/wiki/Planning_fallacy). The question should really be, why would anyone expect Kickstarter projects to meet their deadlines?
985 Beta Invites Left Get your APPMOB invite now
Think of it as increasing the signal-to-noise ratio by $70K?
Are you doing lots of redeploys? Can you alter your workflow to just restart the server process instead?
Federal Trade Commission to data brokers: Show us your data
Open source alternatives to Instagram
Do you have links available for your bug reports?
While it's an interesting idea, it's not just possible with today's tech.

Black rhinos are only one subspecies, white rhinos are just as threatened by poaching and there are around 20 000 of those, so you're looking at around 25 000 rhinos in Africa.

You'd need at least three UAVs per rhino, one on station at any given time, one ready to replace it once its endurance runs out and one spare in case something happens to one of the other two. Then there's the problem of actually tracking the rhino 24x7, through night and bad weather, while ensuring that the base station and recovery team stays close.

You'd also need skilled pilots / operators to keep the UAV on station and interpret what's on the screen and, once again, you'd need more than one per rhino to enable 24x7 shifts.

Once you factor in the number of UAVs, the dispersed recovery and handling teams and the need for skilled operators, you could potentially be speaking of 75 000 UAVs and a similar number of teams and pilots / operators. Even if we assume that UAVs with sufficient endurance for this task could be reduced to $500 000 each, that still results in a capital cost of nearly $40 billion, over and above the sure-to-be-mammoth operating costs. So it's not feasible.

A better approach is to fit each rhino with a GPS tracker, which is being done, and to use ranger patrols augmented by technology like UAVs and ground radar to attempt to spot poachers moving in the parks. That's why this is where SANParks and others are focusing their attention and resources.
The Sunday Startup
The National Acadamy of the Sciences is not just some random "independent" group. Of course, the article states that it's still unclear as to whether they will take more data, or simply review existing studies. Likely, they will do a review first to decide if further study is necessary (e.g., if the methodology used in prior studies was, in fact, unsound). In any case, having unaffiliated scientists consider the issue is a step in the right direction.
Thanks for that, got my comparison wrong. My apologies.
>If you were still interested in having a fruitful conversation you could had ask what data do I have to confirm Americas wouldn't make successful revolutionaries; or at least you would try to explain me why citizens against and pro-government would't kill each other.

As if you could actually know something like that better than I.

>But instead you decided to call me names.

Which was entirely appropriate after your last comment.

And yes, I'm aware of the genesis of drug traffickers in Columbia. Your condescending attempt at a "history lesson" isn't required.
> It took off, raising vastly more money than they anticipated -- and obliterating the original production plans and timeline

I wonder if Kickstarter allowed projects to set a maximum number of backers (or a funding cap), if projects would take advantage of it.

Honestly, such a move wouldn't help Kickstarter (fewer fees to collect), so I'd have my doubts that such an option would be offered. Even if it were, I wonder how many teams are aware enough of their limits to take advantage of such an option.
No it's not. If you book it under "Unplanned expenditures" then you're not insured. If you try to determine your risk in such a way that you can budget a fixed sum for coverage and reasonably expect not to exceed it (ie. not an unplanned expenditure) in the same way an insurance company would do it, they you're insured.
The New Firebase Security API
That's the same age as Perl 5.
I'm glad that you collected this kind of statistical data - it's important, because caloric intake can really be misjudged (even if you are using a calculator).

I'd probably ask that you provide the data, so a better statistical analysis can be done on it than what was provided, and also that, in the future, you present statistics more scientifically. As others have noted, there seems to be some discrepancies with your reported calorie counts and what companies have reported - you should also address those.
Yes, it will be in all these places. But in for example Sweden that is more of a convenience rather than of any actual significance. What is really used is your national identity number.

I virtually never write my entire name in forms. I bet I could use a pseudonym or fake name and nobody would care as long as the identity number is there. The only exception is passports where my legal name is important.
Not really. Obviously, preservation of energy must hold, but body weight isn't just a function of calorie intake because metabolism is regulated by hormones, which affect the rate of calorie burn and fat tissue formation. Human metabolism is far from being completely understood.
The Commodore 64
I wonder when the Pebble Watch will finally ship. As far as I know, the team has stopped posting expected ship dates.
Ah yes, that would be why three national telcos sued my local electric utility when they started exploring the idea of doing a city-wide public access fiber network where any number of competing ISPs would provide transit and support but the physical cable plant would be owned by the municipality. So now ten-years later it's the same cable/telco duopoly as it is everywhere else in the US; speeds suck and are asymmetric, and we have these "bandwidth transfer caps", which wouldn't exist if the playing field were level.

It's not hyperbole, if anything I'm understating the damage that has been done to the public to feed entrenched private interests.
This article is FUD. Complete nonesense really. Continuous integration had nothing to do with the Gmail outage (which mind you was just for the web app, no emails were lost and since my phone/desktop clients kept working I only knew Gmail was down because of Twitter).

> The search giant reported that it conducted an update of its load-balancing software from 8:45 a.m. to 9:13 a.m. U.S. West Coast time, and after the problems were detected it managed to quickly roll back the buggy code. But this didn’t stop some people from questioning why Google would roll out a software update during peak e-mail hours on the West Coast.

Perhaps because the update wasn't to Gmail, it was to the load balancing system? It's not uncommon to have issues arise in load balancing while under load. I'd say the engineers did a good job dealing with the problem all things considered--load balancing issues are notoriously tricky.
Android mobiles hit by spamming computer virus
Marcion's program was to excise the judging Yahweh from what we now know as the New Testament, leaving only the loving, forgiving Jesus. It was born out of an apparent desire to edit the religion into something he found palatable.

My larger point is that the religion of unconditional love has already been invented, as has Paul's detour. An appreciation for this history would save a student from a lot of intellectual blind alleys.

And aptly, it is Marcion's failure to grapple with Christianity's continuity with Judaism, to appreciate the history and deal with its paradoxes, that led him into heresy. His heresy led him all the way to publishing a version of the Bible with the parts he didn't like cut out.

Paul's post here felt very similar to me.
2012: The year Rubyists learned to stop worrying and love threads
Agreed. Exactly my problem with the catch all argument that all these concerns will go away if we buy the service.
How Starting A Business Made Me Broke
They're understandably under heavy load. It worked fine, when I tried it, though.
You know the Irish Data Protection Commissioner force Facebook to make some privacy related changes, right?
in a nutshell: gmail went down for 18 minutes because of continuous deployment[citation needed], which they explain a bit of the rationale for. Then they come back to the headline, basically saying that as more companies do continuous deployment, we might see more breakages, though probably briefer.

Not the most focused article, but kind of cool that they wrote about such a thing. Though the headline feels like pure linkbait.

They also missed my personal favorite attribute of continuous deployment: isolated problems. If you deploy 10 features and something breaks, unless they're completely orthogonal you now have more than one place to look/person to ask/team to deal with. If you deploy one and it breaks, you know where the problem lies.
Cornell researchers release OpenReplica, a toolkit for replication in the cloud
Yeah, that's kind of what I was alluding to with my "that tells us something too" comment. We can't assume that markets are "efficient" in the general case, but we can say that there must be some point at which the ratio of the concentration of gold (or platinum, etc.) in landfills to that in mines will prove irresistible to someone talented enough to harvest it. Long before that point, recyclers will figure out which connectors they want to buy at a premium. They already are quite keen to purchase old catalytic converters.

WRT letting nanomachines loose outside the landfill, I'm not actually as concerned about the "gray goo" scenario as some are. It has seldom been a problem in other engineering endeavors that mechanisms have required too little maintenance, and so in a sense all of our machines face an uphill battle. One could probably make a thermodynamic argument that a given volume of soil contains only so much potential energy, and then calculate how much gold can be moved with that. Then "if the gold concentration is below this value, do nothing" could be a good safety rule to design in.
The question is asking about YC/techstar partners, not founders.
Ok. To me, that sounds kind of like what CSS does for HTML -- less code, faster page loading, that sort of thing. Is that about right?

Thanks.
Unlikely. Considering how the new Data Protection Directive being written goes further than the current one, and seems to be targetting various things Facebook does (like having all it's EU stuff in Ireland). It seems like a lot of EU law is on the side of privacy and data protection.