It seems like a good case for growing these trees for the lumber industry, both to sequester this carbon for good and to provide a faster timeline for harvesting timber which could decrease lumber costs. A good time for it too given the way lumber costs have been going. Is this something you are considering? Is the wood from the trees you are growing suitable for construction of any form?
I have seen no proposal for a wealth tax that is not a marginal wealth tax, in which case the math in this essay is wrong. The Warren wealth tax, for example, is for wealth over $50 million.
The math on this is incorrect. This is not how a marginal tax works. I have not seen any proposals for wealth taxes that are not marginal after a certain (usually very high) level of wealth.
For example, the Warren wealth tax only kicked in after $50 million.
As an aside, I love it when politicians take credit for naturally occurring phenomena like this. Industry go pummeled during that crash and every single business worked hard to claw their way out of the ditch. And then politicians proclaim "The sun went down and we made it come up every morning for the last six years!". You couldn't make this shit up.
Awesome song! Though I think it's more likely that Coolio got the base melody for Gangsta's Paradise from Stevie Wonder, and Amish Paradise grabbed it from Coolio since Amish Paradise is a parody of Gangsta's Paradise.
Having worked with a lot of Javascript frameworks aimed at creating web applications/SPAs (used Cappuccino to build a wireframing tool, Backbone.js to build a dashboard for a payments provider, React/Relay to build a phone calling tool and events platform, and now React/Apollo to build a peer-to-peer texting tool), I can say that React/Apollo/GraphQL is my new go-to stack for new JS projects. It's a pleasure to work with, and a lot of the pain points of creating large apps with JS in the past are handled very well. Congrats to the Apollo team!
After working with Apollo for a couple weeks on a non-trivial side project, I'm particularly happy with how unopinionated the library is. While it's super hip to complain about JS fatigue these days, Relay just wanted to make too many decisions. In that sense, it's a pro and a con: Relay will make more decisions for you, but will present difficulty if you've already made some of those decisions yourself.
Apollo's using Redux is great. The model and API are well understood so it's easy to bring developers on board. Relay seems to follow the same principles, but does them in its own way.
Relay is also opinionated about your server's responses. I know that the cursor pattern with edges and nodes is great for performant pagination, but then our schema has to conform to that spec and I really don't enjoy spending time explaining why we can't just get that user's photos, we have to get that user's photos' edges' nodes. Graph theory has a place, but it's not that close to the frontend, IMO.
More than anything, it seemed very easy to get up and running with Apollo. After reading lots of Relay docs, it still took a lot of experimentation and effort to get this running to begin with. I am very happy with Apollo's docs.
Before we started building Apollo Client, we actually tried Relay, but found it difficult to adopt, so we started a community effort to build a more flexible GraphQL client. Our main goals were to make incrementally adoptable, compatible with all view layers and easy to understand/debug.
While Apollo is easier to adopt and use, it's still under active development, so it's not as stable as Relay, and hasn't been optimized for performance the way that Relay has.
/disclaimer/disclosure/ - when you disclose something, it's a disclosure. (Sorry, personal bugbear, along with e.g. / i.e. confusion. Both are rampant on HN! :) )
I used Slava's blog to learn about Lisp and went on to build a product with Weblocks, which was a continuations-based web framework that Slava created back in the day (I only recently finally deleted a forgotten 8-year old todo about merging in my refactored Weblocks formview). Random trivia (kind of) - the syntax and concepts in Weblocks actually bear some resemblance to Goat, which is a framework that Patrick had created and used to build the original version of the Stripe dashboard (likely just because both of them come from a Lisp-heavy background).
I had just started a new company using RethinkDB, and it was definitely poised to be my go to database for new projects. Anyway, all this is to say, for someone who I know only through his works, I have great respect for Slava and want to thank him for the work he's done. Here's to hoping that RethinkDB finds a way to continue.
Project Description: Brand New Congress is an initiative to primary most of the existing incumbents in Congress with a representative group of progressive people who all agree to enact an aggressive progressive platform once they are elected. You can learn more about our goals and what we're trying to do on https://brandnewcongress.org. The tech team at Brand New Congress works on a variety of tools that will help bring about the revolution, and we are currently focusing a lot on expanding our website and making it way more awesome.
What do you hope to build this month?
Our main focus this month is to create an awesome events portal like map.berniesanders.com v2.0 (https://github.com/BrandNewCongress/website/issues/98), update our dashboard to make it the central hub of where all our volunteers are looking everyday to see how BNC is doing (https://github.com/BrandNewCongress/dashboard), and updating our current sign up and donation flow (https://github.com/BrandNewCongress/website/issues/85). In general, we'd love to use these tasks as a way to find someone that would be willing to take on a leadership role and be able to commit a decent amount of time every week to keep our website updated and think up new ways to use our site/tech stack.
What kind of skills do you need?
Our projects are currently largely Javascript/React based. We're starting to play around with Apollo and GraphQL as our data layer, but don't worry if you don't already know about those technologies as they are pretty new and we'll teach you.
Link to your GitHub or somewhere else you'd like to onboard new contributors, like your project management software or chat room.
https://github.com/BrandNewCongress/welcome
I generally reply openly about my ten-year plan, I promise that it's going to change, and I restate how large a challenge it is to maintain excitement and interest at their company for the next ten years of my life.
I feel that either you misunderstood me or I misunderstand you. I'm leaning towards the first option.
By which I mean - There's a distinction between the kind of interview that happens between a founder and an investor and the one that happens between an employee and an employer. I wouldn't be surprised if an investor asked that kind of question, but if an employer did, I would think it was rather arrogant.
