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)
The Lynx project was originally named independently without thinking this far ahead. Since so much code and so many users already rely on it, we decided to stick with the name rather than change it just for open-sourcing.
You can call it lynx all day long, but it won't be lynx in the Ubuntu repositories as that name is taken, and as you can see above, there are no duplicates.
>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?
I can't tell if this is satire or a hidden advertisement for various tui browsers? A project that is a "popular tui browser" (for the literally dozens of people that use tui browsers?) does not have ownership claim to the name of a big cat genus which has 4k+ other results on GitHub with the same name.
Lynx is a well-known project which has been around for far longer than Github even existed - since 1992, in fact - which is in any case irrelevant, since it's not developed on GitHub: the commits for ThomasDickey/lynx-snapshots are snapshots of the code from the website proper.
I remember listening to a Syntax FM[0] with Zack Jackson from ByteDance, which mentioned this framework briefly. Some quotes and notes from that part of the podcast:
- All ByteDance products, even native apps, are web-based
- They have an in-house framework called "Lynx" which is essentially their version of React Native[1]
- "All apps are Lynx apps. Everything is a Lynx app. It's all backed off the same stack."
- This approach allows them to maintain a unified architecture while having specialized teams focus on different aspects (algorithms, compiler, kernel, etc.)
I work at ByteDance (though not for long). Most of the "sexy" part of the app is native, or C++ crossplatform for things that would normally be in C++. I'm not sure I'm allowed to share what Lynx is used on, but it's a small subset of the app.
I went to watch the podcast – he's heavily overplaying how much cross platform web dev is used on the native platforms. He doesn't seem to be in the biggest channels for both iOS and Android developers (the largest 'IOS'/'Android' release/global channels).
Apple and Google need to talk. They need to collaborate on something truly native to put an end to these bloated frameworks. My goodness the amount of engineering work being put into terrible mobile experiences is worse than how much Nasa is spending to look for water in space.
Any mobile app designers out there think TikTok has good UX? I mean scrolling video is great, but everything else?
Ah, yes, the framework from the dominant browser vendor, that happens to eschew everything good about the browser, to achieve marginally-improved typography, by rendering the whole site in a canvas tag. That should certainly be our #1 model for cross-platform development.
Silly nitpick but wouldn't this be more like asking a crack dealer if this particular crack is great? No matter what their answer, the fact there is a crack epidemic tells you the real answer. People aren't always wanting top shelf crack, some times the hood crack is the good crack.
"We should repeat the same code in multiple languages" is a pretty weird thing for professional pride. Try to be a better engineer instead of promoting gate keepers' platforms and give up "quality" as their responsibility.
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.
Got curious enough to wanting to give it a go, so on the quickstart page it says:
> Lynx Explorer is a sandbox for trying out Lynx quickly.
And then it asks me to use either the iOS Simulator or the Android Simulator, which based on experience, neither are made for anything resembling "quickly".
Anyone know if there are any "pure-web" instructions around? Skimmed around the docs, website and repository but didn't find anything that looked like it was made for just web setup.
> iOS Simulator or the Android Simulator, which based on experience, neither are made for anything resembling "quickly".
It's not adb / avd or some device emulator. It's an app that you install on your device, and then it can load your app from your development device using a link. I was able to run it in 5 minutes without having android studio or any other android development kits on my laptop.
I see there's Lynx for Web[0]. Does that also adhere to the two-threads model (one for UI, one for background)? Also, is this something that React/Native may adopt itself one day? Curious to know if this is a technique that may be adopted by the React ecoystem itself, or if it's just too far outside the bounds of what React is supposed to handle.
I'm also a little confused about how to get started. According to the docs you have to embed it into an existing app[0], but the quickstart suggests otherwise[1].
Seems interesting. Coming from the react native world, competition is good! This seems to have a from scratch layout engine, which is pretty exciting. It looks like it supports some of the more recent/advanced CSS features. It also has a javascript engine based on QuickJS.
I can't wait for a more technical deep dive into how this works and compares to react native.
Readit News
[1]https://en.m.wikipedia.org/wiki/Lynx_(web_browser)
[2] https://w3m.sourceforge.net/
[3] https://github.com/chase/awrit
152007
152007
You can call it lynx all day long, but it won't be lynx in the Ubuntu repositories as that name is taken, and as you can see above, there are no duplicates.
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?
The kids who built this are probably younger than the Lynx project and likely don't know it exists.
I would have stolen a name like Transmission, or Bing instead.
And has done (in various forms) since at least 2001!
https://en.wikipedia.org/wiki/Lynx_(web_browser)
https://en.wikipedia.org/wiki/Links_(web_browser)
Dead Comment
- All ByteDance products, even native apps, are web-based
- They have an in-house framework called "Lynx" which is essentially their version of React Native[1]
- "All apps are Lynx apps. Everything is a Lynx app. It's all backed off the same stack."
- This approach allows them to maintain a unified architecture while having specialized teams focus on different aspects (algorithms, compiler, kernel, etc.)
[0]: https://syntax.fm/show/860/module-federation-microfrontends-...
[1]: The one being released, in the podcast they confirmed they would be open-sourcing it this year
What I assumed from the podcast is that there's a lot of internal reusable tools in C++, and the web-based stuff is mostly about the UI layer.
Is there a lot of WASM to use both at the same time?
Any mobile app designers out there think TikTok has good UX? I mean scrolling video is great, but everything else?
You wouldn't ask a doctor if she thinks crack is great, right?
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.
> Lynx Explorer is a sandbox for trying out Lynx quickly.
And then it asks me to use either the iOS Simulator or the Android Simulator, which based on experience, neither are made for anything resembling "quickly".
Anyone know if there are any "pure-web" instructions around? Skimmed around the docs, website and repository but didn't find anything that looked like it was made for just web setup.
It's not adb / avd or some device emulator. It's an app that you install on your device, and then it can load your app from your development device using a link. I was able to run it in 5 minutes without having android studio or any other android development kits on my laptop.
[0] https://expo.dev/
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.
[0] https://github.com/lynx-family/lynx-stack/tree/main/packages...
[0] https://lynxjs.org/guide/start/integrate-with-existing-apps....
[1] https://lynxjs.org/guide/start/quick-start.html#quick-start
As far as I can tell, it has the same model, at least judging by the directory names (web-worker-runtime, web-worker-rpc, web-mainthread-apis, etc).
I can't wait for a more technical deep dive into how this works and compares to react native.