• Aleks

    Aleks

    2 years ago
    Looking at the 40 message long branching conversation happening in general right now, it makes me wish google wave had survived. It was this magical superset of google docs, reddit, and slack that was just too strange to live.
    Aleks
    a
    +1
    3 replies
    Copy to Clipboard
  • Robert Butler

    Robert Butler

    2 years ago
    I think this audience would appreciate this. It's an hour long talk about "The Art of Code" but I had my mind blown several times throughout. Well worth the time.

    https://www.youtube.com/watch?v=6avJHaC3C2U

    Robert Butler
    g
    4 replies
    Copy to Clipboard
  • Ray Imber

    Ray Imber

    2 years ago
    This is a particular flavor of random for people that like low level things. In particular probably @Robert Butler and @Kartik Agaram. This showed up on Hacker News this morning. It looks like the 8-bit guy going to start selling his retro homebrew computer design either as a finished product or a kit soon: https://www.commanderx16.com/forum/index.php?/home/
    Ray Imber
    Robert Butler
    +1
    4 replies
    Copy to Clipboard
  • Ray Imber

    Ray Imber

    2 years ago
    Also interesting for people interested in the pedagogy of assembly languages and low level computing: This looks interesting: https://keleshev.com/compiling-to-assembly-from-scratch/
    Ray Imber
    1 replies
    Copy to Clipboard
  • s

    S.M Mukarram Nainar

    2 years ago
    https://futureofcoding.slack.com/archives/C5T9GPWFL/p1593188563490900?thread_ts=1593176908.480100&cid=C5T9GPWFL @Ivan Reese Do you happen to have any resources on optimization for front-end stuff like what you mentioned here? I've never come across a systematic account.
    s
    i
    3 replies
    Copy to Clipboard
  • Tim Plotnikov

    Tim Plotnikov

    2 years ago
    Hey folks! Right now I explore an idea about bringing some of the ideas of Functional Relational Programming (“Out of the tar pit” paper, here is a quick summary) to the mainstream development. I have a problem and thought maybe somebody could help me here 🙂 In my app, I have two variables in state and they are somewhat connected: one can be changed programmatically and another one is changed by the underlying system when an event happens. If one of them changed, another one should be changed too to stay in sync. Right now each variable has its own place, its own change callback and basically there are 2 places where code should be written. What I want to do is to create some kind of “relation” between those two in a declarative manner and store it (or just have in code). So, when one of the variables changes, other changes too automatically and in one place. And also, it’ll be nice to create an ability to subscribe to the relation (and not particular variable), maybe put some constrains on it, etc. But I’m struggling with creating that “Relation” entity. What it should be? An object? A function? How can I create a declarative way for creating relations? Does somebody have ideas or thoughts? Thanks in advance! P.S. I do UI development mainly (swift, kotlin, iOS, Andoid), but feel free to elaborate in any language or system, I think I could adapt 😉
    Tim Plotnikov
    Cole
    +3
    13 replies
    Copy to Clipboard
  • j

    Jack Rusher

    2 years ago
    j
    s
    +5
    12 replies
    Copy to Clipboard
  • g

    Garth Goldwater

    2 years ago
    https://twitter.com/s3rioussam/status/1283783492254535682?s=21 the whole network of tweets referenced here are fascinating: the generation appears to be strongly drawn to games with end-user customization (to put it in academic-speak)
    g
    i
    +2
    10 replies
    Copy to Clipboard
  • Cole

    Cole

    2 years ago
    Hey you all, I'm not sure where to share this, butI'm doing a live stream presentation and overview of how we're building Storyscript's natural language development tool at 3PM EST / 9PM CEST tomorrow (Friday). I would love to see some of my friends here on the stream to ask questions! I aim to keep it high-level and quick paced. Something along the lines of:1. What we're building – overarching design & principles 10 min (+ 5 min for answering clarifying questions) 2. High-level view of the tools we're using to build Storyscript's editor (Rust / WASM, a HTML content editor, & the roles of these tools) 3. How we leverage ECS / data-oriented programming for high flexibility and maintainability There's a lot of overlapping problems with language development, but our approach with a rich text editor give us some new ways to approach old problems! https://www.twitch.tv/storyscript
    Cole
    opeispo
    3 replies
    Copy to Clipboard