📕 subnode [[@jakeisnt/2023 09 27]] in 📚 node [[2023-09-27]]
  • Wednesday, 09/27/23 ** 14:46 So much of writing React code is reconstructing state machines with particular primitives.

Is it better to use an abstraction like 'xstate' and rely on a state machine abstraction than to make it explicit? ** 14:47 I don't have a strong enough foundation to build a WebGPU UI framework thing. I barely even know what I want from a UI framework.

  • First: I have to continue building my personal website and add more primitives, more abstractions, logic for transitions. Get comfortable with my own workflow.

  • Build a couple of applications with Next.js or other 'state of the art tools'. Not splash pages or toys. Professional-looking applications.

  • Try building a mobile app or some sort of mobile interface for one of those abstractions.

  • Learn from using those multiple paradigms. Try to figure out what could be better. Try out those Rust Web UI experiments and whatever Swift is doing.

Only after doing these things will I be prepared to revisit all of that graphics rendering stuff!!!!!!!!! ** 16:20 I love Figma. Blown away by how responsive it is every time I use it. Can't wait for the experience to get closer to code.

Feels like user interface style systems should be redesigned 'figma-first'. Flexbox - and similar responsive systems - are great, sure, but we can add those retroactively. 'Convert to responsive component' or something atop of the mockup. So much of this mockup - any mockup - could be trivially converted to code if we had the right system, but this is only possible if the UI framework is tightly coupled to the design tool.

I want this to be real. ** 20:37 The Apple keyboard feels so shallow compared to my other devices; the huge amount of resistance that the X-T3 puts in front of my fingers makes these keys so touchy by comparison, with so little travel... being human is about getting used to our tools so quickly. Joel was shocked that I had a Swedish keyboard - but for me to adjust to it took no time at all.

Let's talk about camera gear.

I can tell that the Fuji's sensor is better - or that, at least, it injects some magic into the colors of each photo - and that's helped shape my style and take good photos.

However: those buttons are painful to press. It's genuinely difficult to change exposure compensation without reassigning a dial, and settings can't be quickly flicked into place; it's either one click at a time or a rough, forced transition for a very different setting. This is not the camera for fast photos.

I know the Ricoh wins, but let's break it down - I want a camera that:

  • Can be shot one-handed
  • Has IBIS to catch movement and enable one handed shots
  • Fits in my pocket or is otherwise unobtrusive when bringing it around
  • Has a versatile focal length
  • USB-C charging
  • Fast lens
  • Quick changing settings

Today it became so obvious how obtrusive the Fuji is - I have to keep it on the end of its 'leash' - camera strap - to guarantee that the image is stable, given no IBIS; the camera's a bit heavy to hold one-handed - tires my arm just enough to want a second hand sometimes - but that isn't much of a problem. Everyone around me reacted to me holding a camera; looked my way, gave me a weird look, tried to hide a bit, posed a little bit... maybe it's just imagined but the Fuji provoked a different reaction. This bus driver stared at me for ten minutes as I took photos around Slussen - and she wasn't even in the photos! I kept having to change settings and miss shots, too... bring the hand up to the camera or the camera down to the hand, make adjustment, repeat. Not a fun process.

📖 stoas
⥱ context