skysight-inc/HackerNews huggingface dataset:
Honestly, I still feel a bit uncomfortable when hearing about something like that. When a company (especially if it's a company making a software product for "internal" use, like programming language or monitoring service) provides "support and training for a fee" I cannot help but imagine how all the documentation disappears or becomes more and more outdated, until only enterprise customers are using that stuff. Because if you are paid for training, why would you care to teach people for free, right?

Of course it's probably only my imagination, but… that's it.
I think there are two possible concerns: 1.) The interest of their clients and the larger community may not align or even directly contradict each other. For example, it has been argued that the consulting work of the OpenSSL developers has been detrimental to the quality of the software and that it may have been one factor leading to the recent security problems. 2.) The Julia developers may at some point decide not to publish future additions to Julia under an open source license. Instead they may decide to sell an "enterprise" version of Julia. I don't know how likely these things are but there is certainly plenty of precedent in the open source world showing that it's possible.
Study finds people willing to be talked into having magnetic field applied to their brain are also willing to accept false statements with little scepticism.
Disclaimer: I haven't read through the details of the language yet.

> The merits of using a functional language to describe hardware comes from the fact that combinational circuits can be directly modeled as mathematical functions and that functional languages lend themselves very well at describing and (de-)composing mathematical functions.

Whenever I read something like this, I cannot really take the language or the language designer seriously. The complexity and difficulty of hardware design is not in the combinational part, it's in the sequential (i.e., state-carrying) part of the circuit [1]. One of the major drawbacks of Verilog, SystemVerilog, and VHDL, is that successive sequential statements have to be translated manually to state machines (at least for synthesizable code – simulation code does not suffer from this restriction) [2].

[1] Source: I'm an FPGA design engineer with a computer science background.

[2] There are of course languages with an improved design, but nearly all of them are research prototypes and unsuited for non-toy/example designs. The more innovative commercial products have hardly any marketshare, because electrical engineers seem to be extremely conservative [1].
That's a fair argument, but it's a matter of trade-offs. All that bartering means that no-one's program will be actually enacted, and when things don't go well there is nobody to take the actual responsibility - including voters, because everybody can always say "well but this wasn't what the party I voted for was proposing" - even if that party got a relative majority.

Personally, I favor a system where there is a clear winner chosen by the majority of popular vote, but where minorities have a "right to representation" where they can make their voices heard in the political debate. Not easy, but possible.
I recently went to Germany for the first time and I had the opposite reaction of this jounalist, I couldn't believe how little income equality there was. There were no homeless people, no slums, no bad neighborhoods, no crime. I was in Stutgart, it's one of the safest cities, but still. There is nothing like it in America. They have some unusual things... widespread legal prostitution, and of course there was the holocaust.. and there were not many minorities there. But, there is still nothing like it in the US. So I'm not surprised that he is stunned by how things are in America.
frontier's just a marketing gimmick for a testnet. "olympic" is a marketing gimmick for a pre-testnet testnet.
How to Build a Unicorn and Walk Away with Nothing
Well, when I used VHDL back in college, I noticed that it had a really hard time with math. So for example it could do look up tables all day (basically switch commands) but if you tried to encode that logic into the kind of math we're used to in a C-based language where A = B (insert operator here) C, it fell down hard and the circuit would be so unstable that it would only run a few cycles before spinning off into some exceptional state that was nothing like we expected.

I think that's because humans have a hard time considering the ramifications of things like boundary conditions and edge cases with respect to types. So maybe we can visualize one register being added to another, but we can't intuitively extrapolate what happens when one is signed and one is unsigned, or their widths are different, or one is floating point, etc etc etc. VHDL doesn't touch on all of these edge cases very well (because for one thing they are hard!) it just does exactly what it’s told. That often flies in the face of intuition, once we’ve analyzed the circuit and seen how much we underestimated the complexity of what we were asking. In other words elegant math doesn’t always translate to simple circuits, and vice versa. So it really needs a meta language that can grapple with these subtle nuances and compile to VHDL without a lot of friction.

Probably what’s going to happen is we’ll see DSP logic (and limited subsets of it like GPU shaders/OpenCL/CUDA) and VHDL/Verilog merge into a functional concurrent language that can cover all of it. It won’t be as explicit as Rust because it will infer what the user is after but allow for overriding default assumptions. It won’t have opaque syntax either like most functional languages today. I’m thinking probably it will look more like MATLAB/Octave but have access to some of the more concise notation of Mathematica. So think Excel except having cells arranged arbitrarily in some ND space rather than 2D, and we’ll be able to specify formulas on groups of cells rather than individually, and in any language we desire that’s then compiled to Lisp and either run on distributed economy hardware or translated to a hardware description language. CλaSH probably isn’t it, but its approach and open source license is certainly a start.

Realized I didn't answer the question - different yes, but probably not different enough to be compelling for mainstream use at this point. Without having ever used it, I have concerns that circuits will still fall down or take up gratuitous chip area because handling the edge cases is one of the more complex problems to solve, and I'm not convinced that functional programming alone is enough.
Irregardless of what one may think about Ethereum as a platform, I have a lot of respect for Ethereum's hiring and retention strategy. Ethereum seems to have a knack attracting, on-boarding and deploying a deep roster of interesting individuals.

Thanks Vinay for weighing in.
I feel like an outsider.

I was curious and simply pressed twice on the button.

Only afterwards I started reading the subreddit and what it was all about. Now it feels kind of overhyped and now I feel kind of left out? It feels like everybody cares about something that I am simply .. apathic about?
There is nothing wrong with being a hired mercenary.

If you consciously attempt to hire true believers, then you will get two kinds of employees: true believers, and people who lie about true believers.

That set of employees is probably pretty small compared to the larger set of qualified employees without such a restriction. You write off a huge pool of talent.

Just because you're a mercenary doesn't mean you won't bring your all to the task at hand.

Also, consider the employee relationship from the other direction. No corporation is going to hire an employee because the corporation is a true believer in the employee's mission. That relationship is a strictly mercenary one: Can you do for us what we need you to do for us?

Full disclosure: I'm old.
Here's the actual article, and which has nothing about "mortality" or such nonsense; it's more about governmental open data programs: http://www.brookings.edu/blogs/techtank/posts/2015/04/27-red...
That kind of stuff was exactly why I stopped frequenting Reddit years ago. It became less of a place to find interesting discussions and more about engaging in mass participation in-jokes and memes.

Or maybe it was always a waste of time and I just got too old...
This is a stale and shallow story, for which I can find no additional follow-up reporting, so I flagged it.

(a) Even putting Larry Ellison aside, the notion that Oracle uses the CFAA to impede competitors is an extraordinary claim, for which no evidence has been provided, let alone extraordinary evidence. If this is true, surely someone on HN has some additional color to add to the claim? Is there a search we can do somewhere to see court cases revolving around CFAA filed by Oracle?

(b) Oracle does not in fact need the CFAA to sue people for violation of its license agreements, which is the claim other stories make for why "Silicon Valley" is resisting this reform. "Aaron's Law" does very little to change civil enforcement of terms of service agreements.

(c) In all stories about Aaron's Law, I think it's helpful to keep in mind that while the law was named in memory of Swartz, it is not in fact a particularly powerful reform to CFAA and probably would not have done much to help Swartz himself:

(1) It retains the damage-based sentence acceleration property that is the worst, most dangerous feature of CFAA, and entirely the reason Swartz wasn't assured of probation even had he been convicted.

(2) It removes ToS violations from the scope of felony CFAA violations --- something that's already happening in the federal courts, post Nosal and Drew --- but Swartz' felony charges were not over ToS violations.

(3) It doesn't modify the Wire Fraud statutes which Swartz was charged under.

(4) The felony damage threshold post-Aaron's Law is $5000 --- basically, the cost of two laptops, or 3 days IT consulting --- which virtually any charged computer crime easily clears.

You can reasonably believe any reform of CFAA is a good thing (I don't: I think once you pass something like "Aaron's Law", you then declare victory and put the reform effort to sleep for a decade), but I still think it's a good thing to remember how little this reform does to fix the real problem with CFAA. Exactly the same people we talk about on HN will be victimized in exactly the same way if the law is passed.
Or you don't do an ASIC and ship the FPGA. That's common as well (for the big manufacturers it's cheaper to do an ASIC, for the not so big, it's more common to sell the FPGA)
The reason this is mentioned (and things like the part about caching array length in your for loop) is that this tutorial was mostly written back in 2006, when things were obviously a bit different with JavaScript.

The article has gotten updates since then (check the history), but not many and not to the extent it probably needs. Not sure why it keeps getting linked.
It is true that binary logic is not the ultimate logic. However, "technically correct" vs "correct" is not a debate of whether one value of true is enough.

The word "technically" is used with "correct" as a rhetoric tool. It seems like they are attacking the truthness of the statement, but in fact they are trying to put the statement into a bigger context. So many people misuse it as such that some even understand it as an attack of the truthness of the statement.
This. Python is strongly typed but the only runtime "checking" you get is the exception raised you try an operation on an object that doesn't implement an assumed interface.

GvR supports optional type checking in Python and has written a few documents laying out its defense, so it is in the works.
The most common large leak I have seen in Android apps is created that way :
-create an object containing a strong reference to an Activity. Activity is kind of a god object in the Android framework. It can loosely be defined as a screen in the app. Views for example always contain a reference to their parent activity.

-Make a screen rotation and persist that object.

-During the rotation, the Activity reaches the end of its lifecycle and a new one is created.

-The retained object keeps a reference to its Activity. It should be collectable by the GC by now but it is not possible because of this object holding a strong reference to it. It does not stop here, the Activity almost certainly contains references to many other objects that similarly cannot be reclaimed.

It might not be very similar to the leaks encountered in c/c++ but it is very easy to create such issues in GC languages such as Java.
If you like audiobooks, EscapePod did a reading of it:

http://escapepod.org/2009/04/10/ep194-exhalation/
Very cool. Anyone know how a sphere (the globe at the end) was printed in a single immersion? Based on what I saw in the video, it seems like it would have to be a different process involving rotating the sphere as it was dipped, rather than the linear motion used for the other objects.
I'm also curious to hear why you like Flummox better than Reflux. I'm using Reflux now, and haven't hit any pain points, which I can't say the same about some of the other Flux implementations.
The TPP is an anti-free trade deal. It's mostly about strengthening intellectual property and giving multinationals their own special courts so that they can sue governments for lost profits if they implement environment/labor legislation.

Nothing very free about any of that.
To be fair, just because something is a standard doesn't mean it isn't a dumb implementation. Just by testing the programming languages on my computer, I can tell you that Python, C, and D all throw errors rather than allow it, which is the smart thing to do.
Is there even any guarantee it would be iterated in the correct order?
It would probably be good to supply a `key` property to the div to ensure that React never tries to reuse it (say, when changing from one GoogleAd to another).
I use it mainly because it defaults to http; I never took the time to actually compare the two.
I'm close to that age, and try to always be growing and improving.

I don't look back at 30yo me with disdain. I do find all of normal programmming pretty mundane and cookie cutter. Design this way or that way, pick your trade offs, investigate gotchas, think about what this code will be like in 10 years (most stuff I write has a long life, I don't do web stuff), trade off robust design with get it out the door, and so on. No biggie.

I get my challenges now with new domains - computer vision, computation, math, etc - stuff that requires reading research papers. It's fun. There is always a universe of things you won't know, you just need the humility to understand that, and I think by 30 or so most of us figure that out. If you don't you are pretty bull headed, as the compiler will tell you 1,000 times a day that you don't really know something if you don't. Most people get the clue after awhile ;)
Haskell wasn't originally designed with Monad in mind either - that came later and syntax was designed once it was proven out.
Floating point numbers in any language are inaccurate, if you're performing say, financial calculations then you can use fixed point numbers by using scaled integers. For example:

var SCALE = 100; // 0.01

var a = 0+1 * SCALE; // e.g. 2.5 would be 2+5 * SCALE
var b = 0+2 * SCALE;

if (a + b == 0+3 * SCALE) {
// this will work...
}

console.log(a / SCALE);
Exactly. There's no "there" there.
There's something you care about that I don't give two shits for.
Hard to say, it depends on what you consider better. It certainly is more concise than the equivalent Verilog (just like Haskell is more concise than pretty much any language I know). This seems especially true when you want to describe repetitive structures (such as their FIR filter).

CλaSH also has a much better type system than Verilog (again, thanks to Haskell), but if you wanted a good type system when describing hardware, you might as well just switch to VHDL ^^

My concern is with the description of state machines. You need to specify if you want a Mealy or a Moore machine, something that is usually implicit. And you're still describing the transfer function between states; CλaSH does not seem to allow you to describe your program in a structured way (such as loop until x becomes true, wait for 3 cycles, read z, while z > 0 decrement z, etc.)
Thick pices of tempered glass are vary durable and could easily outlast asphalt as a road surface. Right now the decreased efficiency makes this a non starter, but long term if solar keeps getting cheaper it may become a reasonable supplement to the power grid.

PS: Bullet resistant glass is surprisingly clear dispite how thick it is.
Whoa, the closure-based circular reference memory leak thing, is that just an IE issue or is that a language level (anti) feature? I need to know because I've very often done something like:

el$ = $('#whatever');
el$.click( function() { el$.find("a").css("color", "red"); } );
I don't think this requires storing anything on the server. That was kind of the point of the whole "store the server state in the continuation token"-thing :)

You want to store enough information in the token that you can easily reconstruct and resume the enumeration.

For example, let us say that the user asked for all comments with a score >= 5 sorted by post time. In that case you could return 100 comments, and a token that encoded something like:

{
"min_score": 5,
"sort": "post_time",
"resume_from_post_time": "2015-05-07T05:34:02Z",
}

To ensure that it is easy to resume the enumeration, the API can fudge the number of returned items so that the returned data always breaks at a nice "post_time" boundary. The goal here is to make it easy for the client to get all the data in the enumeration without implementing all this logic themselves.

True, it will only work efficiently for some types of queries, but a lot of the common queries can be reworked into something like that.
AFAIK, ethdev employees have only stated that the milestones need to reach 100% and SEPARATELY that there would be a 2 week announcement when frontier comes out (today's post, I believe)

The idea that the the milestone triggers the 2 weeks was outside speculation (though please post a link if there is evidence to the contrary I missed...)
I remember driving through the Tenderloin with my friend. We'd just drive through and observe the city life, since we were from the wine country up north a bit. Every time we went there was something new to see.

The Tenderloin was particularly dangerous and we'd usually visit there once in a blue moon. My friend and I would turn onto O'Farrell heading eastbound then take a left onto Larkin where we witnessed some of the worst things. One time we decided to park my car on Cedar, get out, and walk around. It wasn't a very smart idea. My friend got egged while we were walking south on Larkin, somewhere between Post and Geary. We also got offered some crystal meth in front of that liquor store on Geary and Larkin while casually talking to some prostitutes. There were also always a small group of prostitutes on the corner of Larkin and Sutter.

I'm not sure what it's like out there now, if it's any better or worse. Has anyone been around Larkin lately?
A scenario planning for interbank payments and Decentralized Ledger Platforms
Was the sphere inside the globe framework when it was printed? If it was merely a sphere being immersed, then perhaps a polar projection map would be able to cover all of it.
What afl-fuzz Is Bad At
You have a point - clearly my comment over-stated it - let's say that both correctness and performance were design goals.

At the time Upstart was considered "the future" ... read the comment from Scott James Remnant on this post (unfortunately there doesn't seem to be a way to link to a G+ comment directly?):

https://plus.google.com/+KaySievers/posts/C3chC26khpq

The point is that Upstart's event model was found to be flawed, and the copyright assignment policy meant that fixing Upstart was undesirable.

This explains the filesystem problem (both relevant for reliability and performance) and claims that systemd solves it but Upstart cannot:

https://plus.google.com/+LennartPoetteringTheOneAndOnly/post...
Blockchain: The next big thing
>There is something truly compelling about the button. People will engage in activities that create the illusion of control freely and willingly. This aspect of human nature could be a prank or used to take advantage of regular people. Alternatively public officials could harness this force to serve the greater good.

I pressed the button because I was too lazy to read about it first and I was curious what would happen. I was disappointed.
Check out Spent looking for change [0] cool documentary on millions of Americans who can't get a bank account. It's completely different from the article and I understand your criticism, just mentioning it because the documentary addresses the reasons a lot of people actually use services like Ace Cash over banks.

Beyond that, there's generally an information deficiency for poor people. I come from a low-income background but we always did really well because on both sides of my family there's a long tradition of higher education. So forms concerning finances, taxes, housing, education etc, wasn't a challenge.

But I can easily see how not everyone is aware of every single value offer by different banks, especially when so many of them have a history of hidden fees and when you're going to places like ACE Cash for your payday loans anyway.

I mean hell my girlfriend for example, did her Masters', bright girl, upper middle class white family... she's missed out on about $8k the past few years because she wasn't aware of all the tax rules. After I talked her through it she's now netting an additional $1.5k per year. If she'd been poor, parents illiterate, didn't know how to use the internet properly to find information, it'd be even worse. I mean I have educated friends who're in their 50s and they just never use the internet to compare pricing or deals. If two banks offered him an account with minimum balances, and he had one before and got fines because he wasn't able to keep a minimum balance, it's entirely expected that he assumes all banks are like that and goes to ACE Cash.

I fully agree with you, doesn't justify the crappy journalism. That's his job, talk to people and verify their claims and report the story. Just trying to contextualise the experiences of people the journalist probably talked to, trying to explain why they're not using banks.

And I think his point is still valid which is that some of the rioting, e.g. breaking into ACE Cash, might be linked to the predatory practices of ACE Cash that the middle class never has to deal with. Which isn't cashing checks (his mistake), but rather shit like payday loans, where a poor person earns enough, but has crappy cash flow, and has the option of payday loans which have ridiculous 5000% or 7000% interest loans on the people that can least afford them. People who put up their car for collateral lose it. And you see people who borrow $300, and end up paying $400 in interest by the time they pay off the $300 principal, when these are the same people that had to take a loan to pay the rent to avoid becoming homeless and can't afford that. In that context he wants to put the riots, which isn't that crazy.

[0] https://www.youtube.com/watch?v=YAxL4TB6pmQ
Interesting, I feel like you would like what we've done with the Cx language at Synflow. Probably the exact opposite of CλaSH, the language is sequential imperative (C-like even) and focuses on making the sequential part easier (Cx still has first class support for parallel tasks and hierarchical descriptions though). You have synchronous "for", "while", "if", this kind of thing :-)
http://cx-lang.org
Enjoy!