-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Is Echo Dead? #1906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
See #1302 The more you use it, the more you support it. :-) |
its been 2 years, when will it come and which big companies are using ECHO? would you share please? I wanted to fix a GO framework for my Company. so querying things |
https://cyanhall.com/top/go-web-framework/ I have not tried but I would guess that all TOP 10 framework are equally good. Some are more idiomatic go and some are "ports" from other languages. Unless you have thousands of request per second performance difference should be non-issue. For example: If your database/distributed cache call is 1ms to another machine and framework routing/middleware overhead is 1-10µs. This would be 0.1%-1% of total time spent on handling the request. Now if you have bigger latency to other services (database/cache) the framework overhead is even less. Obsessing over these kinds of things is bikeshedding. About |
Thank you so very much! can i ask you an off-topic question? |
I do not know about libraries but I would recommend teaching concepts like
thing is that libraries come and go but these fundamental concepts stay the same. |
thank you! and does ECHO has these concepts? |
Yes, some of them apply to Echo also. I recommend checking out https://echo.labstack.com/guide/ |
Thank You So Much! I wanted to make a project like this site {{ refresh if it appears blank }} |
Is the framework dead?
Is it worth using today? Is it maintaining regularly? let me know!
The text was updated successfully, but these errors were encountered: