COMMENTS:
[1]https://en.m.wikipedia.org/wiki/Lynx_(web_browser)
Names are just names, many people have the same names, and projects can too.
/s
Lynx doesn't have a large user base (I think) but it is installed by default on many linux distros. Having to install two programs with the same name is a pain which is only resolved by renaming one of them (at the distro or the user level).
> Lynx doesn't have a large user base (I think) but it is installed by default on many linux distros. Having to install two programs with the same name is a pain which is only resolved by renaming one of them (at the distro or the user level).
This is a fault of the distros. At some point keeping niche software will cause issues and conflicts.
I am not sure I agree with this argument. This gives a vibe of "make place for me, away with the old guard!"
What if someone called their program "vi" with the argument that noone uses vi anymore?
Besides, who decides what is niche and what isn't? Is a program like lynx which offers better accessibility features than mainstream browsers not worth distributing because it's niche?
Blaming the distros for already having software named like what you decide to call yours isn't terribly cooperative.
Figurative "you" of course, not meaning OP here.
Everyone and their brother knows what "vi" is. Many (presumably millions) use it.
How many people would know what Lynx is. My guess is very few.
> Is a program like lynx which offers better accessibility features than mainstream browsers not worth distributing because it's niche?
Its trivial to understand why this is a bad argument (appeal to emotion)
And mine is that it's more than you think. Especially when compared to the number of people who know what vi is. Neither of us have figures to prove our points. My indirect argument was that the fact that lynx is included by default hints that I am not entirely wrong. Your response to that is essentially that distros packagers don't know what they are doing. I won't get in a debate on the competency of people and accept this opinion as yours.
> You took my argument and basically butchered the main point.
This was absolutely not my intention. If I misunderstood your point, please correct me and tell me how I should have read it.
> Its trivial to understand why this is a bad argument (appeal to emotion)
No. The argument for including software that have specific accessibility features is not to appeal to your emotions. The reason for having accessible software is that, as niche as it may be it is useful. No one should care how non-disabled users feel about this, and certainly no one should care whether you or I think this is too niche.
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.
Anyway...
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!
- 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?
There's a lot of internal tools. I don't know what they're written in. I would not be surprised if it's Lynx, but I'm a mobile developer on the TikTok app, and haven't ever looked into it.
I haven't come across any WASM in my time here, but I'm not in a position to declare that it doesn't exist.
Any mobile app designers out there think TikTok has good UX? I mean scrolling video is great, but everything else?
Google products are an absolute mess. They create android, KM, and Flutter for mobile development. They also created MLKit, MediaPipe, and TensorFlow for AI. They're all over the place with their solutions
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.
They’re impressive in their business success given their code quality.
> 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.
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.
`readonly platform: 'Android' | 'iOS' | 'macOS' | 'pc' | 'headless';`
> Not only is the core engine of Lynx framework-agnostic, but it's also agnostic to host platforms and rendering backends ... expand to even more platforms, such as Desktop, TV, or IoT devices.
I think this could be huge! I'd love to see a SolidJS version
Flutter apps don't scroll at 30/60fps on my aging Mate 20 Pro, but that website is fine for me in Chrome.
Sadly I finally ditched my MacBook for a Linux PC since Expo/EAS has liberated me from needing Xcode. I won’t be able to try this out for iOS development.
Or could someone ELI5 / TL;DR? The whole blog post is basically saying how good Lynx is and what problem it solves without telling me much technical details.
Can you also explain what the advantages are over React Native?
I'm not even in the anti-LLM crowd, but that sentence made me shake my head in disgust
If LLMs are going to be as useful as they claim, they have to be smart/flexible enough to adapt to new information.
item_43264957