I am probably an idiot, but so many tool sites (web, GitHub, ...) don't seem to know how to describe what their tool really does for someone not familiar with the product and maybe not familiar with the class of product.
It all sounds so general. And powerful. And flexible. And Plug and Play.
And I realize these are tools, GraphQL, Phoenix, Ecto that are probably helpful.
And of course, Resources, Authentication, Community, Authorization, Multitenancy, Data Layers, Admin, Extensions, Observability, and Compatibility are necessary features in all things.
And they have sponsors.
And quotes from people who like it.
And its obviously a very nice site, since it let's you opt-in for yummy "essential cookies".
But without using any of the related tools, generic qualities, and wonderful but also generic features, how would I know who would use this, why they would use it. And what is wrong with other tools in the class, that this solves.
Is it a complete win? Or does this tool provide a different tradeoff?
Other than being "better". (I get that "better" is the TLDR.)
Or, perhaps I am an idiot. It is hard to tell, I can't rule that out.
I sorta kinda agree. This landing page likely does well to someone who has just spent half a day ticking each checkbox on their tech stack list with the best library they could find, and then finds this project claiming it has done all that for them. And integrated them already, so they can readily build apps for the use case they have in mind. The pitch is the tech stack itself.
But all they need is a little paragraph giving clear context to technically literate people, of what they are looking at. A chance to educate is not to be thrown away lightly.
I actually want to know. My work takes me places. If I am on a page today, I might need what they have tomorrow.
I am sure they tried, but it is frustrating, and feels myopic, which probably isn't the TLDR/buzzword they are going for.
I tried figure out what I can build with this framework (web apps? native apps?) and what programming language I have to know to use it and after few clicks, also into doc, I gave up.
From the code samples it looks like it might be Ruby, but the documentation doesn’t seem to confirm or deny it either way.
EDIT: I accidentally clicked on the ‘past submissions’ link on HN, and if the titles of its other submissions are to be believed, the language is actually Elixir.
EDIT2: Yes, it’s probably Elixir — the front page mentions it once or twice (though not prominently; I had to search for it).
It all sounds so general. And powerful. And flexible. And Plug and Play.
And I realize these are tools, GraphQL, Phoenix, Ecto that are probably helpful.
And of course, Resources, Authentication, Community, Authorization, Multitenancy, Data Layers, Admin, Extensions, Observability, and Compatibility are necessary features in all things.
And they have sponsors.
And quotes from people who like it.
And its obviously a very nice site, since it let's you opt-in for yummy "essential cookies".
But without using any of the related tools, generic qualities, and wonderful but also generic features, how would I know who would use this, why they would use it. And what is wrong with other tools in the class, that this solves.
Is it a complete win? Or does this tool provide a different tradeoff?
Other than being "better". (I get that "better" is the TLDR.)
Or, perhaps I am an idiot. It is hard to tell, I can't rule that out.