91–98 of 98 posts
I recently looked closely at cross platform mobile mobile development. Despite distrusting Google and despite knowing react I chose flutter. I want something fast with close to total cross platform compatibility. Net Maui is not well spoken of. React native seems slow. The only real choice fir my needs is flutter. Let’s see how long it holds up.
Earlier quoted context omitted.
> Would be interested in using this if not for the lack of LLM support. I'm not even in the anti-LLM crowd, but that sentence made me shake my head in disgust
How so?
Are we intentionally reusing project names now? Lynx [1] is a fairly popular tui browser. I guess it doesn’t support ssl or tls, so is now obsolete? W3M [2] is a decent tui alternative that does. Or if you use kitty, awrit [3] is nice, with images and mouse support (it renders chromium in a terminal window) [1] https://en.m.wikipedia.org/wiki/Lynx_(web_browser) [2] https://w3m.sourceforge.net/ [3] https://github.com/…
>Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting. Name collisions are so common that the guidelines tell us not to talk about them. Why would you assume that this is intentional? And then the rest of your post is just about different tui browsers? How is this the top comment?
Earlier quoted context omitted.
Google already did the talking for both of them. It’s called Flutter.
Does Google use Flutter for building Gmail, Google or other major mobile apps?
TikTok is impressively multi-device. It works well on Android, iPhone, Android TV, and web. Compared to Instagram, where the web version has always been behind the mobile version, TikTok really seems to make each device version the best possible.
I'm pretty sure for Instagram it's by design, not because of their technical stack.
Earlier quoted context omitted.
>Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting. Name collisions are so common that the guidelines tell us not to talk about them. Why would you assume that this is intentional? And then the rest of your post is just about different tui browsers? How is this the top comment?
oops, sorry!
Are we intentionally reusing project names now? Lynx [1] is a fairly popular tui browser. I guess it doesn’t support ssl or tls, so is now obsolete? W3M [2] is a decent tui alternative that does. Or if you use kitty, awrit [3] is nice, with images and mouse support (it renders chromium in a terminal window) [1] https://en.m.wikipedia.org/wiki/Lynx_(web_browser) [2] https://w3m.sourceforge.net/ [3] https://github.com/…