←back to thread

174 points tipiirai | 1 comments | | HN request time: 0.285s | source
Show context
Kaotique ◴[] No.42736637[source]
It is interesting, but I really dislike the way it tries to bash every other tech in the blog post, on the homepage and in the docs itself. The tone is very confident, but it will put you open to a lot of scrutiny.

Instead it could really use a lot more explanation on how it works. If you make comparisons make sure they are fair. The image "JavaScript mixed together" and "Strict separation of concerns" is just comparing apples with oranges. Multiple times in the docs it compares a huge complicated JSX like component and replaces it with 3 lines of html and 3 lines of css. I don't believe that it does the same thing.

Some of the claims are strange. It praises standard HTML but apparently you have to use some custom Markdown syntax to write it. How does that add up? And on top of that it also introduces new syntax for loops and variables.

This could all work perfectly fine. But my suggestion would be to talk more about how it works and what are the advantages and less trying to bring down competitors. It could use less grand claims and focus more on what it really does.

replies(5): >>42737254 #>>42737462 #>>42737988 #>>42738672 #>>42754583 #
tipiirai ◴[] No.42738672[source]
> it could really use a lot more explanation on how it works

How Nue works is _extensively_ documented:

https://nuejs.org/docs/

Most of these questions are also addressed in the FAQ:

https://nuejs.org/docs/faq.html

THe Markdown claim is also explained multiple times on this discussion

replies(2): >>42738848 #>>42741775 #
1. lolinder ◴[] No.42741775[source]
You may have already added this in other locations, but it's worth flagging in each comment that you are the creator. I had a suspicion from your tone, but I had to check your bio to be sure.

And, while on the subject of tone: this is not a very effective way to receive constructive criticism. I had exactly the same reaction as OP, as did apparently a lot of upvoters. Communication is a two-way street, but when a significant number of people misunderstand you or can't find the information that you think you put out there, it would be worth listening to them to figure out what you could do to better communicate.

In the end, most people wouldn't even notice or care if they didn't fully appreciate your project— you are the one who is invested in people appreciating it, so it's up to you to take responsibility for the way in which it's communicated. It's not useful to blame other people for failing to understand your docs.