I had began creating my own sort of thing on top of Hasura which I prefer but this is pretty cool. I'm not at all too big on TS (which is sacrelige apparently) but I'll check this out.
Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
21–30 of 108 posts
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#22I had began creating my own sort of thing on top of Hasura which I prefer but this is pretty cool. I'm not at all too big on TS (which is sacrelige apparently) but I'll check this out.
We already got some feedback from developers who used the generated code to learn Node.js :-) maybe it is your chance to jump into TS
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#23This looks very neat. Why do you require a GitHub account to test it? --- Edit: and after I logged in with my GitHub credetials, I was directed to https://app.amplication.com/github/callback?code=968 [...] which just showed me a 500 error. Hug of Death?
same 500 error for me
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#24Hello, co-founder here: as a backend developer I've had to develop web APIs for various projects over the years. Before I could spend any time on designing and testing my business logic, I had to invest hours into making sure my boilerplate code was valid and provisioning infrastructure, not to mention setting up my cloud environment. We built Amplication so that developers like us could focus on coding the parts tha…
This looks good - seems to be hammered currently?
https://app.amplication.com/ckjuaxw2518112510s6qfb0xi8q shows {"statusCode":500,"message":"Internal server error"} for code download, and has been waiting for a sandbox environment for a while.
But I'll be back to try it again in a few days :)
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#25This looks very neat. Why do you require a GitHub account to test it? --- Edit: and after I logged in with my GitHub credetials, I was directed to https://app.amplication.com/github/callback?code=968 [...] which just showed me a 500 error. Hug of Death?
Sorry to hear that. We will make sure to check the logs. As for the login, we ask for a GitHub sign since we thought it would be most convenient and cost affective at this stage since all users are developers. Also, we use it to send the generated code to your GitHub repo.
Wanted to test too...
I'm getting " Error: Error in connector: Error querying the database: db error: FATAL: remaining connection slots are reserved for non-replication superuser connections " when deploying.
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#26This really closely mirrors my preferred stack, so I'll definitely be taking a close look at this for my next project.
One pipedream I've had with TS backed APIs is sharing the types between the backend and the frontend to prevent duplication. I didn't see anything in the API consumption docs, but is there anything here that tries to accomplish that deduplication?
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#27Wondering how many GQL programmers are aware of GQL injections.
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#28This really closely mirrors my preferred stack, so I'll definitely be taking a close look at this for my next project. One pipedream I've had with TS backed APIs is sharing the types between the backend and the frontend to prevent duplication. I didn't see anything in the API consumption docs, but is there anything here that tries to accomplish that deduplication?
We are using this exact technique on the Amplication server where we automatically generate the models for the clients from the graphQL schema on the server.
When you build your app with Amplicaiton you anyway get a generated code including the models both for the client and the server so you get exactly this OOB.
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#29Built on top of immature overhyped tech (nestjs, prisma, etc...) with lots of issues. Something very common in the JS/NPM that always gives you headaches down the road. There's an arms race to sell hosting through immature buggy magical frameworks in the JS world, so this is to be expected. I'll take the one/two days to set up node, express, postgres with libs for now. What takes up the majority of the time is domain…
I've been developing web apps in Node for a couple years and I'm done with it - I'm all in on Django + DRF now.
I only made the switch a couple months ago and it's amazing how cozy I am with it: everything feels mature, stable and reliable. I reach out for 3rd party packages as needed but it doesn't feel like I'm gluing a Frankenstein together, or that I'm rolling out a bunch of code I don't want to own, or that I'm overthinking for the umpteenth time how I should structure my app. I think after a couple months with Django I'm nearly as productive as I ever was Node.js. Granted that many web dev concepts just carry over, but the feeling is uncanny regardless.
Also, the "language context switch penalty" is a complete myth. I picked up Django by reading two books in 2-3 days, and didn't need to even bother front-loading Python - I just picked it up as I went. I now switch between Python and JS/React seamlessly; I enjoy writing both and I really like the variety (though as dynamic, duck-typed languages maybe they're not that dissimilar). Every thousand characters I type in Python I'll make a silly mistake where I write some JS syntax and that's it - hardly what I'd a call a cognitive penalty.
As it stands, I'd only develop something in Node.js if I really needed its performance characteristics (and then, I may be able to get close to them with Python's asyncio - though I haven't researched this avenue yet so there may be pitfalls I'm not aware of).
All in all, I find it baffling that in over a decade of existence Node.js hasn't produced a web framework that even comes close to Django or Rails.
I do wish OP, Nest, Prisma and all the devs in the Node ecosystem the best of luck nevertheless. I love JavaScript and if someone produces a web framework that really emphasizes developer productivity and happiness I would consider coming back in the future.
Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API
#30“Nodey On Rails”?