I like the ideas presented, but you can only read so many variations of
> But an unbounded queue isn't a safety margin, it's a debt that keeps compounding [1]
before getting a headache.
I wish the whole thing was written better, because the idea of designing a codebase for humans and our limitations sounds fascinating. It's why I personally love type systems, you can keep less things in your head and let the type checker alert you of any possible errors.
Thanks for the honest feedback. I genuinely wish I was a better writer. The posts in particular are all quite formulaic, but the idea is that they just provide a narrative access to the manifesto itself which is where the real meat of the argument is.
I would please urge you to read further into the manifesto itself but would also recommend you start at the foreword so you can understand the reason for the use of AI assistance in my writing.
There's a section [1] on the page that has instructions, and video [2] too. I had to select the English (US) language to get the option to select ClearFlow.
Thanks. It's available only for the US layout, not UK.
I'm writing down a few impressions:
- the layout is unusual, but I get the motivation. Distances are minimised and letters are arranged so that ambiguity is removed.
- although I'm very slow, I haven't made a single mistake so far. Clearflow allows me to swipe much more accurately than stock gboard.
- the square keyboard layout unfortunately means that half the letters are constantly hidden behind my thumb. As I'm unfamiliar with the layout, this means that before swiping a word, I have to look at the layout, memorise letter locations and plan the movement
- since I write in multiple languages and Clearflow is available in only one of them, I would have to memorise a completely new layout for a language I write in only half the time.
Hi,
Yes I'm in the same boat as you - had to switch to US language instead of UK. I've been addiing the anglisised versions of words to my dictionary as I go along so it's becoming less of an issue over time. Maybe I'll switch to FUTO in order to not have to deal with this anymore. Gboard has one nice feature though in that I have multiple languages enabled so I get correct predictive completion in non-English languages.
For learning ClearFlow, I used the Games app available from the "Clearflow Games" section on their website: https://clearflowkeyboard.github.io/
I also have the issue of the thumb getting in the way so I spent a couple of days playing the games to get my layout memory up and then it became usable without frustration and I'm not looking back now although I occasionally still forget the odd letter location.
The human refuses to do it because another human (the user who opened the issue) also refused to do it. If the user asked the machine to do it, and didn't even bother to verify the output, why should the maintainer read it?
The website seems to have some bugs on mobile, seen on Chrome 147.0.7727.137
- Cannot horizontally scroll the code snippets on homepage when it overflows. The scroll bars appear but swiping the snippet does nothing.
- Footer links are unresponsive (loon, GitHub, MIT Licence links)
- In the changelog page, scrolling makes the hamburger menu hide release dates behind it
- Hamburger close chevron looks misaligned (not sure if this was a deliberate choice)
The UI was a little unresponsive on mobile, and when I opened the "Media" page on desktop I got multiple block rendering errors. Opening the console reveals a syntax error (missing ] after element list) and some type errors.
Also, it looks like you have to get the subscription to use it in any way? It's hard to gauge whether it is for me or not if I have no way to trial it. I found the UI a bit confusing too, I was not sure what I was supposed to do after logging in. As another commentator mentioned, it's asking me to set a reference language but I see no way of configuring it.
Block rendering errors on the media page is new to me. I will look into it.
The reference language error should not be shown (I mean it’s not incorrect, but there is a “no expressions error” that should take precedence).
A video is coming :) I didn’t expect so much interest from a comment in this thread. If you get in touch, I can walk you through it personally, otherwise check back in a couple weeks and there will be a video overview.
> But an unbounded queue isn't a safety margin, it's a debt that keeps compounding [1]
before getting a headache.
I wish the whole thing was written better, because the idea of designing a codebase for humans and our limitations sounds fascinating. It's why I personally love type systems, you can keep less things in your head and let the type checker alert you of any possible errors.
[1]: https://shapeofthesystem.com/posts/2026/05/10/the-queue-that...