Meteor Licensing Update promised on Friday

Meteor Licensing Update promised on Friday

Email sent directly to me from the Meteor mailing list:

[Summary: Huge launch, caught by surprise. Big license announcement FRIDAY.]

A week ago we posted meteor.com to Hacker News. We thought a few hundred people would see it, maybe a thousand if we were lucky. Then, the theory went, with the veil of secrecy lifted, we could start in on the hard part -- convincing anyone to look at what we were doing, or care.

Five minutes after clicking the submit button, it was already clear that we had miscalculated by three orders of magnitude. No, the dashboard wasn't broken, there were 5,000 simultaneous users on the website. (And the single-process Meteor app running the site was doing fine.) We expected a few dozen deploys but got ONE THOUSAND THREE HUNDRED. Vimeo says that 70,000 people watched the screencast. What fraction of all living JavaScript developers is that?

"Makes me want to build things." "Blew my mind." "Is this the future of web development?" (Yes, Alex, it is.) "I think I just saw the future." "crazy voodoo magic" "dark sorcery" "This is completely bananas." "I am falling in love."

Even as I write this, 100 people are active on docs.meteor.com and a new app is getting deployed every three minutes. 150 people are hanging out in IRC, and people are answering each other's questions on Stack Overflow and Quora. It's like a perpetual, international Meteor hackathon.

It's all happening much faster than we thought. It's going to be a wild ride, and I'm so happy that you've decided to ride with us. We have some hard work to do now, though. We have to turn this excitement and energy into a real community, and we have to implement the rest of the roadmap and ship a 1.0.

LICENSING UPDATE

Licensing is the first order of business. Many people sent comments. There were three kinds:

1) People who were frustrated because they wanted to use Meteor for a project, but couldn't tell if it was allowed or how much it would cost.

2) Detailed analyses of legal, strategic, and technological implications of every possible choice we could make. This was AWESOME and was incredibly helpful. Some of the people who wrote in are smarter and better informed than any license attorney I've ever talked to.

3) "You suck, you really screwed this up, you are bad people." These comments weren't as helpful, but we're still glad to have them.

I really apologize to everyone who was frustrated. We thought it was going to be months before anyone was interested enough in Meteor to care about the license. Clearly that was wrong.

Licensing is tricky. We're working hard to fix the problem. ON FRIDAY AFTERNOON, we will announce the options for using Meteor in closed-source, commercial software. I think nearly everyone will be happy with the solution. We'll post the announcement on Hacker News, and we'll also send an email to the list. I hope you'll upvote and redistribute as you find appropriate, because even though there are 6,000 people on this list, that's still only 5% of the uniques we've seen on meteor.com.

See you on Friday :)

-- Geoff, Matt, Nick, David

Discussion 0 comments · 2 points · havemurci · 2012-04-18
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.