This is nuts! If this advances as fast as AI image generators have, the music industry is going to be affected. This is a crazy tool for song writing inspiration for sure.
Rails. It's all about developer comfort. ruby as a language is a delight to work with. Rails as a framework has all the features I need and then some more. Postgres as the database of course!
No, it is not fair, nor is it correct. The professional response is, that for the most part it is a matter of preference what tools you use and as long as you are proficient with them and you get the work done, it is more important that you can use tools you are comfortable with and accustomed to, because you will be faster.
Nowadays there are few differences between firefox web developer tools and chrome's tools.
IDEs can be powerful tools. To me it seems that in some programming languages they are the default, in others not so much. I don't see much IDE usage in frontend development. But it could be useful when writing TypeScript maybe?
If you're a w3m user, you must surely know that w3m usage is not suuuper common right? Maybe, just maybe, this project is not for you. Not everything is for everyone.
Sure. You can also use lynx. Both browsers already solve the problem of browsing text based web sites on the command line. I am just wondering why you'd want another one, that isn't even a regular browser.
I'm sure lynx + w3m together hold less than 0.01% of the global browser usage.
Why would you even want lynx or w3m when curl/netcat already exists and allows you to view text on the commandline from http/s servers? Because it's more comfortable for you. Just like this tool is more comfortable for you if you just want to visit Wikipedia articles in the commandline.
Some tools are specialized, I'm not sure why you think that's such a bad thing. Otherwise we'd all use netcat to view websites, then you can read most protocols too, not just http/s.
It seems to me that they're explicitly asking how this tool is more comfortable to use than w3m. Not sure how browser market share has anything to do with that.
This tool being specialized to do this one job doesn't mean it's automatically better at it than one with a wider range of functions. For example, in a Wikipedia-only browser you can't open references (without using another application) which arguably results in worse UX.