βοΈ Not subscribed yet? Subscribe to the Newsletter
Future of Coding Weekly 2025/10 Week 2
2025-10-12 23:07
π Architecture for a multilingual Wikipedia π Subway Builder π₯ VibeCard: a todo list app in 5 minutes and 1 line of js
Share Your Work
π¨οΈ guitarvydas: π The Marketing of C & π Hardware Stockholm Syndrome
π§΅ conversation @ 2025-10-06
π¨οΈ Denny VrandeΔiΔ: π Architecture for a multilingual Wikipedia
π§΅ conversation @ 2025-10-07
I think I shared this before, but Ivan told me to share this again because he thinks it is fascinating: I am working on a project called Wikifunctions. Wikifunctions was built in order to support Abstract Wikipedia, as described in this paper introducing Abstract Wikipedia and Wikifunctions. It is a short paper (here's the PDF), but there is also a long version with far more details.
The goal of Wikifunctions is to allow for the creation of Abstract Wikipedia, to create natural language text from a language-independent notation anyone can edit directly, using functions from Wikifunctions. These functions are aimed to be writeable and maintainable also by non-programmers.
So far, Wikifunctions has collected a catalog of more than 3100 functions, in diverse areas such NLG, chemistry, maths, colors, etc.
π Architecture for a multilingual Wikipedia
Wikipedia's vision is a world in which everyone can share in the sum of all knowledge. In its first two decades, this vision has been very unevenly achieved. One of the largest hindrances is the sheer number of languages Wikipedia needs to cover in order to achieve that goal. We argue that we need a new approach to tackle this problem more effectively, a multilingual Wikipedia where content can be shared between language editions. This paper proposes an architecture for a system that fulfills this goal. It separates the goal in two parts: creating and maintaining content in an abstract notation within a project called Abstract Wikipedia, and creating an infrastructure called Wikilambda that can translate this notation to natural language. Both parts are fully owned and maintained by the community, as is the integration of the results in the existing Wikipedia editions. This architecture will make more encyclopedic content available to more people in their own language, and at the same time allow more people to contribute knowledge and reach more people with their contributions, no matter what their respective language backgrounds. Additionally, Wikilambda will unlock a new type of knowledge asset people can share in through the Wikimedia projects, functions, which will vastly expand what people can do with knowledge from Wikimedia, and provide a new venue to collaborate and to engage the creativity of contributors from all around the world. These two projects will considerably expand the capabilities of the Wikimedia platform to enable every single human being to freely share in the sum of all knowledge.
π¨οΈ Mariano Guerra: π₯ VibeCard: a todo list app in 5 minutes and 1 line of js
π§΅ conversation @ 2025-10-10
Initial release of VibeCard, try it here: https://marianoguerra.github.io/vibecard/
π¨οΈ Daniel Coutinho Ribeiro:
π§΅ conversation @ 2025-10-12
can i get your thoughts on my project: https://github.com/creact-labs/creact
DevLog Together
π¨οΈ Arcade Wise:
π§΅ conversation @ 2025-10-08
I've been working on an app that provides a user-friendly interface to Linear Programming solvers, specifically for resource allocation problems. I have a UI that works, and it is getting data into the solver, however I don't think I'm setting up my solver correctly yet :0
Thinking Together
π¨οΈ Daniel Harris: π₯ shopping interface
π§΅ conversation @ 2025-10-11
What the hell am I doing? I've built (with AI) a mock up of a shopping interface where I can make it more complex and more simple. But in a usable, production version of this I'm imagining nothing in the user interface is hardcoded and the UI responding to a variable quality of complexity. But how would we go about encoding the interactive elements so that we could filter based on the quality of complexity? And how do we do this for other quality vectors? How do we take a slice through a set of interactive logic? How do we represent the logic of interaction? I don't really know how I got here. But now that I have I need your help to figure out how we do this without AI. Because I want to do this not just for a shopping interface but for all my computing. I want malleable interfaces and interactions where I can filter qualities of the interface easily. If you don't know, then take a guess because I'm after any threads I can get. Cheers!
Linking Together
π¨οΈ Arcade Wise: π Subway Builder
π§΅ conversation @ 2025-10-09
Y'all may appreciate this new indie game whose development I've been following, where you get to build a subway system based on modern US census data! The dev manually recreated the Apple Maps style in WebGL too.
https://www.subwaybuilder.com/
A game for building your own realistic subway system
π¨οΈ Jasmine Otto:
π§΅ conversation @ 2025-10-11
thinking about Kartik Agaram's lenses of malleability & literacy https://akkartik.name/post/2025-06-12-devlog
in relation to rich discussions of annotation, embedding, & extension at LIVE workshop
Orion Reed and I submitted a positional paper for LIVE 2025 called "Live Programming in Hostile Territory". Now that it's been accepted, I'm excited to hear peoples thoughts and feedback! It touches on a topic wider than just live programming and, at least to me, is very relevant to the FOC community. Here is the abstract:
Live programming research gravitates towards the creation of isolated environments whose success is measured by domination: achieving adoption by displacing rather than integrating with existing tools and practices. To counter this tendency, we advocate that live programming research broaden its purview from the creation of new environments to the augmenting of existing ones and, through a selection of prototypes, explore three _adversarial strategies_ for introducing programmatic capabilities into existing environments which are unfriendly or antagonistic to modification. We discuss how these strategies might promote more pluralistic futures and avoid aggregation into siloed platforms.
https://folkjs.org/live-2025/
π¨π½βπ» By π @[email protected] π¦ @warianoguerra
π¬ Not a member yet? Check the Future of Coding Community
βοΈ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS
ποΈ Prefer podcasts? check the Future of Coding Podcast