This is an early preview of Sandcastle, a new game I am working on. It's a relaxing sandbox (literally) where all you have to do is build the nicest sand castle! 🏖️
You can wishlist it if you want -> https://t.co/9L2GQFNq7b
I'll post more dev logs here and on my discord
@linear I imagine hardly anyone would ever end up in this situation, but I was curious about what happens if you go deep, there's a small UI issue here
It's a little late here, so I'll post more tomorrow and reference inspiration, but happy to say I have a toy version of odyss-cache working with the following tentative API.
cc: @_buildspace@_nightsweekends
Decided to join nights and weekends s5, I'm going to use the next few weeks to explore an idea around cache invalidation management. I'm calling it Odyss.
cc: @_buildspace@_nightsweekends
@chronark@RhysSullivan They can significantly slow down most people's default approach to test suites/linting that follow all non-cached imports they find in them, even if they're irrelevant to the file importing from that barrel file https://t.co/Plp5y19pWg
@rannbouusagi @_buildspace@_nightsweekends I think the one liner is too generic and could be more specific about what makes this game special. It seems to be about collecting items, it might be worth referencing that and then going deeper into why that's interesting in the second part. Hope that helps! 🙂
@sm0junior @_nightsweekends@_buildspace The one liner here doesn't paint a picture for me of what this is. From the tweet text I think it involves donating to people in need, but that's not instantly clear from the one liner. Hope this feedback helps 🙂
@Breakthruapp@_buildspace@_nightsweekends For me this description is not super clear on what this saas actually does. For example what is storytelling in this context, is it fiction, marketing or maybe something else? Hope this feedback comes across as useful 🙂
Decided to join nights and weekends s5, I'm going to use the next few weeks to explore an idea around cache invalidation management. I'm calling it Odyss.
cc: @_buildspace@_nightsweekends
@mattpocockuk's approach is spot on for libraries like this and helps you consider the tradeoffs appropriately. As creator @MichaelArnaldi mentioned in the thread, it's an Embedded Domain-Specific Language.
My current mental model, which the maintainers might disagree with, is this:
Effect should be treated like a new language, like Elm or ReScript, that happens to use TypeScript syntax.
This language has a ton of benefits. Strongly-typed errors. Built-in handling of complex things like concurrency, timeouts, data validation. Awesome composability with less FP bullshit.
Basically, you choose Effect as a new language to work in if you think that TypeScript is too loose. It makes your code more robust, and you ship fewer bugs.
Thank you to all who came to @remix London last night, I hope you had a great time it was lovely to see everyone! Special thanks to @chatsidhartha, @threepointone and @moishinetzer for providing awesome talks and @cloudflare for hosting!