skysight-inc/HackerNews huggingface dataset:
If I may give my take on this:

Federated: Provide a little better anonymity as many operations are done behind firewalls/NAT/VPNs rather than using public data and point to point sockets. However it has a single point of failure for each nodes and switching from one federated node to another is either problematic or impossible. The federated node can also fall and shut down at anytime.

Distributed: Doesn't required accounts. Base identity on cryptography rather than a web service. It use point to point or point to proxy to point communication. Some meta datas, such who talk to who, when and for how much time are available to anyone (cough...) who can tap on ISP connection metadatas. This service is more robust and cannot really be taken down in ways that cannot be fixed.

Ring support both federated SIP networks and the distributed DHT network (and a mix of both).

(the anonymity problem can be mitigated using tor like onion routing for the negotiation, but it is unrealistic to use real time communication over an onion network. [D]DOS attacks can be handled in a variety of ways, so are DHT trashing ones, bittorrent is still alive and well).
It depends on what those columns are. For this case multiple columns are probably better, but if you're trying to search over multiple document types a JSON column could be more flexible.
This Bitcoin Simulator Is an Insane Trip Through Cryptocurrency Hell
It's insane because it covers a very narrow range of topics. We make people doctors after 8 years of study, only a few of which involve actual practice.
Probably because there is more than just nigiri on the menu... and there is more than one kind of fish, etc.
Hi Javier,

> There are tons of people that will be glad to collaborate and participate in such meetups here in Cuba.

Sure... we know there're tons of people interested. That's exactly the main reason to organize an event like this...

Any kind of collaboration is really appreciated. Drop us a line whenever you want...
There should be an xkcd about people overusing that xkcd in every possible context
What would he really need say about io.js at this point? Him stepping down means he's no longer involved in the decision. And any comment from him might color the debate, and/or limit the next lead's ability to bring their own opinion.
Had the very same idea. To be able to read this, I opened a TextEdit window where I copy&pasted the questions.
I think its mostly the fact that technology caught up and became cheap enough. Battery technology, motor technology (brushless), electronics (ESC's which control the motors, and the onboard boards with gyros and accelerometers) and many other things.

I'd attribute it the most to battery technology. As part of the hobby myself, Ni-Cad batteries were the go-to's. But they were crappy. Li-Pos have existed before, but the thing about multi-rotors and flying in general is it doesn't need a high capacity, but a high output rate, which we can get now.
I guess that's what indieweb is all about. /s
I don't see how that is relevant. The author's complaint isn't that there are too many languages, but that none of them are good enough.
The problem with flow-based programming is the debugging. If that if you put a breakpoint on some message-processing code in a thread and examine the backtrace, it ends in up in some "read next message and dispatch" loop. Thereafter, the trail runs cold. Where did the incorrect message come from? Oh, the "left neighbor". What's it doing now? Something no longer related to what it was doing when that message was produced; it's sitting in its own loop, blocked on receiving the next message.

Spaghetti algorithms emerge. Some crucial behavior is implemented using ad-hoc messages involving several distant threads. "If we inject this new message type here, then massage it here, then finally process it over there, we can achieve such and such a scenario". The message is then like the data equivalent of a rampant goto, not to mention that the plumbing is a giant global variable.

The approach is good for eliminating deadlocks, though. No module calls into another module where it has to acquire that module's locks.
Instead of forcing a person thru a decade of trials in the dojo, and promoting those that manage to learn how to pass the trials one way or another - we took the successful people and had them teach how to be successful.

It's so much more efficient this way. It might still take 5 years of training for someone to have masterful control over her or his body, but so long as they obey and work hard, success will come eventually.

These aren't the stone ages, where we'd grasp around in the dark for effective self-defense techniques. The road to success is long and hard, but it's well-paved and clearly marked today. We have maps, and also Search & Rescue standing by to catch people as they wander out of the Rye field of success.
Do you also expect engineers to drop like flies as they get older so that their numbers would become more in line with the number of available managerial positions? Cause that sounds like a serious flaw with your thinking.
> The LXC team are trying to move the needle with LXD. It uses unprivileged containers by default (non root users can run containers, this is not capabilities drop) multi host management with a REST api so you can query the LXD daemon for container orchestration across hosts and live migration. These are big steps forward and they really do need the support of the community. They have been doing this for 7 years and is thanks to then containers exist.

I'm always surprised when people omit to point out that "the LXC team" is basically Canonical, the corporate sponsor behind Ubuntu (including the kernel bits).

People love to bash on the company, it'd be nice to acknowledge the achievements as well :)

Full disclaimer: I'm a Canonical employee. I hope that doesn't come out as a corporate shill, I genuinely love LXD.
Strings are going to be bad anyway because there's a high chance you're hitting a cache miss just to get access to the heap allocated string data.

Yes, only the histogram pass has random writes and if you pick your bucket size appropriately(like I mentioned above) then the surface area for those random writes can land within a cache line or two.

Summing the histograms are a very nice linear read/write pass.
Definitely a valid point. I updated the wording a bit already. It was definitely not meant for a larger audience in its current form.
True, should have mentioned that (edited it in). Relatively certain it was afterwards.
Given 3-5 year tenure of a typical employee at a typical tech company, this is less than expected attrition at a company.

It is not inconceivable that anyone who wanted to leave the company between now and the end of the year took this.
I'm one of the "gurus" - feel free to ask more questions here (see bio for more background)
Similar, similar, only if you don't look too closely: what about break and continue? They are usually supported by native foreach construct but are difficult to build with macros..
I completely agree. It's just a process. The people trying to say that it takes years are just glorifying old standards
"The ability to make good decisions regarding people represents one of the last reliable sources of competitive advantage, since very few organizations are very good at it." ~Peter Drucker
The author really likes to mention how very true and factually accurate this story is.
HHVM going into a performance lockdown for two weeks
For warehouse associates. This doesn't apply to engineers.
I wonder what percentage of the 14% are existing managers that perhaps can't or don't want to move on to different roles?
This looks pretty cool!

It's one of those things where I'm like, Ah why didn't I not think of that :D!
There are some pretty good proposals about spam. So far it hasn't been a problem, but it's good to have tools in place.
There seems to be a very high overlap between the prepper 'community' (I hesitate to use the term about such self-avowed rugged individualists) and those who anticipate a race war, war with Islam, or some similarly catastrophic political event. There are many people who still have a chip on their shoulder about the civil war, and seem to yearn for a different social order.
"reported that women entrepreneurs make realistic projections and align words with actions. Women are more likely to meet their milestones and are more frank when mistakes happen"

This right here is a generalization. I thought generalizations were bad?
The further differentiation of belt rank is an Americanization of the art - it's equivalent to handing out Participant medals once every few months.

When I learned, we had 9 ranks. Today, most studios have more than 27, so every form and throw and move has its own test and belt. It's maddening, but it's not unlike unit testing. (Should we apply principles of software development to martial arts education?)
American here. Everyone I know calls McDonald's a restaurant. They may choose not to eat there for health or ideological reasons, but everyone agrees that it is a restaurant, and has been a restaurant since its inception decades ago.
Warning: Misleading title. It is talking about what happens to your physical body, something everybody already knows what happens after you die, though perhaps not to that level of detail. NOTHING TO SEE HERE, move along now.
People are also working on that. The full stack needs an upgrade, and it's nice to see that happening across the board.

It's more than blog + XFN + pingbacks. The combination of technologies really does allow for decentralized social activities (not just replies), potentially in real-time.

If you don't want to mess with a server, we started an indieweb platform at https://withknown.com. You can always take all your data and move to your own server later on.
Well, to be fair, Flask is kind of crappy and does anyone even use Tornado anymore?

I always just set up a project myself using Werkzeug, in the era of WSGI, almost all of the heavy lifting for web apps is done automatically and outside of your application anyway.
Small MySQL feature request ignored for 9 years
I'm in SF but have Cuban roots. If anyone is interested in chatting drop me a line.
A few mockups or screenshots would have helped me immensely to understand this "next gen text-based-programming killer", that is ironically described exclusively in plaintext. In my head, ideas range from visual programming language to programmable spreadsheet, with no clear picture of even how the language looks.

I'm so confused...
15 tech jobs that pay over $100,000
The indieweb is a social web where everyone runs their own profile, on their own (sub)domain, potentially on their own servers - while being able to talk to their friends as easily as they could on Facebook or Twitter.

All based on open technologies, rough consensus, user-centered design and running code, rather than endless mailing lists and technical debate.
> This query takes about 50ms!

Would be useful to know how many rows you had in the table (?)
Will it have e.g. unsigned floating point types or it's the same old match-to-hardware approach?

PS: might be a false dychotomy but then next-gen is an exaggeration.
Pro tips:

* Be courteous when offering constructive criticism (that means, for example, don't swear at people)

* Often it's not the project owners posting things on HN - many projects aren't necessarily ready for public consumption when they end up on here

* This doesn't even appear to be a "product". It's an open source project that seems to have been recently put out there

Absolutely typical that this is the top rated comment. Hacker News, you SUCK.
Corporate loyalty is a two-way street.

In medieval times, the vassal paid homage and swore fealty in a commendation ceremony, and the lord granted him a fief. The vassal had a duty to aid his lord, and the lord had a duty to protect his vassal. The vassal gave loyalty, and got a secure income in return. It was a permanent relationship. To dissolve it, you had to use an axe, rather than a pink slip.

Corporate loyalty died when management culture forgot that the company owes duties to its employees in addition to its shareholders. Defined benefit pensions became defined contribution retirement plans. Then the employer contribution disappeared. Health insurance plans dwindled from all medical expenses paid to you paying 80% of the premium, $30 co-pays at every turn, and deductibles that are met midway through the twelfth month of the plan fiscal year, then reset. Training programs evaporated. Severance packages got smaller, or vanished. Even the amount of notice I get whenever permanent layoffs are to occur has become days, rather than months.

So there are no more loyal vassals. We are all mercenaries now. I'll start sending out resumes if I so much as notice that the building has a new janitor.

H. R. tells new hires:
"How great it is to work here!"
Give me cash, not lies.

If corporate loyalty is dead, it is because corporations have killed it.
Ok, no sweat off my back. ¯\_(ツ)_/¯
What would merging with io.js mean?

Is there any reason to use node over io.js for a new project? Are the reasons not to switch to io.js for an old project the same reasons that node will not merge io.js?
Sure, albeit that describes everything.
I tried the windows version. It hung after I entered a username.
Question: Have you and your co-founders each executed an agreement assigning all right, title and interest in and to any IP to the company? If so, the code isn't yours to take, and it makes no sense for your co-founders to give away any IP rights (copyrights and potential patent rights).

Your narrative tends to cast your partners as distracted by other business ventures, it seems that you are searching for a way to disengage. If they were savvy, they would not agree to your proposal. The code base is company property (that is if you have completed the process of corporate formation). You might believe that your contribution in teh form of code disproportionately exceeds your co-founders contributions. Had you actually formed a company, assigned the IP to the company, determined the value of each founders contributions in addition to any IP (cash, equipment, space, expertise, time commitments) you would be able to foresee how your co-founders will respond to your proposal.

IF I'm incorrect and you have filed articles of incorporation, drafted bylaws, and executed agreements issuing founders stock, then I suggest you consult with your outside counsel (you know, the attorney(s) who drafted all those agreements for you) to help ensure you don't f_ck up the operations of your "profitable home services business".

Suggest you ask yourself the following "why am I walking away from a profitable business? Especially when I committed to building that business with my co-founders?"

Maybe you have realized you don't get along and so you want out. In that case, offer to purchase the code base, and agree to payment terms that provides enough runway for you to generate revenue and pay for the code base over time.

Finally, you wouldn't be "giving" equity to your co-founders. You would be issuing equity in exchange for the "home services company" assigning all right, title and interest in and to the code base and any associated IP to your new company. If your platform is adding value, it makes little sense for them to agree to an assignment. Instead, they should offer to license it to your new company for royalties, equity, and continued development.

Summum Bonum.
The buyout is so that you get mediocre, financially motivated people to leave. The idea is that you give them enough cash that they can be reasonably sure they will find another job before running out, but not as much as you would pay out in salary if they stayed.

Imagine your employee base graphed on two orthogonal dimensions: their performance level, and their motivation for working for you. (In reality, "motivation for working for you" is actually many dimensions, and performance is likely to be somewhat correlated with certain motivations, but this illustrates the point at least.) The buyout offer doesn't affect people who aren't financially motivated, so take them out of the equation, and look only at the folks who are strictly financially rational.

You can loosely group them into high-performers (those who are known achievers, who always have an offer in hand as soon as they make overtures toward searching), mid-performers (those who pretty much amble along, and for whom the job search provokes intense anxiety, because they typically have to put in 3-6 months of full-time searching to find a new position), and low-performers (those who don't do anything and everyone already knows it). In most companies, the distribution of these is roughly 10-80-10. You can fire all the low performers; the point of bucketing them into the "low performer" category is that their underperformance is obvious enough that they leave a documented paper trail that makes this unambiguous. And in a company that's run into financial difficulties, the top 10% has probably already left, because they continually get job offers and when your company is going down the tubes, it's to their advantage to take them. That means that most of your financially-motivated employee base probably fits into the middle range, the folks who are average employees and will have average difficulty finding a new job.

The point of a buy-out is to reduce the anxiety levels surrounding getting that new job to the point where anyone who is unhappy at your company but isn't sure they have enough money or skills to go elsewhere ends up taking the leap.
Anthony Burgess, writing of 1947 in Little Wilson and Big God:

At the time of educational reform, grammar schools, which had been founded to teach Latin grammar, had fallen into disrepute. Secondary modern schools and technical schools were to be considered as, if not more, important. The elitism of the public school was to be allowed to continue for a time, if only because so many socialists sent their sons to Eton, but the grammar school was to confer no social advantage on its pupils. Theoretically at least the path to a university could brand out of a secondary modern school. The egalitarian philosophy ofthe postwar era may have been accepted, cynically, I believe, by members of the Labour Party, but parents and teachers alike knew the truth: that the road to the smaller distinctions -- the greater ones being reserved to Harrow and Rugby -- began in the grammar school.
Diaspora is one product, whereas the indie web is a set of really lightweight technologies that allow you to join in from virtually any website. It's not dependent on any one vendor or project.

I think the coolest bit is that each of the pieces is so simple that a coder can get up and running from scratch in an afternoon. That's very different to a lot of the federated social web technologies to date.
Looks like you have big experience in this field :)
In addition to your collection, my usual style of work: I almost don't spend time to "marketing myself", I rarely switch clients (usually clients prefer to work with me full-time and even more), I use per-hour rate (because 100% of clients I had chance to work with, didn't know full set of features they need, and most of the time goes exactly to additional features). I'm learning new things constantly, listening podcasts, watching video tutorials, reading blogs, trying out new things in practice - it's not a luxury but necessity, otherwise soon you will meet more skilled competitors :) My price for stable (by freelancing measures) income is lack of "jackpot projects ", when you can make few thousands for week and relax rest of the month. I don't have free time, I feel exhausted often. I don't work over 40 hours limit to have time for family. My family very happy when I finally can spend few hours with them :)
Origins of Electrical Body Activity
Perhaps you didn't read my full comment.
Slack Slash Commands as a Service
Hiya! Looking forward to meet you guys and remember those times at UCLV.... Best wishes!
Show HN: Tivia, a mobile clubhouse for your group (x-platform, Titanium-based)
> Perhaps 70% of developer time is spent dealing with parsing, serialization, and persistence. Values are encoded to and from JSON, to and from various binary formats, and to and from various persistent data stores… over and over again.

> Another 25% is spent on explicit networking. We don’t merely specify that a value must be sent from one node to another, we also specify how in exhaustive detail.

>Somewhere in between all this plumbing code is a tiny amount of interesting, pure computation, which takes up the remaining 5% of developer time.

> These numbers are made up, of course, but if anything they are optimistic

Optimistic for your argument, that is.
And not happy with current job.

If I'm happy, I'm not quitting even though I could easily get another job. It's not always about the money.
Thank you for the detailed reply.

Can I confirm that without ZRTP, or rather, with the current implementation, there's no forward secrecy; so should the keys get compromised either through technological or legal attack, all bets are off?
> * Be courteous when offering constructive criticism (that means, for example, don't swear at people)

This may shock you, but the internet wasn't fucking built for five year olds.

> * Often it's not the project owners posting things on HN - many projects aren't necessarily ready for public consumption when they end up on here

That doesn't mean that they aren't open to constructive criticism.

> * This doesn't even appear to be a "product". It's an open source project that seems to have been recently put out there

Fine. s/product/project/. Better?

> Absolutely typical that this is the top rated comment. Hacker News, you SUCK.

Language!
It's very difficult to deduce causality in that situation. She could have been fired due to not fitting in with the organization due to her valid concerns, or she could have brought up concerns due to bias from being fired. It is most likely somewhere in the middle, where her observations were somewhat truthful and somewhat biased.
It was the same at British telecom when there where such good incentives to leave that many of the key technical staff left.

Most of the Uk's mobile networks was designed and built by ex bt people who took redundancy
Whether you have a single process or not, the "parent" application will responsible for maintaining and executing subprocesses/subroutines.

Applications still have the ability to spawn processes with single process containers, you're just doing it through a different OS/process management system.

By keeping the multiple processes in the same container, you're likely decreasing modularity by introducing interdependencies via the file system.
Great TED talk on the "Filter Bubble": http://www.ted.com/talks/eli_pariser_beware_online_filter_bu...
Microsoft Answers the Question, 'Why Windows Phone?'
Congrats man! We met a couple years back, glad to hear things ended up going well for you guys! If you're ever back in Akron let's grab a beer.
Yeah in my experience, the real time sink is the disproportionate cost of making a decent user interface, regardless of framework or environment.
Programmers routinely underestimate the complexity of every other field.