Recent submissions

Comment · 9 years ago
Comment · 10 years ago
Hi James,

I'm really sorry to hear about the difficult time you've been having. I can see how that would make an already thankless job like maintaining an open source project even more frustrating.

During my time as a Lerna contributor I was careful NOT to abuse my power. The few times I merged PRs I checked with Henry first. I pinged you at the beginning, too, but stopped eventually when I didn't hear from you. Mostly what I did, though, was triage issues and work with other contributors to get PRs into shape. I spent a lot of time over the summer working on Lerna, and only a small part of that was the code I wrote myself.

Then, suddenly, you started deleting my comments and locking my issues. You removed me from the organization without any discussion. That seemed to me an abuse of YOUR power. It hurt.

Please re-read the first comment of mine that you deleted. It wasn't meant to be aggressive. It was a plea.

---

My inspiration here comes primarily from two sources:

1. Using Lerna every day and thinking about how it could be improved to make my life easier.

2. Listening to feedback from _other_ Lerna users about how it could be improved to make _their_ lives easier.

You're one of the original core team, and I don't want to alienate you. Your rewrite of Lerna put in place a foundation that has been a pleasure to work with. But lately maintenance and improvement has continued in your absence thanks to contributions from Lerna's fledgling user community. Do you plan to reassume this responsibility?

---

That was here [1], but you deleted it and then locked the issue. I hope as you read it now you can see why it was surprising and hurtful that this was your response.

[1] https://github.com/lerna/lerna/issues/334

Comment · 10 years ago
Oh, hadn't considered that interpretation. Our full project description on GitHub is "React framework with server render for blazing fast page load and seamless transitions between pages in the browser". The tag line on the website is shortened from that. I think the full version is a little less ambiguous, but it's a little too wordy in the context of the site.

Will have to think about a better tag line... Thanks!

Comment · 10 years ago
For routing of URL paths to "page" objects we use Yahoo's `routr`.

We've tried to keep data store selection out of React Server core. There are so many good options in the React ecosystem that picking one seems limiting.

The data bindings that the framework cares about are at the http request level. We have a wrapper around `superagent` that manages transfer of response data from the server to the browser. So, when the client controller wakes up in the browser and tries to make the same requests that the server just made while _it_ was rendering the page, the data is already present and the requests are short-circuited.

Comment · 10 years ago
Yes, definitely agree! We need better tutorials!

We need better docs in general. Contributions welcome! :D

Comment · 10 years ago
The website itself is meant to serve as a demo. :)

When you land on the site the first page is rendered by the server. Then the client controller wakes up and subsequent page views ask the server for data, but render in the browser. That's what we mean by "seamless transitions".

Comment · 10 years ago
Actually, the website _is_ powered by React Server! :)

We wanted the project website to serve as a demonstration as well as a source for documentation.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton