HN user

da_rob

182 karma
Posts7
Comments30
View on HN

Well-written article!

I wish there was some kind of standard to tell CLI apps what features to expect from the system pager, so they can act accordingly …

Right now, apps can talk to the terminal to check for feature support, but all of that falls apart when the output is piped to a pager. (Do we support inline links? ANSI colors? Sixel support??)

Shameless plug, specifically regarding Sixel support: I needed a pager with better image support than just less -r and made https://github.com/roblillack/lessi

Wow, this project (and actually the whole thread here) is awesome. Love it! Our (iPad-based) kitchen timetable[1] is nothing compared to the work (and money) Joel sank into this.

If someone wants to go the easy route towards something like this: iPad (Air 1, I think) is connected to the charger 24/7 and runs in Kiosk mode. Application is just a React website hosted on Vercel, client credentials are stored in localStorage …

[1] https://roblillack.net/unser-stundenplan-family-timetable-vi...

For complex scenarios (i.e. the user interacting with the UI while there are some long-running processes in the backround doing this, too), managing the state quickly gets unwiedly: You need to write callback code everywhere that carefully has to inspect the current status of all other activities and might then updates 10s of widgets accordingly.

With the reactive approach you are able to write a single rendering function that describes the interface for any given state and the framework takes care of the rest (when to call that function, what "input" to give it).

It's just way easier to wrap my head around this and after working with React it is hard to go back. Hence the experiment to see if something comparable could be done in Go.

While I agree, that the virtual widget tree has a certain overhead, the typical desktop app you would create with Spot probably does not have 1000s of components—more like ten to twenty probably. Compare that to the immediate mode GUIs that currently are en vogue, that re-render all controls all the time.

Spot does not have any optimizations regarding render performance at the moment and it might never be necessary to add them.

On the other hand, due to the reactive programming model, I really like how state management get a lot clearer—especially when working with multiple goroutines.

Biome 3 years ago

The possibility to use dprint plugins (Dockerfile, TOML, Markdown, custom ones) would be awesome.

Biome 3 years ago

Congrats to the team, the rebrand was overdue!

I'd love to see some kind of collaboration or interoperability with dprint in the future.

True.

I think the issue was that there was lots of uncertainty for people that actually want to keep their Google account for Google Photos other other products and that do not care for the custom domain (anymore). The official wording before this change was: “upgrade and pay or ..... Photos ‘may’ not work anymore”

Thanks for the suggestion! I added Zoho Mail and Tutanota to the list of services to try.

Honestly, though, my gut feeling about Zoho is not that good: Whenever I hear the name, it seems to be some kind of negative story.

A quick search on HN led to this: https://news.ycombinator.com/item?id=18059792 (worth reading the comments). I even remember someone here talking about having done a due diligence that didn't end too well—can't find the comment, though.

True.

Since I got introduced to this simple but effective visualization (in my 30s!), I tend to use it everywhere.

Out of the “chart generation” apps listed in the catalog, only Vizzlo seems to support it: https://vizzlo.com/create/waterfall-chart (and Tableau, I suppose, but IDK if I'd count this as a simple chart generator). I did not check the listed charting libraries.