| • Nick Nisi attending Squiggles conference | |
| • Jerod and Kball discussing React Summit US and the upcoming event on November 19th in New York | |
| • Discussion of JS Party's presence at both React Summit US and JS Nation US conferences | |
| • Announcement of Evan You's new company, VoidZero, and its $4.6 million seed funding for a unified development tool chain for JavaScript | |
| • Kball's concerns about the potential risks of VC-backed open source tooling infrastructure | |
| • Jerod's observations on Evan You's financial stability through Patreon and GitHub Sponsors, and the implications of his decision to raise capital | |
| • Creation of VoidZero and its goals | |
| • Concerns about a unified JavaScript tool chain being driven by VC funding | |
| • Impact on existing open-source projects (Vite, Vitest, etc.) | |
| • Challenges in making a for-profit company work with open-source projects | |
| • Comparison to Deno's approach to monetization | |
| • Potential for sponsorships and partnerships instead of venture capital funding | |
| • Vite is the fastest-growing tool chain in the JavaScript ecosystem | |
| • Kevin Ball expresses reservations about Evan You's decision to take VC funding and its potential impact on Vite's open-source nature | |
| • Jerod Santo proposes crowdfunding as an alternative approach to raise funds without sacrificing control or shifting focus towards paid services | |
| • Discussion of Evan You's background, ambition, and possible motivations for taking a big shot with VoidZero | |
| • Matt Mullenweg's controversy surrounding trademark infringement, lack of open source contribution, and recent buyout offer to employees at Automattic | |
| • 80% of Automattic employees worked on WordPress, while 20% worked on other projects like PocketCasts and Tumblr. | |
| • A person took $30,000 buyout offer two days before the deadline, giving a shout-out in the post. | |
| • The conversation discusses how Matt Mullenweg's behavior may not align with his previous character, potentially due to lack of advisors or pressures from the environment around him. | |
| • Automattic raised VC funding at the peak of the 2021 funding craze and is now facing financial strain, which could be affecting their behavior. | |
| • WP Engine's success and contribution to WordPress are being compared to Automattic's, with some suggesting it's a "social contract" for competitors to invest in the common foundation. | |
| • Ripple effects of actions in open source development | |
| • Trust cascades and loss of trust among users and customers | |
| • The role of a Benevolent Dictator for Life (BDFL) and consequences when no longer benevolent | |
| • Potential community fork of WordPress due to WP Engine controversy | |
| • Similarities with HashiCorp's relicense of Terraform and creation of Open Tofu | |
| • Risks of marrying open source and big backing companies | |
| • Challenges of finding sustainable funding models for open source development | |
| • Commercial open source software, including open core models and the role of venture capital | |
| • IndieVC model as an alternative to traditional VC funding | |
| • Starting a startup is often not enjoyable, so people are incentivized with large amounts of money to make it seem sexy. | |
| • The Web Components debate has been ongoing, with some arguing it's not the future of the web and others seeing its benefits. | |
| • Ryan Carniato argued that Web Components pose a risk to the web's future due to their limitations in building complex applications. | |
| • Cory LaViska responded that Web Components are currently being used as dynamic components within web pages, but not necessarily designed for full application development. | |
| • There is value in using Web Components as part of a larger component architecture, rather than trying to build entire applications with them. | |
| • Some experts recommend ignoring certain features of the Web Components API (such as the shadow DOM) to simplify and improve development. | |
| • Debate around reactive vs declarative programming models | |
| • Value of debates in advancing community thinking and problem-solving | |
| • Criticism of Web Components rollout speed and limitations | |
| • Browser companies' bias towards backward compatibility | |
| • Importance of building cool stuff and focusing on innovation, rather than litigation or shutting down others |