I think a neat route would be to use this as an authoring plugin in VS Code, like prettier: write Duper (or JSON5, or whatever), and then downlevel it to regular json automatically when pressing cmd-s. You wouldn't get to keep your comments (or they could be transformed to { "//": "comment text" }). Outside of that, it's tough to compete with JSON in the "human readable unschematized serialization format" market,... - Source: Hacker News / 10 months ago

React's bundling system and published packages has gotten noticeably more complicated over time. First, there's the separation between the generic cross-platform `react` package, and the platform-specific reconcilers like `react-dom` and `react-native. All the actual "React" logic is built into the reconciler packages (ie, each contains a complete copy of the actual `react-reconciler` package + all the... - Source: Hacker News / 11 months ago

These numbers don't reflect anything useful. This is the total size of the code in the package, most of which will be tree-shaken. In Zod's case, the package now contains three independent sub-libraries. I recommend plugging a script into bundlejs.com[0] to see bundle size numbers for a particular script [0] https://bundlejs.com. - Source: Hacker News / over 1 year ago

[bundlejs](https://bundlejs.com/) is the better alternative to check your dependency sizes with. - Source: Hacker News / over 1 year ago

I was closing out some long lived issues over on bundlejs, when issue #50 reminded me of the ongoing debate about how bundlejs should handle the ESM and CJS packages. - Source: dev.to / about 3 years ago

This... exists? Did they even search for it? https://github.com/open-source/sponsors. - Source: Hacker News / 8 months ago

Community-Driven Upgrades: Increased integration of real-time community feedback via platforms such as GitHub Sponsors and social media channels (e.g., Twitter (@fsf)) could drive iterative improvements in the license. - Source: dev.to / over 1 year ago

Chad has been leading the Open Source Pledge, a simple framework to get companies to fund the projects they rely on. The idea is straightforward: for every developer your company employs, allocate $2,000 per year to open source. Distribute those funds however you want—GitHub Sponsors, Open Collective, Thanks.dev, direct payments, etc. The only other ask is to publish a blog post showing what you did. - Source: dev.to / over 1 year ago

Abstract: This post dives into the evolution and global expansion of GitHub Sponsors and its impact on funding open-source projects. We examine its inception, supported countries, technical challenges, and how blockchain innovations and alternative funding models are shaping the future of open source development. From core benefits and practical use cases to potential hurdles and forward-looking trends, this... - Source: dev.to / over 1 year ago

This post explores the critical issue of sustainable funding for open source projects. We dive into historical challenges, innovative funding strategies, and future trends that aim to support the collaborative spirit of open source development. Using examples from corporate sponsorships, non-profit foundations, crowdfunding methods, subscription models, government grants, and commercialization, the article... - Source: dev.to / over 1 year ago