Some constructive feedback to the folks who made this webpage, and perhaps the user who submitted it:
I’ve spent about 15 minutes trying to answer the question “what is this thing, and what are the tradeoffs of using it?”, which I think is a question most developers would want to be answered, and I’m having a hard time saying I’ve found out.
The landing page does convey that it’s some kind of tool for building cross platform applications, that much is clear. The natural next question is: why about is better/worse/different from the assortment of existing tools that are in this space? The blog post mentions a number of such tools, but doesn’t really explain what this tool’s relation to them is. Some questions that would be great to get answered right away:
If I use this thing what language am I going to be writing in? (you can find this on the blog post, it’s actually not on the home page anywhere. I guess people could guess from the domain name)
Is this a webview kind of thing?
Lynx is “web inspired”, I figured out it’s javascript based, how much of the typical web API can I expect here? W3C DOM? Custom document model? Do I have the use the lynx-react thing, or could I bring react-dom along if I wanted to?
What’s the interface to native code look like? Can I ship my own native code with an app?
Probably most importantly: performance is heavily advertised as a selling point. How exactly are we getting this great performance? What allows Lynx to be faster that say phonegap, flutter, or react native? Is it? I don’t think anyone is going to be willing to believe that these other projects perform worse than lynx because of the incompetence of their authors, at least not on a marketing page’s say so, so what is being traded?
I thought it was about the text based web browser. It is not.
Some constructive feedback to the folks who made this webpage, and perhaps the user who submitted it:
I’ve spent about 15 minutes trying to answer the question “what is this thing, and what are the tradeoffs of using it?”, which I think is a question most developers would want to be answered, and I’m having a hard time saying I’ve found out.
The landing page does convey that it’s some kind of tool for building cross platform applications, that much is clear. The natural next question is: why about is better/worse/different from the assortment of existing tools that are in this space? The blog post mentions a number of such tools, but doesn’t really explain what this tool’s relation to them is. Some questions that would be great to get answered right away:
Firefox consumes circa 180 % CPU when I open this site.
Previously