ryscheng

I wrote a draft of this article back in 2018, but never published it. Reading back on it now, I'm surprised how much I still agree with the fundamental premise.

For me, it wasn't about tokenization. It was exciting that we could build trustworthy decentralized systems, without entrusting any single centralized party with power.

Now 8 years later, it's interesting to see "blockchains" that aren't really BFT, or semi-centralized. - For the chains that stuck to their decentralized BFT roots, I'm bullish. - For the chains that are trying to tokenize on software that is strictly harder to use than straight up web servers. Good luck with that. Banks seem to be pretty good at launching stablecoins without it.

Author here

I think it’s time we create a coalition of open source projects that band together and re-license in a way that requires that companies fund their dependencies. In my proposal, I’m trying to maintain as many of the freedoms of free software as possible (to run, study, modify, distribute), while adding simple license terms that force companies that use and make money off of the software to give back.

Let me know if you have any questions or feedback, I’d love to make something work for a wide spectrum of projects!

Congrats on the launch! I’ve been following this project and I’m really excited to see how much it has matured. For projects currently on GitHub, what’s the best way to migrate? Is there a mirror mode as we test it out?

I’ve been using Plasmic for the last 6 months to build rich featured Dapps in the web3 space. It takes some time to import all the React components I need but once you do, it is really incredible how much this speeds up my development. We now have non-developers (like designers and PMs) regularly shipping entire features to production without developer help. Really takes some of the pressure off the engineering team while drastically improving team velocity.

Just for fun during the ETHDenver hackathon, I shipped an LLM-powered NFT generator, with 0 lines of code in 3 hours, and won a cash prize. This tool completely changes the game for me and my team.

I am so delighted to see this go open source!!

I love it! and so glad you guys made it open source. nice work!

Hi there! OP here, very open to feedback and questions. Because there doesn't seem to be a single canonical way to do localization in React, I got stuck down a rabbit hole of exploring all the different options (and there are many!). Here's a write up of my findings, which I hope might be useful to someone else in the planning stages. In other words, you haven't already decided you want to use a particular library, but want to see at a high level the pros and cons of different approaches (e.g. i18n libraries, CMS'es, automated services etc).

On the other side of this, it's fascinating how often people fall susceptible to arguing why something should or shouldn't exist for someone else, rather than just making a limited statement about utility for themselves. Something to stay cognizant of, this article is a good lesson on empathy!