home.social

#lovebytetcc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lovebytetcc, aggregated by home.social.

  1. Thanks my friends at @FieldFX for adopting the demoparty timezone switcher code! ❤️

    Field-FXmas starts at 7pm GMT.
    It's a fully remote event, with demo showcases, #lovebyteTCC recap and #liveCoding #TIC80 #ByteJam with DJ @gsuberland 🥳

    Join us from wherever you are in the world. Schedule here:

    field-fx.party/

    Poster: mastodon.social/@FieldFX@masto

    See you there!

    (If you're orga/support for a #demoparty, there's a link to the timezoner script at the top of this thread 👆)
    #demoscene

  2. Thanks my friends at @FieldFX for adopting the demoparty timezone switcher code! ❤️

    Field-FXmas starts at 7pm GMT.
    It's a fully remote event, with demo showcases, #lovebyteTCC recap and #liveCoding #TIC80 #ByteJam with DJ @gsuberland 🥳

    Join us from wherever you are in the world. Schedule here:

    field-fx.party/

    Poster: mastodon.social/@FieldFX@masto

    See you there!

    (If you're orga/support for a #demoparty, there's a link to the timezoner script at the top of this thread 👆)
    #demoscene

  3. Thanks my friends at @FieldFX for adopting the demoparty timezone switcher code! ❤️

    Field-FXmas starts at 7pm GMT.
    It's a fully remote event, with demo showcases, #lovebyteTCC recap and #liveCoding #TIC80 #ByteJam with DJ @gsuberland 🥳

    Join us from wherever you are in the world. Schedule here:

    field-fx.party/

    Poster: mastodon.social/@FieldFX@masto

    See you there!

    (If you're orga/support for a #demoparty, there's a link to the timezoner script at the top of this thread 👆)
    #demoscene

  4. Thanks my friends at @FieldFX for adopting the demoparty timezone switcher code! ❤️

    Field-FXmas starts at 7pm GMT.
    It's a fully remote event, with demo showcases, #lovebyteTCC recap and #liveCoding #TIC80 #ByteJam with DJ @gsuberland 🥳

    Join us from wherever you are in the world. Schedule here:

    field-fx.party/

    Poster: mastodon.social/@FieldFX@masto

    See you there!

    (If you're orga/support for a #demoparty, there's a link to the timezoner script at the top of this thread 👆)
    #demoscene

  5. Thanks my friends at @FieldFX for adopting the demoparty timezone switcher code! ❤️

    Field-FXmas starts at 7pm GMT.
    It's a fully remote event, with demo showcases, #lovebyteTCC recap and #liveCoding #TIC80 #ByteJam with DJ @gsuberland 🥳

    Join us from wherever you are in the world. Schedule here:

    field-fx.party/

    Poster: mastodon.social/@FieldFX@masto

    See you there!

    (If you're orga/support for a #demoparty, there's a link to the timezoner script at the top of this thread 👆)
    #demoscene

  6. Here you go! Enjoy a lazy retro-CRT-effect version…

    (probably only works if you view the video larger than a thumbnail on a high res display)

    #LoveByteTCC #FlitterLang #CreativeCoding #RetroComputing

  7. Here you go! Enjoy a lazy retro-CRT-effect version…

    (probably only works if you view the video larger than a thumbnail on a high res display)

    #LoveByteTCC #FlitterLang #CreativeCoding #RetroComputing

  8. Here you go! Enjoy a lazy retro-CRT-effect version…

    (probably only works if you view the video larger than a thumbnail on a high res display)

    #LoveByteTCC #FlitterLang #CreativeCoding #RetroComputing

  9. Here you go! Enjoy a lazy retro-CRT-effect version…

    (probably only works if you view the video larger than a thumbnail on a high res display)

    #LoveByteTCC #FlitterLang #CreativeCoding #RetroComputing

  10. Here you go! Enjoy a lazy retro-CRT-effect version…

    (probably only works if you view the video larger than a thumbnail on a high res display)

    #LoveByteTCC #FlitterLang #CreativeCoding #RetroComputing

  11. Tried something different for Tiny Code Christmas today: an attempt at doing the most literal translation of the “Rasterbars" problem that I can do into Flitter. I was interested in seeing how close I could get to the TIC-80 demo and the starting code.

    The core drawing function is surprisingly close to the Lua original, despite Flitter being a completely different paradigm:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day6 #extra #FlitterLang #CreativeCoding

  12. Tried something different for Tiny Code Christmas today: an attempt at doing the most literal translation of the “Rasterbars" problem that I can do into Flitter. I was interested in seeing how close I could get to the TIC-80 demo and the starting code.

    The core drawing function is surprisingly close to the Lua original, despite Flitter being a completely different paradigm:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day6 #extra #FlitterLang #CreativeCoding

  13. Tried something different for Tiny Code Christmas today: an attempt at doing the most literal translation of the “Rasterbars" problem that I can do into Flitter. I was interested in seeing how close I could get to the TIC-80 demo and the starting code.

    The core drawing function is surprisingly close to the Lua original, despite Flitter being a completely different paradigm:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day6 #extra #FlitterLang #CreativeCoding

  14. Tried something different for Tiny Code Christmas today: an attempt at doing the most literal translation of the “Rasterbars" problem that I can do into Flitter. I was interested in seeing how close I could get to the TIC-80 demo and the starting code.

    The core drawing function is surprisingly close to the Lua original, despite Flitter being a completely different paradigm:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day6 #extra #FlitterLang #CreativeCoding

  15. Tried something different for Tiny Code Christmas today: an attempt at doing the most literal translation of the “Rasterbars" problem that I can do into Flitter. I was interested in seeing how close I could get to the TIC-80 demo and the starting code.

    The core drawing function is surprisingly close to the Lua original, despite Flitter being a completely different paradigm:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day6 #extra #FlitterLang #CreativeCoding

  16. "Tiny Code Christmas" day 4 with #pico8: animated plasma effect in 54 tokens.

    @lovebyteparty #lovebytetcc

  17. "Tiny Code Christmas" day 4 with #pico8: animated plasma effect in 54 tokens.

    @lovebyteparty #lovebytetcc

  18. OK, decided to do the TCC day 2 extra challenge “meta-balls” after all!

    As expected, the rendering is a custom shader, but fed from a Flitter 2D particle system modelling gravity and reflections off walls. I experimented with different output equations looking for the most interesting thing I could do in the remaining characters. I enjoy the starkness of the black bands here.

    Code comes in at a neat 400 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day2 #extra #FlitterLang #CreativeCoding

  19. OK, decided to do the TCC day 2 extra challenge “meta-balls” after all!

    As expected, the rendering is a custom shader, but fed from a Flitter 2D particle system modelling gravity and reflections off walls. I experimented with different output equations looking for the most interesting thing I could do in the remaining characters. I enjoy the starkness of the black bands here.

    Code comes in at a neat 400 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day2 #extra #FlitterLang #CreativeCoding

  20. OK, decided to do the TCC day 2 extra challenge “meta-balls” after all!

    As expected, the rendering is a custom shader, but fed from a Flitter 2D particle system modelling gravity and reflections off walls. I experimented with different output equations looking for the most interesting thing I could do in the remaining characters. I enjoy the starkness of the black bands here.

    Code comes in at a neat 400 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day2 #extra #FlitterLang #CreativeCoding

  21. OK, decided to do the TCC day 2 extra challenge “meta-balls” after all!

    As expected, the rendering is a custom shader, but fed from a Flitter 2D particle system modelling gravity and reflections off walls. I experimented with different output equations looking for the most interesting thing I could do in the remaining characters. I enjoy the starkness of the black bands here.

    Code comes in at a neat 400 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day2 #extra #FlitterLang #CreativeCoding

  22. OK, decided to do the TCC day 2 extra challenge “meta-balls” after all!

    As expected, the rendering is a custom shader, but fed from a Flitter 2D particle system modelling gravity and reflections off walls. I experimented with different output equations looking for the most interesting thing I could do in the remaining characters. I enjoy the starkness of the black bands here.

    Code comes in at a neat 400 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day2 #extra #FlitterLang #CreativeCoding

  23. I am kind of trying to convince myself that finding new ways of doing things and improving Flitter makes these exercises a useful way to spend my time… 🤣

    #LoveByteTCC

  24. I am kind of trying to convince myself that finding new ways of doing things and improving Flitter makes these exercises a useful way to spend my time… 🤣

    #LoveByteTCC

  25. I am kind of trying to convince myself that finding new ways of doing things and improving Flitter makes these exercises a useful way to spend my time… 🤣

    #LoveByteTCC

  26. I am kind of trying to convince myself that finding new ways of doing things and improving Flitter makes these exercises a useful way to spend my time… 🤣

    #LoveByteTCC

  27. I am kind of trying to convince myself that finding new ways of doing things and improving Flitter makes these exercises a useful way to spend my time… 🤣

    #LoveByteTCC

  28. Revisited the fire from yesterday rather than do today's “metaballs" challenge.

    I realised that I could use Flitter's vector maths to calculate a single column at a time. I had to add a new collating mean function, but that’s a generally useful thing. I also leant into it being my own language to add some new convenience syntax for nested loops.

    The result is both smaller and much faster! I can render a 27,000 element grid at 60fps.

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  29. Revisited the fire from yesterday rather than do today's “metaballs" challenge.

    I realised that I could use Flitter's vector maths to calculate a single column at a time. I had to add a new collating mean function, but that’s a generally useful thing. I also leant into it being my own language to add some new convenience syntax for nested loops.

    The result is both smaller and much faster! I can render a 27,000 element grid at 60fps.

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  30. Revisited the fire from yesterday rather than do today's “metaballs" challenge.

    I realised that I could use Flitter's vector maths to calculate a single column at a time. I had to add a new collating mean function, but that’s a generally useful thing. I also leant into it being my own language to add some new convenience syntax for nested loops.

    The result is both smaller and much faster! I can render a 27,000 element grid at 60fps.

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  31. Revisited the fire from yesterday rather than do today's “metaballs" challenge.

    I realised that I could use Flitter's vector maths to calculate a single column at a time. I had to add a new collating mean function, but that’s a generally useful thing. I also leant into it being my own language to add some new convenience syntax for nested loops.

    The result is both smaller and much faster! I can render a 27,000 element grid at 60fps.

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  32. Revisited the fire from yesterday rather than do today's “metaballs" challenge.

    I realised that I could use Flitter's vector maths to calculate a single column at a time. I had to add a new collating mean function, but that’s a generally useful thing. I also leant into it being my own language to add some new convenience syntax for nested loops.

    The result is both smaller and much faster! I can render a 27,000 element grid at 60fps.

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  33. Had a go at the @lovebyteparty day 1 "extra" TCC challenge for today: "Fire”.

    I'm using Flitter's counters as a mechanism for storing the state. Unfortunately, I couldn't get the code much below 450 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  34. Had a go at the @lovebyteparty day 1 "extra" TCC challenge for today: "Fire”.

    I'm using Flitter's counters as a mechanism for storing the state. Unfortunately, I couldn't get the code much below 450 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  35. Had a go at the @lovebyteparty day 1 "extra" TCC challenge for today: "Fire”.

    I'm using Flitter's counters as a mechanism for storing the state. Unfortunately, I couldn't get the code much below 450 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  36. Had a go at the @lovebyteparty day 1 "extra" TCC challenge for today: "Fire”.

    I'm using Flitter's counters as a mechanism for storing the state. Unfortunately, I couldn't get the code much below 450 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  37. Had a go at the @lovebyteparty day 1 "extra" TCC challenge for today: "Fire”.

    I'm using Flitter's counters as a mechanism for storing the state. Unfortunately, I couldn't get the code much below 450 bytes:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #extra #FlitterLang #CreativeCoding

  38. Played a bit with #pico8 for "Tiny Code Christmas" day 1 - ended up with a christmas tree with red bulbs and animated snow.

    @lovebyteparty #lovebytetcc

  39. Played a bit with #pico8 for "Tiny Code Christmas" day 1 - ended up with a christmas tree with red bulbs and animated snow.

    @lovebyteparty #lovebytetcc

  40. Played a bit with #pico8 for "Tiny Code Christmas" day 1 - ended up with a christmas tree with red bulbs and animated snow.

    @lovebyteparty #lovebytetcc

  41. Played a bit with #pico8 for "Tiny Code Christmas" day 1 - ended up with a christmas tree with red bulbs and animated snow.

    @lovebyteparty #lovebytetcc

  42. Played a bit with #pico8 for "Tiny Code Christmas" day 1 - ended up with a christmas tree with red bulbs and animated snow.

    @lovebyteparty #lovebytetcc

  43. I should be leaving this alone since I have, you know, actual work to be doing, but here's a variation on the tree that better distributes the branches and manages to look a bit more tree-like, while coming in at exactly 400 bytes. New code pushed over the old.

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding

  44. I should be leaving this alone since I have, you know, actual work to be doing, but here's a variation on the tree that better distributes the branches and manages to look a bit more tree-like, while coming in at exactly 400 bytes. New code pushed over the old.

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding

  45. I should be leaving this alone since I have, you know, actual work to be doing, but here's a variation on the tree that better distributes the branches and manages to look a bit more tree-like, while coming in at exactly 400 bytes. New code pushed over the old.

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding

  46. I should be leaving this alone since I have, you know, actual work to be doing, but here's a variation on the tree that better distributes the branches and manages to look a bit more tree-like, while coming in at exactly 400 bytes. New code pushed over the old.

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding

  47. I should be leaving this alone since I have, you know, actual work to be doing, but here's a variation on the tree that better distributes the branches and manages to look a bit more tree-like, while coming in at exactly 400 bytes. New code pushed over the old.

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding

  48. It's @lovebyteparty Tiny Code Christmas time again! Day 1 is “Making Shapes” and the example is a xmas tree.

    I’ve made mine out of 20,001 cones with recursion. Recursive functions are something I've added to Flitter since last year, so it's a good first example.

    Excluding comments and the code to record a video, this is 399 bytes. I'll try and stick to less than 400 like last year and see how far I get. Code here:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding

  49. It's @lovebyteparty Tiny Code Christmas time again! Day 1 is “Making Shapes” and the example is a xmas tree.

    I’ve made mine out of 20,001 cones with recursion. Recursive functions are something I've added to Flitter since last year, so it's a good first example.

    Excluding comments and the code to record a video, this is 399 bytes. I'll try and stick to less than 400 like last year and see how far I get. Code here:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding

  50. It's @lovebyteparty Tiny Code Christmas time again! Day 1 is “Making Shapes” and the example is a xmas tree.

    I’ve made mine out of 20,001 cones with recursion. Recursive functions are something I've added to Flitter since last year, so it's a good first example.

    Excluding comments and the code to record a video, this is 399 bytes. I'll try and stick to less than 400 like last year and see how far I get. Code here:

    github.com/jonathanhogg/flitte

    #LoveByteTCC #Day1 #FlitterLang #CreativeCoding