โœ‰๏ธ Not subscribed yet? Subscribe to the Newsletter

Future of Coding Weekly 2024/08 Week 2

2024-08-11 23:43

๐Ÿ“” Userspace notebook editor โ›๏ธ Bootstrap post-collapse OOP technology ๐Ÿ”Œ cables.gl is now open source

Two Minute Week

๐Ÿ’ฌ Marek Rogalski

๐Ÿงต conversation

This week I've implemented serialization format for machines built in Automat. Simple JSON file (pretty-printed) stored next to the executable. Turns out its quite handy during interactive development. And also opens the way for regression testing. Restoring the window state was (surprisingly) the hardest challenge (due to DPI and monitors) and I didn't manage to correctly persist it. Both on Linux and Windows, the window managers just don't want to share some of the window properties... (especially around window tiling)

๐ŸŽฅ Demo

๐Ÿ“” observablehq.com/@tomlarkworthy/userspace-editor via Tom Larkworthy

๐Ÿงต conversation

What would it take to make an open source front end to the Observable Runtime? One where you have control over the runtime and layout and are free from iframe sandbox restrictions?

๐ŸŽฅ open-notebook

Our Work

โ›๏ธ Bootstrap post-collapse OOP technology (Part 1) via Mariano Guerra

๐Ÿงต conversation

How do we preserve the ability to program OOP through civilizational collapse?

2024-08-09_12-25.png

2024-08-09_12-26.png

Devlog Together

๐Ÿ’ฌ Ivan Reese

๐Ÿงต conversation

Got the visual design of the wiki mostly fleshed out. Fluid layout, one breakpoint that moves elements around for smaller screens, light and dark modes, nice keyboard nav, etc etc. Thoroughly documented too, since I figure some folks might want to peek at the css but aren't up on all the new weird stuff you can do.

Also, I'll be eating my hat now: everyone who scolded me for attempting to parse a markdown-like syntax with Regex, well, yeah, it kinda stinks. Not sure what to do about this, given the values I'd like to impart in this project. Since it's not a blocker on writing pages, I think I'll ship it half-finished and we can talk about it. This feels like a great area to draw on the wisdom of the crowd.

Markdown or not, we'll still need a build script, I reckon, unless we want to ~require~ that anyone adding a new page also add their page to any relevant indexes โ€” since, I reckon, we'll need some indexes just to get through the early phase where the wiki will be sparsely interconnected. To start, I'm thinking one index of broad categories (or maybe tags, dunno), and then another that's just a list of all pages. But if anyone has strong feelings about the right way to do this, I'm at least 75% ears.

Thinking Together

๐Ÿ“ How I program in 2024 via Andreas S

๐Ÿงต conversation

Kartik Agaram is that your blog?

Content

๐Ÿ”Œ cables.gl via Ivan Reese

๐Ÿงต conversation

The cables.gl visual programming language for making cool WebGL shaders was just open-sourced.

๐Ÿ’ฌ Beni Cherniavsky-Paskin

๐Ÿงต conversation

  • Just found Mr. 4th Programming Conversations podcast which mentions multiple FoC topics ๐Ÿฐ. Visual programming, Bush & Englebart...
  • Developer Voices podcast is maybe less 1:1 match but interviews many developers building new/experimental/visionary languages.

๐Ÿค–

๐Ÿ’ฌ Mark Dewing

๐Ÿงต conversation

We now have two examples of systems that can turn text descriptions into code - humans and LLMs. And we don't understand how either of them works.

๐Ÿ“ No apps no masters via Kartik Agaram

๐Ÿงต conversation

Present Company

๐Ÿ’ฌ Dany

๐Ÿงต conversation

So I have this c/c++ codebase, around 116,000 lines of code. A full release compilation takes 6:25 minutes. Not too bad to work on.

If I break this down, a single line of c/c++ code takes 0.0033s (3.3 miliseconds). For comparison, a game that runs at 60 fps, draws a new frame in under 16 miliseconds. So while a game simulates and renders a frame, a c/c++ compiler compiles 5 lines of code. That is usually not even a single function.

My cpu avarages at around 10 instructions per clock cycle. At 3.6Ghz it can do 3.6 * 10 * 1,000,000,000 instructions on each core, per second. That's 36,000,000 per milisecond, on 8 cores.. but let's add some cache misses, any instructions can either go full speed 1x or go to main memory around 200x slower.

We are looking at around 5 million instructions per milisecond.

If we print out (9pt font) all instructions executed to compile a single line of c/c++ code, we'd end up with over 6 kilometer long paper.


๐Ÿ‘จ๐Ÿฝโ€๐Ÿ’ป By ๐Ÿ˜ @marianoguerra@hachyderm.io ๐Ÿฆ @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

Contents ยฉ 2024 Mariano Guerra - Powered by Nikola