skysight-inc/HackerNews huggingface dataset:
The last one really just prevents the (immediate) death scenario. The something you know could presumably be why they're torturing you in the first place, caveats about the effectiveness of torture notwithstanding.
Why is that offensive? How would you phrase it correctly?
"The Play framework works with Java"...yeah so does Akka, Spark, etc but my experience is that it isn't first class support and many things are just tacked on for a Java API to underlying Scala constructs.

"slim down the amount of required tooling"...how? You can't even properly navigate the Play source code (e.g. "go to reference") without a Scala plugin (IntelliJ or Eclipse). And the libraries they use are still gonna carry around the big 'ol Scala runtime with them.
I'm not expert in any of this stuff, but reading that slide, I was kind of getting the impression that existential types and higher-kinded types are being unified, in the grand scheme of Dotty exploiting theoretical equivalences of previously separated concepts. Same with the type parameter/member thing. I think the idea is that syntax will support both options, as seen with the analogous introduction of the value parameter syntax for traits, but the underlying implementation will be abstract members. This seems like it will make writing type level code or interop code much simpler, because there's only one underlying implementation to worry about. But re-reading your comment, I think you agree with that benefit. Do you know why abstract members were chosen as the underlying implementation? Are they more general?

I agree that native HList functionality within tuples and case classes would be really huge for practical programming. It's a huge pain to abstractly define transformations over families of classes. It's awesome that Shapeless works, but more native support within the language could maybe help remove some of the challenge of actually using Shapeless.
I disagree about Ted being wrong.

A key phrase in Ted's article is Hopefully the simulacrum retains the essence of the problem.

What Tedbleed, as your article calls it, demonstrates is a bug similar to Heartbleed: reuse of a buffer in a memory-safe language is susceptible to leakage of secrets.

While I might answer the question are Rust’s memory safety features being oversold by uninformed zealots?, no I don't think so, but I would suggest that thinking that memory safety ends all security issues is a not good plan.

The key is Unless you venture into the (explicitly demarcated) unsafe portion of Rust, you will not see memory exposure vulnerabilities like Heartbleed: the language does not prevent this. Perhaps your post will stimulate Ted to go further with his example and write an erroneous complete TLS stack in Rust, showing how it too can do Heartbleed. Perhaps you agree that this can be done.

Among the scariest mass vulnerabilities relating to total information disclosure, the Padding Oracle Attack, the BEAST attack, the compression flaw CRIME, none have to do with memory safety of languages. Rust there would not have helped one whit.

Memory safety is just one issue in writing secure code.

Edit: typo
The advice I champion to anyone out of college is for them to commit themselves to quitting whatever job they get out of college within 18 months, preferably with a big company.

Then do it again, preferably with a small company.

After that, do whatver you want. You've learned from the scars of veterans with the big boys, you've dug trenches with the new kids, now the world is your oyster.

Go choose your fate.
I initially attributed this kind of omission as originating from laziness or just not knowing how to copy-and-paste* into their email client. Now I think it actually stems from a much bigger problem: the average computer user's inability to understand cause-and-effect, and their belief that there is just "the error", with a corresponding "the solution", because they think there is only one reason (and not really a real "reason", as it seems to be only understood by "neckbeards") that a computer error could occur.

Thus, it's not laziness, just something that logically follows from the erroneous assumption that there is only one kind of error, and thus, a competent programmer should automatically know the one solution to it.

* In terms of people not being able to copy-and-paste...just because they can do it in Word doesn't mean they realize that function exists in other apps. Take Google's finding that 90% of users didn't know how to use Ctrl-F (http://www.theatlantic.com/technology/archive/2011/08/crazy-...)....just a couple days ago, in the final week of my programming class, one of my students was amazed when I did a Ctrl-F in the terminal.
The keyboard/menu one, in times past, used to just scale the text. It was, quite literally, Text Zoom. Then at some point Safari changed it to be just "Zoom", and made it scale the entire page. But you're right, it doesn't actually scale the width of the document, which means it reflows when you go larger.

I think the current behavior of keyboard/menu Zoom is meant just as an aid to people with poor eyesight who can't read small text. The change from Text Zoom to Zoom is just because increasing the text without increasing anything else can cause layout issues, so it increases everything. But it keeps the document width the same because scrolling horizontally to read text sucks.

Meanwhile pinch-to-zoom scales everything because it acts just like iOS, and because pinch-to-zoom isn't supposed to ever reflow anything (as that would be inconsistent with pinch-to-zoom everywhere else). So pinch-to-zoom is useful when you want to quickly zoom in on an element, as opposed to increasing the text size of the entire page.

All that said, it's still interesting that keyboard/menu Zoom doesn't handle layer scaling correctly. I'm guessing this is because the Zoom is not, in fact, scaling the whole page. It's reflowing. I could imagine that if it simply scaled all transforms you might get some odd behavior in various cases where it escapes the bounds of the document. That said, the current observed behavior is even stranger. It's hard to imagine what exactly is going on with that transform as I adjust the keyboard/mouse Zoom.
incidentally, I think Edison's test is trying to measure curiosity

This test is ahead of its time and it is perfectly consistent with what we understand about Thomas Edison. I doubt anyone memorized the answers to this test - he is looking for signs of creativity.

Edison's formula: Invention is going to come from trying 99 dead ends to find the 1% that works.
Andreas Rossberg comments a bit on the differences between ML modules and Scala objects/traits here [0].

[0] http://stackoverflow.com/questions/23006951/encoding-standar...
Yes lint does exist since 1979 and Ritchie remarks in his notes that it was already a need back then.

The problem got worse when C dialects started to appear outside UNIX without Lint. Or the compiler vendors selling it separately of the compiler.

The problem with languages that trust the developer is that they are based on a set of false premises, namely:

- the team is composed from top skill developers

- the team never changes

- everyone knows the whole code base

Which are all false in the majority of corporations.
10 Points for Server Maintenance
Show HN: slack-irc – Connect Slack and IRC channels
Which one is the Chilean company?
This seems like a surprising deviation from their traditional stance of "throwing more people at a problem is never an acceptable answer" (which is almost literally their justification for off-loading the bulk of their support to an online manual and a "users helping users" forum with "actual humans" being a scarce resource even paying customers are usually allowed to tap into).
> One issue I have with it. I don't think it's complex, but I think people are not spending the right time learning it. People learn the subset of features they like and stay with it, and because there are so many ways to skin a cat with it, everyone have their own style. It could have benefit from the concept that other languages have of "there is always one best way to do things".

I think that's the dark side of having both the OO side and the FP side working well.

I'm not sure if I want something like OCaml, where everyone tells you to just ignore the OO part of the language.

---

I think the talk mentioned all the right things, and shows that the people in charge listen and address issues raised by the community.

Also, just look at the productivity. Which other language can claim that people work on a redesigned compiler, a new IR, a shared bytecode backend, and a rewritten macro engine at the same time, in addition to developing and evolving the current language, compiler and library?
You don't; and most models don't even try because the causes behind market crashes are often complex, interdependent relationships that often aren't fully understood until after the crash has happened. But you can use other tools to perform a catastrophic risk analysis that basically asks questions like "Let's say our assumptions change; what does this model look like in a world where every mortgage-backed security drops to junk status?".

Problem is, the companies selling said securities have no interest in identifying the downside. Nor are they legally obligated to since they are selling these products to "professional investors" who ostensibly should know better.
In a capitalist predatory economy and society like ours public resources and assets should almost never be used for private purposes

So, in non-capitalist economies, they should? :)

I find your rant misguided. Parking spaces are public resources being used for private benefits, i.e., for car owners. As a member of the "inferior" class of transit and foot travelers, I see no reason why your private use trumps any other.
In the case of argv though on main it is defined to be null terminated on argv[argc] according to the standard. Assuming the pointers are the same size though what I said will work but is bad practice.

> sizeof( char* ) == sizeof( char* * )

True, I forgot that different architectures/compilers can produce different pointer sizes. Thanks!
It's a PR victory for KP that the media generally refers to this as the "Ellen Pao Trial" rather than the "Kleiner Perkins Trial"
True... and to be fair, I also don't watch television, use any of the popular social networks other than Github, I don't have a cell phone, and my default position on anything uttered by a politician is that it is a lie.

My comment was more an indictment of mainstream news at large, so if I inappropriately cast aspersions on a good publication, I apologize.
Having grown up in the ecosphere of Lethbridge, I never heard that construction until I came back east. (We would frequently watch "Front Page Challenge", one of the longer-running TV programs anywhere.)
Whether you're a troll or actually serious you've given yourself a very appropriate handle/name. What value did you hope to add to this discussion with this inaccurate rant?
It's stated in the prompt that the pitch could be for a "new business idea, solution or product". That seems clearly inclusive of existing businesses regardless of age. i.e. A 5 year old business releasing a new product. Sounds like fair game to me.
Show HN: CoRM – Lightweight Contact Relationship Management with API Access
Yeah, that's what I would guess. Many academics simply have no interest in running a business (often because they've tried and found that engineering is more fun).
The trick in this case is for the project to have enough momentum so that you want to try and stay in sync with it and not maintain a bunch of your own changes.

> And frequently they won't, leading to fragmentation. This happened a lot before the GPL became de rigeur.

What time frame are we talking about? My experience was that the GPL probably was at its most popular in the late 90ies, but has gradually declined since then. Most things these days - Rails, Node, Android, Go off the top of my head - seem to have more permissive license.

People are a lot more connected now than even 20 years ago, so contributing back is also much easier. Also, more people get open source, at least for infrastructure type projects.
The fact that it's such a small thing that they're testing is what makes the large reaction so interesting. They were trying to determine what part of the brain is involved in detecting an object, but just that tiny bit of awareness seems to be widely spread out.
Or if your device manufacturer decides it's time to store that data on their cloud and forces you to use their proprietary security tools. Good times.
Wouldn't the Humble Bundle store fall in that category?
Maybe when io.js and node.js merge :)
Han Solo and Bayesian Priors
Webinar OnDemand: Hosting Alternatives You May Not Know About
Not the best medium for teaching such kinds of skills. I showed it to my friend who is a beginner and he got frustrated after the first layer.
Yeah, but even if nobody in a field blames everything on something, as long as many people have a propensity to investigate if something was because of something and publish, then it ends up looking to the uninitiated that the field is blaming everything on something even when it isn't.
A lot of users have been trained by viewing years of essentially meaningless error messages: "Program has encountered a problem and needs to close", "Error!" or something which actually useful, but its by no means understandable to non-programmers.

Maybe people complaining about not being sent errors should make the errors themselves more approachable.
Googler comments on BlackBerry's new tablet
>you can expect the output of a decompiler to resemble minified code.

I doubt that. When your C++ is ran through LLVM's optimizer it's structurally changed to a huge degree.
Just because the collective assumes Valentine's Day to be of importance has no bearing on my interactions. In fact, my SO and I do NOT celebrate Valentine's day. At all.

My SO also goes out drinking with other men. Without me. In private.

Why bring any of this up? Because I do not condemn expressions of affection just because the collective makes some childish assumption that grown adults must feel one emotion at a time per person.

Plot twist: You can feel affection for someone and not desire sexual activity from them in the same exact way you can feel bloodthirsty rage for someone and not desire to kill them. Yes, I know, it's a mind-blowing concept... the idea of people having complex and nuanced relationships instead of easily codified stateful interactions. (Once again, programmer bias trying to dictate how life should be)

Because we must all strive to make life easier for faceless administrators to conduct their soulless policies. /s
If you like it someone else might. And submitting it spares the you trouble of maintaining a fork when you upgrade. But making it a project service might be hard. So feel free to not submit it. Alternatively you could write a small blog post about it, maybe it inspires someone else to contribute.
Watsi is one, presumably.
you can certainly do it as DIYer but to ameliorate it and commercialize it you are going to deal with patenting. SLA patents just recently started to expire and this has already created an explosion of new developments. see here for instance http://qz.com/106483/3d-printing-will-explode-in-2014-thanks...

you may also want to check to formlabs last year, and their litigation on the patenting.
Suspicious Code Fragments in CoreCLR by PVS-Studio
Eric Schmidt Repeatedly Interrupts Female US CTO at SXSW
Snapchat success came by fraud. They lied their audience about the self destruction of their messages.
You don't need to only worry about your device being compromised, your biometric credentials are being leaked by your mere existence.

Before long, I can imagine someone being able to build facial models capable of fooling recognition systems using only a few source images. Your finger prints are everywhere. Iris would be a bit harder, for now, but potentially possible with an image of high enough resolution.
Obama: Disturbing That Climate Change Denier Runs Senate Environmental Committee
During the 2001-2003 bust, rents fell quite a bit along 101 and the south bay. For an average apartment, from ~4,000 to ~2,500. High end apartments fell from ~8,000 to ~3,500
Show HN: A St Patrick's Day Promo:  Soylent Green Is Keto
YouTube glitch allows music label giant to ‘hijack’ videos
Not gonna lie, under threat of severe physical damage or death, I'd give away everything I know. Granted, I don't have access to nuclear weapons or anything, but I wouldn't care who gets effed up as long as I'm intact...
Introducing the Uber Request Endpoint
> Clumping together widely separate areas of law like copyright, trademark, patent, and trade secrets and casting it as something related to physical property is great if you want to deceive people, but very bad if your intent is to educate and help people understand the aforementioned areas of law.

Ignoring the structure of actually related areas of law, as ditching intellectual property as a category would be doing, is great if you want to deceive people, but very bad if your intent is to educate and help people understand the law.

IP is a subcategory of intangible personal property, which is a subcategory of personal property, which is a subcategory of property. There are legal principles that are generally applicable to property, others that apply to personal (as opposed to real) property, others that apply to intangible (as opposed to tangible) personal property, etc.

IP isn't particularly closely related to "physical property" (which isn't a particularly useful category); nor does the term suggest that it is. Real property is in a separate branch from IP at the highest level of categorization of property rights, and tangible personal property is at the next level down. It is more closely related to things like debts and choses in action (rights to sue), which are, while not IP, also intangible personal property.
Scala's clearly doomed...if the comments here hold water that is. Got a chuckle over a claim in this thread that OCaml and Haskell compile times are "lightning fast" compared to Scala -- wow, maybe OCaml, but Haskell, I mean, seriously, even Haskellers will raise their eyebrows with that claim...
Thanks for providing a real world example!

But I think the data can be interpreted in several ways.

If home prices are rising while apartments are being constructed, that doesn't have mean the price increase is caused by the construction.

For one thing, these units won't exist until 2016¹, so supply hasn't actually increased. It could also be that the area needs 1000 units to offset the increased demand. Or, as you imply, that the higher level of services make the area more attractive, rather than the added units themselves.

I would like to see actual studies by real economists to change my thoughts on this.

¹ http://www.mercurynews.com/business/ci_27717752/facebook-flo...
Sam Altman “Super Impressed” with Waterloo Region
> . i heard iOS provides warnings atleast.

Not necessarily. If you blatantly disregards their terms, then your app will be rejected for sure. Now, if the issue is more nuanced, then it could take some time.

Source: I developed an app that, among other things, could let people know about DIU checkpoints (not in the US, mind you). It survived for more than a year in the store, only getting an email from Apple when we changed it from free (with ads) to a paid app, returning more revenue in a month than the past months put together (which nevertheless was enough to pay the monthly office rent).

Instead of engaging Apple, we decided to pull the app ourselves from the store.

We did get an email from an actual person, instead of getting the app pulled from the store with no explanation. I also guess that, had we decided to discuss things with Apple, that we could have reached some sort of agreement. We'll never know, but that's what I inferred from the tone of the email (surprisingly friendly, mind you).
It is "Companies with a " (above) black " founder" (below).

Though as I understand it, African-American is the most current terminology.
Yes, it does still slice into layers. Those layers were demonstrated in their paper as small as 1µm in thickness.

From the paper:

"Because CLIP is continuous, the refresh rate of projected images can be increased without altering print speed, ultimately allowing for smooth 3D objects with no model slicing artifacts."

"elevated at print speeds of 500 mm/hour"
I remember him! He spoke at Hack the North, and brought a YC panel to the event as well!
Undrtone – share and discover music you love
The Denouncer
The code that led to the Heartbleed vulnerability was checked in in December 2011. The first pre-Alpha release of Rust was in January 2012 (source: Wikipaedia for both). Would technology from the future have prevented it, is the actual question, and the answer should be obvious...
> The city already owns the parking spots. No need to condemn anything. Just change the use.

OK, I'll be more explicit: I don't see any evidence that parking lots are special here. It sounds like you could build a park in the place of just about anything else and get the same benefit. It's not clear that this has anything to do with parking lots per se.

> It isn't anti-car propaganda to point out that huge swaths of valuable public real estate are dedicated to providing free storage for empty cars, and to suggest that there are other uses that would be more beneficial to more people.

How is that not an expression of anti-car sentiment? Are you not suggesting making it less convenient to drive cars?
There are some really really desperate people in this thread who keep posting this "the sky is falling!!!" type of claim in every Scala-related submission. :-)
Unfortunate or not, my point was that it did help proliferate the idea of open source software, even of different licenses.

Of course it is a "what would have happened if" kind of argument. But that is just my opinion.

In other words, I am saying, BSD/MIT/etc type licensed software would not have proliferated as much if GNU/GPL wasn't there from the start. From RMS's point of view, it was probably not an intended consequence, I agree.
I originally wrote this when I worked at Facebook. The intended audience (who were submitting these reports at the time) was professional software engineers.
3 reasons Snapchat should buy Meerkat
> Apple tells you before your app goes live.

Look at the situation with PCalc and Transmit. Both apps which offered a killer feature, got approved by review and even featured by the editorial team, then pulled after having been on the front page of the App Store.
As a maker of a food product that falls into the new food category of "soylents" we constantly get questions about the relationship between the name and the movie. We thought we'd have some fun with it and sell a limited-edition version that was actually green.

We decided to make two versions, one that plays up the dystopian nature of the film and another that plays up the Irish. Aside from a slightly different label on the bag, they're the same product.
Mars One is a scam
Interesting thought. In many cases I've had its the first case (not knowing how to copy and paste).

But this reasoning makes a lot of sense for the ones I get from people that definitely know copy-and-paste. For these folks, I get a screenshot and/or text of the error but still the "its broken" without much else.
> Civil lawsuits != prosecution.

Yes, the act of initiating legal action is prosecution, whether the action is civil or criminal. We don't call the people doing that act "the prosecution" in a civil case, but the act itself is still prosecution.