Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

github.com

Post reply on HN
Print view View original

81–90 of 108 posts

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#81

Post by VectorLock »

arcturus17 wrote: post #29
ithrow wrote: post #17

Built 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…

What do you use for developing the 'front end' of your web apps with Django, do you just generate HTML from templates with Jinja, etc?

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#84

Post by rpcwork »

cutler wrote: post #83

Why do I have to run Docker to run the server locally? This always raises a red "over-engineered" flag for me. Docker is for deployment, not development.

Our giants came before us, swallowed the enormous complexity and presented us with simpler abstraction to build on.

When you move your work across environmental abstraction, these beneficial abstracts tend to show their cracks.

By keeping the production and the development environments similar, my team avoids deployment surprises and disasters. More importantly, we avoid the escalation calls that take you away from the family dinner table.

If you are gonna delpoy in a docker container, maybe develop in the docker container.

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#85

Post by elwebmaster »

Interesting idea but I looked at the sample app and the amount of code it generates looks excessive for the features it provides. Thinking about the effort to maintain and extend this code I am not sure if it would be a good starting point for MVP projects.

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#86

Post by Glyptodon »

qudat wrote: post #73
ithrow wrote: post #17

Built 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'm inclined to agree. This is nothing against the OP but I never reach for boilerplate generators, even ones like `create-react-app`. Here's a great example of why: I do a bunch of research before I started my project ( https://listifi.app - for anyone curious) and decided to go with prisma.js. It looked like it was exactly what I wanted for a REST API built with koa. I've dumped probably a month fulltime on the pro…

I'm curious what you don't like about Prisma?

I like Active Record + Arel (from Rails) a lot, and have found Knex relatively unpleasant in comparison, offhand Prisma has looked more pleasant/usable to me...

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#87

Post by yuvalhazaz »

zappo2938 wrote: post #82

I'm using the same ecosystem with React and Nest.js. Very awesome to see an app built with best practices for JavaScript in 2021. You might have saved me hundreds of hours of work. Why Prisma and not TypeORM?

TypeORM is no longer maintained in a frequency that gave us enough confidence about the future.

See this discussion https://www.reddit.com/r/graphql/comments/duecak/comment/f77...

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#88

Post by smrq »

sombremesa wrote: post #67
arcturus17 wrote: post #63

Earlier quoted context omitted.

> you can absolutely write great software in it I wouldn't question this for a second. Nor that some people may be extremely happy with it. But me personally, for my most common use case (end-to-end monolithic web apps, complete with client and back-end) it feels like it places a higher cognitive burden than the alternatives, due to all the things we're mentioning (eg, lack of an established ORM) > Comparing Django t…

> Well, yea, but that's the point of my whole comment - Node could have a Django or Rails equivalent after ten years, don't you think? It's not that such a thing hasn't been developed, but that by the time such a thing gets developed (for example: [0]), NodeJS devs have already decided they don't like gulp (even though just last week gulp was the new thing vs. grunt), they like webpack; they don't like AngularJS, the…

Five years ago I might have agreed with you. I think it's pretty telling though that the techs you just listed have now been around for longer than Angular or Gulp were ever popular (at least according to my recollection). Seems to me that the churn has slowed significantly; people are generally happier with React and Webpack than their predecessors.

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#89

Post by ZephyrBlu »

VectorLock wrote: post #81
arcturus17 wrote: post #29

Earlier quoted context omitted.

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…

What do you use for developing the 'front end' of your web apps with Django, do you just generate HTML from templates with Jinja, etc?

They said they use Django REST Framework (DRF), so presumably they use a frontend framework and communicate with the backend via API.

Re: Show HN: Amplication – Instantly Generate Node.js Apps with GraphQL and REST API

#90

Post by qudat »

Glyptodon wrote: post #86
qudat wrote: post #73

Earlier quoted context omitted.

I'm inclined to agree. This is nothing against the OP but I never reach for boilerplate generators, even ones like `create-react-app`. Here's a great example of why: I do a bunch of research before I started my project ( https://listifi.app - for anyone curious) and decided to go with prisma.js. It looked like it was exactly what I wanted for a REST API built with koa. I've dumped probably a month fulltime on the pro…

I'm curious what you don't like about Prisma? I like Active Record + Arel (from Rails) a lot, and have found Knex relatively unpleasant in comparison, offhand Prisma has looked more pleasant/usable to me...

This is where our preferences probably differ.

I’m not a fan of ActiveRecord or ORMs in general. I’d much rather write raw sql queries with a little help to improve reusability.

I found Prisma to be super basic. Anything complex like joins or a composition of where’s and ors and it didn’t work.

It also nests related objects where for my purposes I wanted everything to be flat. So if a list has a user associated with it, I want to flatten it like: { list, user }.

I also didn’t like how Prisma has a generate cli to integrate end developer models that must be integrated into your build step to deploy if you’re using typescript.

Its schema cli command worked but in weird ways that I didn’t like. Sharing Prisma types with the client was not automatic. For example, Prisma coverts datetime columns into dates, which sounds nice, but when I send that data as an api response it turns into a string. Now I can’t use their interfaces without plucking the date times and converting it to a string. It just wasn’t as useful as I had hoped.

Knex does exactly what I want and nothing more. All of my raw sql queries were easily converted and worked perfectly. I build the interfaces and knex uses them. There’s no special command that converts their schema format into something I can kind of use.

Their typing was nice once I got it working however, and for simple things it worked fine. I just noticed I had to write a lot of raw sql.

Post reply on HN