diff --git a/collections/_posts/2024-11-21-here-we-are.md b/collections/_posts/2024-11-21-here-we-are.md deleted file mode 100644 index c5823e310..000000000 --- a/collections/_posts/2024-11-21-here-we-are.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -title: Here We Are -author: DerekNonGeneric -category: meta ---- - -Hello everyone! We're three friends passionate about building tools that empower -the open-source community. Welcome to the first entry in the OpenINF blog! Here, -we'll share updates about our journey, from the inception of OpenINF to the -exciting tools and projects we're developing. - -OpenINF started with an idea: **How can we help open-source developers -aggregate, curate, disseminate, and apply information more effectively?** As we -explored this question, we realized the tools we envisioned weren't readily -available, so we created them ourselves. - -Our flagship project, the **INF Development Kit (IDK)**, is a JavaScript toolkit -inspired by the modular and extensible principles of Brendan Eich's ideas for -JavaScript. It's designed to make building and expanding open-source projects -more straightforward and enjoyable. - -We're in the early stages of development, crafting the foundational components -of IDK and laying the groundwork for future projects. Like any ambitious -project, OpenINF has its challenges — we're balancing development with our -day jobs and managing everything on a shoestring budget. But we're passionate -about this project's potential to make a difference in the open-source world. - -We're eager to share our progress with you and the community. Your feedback will -be invaluable as we refine our tools and ensure they're as impactful as -possible. Over the coming weeks, we'll post updates about our development -process, challenges, and the milestones we're working toward. - -This blog, like OpenINF itself, is a work in progress. You might notice the -occasional rough edge — code that needs updating or half-finished pages -— but that's all part of the journey. We appreciate your patience and -support as we continue to build. - -Thank you for joining us on this adventure. We're excited to see what we can -create together! Stay tuned for more updates, and feel free to reach out — -we'd love to hear from you. diff --git a/collections/_posts/2026-08-18-here-we-are.md b/collections/_posts/2026-08-18-here-we-are.md new file mode 100644 index 000000000..95a9af362 --- /dev/null +++ b/collections/_posts/2026-08-18-here-we-are.md @@ -0,0 +1,55 @@ +--- +title: Here We Are +author: DerekNonGeneric +category: meta +--- + +Hello everyone! I'm passionate about building tools that empower the open-source +community, and this is where I'll be sharing what comes of that. Updates about +the journey, from the inception of OpenINF to the exciting tools and projects +taking shape along the way. + +OpenINF started with an idea: **How can we help open-source developers +aggregate, curate, disseminate, and apply information more effectively?** As I +explored that question, I realized the tools I envisioned weren't readily +available, so I set out to create them myself. + +That work has a name and a date now. The **OpenINF SDK** — ten small +TypeScript packages inspired by the modular and extensible principles of +[Brendan Eich's ideas for JavaScript][] — arrives in Q4 2026. + +What they cover is the unglamorous middle of Node.js work: type guards and +argument validation, structured errors, object and array helpers, text that +behaves itself in a terminal, and a couple of things that fit nowhere else. None +of it is the interesting part of your program. All of it is the part you end up +writing again on every project. + +It is not starting from nothing, either. Six of these packages have lived on npm +since April 2022, already written in TypeScript, with type declarations from day +one. What they had not done since then is change. Several leaned on small +third-party modules nobody was maintaining, so I wrote replacements, checked +each against the original, and dropped the dependency. Nine of the ten now carry +no third-party runtime dependency at all, and what remains depends only on a +core that depends on nothing. Four packages that have never been published are +joining the six. + +Like any ambitious project, OpenINF has its challenges. I'm balancing +development with my day job and managing everything on a shoestring budget. But +I'm genuinely excited about this project's potential to make a difference in the +open-source world. + +This blog, like OpenINF itself, is a work in progress. You might notice the +occasional rough edge — code that needs updating, or a half-finished page +— but that's all part of the journey. + +Thank you for joining me on this adventure. Your feedback along the way will be +invaluable, so stay tuned, and please feel free to reach out. I'd love to hear +from you. + + + + +[Brendan Eich's ideas for JavaScript]: https://brendaneich.com/2011/01/harmony-of-my-dreams/ + + +