In this thread: Some demos shown at the FOC meetup...
# share-your-work
n
In this thread: Some demos shown at the FOC meetup in Bangalore yesterday (not everyone has joined this Slack yet):
Paras Chopra: Program synthesis via naive search and genetic algorithms, with/without leveraging abstractions
Adithya: Personal AI server (cloud-in-a-box)
Me: Implementing Eric Hehner's unified algebra
Ruturaj Mohite: Circuitverse: Web-based Digital Logic Circuit Simulator
Ishan Bhanuka: Semantic Code Search using Data flows
Advait: Remote-compute for video editors
Tagging @unnati patel@Prabhanshu Gupta @Atharva Raykar @KS Sreeram about their demos.
Shubhojit Basu: Agent-based swarm simulation with Love2D and Lua (and its use for EV battery swapping network optimization)
m
Very cool that there's a FoC meetup in Bangalore!
p
My demo: An alternative formula language in spreadsheets (functions and frames!).
k
OMG, why have these projects been flying under the radar until now?! I need more companions on #C03RR0W5DGC so people who are on the Slack: represent!
a
(crosspost) a small tool, built live, at & for a small gathering: https://futureofcoding.slack.com/archives/C05V6D72U1K/p1727540887587169
1. the flow is a simple one: an entry screen where you pick a colour, icon, a few tags for yourself / the "room" where everyone hangs out / and an overlay to show you anyone's avatar/name/tags 2. this is the nodegraph for the "room" view: here you'll see the api calls to the service returning your profile and everyone else who's joined, some decision logic to show a different profile card, and navigation actions, etc. a. everything is "data" so it can flow from node to node (live of course :-)) b. yellow lines are data, blue lines are cards, pink lines are action messages c. there are lots of node primitives, like object, filter, lookup, join, database queries, card, component, decision, state machine, various actions like save, navigate, API calls, etc. etc. etc. 3. the "cloud agent" is a simple one, no params even in this case, it just queries the data store it's sitting in and returns all the records to the caller (which is in the view in #2 above)