On the discussion of the right or wrong tool, I find it possible that the ability to reason towards a goal is more valuable in the long run than an intrinsic ability to achieve the same result. Or maybe a mix of both is the ideal.
Good work. I've been thinking about this for awhile and also experimenting with letting the LLM do all the work, backend logic plus generating the front-end and handle all front-end events. With tool use and agentic loops, I don't see any reason this can't work where it meets the latency needs (which hopefully could be improved over time).
I've had a flip 3 and flip 5 which both had screen and hinge problems within a year. I love the form factor but just don't take it to the beach.
My flip 5 inner screen is currently unusable so I'm stuck using the small square cover screen which I'm enjoying quite a bit too. I don't know if my next phone should be a flip phone or a small phone, but nothing gets as small or as good hardware as the front cover of these flip phones, vs other small phones
It's the cover screen of my zflip 5 with the inner screen being broken. It's surprisingly usable and I find myself wishing more phones were purposefully built at this size and shape.
> it will be harder to find someone to talk to understand what they were trying to do at the time.
These are my favorite types of code bases to work on. The source of truth is the code. You have to read it and debug it to figure it out, and reconcile the actual behaviors with the desired or expected behaviors through your own product oriented thinking
The only feature I need that would accelerate my workflow that text file editors don't currently have is a column with the last modified timestamp of that particular line, and maybe some color indication to show which lines were modified the most recently compared to others. And this would be based on change, not based on save or commit.