@MinaMarkham I used to have such issues but I swear by the Alexander Technique. It fixes your back through learning better posture for sitting, standing, etc
Notes
- RT @warianoguerra: 📰 Future of Coding Weekly 🎼 Compose Realtime Apps 🧑🏫 Review Jam 🐛 @replayio Time Traveling Debugger ➿ Digital Tape Dra…
Reposted by Steve
Text may be partial · Read original
- RT @ziontree: What do you meme? 🍌 #reactnow https://x.com/ziontree/status/1439271880620449797/photo/1
Reposted by Steve
- @Glench @alexobenauer Thanks @Nadagast for sending me his way!
- @Glench I just got off the phone with @alexobenauer. We had a great chat!
- @Glench Look who submitted it to HN 🙃
- @wilgieseler https://www.youtube.com/watch?v=_CBU8slKeN8
- RT @JanPaul123: Do I know anyone who has experience integrating Chromium into native apps? Using CEF or Electron (or something else)? I wan…
Reposted by Steve
Text may be partial · Read original
- @wilgieseler Do you use telekinesis?
- @ccorcos Someone said something about a triple stores...? 🙃 Another idea is to use a more restricted, performant data structure than a JS array, say "SQLTable", which uses a database under the hood. The reducer function "runs on the server" so we can "recast" it into SQL
- @zachweinberg Uh it's called Google Photos. Just search for "toilet" in the searchbar and delete or archive from there. Too bad you can't build a filter on top of this the way you can for people's faces
- @_ryanbloom Well said. Thanks for watching. I hope you're right!
- fuuuuuuck this so much https://x.com/stevekrouse/status/1438490683548053508/photo/1
- RT @stevekrouse: @ccorcos Well that wasn't hard. I wonder why I didn't start with this 🤦♂️ https://x.com/stevekrouse/status/1438426537171247104/photo/1
Reposted by Steve
- @ccorcos Well that wasn't hard. I wonder why I didn't start with this 🤦♂️ https://x.com/stevekrouse/status/1438426537171247104/photo/1
- @ccorcos Ha, amazing! That's exactly what I'm working on today, doing it in React instead. You're just missing the reducer function that accumulates messages from the stream into an array.
- RT @pomber: Had to build a new blog and some tools to be able to publish this post with the format I wanted. It took some time but it's fin…
Reposted by Steve
Text may be partial · Read original
- @ccorcos Good question ! I don't know how...
Text may be partial · Read original
- PSA: you can join the inside joke by going to @It_nikkimanaj's timeline, and reading from this tweet forward https://x.com/NICKIMINAJ/status/1437532566945341441?s=19
- @OnePlaybookHQ @FISSIONcodes Me too!
- @Glench This is an example of a persistent/realtime open source component I actually used for WoofJS. It was awesome! There should be many more of these! https://firepad.io/
- @Glench I think there are a lot of SaaS companies that could be open-source Compose components, like Intercom and Discourse. The only reason they are companies is because we can't build persistent/realtime open-source components
- @triketora david stole your gene for this to be doubly good at it
- @abanduk (This cyclical style of dataflow is a bit wonky, but it's central to "pure" FRP, and also Compose. Learning more about FRP will help you if that's your stumbling block.)
- @abanduk One way is to create a third piece of state that ingests from each of the two components, and if desired, maps back into each of them. Compose is trying to be flexible enough to allow you to express the merge semantics that are right for your use case
- @Glench One thing Compose *might* be able to unlock is the dream I share with @geoffreylitt of a build-your-own-email-client kit: mix and match components others built in Compose (including a Composified Gmail API) to craft your own email space
- @Glench Ha - you and me both! I'm most excited about people being able to recompose *running components, bringing their realtime, persistent state along with them*, much like you can embed a Tweet anywhere, and its live, and also supports likes from its new location
- @Glench In short: yes to all those, well said!
- @Glench We're prototyping in Haskell and JS/TS simultaneously. The problem with my Haskell demos is that nobody could understand the syntax. The problem now is that the Turbine semantics are giving people trouble...
Text may be partial · Read original
- @Glench The benefits of Compos are the benefits of FP - if you believe in them - which you get from immutability and tightly controlled side effects. Compose brings F(R)P semantics to the persistence layer: immutable reactive backend streams! 🤯
- @alfhir80 @meinte37 What's important to me is that the employee has a say over what they're machine should be. They should have the option to bring their own or have the company pay for one of their choosing
- Addendum: nest the chatApp widget underneath each message for infinite-depth subcomments https://x.com/stevekrouse/status/1437806608030052354 https://x.com/stevekrouse/status/1438084315678715905/photo/1
- @meinte37 Definitely agree to the first two! Haven't had issues with that last one myself, so I'm less passionate about it
- The new benefits stack for programmers: * remote first * async default * no location-based salary adjustments
- @Glench There's a significant chance I misread your question or that my answers came of as flippant. Apologies! Difficult to explain whacky new abstractions in tweets 😬
- @Glench Backend-only API access (ie not putting secrets in frontend code): Create a **function-valued** `ServerBehavior (a ->b)` Then remove the code you used to create it (with the secret) and refer to it by its ID in future front-end code
- @Glench Yes! I do have a story for users / access control: Keeping data secret: encrypt it with the public keys of the people who should be able to read it Keeping writes controlled: filtered out writes not signed by approved users
- @Glench Cool! This is exactly the vibe I'm going for with database persistence in the mix :)
- @abanduk Yes! I have some sketches in the offline-first direction, but the more immediately exciting part is that any Compose component is embeddable anywhere (like how a Tweet is embeddable). The idea is that any Compose app is end-user-scriptable by default
- @moonriseTK Does that clear it up for you? Appreciate your help!



