skysight-inc/HackerNews huggingface dataset:
Andy, I just learned about your Genesis project, and it's great to see people pushing towards collaborative DAWs. I've been doing detailed planning for my own vision for a collaborative DAW for years now, though various other projects have kept distracting me from giving it enough coding time to get it off the ground!

I'm curious how you're thinking of solving latency & disconnection issues between participants. It looks like you're representing things as a sequential list of transactions, and immutable transactions are definitely the starting point for everything I've considered! The question is: what happens if multiple people send each other conflicting transactions at the same time? Google Wave solved this by enforcing a single server-side ordering of all events, and making sure that all transactions would be accepted using Operational Transformation even if they occurred out of order. Without OT, you may have cases where Alice makes a change, only to have it invalidated and essentially erased by Bob's change that may have "won" on the server side. And while OT may be largely "solved" for text content, it doesn't seem well-studied for music or other timeline-based content.

As an alternative, source control manages to get along fine without automated conflict resolution/OT, since we're willing to dive into merge conflicts and resolve things ourselves. So theoretically, you could create "Git for Music" and drive that from your app. But what's the UI equivalent of version control in a DAW? What, exactly, does a "diff" look like in musical notation? And how do you make it unobtrusive to non-coder musicians?

All very interesting problems, and it's always great to have multiple innovators in this space! Would be happy to connect offline if you'd like.
>I don't find it surprising that so many distributed databases fail at ensuring consistency; it's a very hard problem

It's not hard — it's slow. Sending reads and writes through Paxos or Raft gives you sequential consistency. But not surprisingly, touching a quorum of nodes for every operation is too slow to be practical for many workloads.

And that's usually fine — most data aren't bank account balances.
We need to fix the problems of racism and sexism, which means we shouldn't be excluding anyone from any program or job based solely upon their race or sex. Programs like this fly in the face of that goal and ensure that these problems will continue in perpetuity.
I like the idea of a Universal Basic Income but running the numbers is eye opening:

£1,500 ~= $2,274

$2,274/person/mo * 12 mo/yr * 300,000,000 people = $8,186,400,000,000/yr. $8 trillion a year to provide that level of UBI to all 300,000,000ish Americans.

Not an inconsequential amount of money!
The Titanic was dubbed unsinkable by the press, not by Harland and Wolff nor the White Star Line.

Driving a liner full speed into a stationary iceberg is not really the fault of nature any more than having a tree jump out in front of your car :-)

The Titanic was actually one of the safest designs afloat in her time.
New Private Cloud Option
class and __type__ are no keywords here. They are just the names chosen for those attributes/methods.

I was just pointing out that what you considered unreasonable syntax was actually pretty common syntax. That the function/method names could be better, I agree. But that's an entirely different matter.
Which argument can be seen as a roadblock thrown up to avoid having to do anything. "I can't fix this problem because no solution is perfect!"

That said, I agree the recruitment could be of any underserved youth with potential, and not compromise the usefulness.
So what are you calling 'dream'?

Your seem to be saying people don't even want that any more.

If so, what's the problem?
Majority of the programmers I work with in the valley are Indians and Asians. It's been that way for years.

I'd venture a bet that my silicon valley co-workers are much more diverse than the NY Times writers who love to preach about diversity.

Quick check:

- NYT Executive Leadership: 90% white
- NYT Board of Directors: 92% white
- NYT Opinion Writers: 91% white

Media has a diversity problem!!
That's the questions that I ask myself every time I see "Call me maybe" posts. Is there a good solution?
If only there was a compelling reason to use eclipse...

I was quite an active proponent of eclipse a few years ago and even implemented a small plugin, which was quite a hassle to be honest, but I was happy with eclipse.

Then came a time when eclipse didn't do a single thing better than IDEA. Especially PHPStorm beat eclipse's PDT by miles, and I wasn't even doing heavy Java work back then. So the only advantage was the price.

I haven't looked at eclipse in quite a while - I have an IDEA license I don't have to pay for, so even this is gone.

So I wish eclipse all the best, but I didn't have the impression that contributing was in any way easy back then, maybe it is now. And I also hope the quality of the language plugins picks up - but for now I don't see myself using it in the near future.
I think the takeaway, about a dozen posts back, was that your clustered database is shit and you shouldn't rely on it. Sharding at the client level may be the best approach. Sometimes the old ways are best.
Wait a second. Nasa is the US government. This manual is therefore not protected by copyright, at least not within the US. And they are charging 79$? They can do so, but 79 seems a little high given that once anyone gets their hands on it they can in turn sell their own copies again. How much for the pdf?
Yep. Try also with https://github.com/globalcitizen/taoup
This script is better than most of the episodes on the show, Blake should seriously take up screen writing.
RSS/Atom would be ideal for me in particular, but I'm not sure if this would be the majority's preference. An email would be just fine. Both would be superb.

This is a bit of an issue I have with GC as a whole. Some products don't even have release notes. And I have to check a bunch of different release notes pages for each service, unless something gets announced on the blog.

I really want to stay on top of this stuff, but it's pretty difficult to right now.
Almost a complete rip of the original Motherboard article from the start of this year: http://motherboard.vice.com/read/soviet-arcade-museum
I'm still looking for a open source version of this so I can create a nice collection of algorithm problems.
Yes, I absolutely agree. I'm sure I've been guilty of it (I'd rid them if I noticed of course) but it's a pretty sloppy-looking project. Not holding my breath for it to replace vim.
I don't think either of us understands that experiment. Fortunately, actual engineers have proven that bicycles don't stay upright from gyroscopic effects. [0] [1] If you want to experiment, try riding a bike that can't be turned. You might want to wear a helmet for that one.

[0] http://www2.eng.cam.ac.uk/~hemh/gyrobike.htm

[1] https://www.youtube.com/watch?v=YdtE3aIUhbU
I hear she worked with Charles Babbage: Studmuffin of computing. Really, Nature?
All good points, but my delusions rely on one piece of magic: determined people from disadvantaged backgrounds can become successful anyway.

This won't all be fixed in 15 years, but it will start to be fixed just by numbers. Yes, the current numbers are awful, but they must get better in the future. If they don't get better, the US will end up as 90% poor and 10% CEOs. Many racial-cultural ghettos throughout the country do exist and drive down the future potential of millions of children, but everybody won't stay there forever. Maybe it only takes a few breakthrough tech successes to set the stage—people to look up to, not "smart is bad" culture.

(Also, with current numbers, there are isolated pockets. Sure baltimore is 65% black, but that doesn't put pressure on employee availability (employers can relocate people from elsewhere). But when the entire country is 80% mixed hispanic-white-black-chinese in 100 years, employees must come from society as a whole somewhere.)

It is a generational problem and it will take another one to three generations to fully be considered a non-issue anymore. (Assuming, at some point, the US decides to invest in education and children and growth again instead of choking off all avenues of social mobility as have been routine for the past dozen years.)
Ahem. "What I got was something security related to MariaDB."
>I never quite understood what makes people that make 100's of thousands of dollars per year so cheap that they would balk at paying a few hundred $ for their main tool of choice.

You make an assumption that we developers make hundreds of thousands of dollars a year. That may be true in some places and for some fortunate people but it's not true everywhere.

Besides, the main complaint I see here is that the subscription model makes all your code assets hostage to JetBrains' fortunes, since the moment they go out of existence all the software you depend on stops working. People are not balking at the thought of paying a few hundred dollars for a tool - they are, in fact, asking for the opportunity to do just that.
Even more important, 305 bytes is only a small part of a packet. Much less chance of a packet needing retransmitted on a low/poor quality connection.
Well, here's the thing, if the level it is set at leads to output-reducing withdrawal from the workforce more than output-increasing effects, then it also leads to inflation which drives price levels up and drives people back into the workforce [0] -- its self-limiting.

The bigger problem is that the economy might not yet be able to sustain a level at which UBI isn't substantially worse for the neediest populations than existing support programs -- increasing capacity through automation will get us there eventually, but its far from clear we're there now.

Which is why, while I think UBI is a great idea to adopt and phase in, I don't think a big-bang short-term conversion is a good idea.

[0] unless it is pegged to inflation, then if its set initially in a bad place, its stuck there. So, if you are going to index it rather than manually adjust it, don't index it to inflation, index it to output/revenue measures, not price levels.
Zookeeper came out looking good:

https://aphyr.com/posts/291-call-me-maybe-zookeeper
This again.

I'm sure everyone would agree that in an ideal world we would be working to simply pluck racism out of the air and get rid of it once and for all. How do you propose we do that?

The reality is that this program is doing something achievable to address the effects of racism. No, it isn't directly tackling the causes of it. There is no reason why we cannot do both.

Proposing this "all or nothing" approach almost always ends up with "nothing", and it's almost always proposed by people who do not see the benefit of these programs.

Edit: just noticed your edit. Being that hyperbolic does you no favours.
This looks a lot like Mesos. But of course they will never admit that. Amazon and open source, a long history.
I recently had to use Eclipse again, after 5+ years of Emacs mostly coding sessions, and boy it was tough. I kept thinking it's just one IDE, and others are better, thinking about IntelliJ. Heh.

ps: people, take a look at Emacs, it really is nice, and only needs 8MB cough
>This seems an unreasonable standard to apply to anything. Hardly any policy is a Pareto improvement. Applying such a tough standard amounts to very strong status quo bias.

Sorry I wasn't clear. I wasn't making that statement as a "justification" for not implementing UBI. It was about how it's being "sold" politically.

Personally, if I were to push for UBI, I'd tell people that the only realistic way we can afford it is if we all agree to take a hit in standard-of-living. I don't have irrefutable proof but that's what I think will have to happen. However, it doesn't necessarily we shouldn't do it. With the mass effects of citizens avoiding low-wage jobs, maybe it's better for society that Walmart is open 6 days a week 9am to 7pm instead of 24/7 and for Amazon-Prime to scale back to 1-week delivery instead of 2-day, etc, etc. Or Amazon-Prime costs $199/year instead of $99.

If sophisticated dynamic equations show that middle & upper class will have to "suffer" a bit to provide the entire country a UBI... fine. But sell it that way to them and let everyone have open eyes going into it. I'm skeptical that we can fund UBI just by renaming existing govt assistance programs so that it ends up being virtually "free" to taxpayers.
In Miami, the population is 60% hispanic, and i would guess at least 40% of the programmers here are hispanic.
When is YC going to fund a startup which will run a school which uses the techniques of the class featured in this article[0] found on HN today[1]? Note that this is the first comment on either this YC post or the wired one. Do this and FUCKING CHANGE THE WORLD. [please excuse the all-caps, but this could FUCKING CHANGE THE WORLD, couldn't it?]

[0] http://www.wired.com/2013/10/free-thinkers/

[1] https://news.ycombinator.com/item?id=10169442
The point is to receive peer review from domain experts (including those in academia). But aphyr already gets that anyway :P
Can we call such a clown convention a "company"? It seems they lack a degree of seriousness that one might expect from a firm in which investors have invested capital.
Lot of interesting links in this post.
3 year old issue on Bitbucket, no response so far
Zippers clicked for me when I realized that they are a way to traverse immutable data structures by allocating like crazy. For example, you can have a pair of lists, "left" and "right". To "move left", you create a new pair of lists: the left list minus one element, and the right list plus one element. The same idea also works for traversing other data structures, like trees.
my silicon valley co-workers are much more diverse

Twitter had a neat turn of phrase in their recent diversity document: "these new goals focus on increasing the overall representation of women and underrepresented minorities"

underrepresented. You don't count as a minority if there's already too many of you being successful.
While the cause remains unknown there's research showing that OCD may in part be triggered by infection:
http://www.nimh.nih.gov/health/publications/pandas/index.sht...
FoundationDB... which is probably one of the reasons that they were acquired. Aphyr mentions them at the end of the article:

"You might adopt a different database–though since Galera is the first distributed SQL system I’ve analyzed, and FoundationDB disapparated, I’m not sure what to recommend yet."
If you're interested in this idea where derivatives form one-hole contexts then you might also be interested in derivative parsers: http://matt.might.net/papers/might2011derivatives.pdf
To say it is a generational thing doesn't mean it is always the current young generation, it means it is specific generation(s), i.e. generation X, millenials, etc.
The rear-engine design was pioneered in the 1950s by Sud Aviation with the SE 210 Caravelle. It was very successful for its time....

https://en.wikipedia.org/wiki/Sud_Aviation_Caravelle
Yes, it was called "pinball".
Of course, the Elligator and related mappings allow for (a subset of) valid curve points to be mapped to indistinguishable bit strings, which is very handy in some protocols. A backdoor merchant using Elligator 2, or Elligator Squared, in this particular setup wouldn't be detectable.
Thanks!

Looks like bingo with my first search (a google for 'rrrs mailing list rational fraction float'):

https://groups.csail.mit.edu/mac/ftpdir/scheme-mail/HTML/rrr...

I've loved lisp's power since I first encountered it in the early 80s and also admired the great care put in to various aspects of Common Lisp (which is mentioned as the foundation for scheme's number decisions). Great stuff and still very relevant.

:)
Another way of looking at it that's nice is that they "rewire the pointers". If a LL looks a bit like this

[1] -> [2] -> [3] -> [4] -> []

where the [n] location actually represents a data pointer then stepping into the zipper rearranges some of these...

[1] <- [2] -> [3] -> [4] -> []
[1] <- [2] <- [3] -> [4] -> []

To be a bit more explicit we should talk about where "we" are

* -> [1] -> [2] -> [3] -> [4] -> []
[1] <- * -> [2] -> [3] -> [4] -> []
[1] <- [2] <- * -> [3] -> [4] -> []

etc etc.
I always thought "less" preceded mass nouns and "fewer" preceded count nouns. "less acres" feels slightly sloppy to me. But we all understood what was meant, so maybe it doesn't matter.
We've been using EC2 Container Service for a few months now and at first glance it appears great but we've ran into quite a few problems using it:

- You can only bind 1 port and 1 ELB to a service. This means, for example, if you have nginx listening on port 80 and 443 you need to manually configure the ELB and can't take advantage of automatically generated port numbers on the host (So you basically can only have 1 HTTP(s) server on a host)

- There is no way to cleanly decommission a host from a cluster. Say if you want to reboot or replace a server in the cluster you can't tell ECS to drain connections from the ELB and move the containers off the host

- Unable to specify rules for which hosts services should run on. For example you can't say that the service needs to make sure it has instances in X AZs or don't run multiple instances of the same service on the same host.

- No easy way to implement any kind of service discovery, you have to roll this yourself or set up loads of internal ELBs as a sort of service discovery.

- Worst of all the ecs-agent is very buggy. It has releases where it just keeps crashing [1] and leaving untracked running containers just hanging around to an issue where they released a new version with a newer docker library that changed how it handled certain parameters causing our entire cluster to fail until they hot fixed it with a change to how their API sent data to the client.

We're currently looking at alternatives for our docker infrastructure.

[1]: https://github.com/aws/amazon-ecs-agent/issues/156
Adobe CEO avoids a question about why its priced $1400 more in Australia
Wireless networks usually exhibit bursty packet loss on top of a base packet loss rate, which poses challenges for streaming (and everything else). QUIC uses forward error correction in some cases to mitigate this: https://www.chromium.org/quic

One model widely used for simulating packet loss on wireless networks is the Gilbert-Elliot model, http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.90.... which is supported by http://info.iet.unipi.it/~luigi/dummynet/ if you want to play with this yourself.
Asian-Americans simply don't count when it comes to racial diversity. If tech companies are not diverse because the vast majority of workers are white and Asian, isn't the NBA similarly non-diverse because the vast majority of players are black and white? Would there be a similar uproar about the lack of racial diversity in tech if the representation of Asian-Americans and blacks working in tech were reversed? I very much doubt it.
Like $3000 a month? Not enough to live in a major city, but you should be comfortable living somewhere in the US. Major city livin' is in short supply and is thus a luxury--- we'll never be able to have a high enough UBI for us all to live in NYC.
On termination of cartel agreement, they had to immediately boost wages. A cartel doesn't have to be 100% effective to be, nonetheless, effective. And they had just re-priced options in early 2009.
Genesis looks super interesting. After going through the first posts I have a lot to say about it - I will probably write to you, or post a rant somewhere. But I will say this right away: I'm unlikely to ever use it, unless some holes are poked into the walled garden that you're planning. Digital musicians are hackers, and a quick glance at the history of DAWs should reveal the paramountcy of free modularity.
The Notebook – Fighting Scene (PARODY)
I'm a bit new to this, so not quite sure why you say Kuebernetes has its own load balancer. E.g. you can run Kubernetes on AWS. If you do then it uses ELB for load balancing.
Not sure exactly what you meant, but an app that does sentiment analysis on your text conversations on your phone would be pretty cool.

It wouldn't just detect potential betrayal; it could show all kinds of cool (but useless) stuff.
Thinking about the one single scenario where it goes on forever, as if it were an event unto itself, is misleading imo -- by that reasoning, in that scenario, you would win an infinite amount even if you were only getting paid $1 on each flip. But the EV is clearly not infinite for that game. The increasingly huge rare payouts are essential to the EV calc.
> But surely similar things would happen?

The difference between a UBI and an income guarantee like the Speenhamland system is that the latter is a means-tested program that eliminates the marginal benefit of additional work and requires more administration, while the former, because it is unconditional, providing a fixed benefit regardless of outside income, has less administration and preserves the marginal benefit of additional work.

> Let's say your wage is 30K per year. On Jan 1 a UBI of 12K per year is to be instated. What would happen to your wage in a year? Personally, given that most all businesses want us to be loyal to them with no loyalty returned to us, my guess would be that you are let go and someone would be hired to do your job for 20K per year.

If they could get someone to provide the value you do for $20K now, they would. If you think UBI makes that more possible, you have to believe that it also makes it just as much more possible that you'd be able to get someone else's former 30K job for 20K of job income, which, with a 12K UBI, gives you a 6.67% increase in total income.
You don't seem to understand that various kinds of arcade games existed before video games. Go to the article and scroll down to the “Winter Hunt” and ”Basketball” machines.
The title is a reference to Babbage's own appellation for Lovelace as "the Enchantress of Numbers".
I can see how it could feel that way, but look at this this way:

Problem: your ratio of X's to Y's is too low due to long-term, subtle discrimination. You have finite resources to solve the problem.

Potential solution #1: put money into training more X's and Y's indiscriminately.

Upside: no exclusion, seems "fair".

Downside: while it may improve your X:Y ratio, it does so very slowly and with a lot of that training money "wasted" on something that wasn't really your goal. It also doesn't really work if it's basically the same as your old training programs, because whatever subtle discrimination occurred there will just occur here too. Also, as soon as you stop, the existing discriminatory training systems will put the ratio right back where it was.

Potential solution #2: put money into just training X's.

Upside: very targeted, and effects are much faster. Can balance whatever subtle discrimination lead to the problem in the first place, like by placing training centres near where the X's live or exploiting other things they may have in common. May solve the problem more permanently by increasing the number of X's with the better knowledge of how to train future X's.

Downside: can feel "unfair" to Y's.

The fact is, if you want to increase your X:Y ratio, you'll get here faster and cheaper via X+1:Y rather than X+1:Y+1.