bhuga

They have been accepting community contributions on dotnet/coreclr, among other projects:

https://github.com/dotnet/coreclr/pulls

We do not charge for hosting any open source project, large or small.

It's an incredible statement on the depth of the bay area talent pool and VC money network that so much tech concentrates in such a tiny place (and thus drives up the rent, as in the article). Nowhere else in the world can compete.

It's not for lack of trying. Louisiana, for example, will pay 35% of a programmers salary indefinitely[1]; other states and cities have similar programs. That's serious competition. But the talent/money vortex of the bay area is not just winning, it's actually getting stronger.

The other areas with real companies, like Austin, Seattle, and New York, still feel like also-rans compared to SF and the valley. If you want to raise money, it's still the place to go.

It's just incredible to think about. Is there any other field where there's just one geographical place that's just so far ahead of anywhere else? Especially fields like biotech, where geography isn't directly related to the business?

[1]: http://gnoinc.org/about/digital-media-incentive/

To be fair, the agreement is clear that it only applies to 'confidential information' as opposed to reviews or things you create (and as opposed to feedback "provided to Amazon", which they own).

But 'confidential information' is not defined in the agreement, and without expiration, I'd still be nervous. Perhaps I overworry.

This NDA has no expiration, neither date nor conditions. You're arguably bound by it after the API is public. Yuck.

This was a pain for me for years when I was a nomad. The US and North Korea are the only two states that tax citizenship instead of residence.

Since US taxes were unescapable, I eventually went for tourist visas, moving every 3 months. The host country does not consider you taxable. I used this in Spain in particular. It worked out fine. I had a spanish lawyer and a spanish accountant, both were of the opinion that it was above board as long as I took longish trips every few months. As long as you're still working remotely and not using social benefits, there's no real legal category for you yet.

There is private health insurance explicitly designed for Americans living abroad. It's dramatically better (and cheaper) than regular american health insurance. Mine, for example, was $1700/year for 100% coverage outside the US and an extra $2900/year for 80% coverage if I wanted it active in the US too.

The text-to-speech is actually a little nicer than Siri or Cortana, but not groundbreaking. This was the only one of the 5 that I thought did well. The rest might have been better without demo pages.

For visual recognition, I used a picture of a snowmobile from http://www.1888goodwin.com/2013/11/14/what-do-you-need-to-do..., which it identified with 73% confidence as "Invertebrate".

Speech to text is a parody twitter account waiting to happen. Here's me asking it how it does with technical transcription:

How do you doing technical words.

If you were going to have to talk about get an jute cushion pull.

And you wanted to discuss the impact on a file server memory.

Issues that cross processes talk about home forks rivers slowed difficult.

That was quick. Awesome! Do you have a sample pull with the new setup?

> I think you're conflating instrumentation and alerting.

A bit, because I'm hesitant to cram into a time series database data that I consider boolean. I'd move past this for consistency if the checks were easy to create, though.

> Prometheus has many instrumentation options. For your example I'd suggest a cronjob that outputs a file to the textfile node_exporter module (echo old_libc_process $COUNT > /configured/path/oldlibc.prom).

Interesting. That architecture or configuration of this exporter isn't documented yet, but if just magically sent numbers upstream from text files that I keep up to date, that might be worth a migration by itself. Nagios SSH checks are ridiculous to manage.

Thanks for indulging my conversation in any case. I'll put this on my radar and watch where it goes.

I haven't used Prometheus yet, but I'm not sure I agree that it makes sense to send dimensional time series all the way down the alert chain. It allows full-featured alerts to be used, yes. But you're not going to be able to put all of your alert logic into the prometheus chain, so you're going to end up having alert rules in at least two places.

For example, in response to the latest security hullabaloo, we recently added a Nagios check for libc being too old, and for running processes that are linked to a libc older than the one on disk. This isn't a time series check; it's just an alert condition. Polling for that alert condition isn't what Prometheus is going to be good at, so cramming it into that alert pipeline is awkward. If we used something like Prometheus, we'd have rules in two places already.

Polling prometheus for saved queries and simply alerting on a threshold might result in a simpler system. The rules that could be expressed in an alert pipeline could be expressed as different queries, and all rules about thresholds, alerting or notifications could be done further down the pipeline. There's still some logic about what you're measuring in Prometheus, but not about what thresholds are alerts, or when, or for how long, or who cares. Threshold rules could all live in one place.

This isn't a knock on Prometheus, which of course supports a workflow along those lines, and seems interesting. Nor is it a knock on the prometheus alert system. I just wonder why software in the monitoring/notification/alerting space always ends up muddy. I believe the overlapping boundaries between projects are a symptom, not a cause. I keep asking myself if there's some fundamental complexity that I'm not yet appreciating.

I think he's commenting on the approach of how the system reports, not its usefulness. Have you considered bundling up the results as a second commit status[1] rather than making comments?

1: https://github.com/blog/1935-see-results-from-all-pull-reque...

It's great to see new entrants into the monitoring and graphing space. These are problems that every company has, and yet there's no solution as widely accepted for monitoring, notifications or graphing as nginx is for a web server.

Not that I'd do a better job, but every time I further configure our monitoring system, I get that feeling that we're missing something as an industry. It's a space with lots of tools that feel too big or too small; only graphite feels like it's doing one job fairly well.

Alerting is the worst of it. Nagios and all the other alerting solutions I've played with feel just a bit off. They're either doing too much or carve out a role at boundaries that aren't quite right. This results in other systems wanting to do alerting, making it tough to compare tools.

As an example, Prometheus has an alert manager under development: https://github.com/prometheus/alertmanager. Why isn't doing a great job at graphing enough of a goal? Is it a problem with the alerting tools, or is it a problem with boundaries between alerting, graphing, and notifications?

Project management is a market that defies solving.

Every company (and person!) has their own workflows and requirements, or there'd be no way for businesses to differentiate themselves on operational efficiency. It's possible to encode those workflows into very flexible systems like Jira, but as is usually the case, that comes at a large cost in design and ease of use.

This creates a market for thousands of small project management solutions, each a well-designed, slimmed down service, often equivalent to a particular customization of ClearCase or Asana but far easier to set up and use.

That makes sense. Thanks for clarifying.

Wouldn't this result in an ever-growing diff? You'd see everything that's gone into master since the branch last rebased/merged master as "changed". When I think about a branch, I want to see changes unique to it, not what's going on in the rest of the codebase.

Showing merge conflicts inline like that is pretty cool, though.

I always watch conference talks at double speed, speaker speed permitting. Alan Kay's voice works fine.

(But I didn't upvote, and your question is valid)

Emails are part of commits, which are hashed as part of normal git operations. There's no way to make repositories public and not make emails public.

Thanks for ag. It was a game changer for me.

http://gerrithub.io/ is a take on exactly this. It uses GitHub's API to turn pull requests into gerrit reviews.

Any repository served with a DMCA notice can file a counterclaim, as outlined in: https://help.github.com/articles/dmca-takedown-policy/#b-cou...

Most open source projects do not need a foundation or company patenting things related to the work and acting as a guardian. Why does NuPIC?

The blog post (which is not a legally binding contract in any way) also has this little gem:

"It should be noted that Numenta/Grok holds patents that do not pertain to the algorithms released in NuPIC. We do not view these patents as covered under the GPL, and we reserve the right to use these patents in the normal course of our business."

Assuming this were a legally binding document--which it's not--who would decide which of Numenta's patents are assigned by the GPLv3 and which are not?

I'm happy you are trying to open-source such a cool piece of tech. But this is the patent policy of a company hedging its bets, not a company that's giving something to the world. It leaves Numenta legally in charge of the NuPIC community, instead of letting it evolve, because it's the only entity that can write a GPLv3 on future patents.

At least I can download and play with the GPLv3 version. The old license was so onerous that I didn't want to see the code, lest I open myself to patent liability 10 years down the line for using something kinda sorta like NuPIC.

But I wouldn't build a business on software with this kind of patent policy, and the commercial licenses Numenta sells make me think you'd rather I didn't.

When I read On Intelligence and from there found Numenta's stuff years ago, I was pretty excited. There were some crazy cool demos back then, and they've occasionally popped back up with more.

So it's too bad about all of the patents, then, now, and forthcoming. They promise not to sue [1], and pledge that future patents are for the 'protection of the NuPIC community'. Maybe, but I'll spend my time with one of the many open-source projects without patent pledges of nebulous enforceability. Most of them seem to do just fine without patent guardians.

[1]: http://numenta.org/blog/2013/07/01/patent-position.html

It will depend on exactly which feature set you use, but it's under active development and has improved a lot recently. There's still a lot of open feature requests, but a lot of non-trivial actions work. Most of the missing or buggy motions are very simple fixes, and contributions are welcome.

This article picks on Atom, but it's really arguing Vim vs Every Other Text Editor based on composed commands vs monolithic commands.

I agree that Vim's style of composed commands is somehow more natural. But Atom's core value is hackability. Atom's vim-mode package performs every operation in the article and countless more, and does it all without any special APIs or permissions. The commands that are not in the editor API, or are but are slightly different from Vim, are written using editor primitives. That hackability is Atom's special sauce, not the set of convenience commands the editor API supports.

Sublime would have been a better "target" for this comparison.

The github package [1] does both of these, although the blame is done on GitHub instead of locally.

1: https://atom.io/packages/open-on-github

I used the new 'consultant' model last week and loved it. I really liked that the consultant could help me get what I wanted, not what I asked for ("I'm cold, put me in South America." "Buenos Aires is expensive. How do you feel about La Paz or Lima?").

I hope they standardize on it. The rest of the site seems to reflect the old models. For just one consultant, why do I need 27 different pricing options for 'kinds of flights'? I don't know what I want. Just charge me one price and be done with it. And the ratings system needs a field akin to 'money saved vs kayak' in addition to the 1-10 scale, because I'm no longer sure I got the lowest price as opposed to a consultation.

But I loved it all the same and will be back. Flightfox is doing a great job.

Thanks for posting. Inspiring breakfast read. Relevant 60 years later.

'Are you now, or have you ever, been associated with any terrorist organizations?'

Thank god someone is doing this. I'd been looking for a way to dedicate a core of my laptop to animated gifs.

A classy, concrete response in a human voice. This is exactly how great companies communicate.

Putting together a bug bounty program for a company like Yahoo is a lot of hard work with tons of tiny gotchas. It can take forever, and it's never ready when it needs to be. Looking forward to it.

The translation is not amazing. The original German reveals responses that are rather dodging the question, but which very flatly state that they are able to 'generally decrypt, at least partially, communications via SSH or PGP'.

It's not clear if they mean 'parts of all communications' or 'a part of all communications', and specific attack vectors are not even touched on.