Echo JS 0.11.0

<~>

kali comments

kali 404 days ago. link 1 point
There's an issue open since 9 hours ago, pointing out that the links in the readme -and more- don't work.

In particular, the homepage and demo are 404ing. That means, the only useful information is... not in the README itself, because unfortunately it's full of garbage marketing-speak. The actual product page on the site ( https://codepym.com/products ) does give a better explanation of what this is:

> School Management Software that simplifies school processes. Designed with schools in mind, Grad is all you’ll ever need to run your school smoothly.

By the way, the application seems to be written in Dart.


@benpaul I say this without any animosity: You need to learn how to do these things better.

1. You cannot go around posting the link to your thing if your thing is not ready. First take the time to make sure everything is working correctly, all the links are ok, etc. *Then* you can advertise your thing. If you don't, the first impression for many people will be disastrous.

2. Don't put marketing-speak blurb in your README file. Put a concise description of what your thing is and what it does. The two sentences I copied above are a thousand times more clear and valuable than the paragraph you currently have in the README.

3. Finally, when you do go around posting about your thing to sites like this one -or others- do take a minute to actually write both an understandable title and a short but clear description. "Grad saas app" is completely meaningless and sounds like a Dutch morning greeting or whatever. "Grad edtech software. an saas software" is marginally better but still far from useful to understand what is it that you're trying to say.

In other words: You need to make an effort; you need to really care, not just "paste link, type three shit words, see if it works".
kali 407 days ago. link 2 points
They already posted it to HN a bunch of times in the last few days.
kali 407 days ago. link 1 point
The official docs on useEffect actually point out the problem in the code that serves as the starting point for this article.

However, the solution is as simple as rearranging the code a bit, making the whole article pointless and the convoluted ways to solve this non-problem completely unnecessary.
kali 408 days ago. link 2 points
I don't understand what you're trying to accomplish by re-posting this again and again, but it's kind of annoying.
kali 434 days ago. link 1 point
This article casually ignores that the TS community already:

 - had a quite lengthy discussion about the strict-ness of Omit ( see: https://github.com/microsoft/TypeScript/issues/30825 ), where pros and cons of extending keyof any vs keyof T have been clearly debated.

 - provides a fair amount of implementations of a OmitStrict in various libraries, such as ts-essentials, type-zoo, or others.

With this, I don't mean to imply you shouldn't do this. But the casual tone in which the article ignores all of the previous discussion and the other options just feels too misinformative and may cause other problems elsewhere in a project.
kali 446 days ago. link 2 points
I don't manage the site so I can't really tell you. But as a bystander I can suggest that you take a good read through https://www.echojs.com/about

There:

 - You'll find the rules for submissions, which include not posting summaries, which you seem to have done a few times (posting a link to some dev.to post which only contains a couple of paragraphs about something you already posted a few days ago), or posting only JavaScript related content.

 - You may (or may not) find some ways to contact actual administrators of the site, which may be better than posting this here.
kali 458 days ago. link 1 point
You already posted this 8 days ago. There haven't been any changes or additions to it.

Annoying people will not get you any of those stupid github stars you crave.
kali 476 days ago. link 2 points
Spam

1. Unrelated to JS
2. Typical generic article that ends up making a pitch for their product.
[more]