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

Prisma Raises $12M Series A

prisma.io

Post reply on HN
Print view View original

101–110 of 114 posts

Re: Prisma Raises $12M Series A

#101

Post by gsvclass »

gsvclass wrote: post #100
purplerabbit wrote: post #90

Earlier quoted context omitted.

Are there any tools out there that provide generated GQL APIs with auth provided via middleware? This looks nice, but I'm hesitant to use anything this config-file driven

That almost describes Super Graph. It's not exactly config file driven it can be used as a library within your own GO code and it's configured via a config object. In fact if you look at the example here we're passing null (nil) for the config since unless you want to do something more complex out of the box it just works config is not needed. https://supergraph.dev/docs/home#using-it-in-your-own-code

The config file is for when you use Super Graph as a standalone service that you can just deploy to Cloud Run, App Engine, Digital Ocean or whatever. The standalone service is the same core compiler library with a lot more valuable add-ons like auth middlewares, compression, etc.

Re: Prisma Raises $12M Series A

#102

Post by steve_adams_86 »

nogabebop23 wrote: post #80
bovermyer wrote: post #14

The graphic under "Database tools are stuck with legacy paradigms" made me chuckle. Just because the tech under the "Legacy" column isn't the new hotness doesn't mean they're suddenly irrelevant or even a bad choice.

They graph control vs. productivity and then throw their solution way up near the top-right in the success quadrant, with a bunch of questionable "benefits" and very little justification. It's not like I need to choose between an ORM, query builder and plain SQL either... Why can't I use any of them as the problem dictates?

Yeah, that graph is not something I can take seriously. It feels like they’re trying to convince me with pictures when they should be letting the product speak for itself.

In my experience, not much software is an outlier in performance like they’re claiming here. There are some standout projects that I really love and depend on (Postgres, rust, typescript, react), but even those aren’t ‘top right quadrant’ solutions. They also don’t claim to be, as far as I know

Re: Prisma Raises $12M Series A

#103

Post by steve_adams_86 »

jrumbut wrote: post #42
bovermyer wrote: post #14

The graphic under "Database tools are stuck with legacy paradigms" made me chuckle. Just because the tech under the "Legacy" column isn't the new hotness doesn't mean they're suddenly irrelevant or even a bad choice.

Yeah when I got there I went from curious to put off. That was the place to put an example showing something impressive rather than an iffy summary of web dev trends. I clicked around a bit. I heard a lot about motivations but couldn't figure out a specific situation where I would be really happy to be using Prisma.

This is exactly it. I know prisma developers are here, and if I could express one concern to them, it’s that the content I saw was pretty fluffy and I left without a clear idea of why it’s worth adding into my tool chain.

Re: Prisma Raises $12M Series A

#104

Post by hervelabas »

addandsubtract wrote: post #8

How does Prisma compare to Objection?

Prisma is a Query Builder, not an ORM (like Objection). We chose this approach since ORM suffer from the object-relational impedance mismatch problem (described here: https://en.wikipedia.org/wiki/Object-relational_impedance_mi...) We explain this in more details here: https://www.prisma.io/docs/understand-prisma/why-prisma#orms... or there: https://dataguide.prisma.io/types/relational/comparing-sql-q...

Re: Prisma Raises $12M Series A

#105

Post by hervelabas »

lordofgibbons wrote: post #43
kevas wrote: post #13

I’m not seeing why I’d use this over sql. Can someone please enlighten me as I find this to be much more gobbledegook than sql.

My first instinct was to say type safety, but you don't really get that with JS either way. Maybe it would be popular for new engineers that don't feel like learning SQL. Same reason why MongoDB got popular.

> My first instinct was to say type safety, but you don't really get that with JS either way.

You get type safety if using it with TypeScript though: this is where Prisma adds a lot of value. Compile-time warnings, ease of refactoring...

Re: Prisma Raises $12M Series A

#106

Post by disgruntledphd2 »

yagodragon wrote: post #68
pmart123 wrote: post #63

Earlier quoted context omitted.

Same thing happened with Python for data science in 2023-2015. ie reinvent SQL using Python DSL.

Have you tried jupyter notebook + pandas dataframes? You just import a csv and you can explore, clean, manipulate data and make any sort of calculation using a real programming language. On top of that you can use something like seaborn and create visualizations. Then you click print pdf and you're ready. It almost feels like cheating. You can say all you want about how fast,optimized and superior SQL is, but the pyt…

Not the OP, but I have.

I've spent years doing the work that you specify above, and pandas & notebooks are probably one of the least good tools for it. SQL is super fast and useful (and everyone understands it, at least in the data world), while dplyr and ggplot2 are basically a DSL for this work, while pandas is an irritatingly bad clone of base-R which manages to keep the bad parts of both Python and R, while having the good parts of neither.

I really feel like you should try Rmd with R if you like the notebook flow, as it's similar but much much better.

If you really want to stick with Python, then org-mode is a much better notebook than anything else.

Re: Prisma Raises $12M Series A

#107

Post by sorenbs »

SkyPuncher wrote: post #86
sorenbs wrote: post #65

Earlier quoted context omitted.

I'd suggest you watch the Prisma Day talks when they are published or give it a try. If you are a grumpy HN troll, then Prisma might not be for you, and that's okay. SQL is great for many cases, and you might not need to expand your horizon. If you do choose to look into Prisma and have serious thoughts on how we could improve, then I would love to get on a call to talk about it (contact info in bio).

I just cannot wrap my head around the co-founder reacting this way in a thread about his company. I too don't understand what I would use this product for. That doesn't mean it's a bad product, I just don't have a personal need for it. I don't really like eating grapefruit. If you're a grapefruit farmer, it doesn't mean you farm a bad fruit. Lots of people like grapefruit. I just don't like it personally. Calling som…

Kevas is asking why he would use Prisma instead of raw SQL. There are numerous user testaments on this very page from developers explaining why they prefer Prisma over raw SQL. But it is much more fun to just call us "gobbledegook" instead of engaging with the people who are right here.

If you scroll down the page, you will see a different thread where Kevas compare Prisma to left-pad.

Kevas is a grumpy HN troll, and I have no patience for that.

As you will see from all other interactions on this page, on twitter and on our 30.000 developer strong Slack community, we engage happily and constructively with anyone who comes with curiosity and an open mind. But if you come with negativity we will ask you to find another community to hang out in.

Re: Prisma Raises $12M Series A

#108

Post by disgruntledphd2 »

SkyPuncher wrote: post #84
nogabebop23 wrote: post #81

Earlier quoted context omitted.

>> If you are a grumpy HN troll I guess I am, since I expect a new company with a confusing value proposition to show me why they're better than 50+ years of proven RDBMS technology vs. an "OK Boomer" watch a video and "serious questions only". And you WORK for this company? Better develop a thicker skin...

> And you WORK for this company? Better develop a thicker skin... Not only does he work for this company. He co-founded it. Unbelievable response from a co-founder. I've had my reservations about Prisma (I don't think it solves a problem for me), but this pretty much discourages me from using it entirely.

To be fair, you're not going to get a fair and balanced viewpoint about a product from a founder.

Re: Prisma Raises $12M Series A

#109

Post by pmart123 »

yagodragon wrote: post #68
pmart123 wrote: post #63

Earlier quoted context omitted.

Same thing happened with Python for data science in 2023-2015. ie reinvent SQL using Python DSL.

Have you tried jupyter notebook + pandas dataframes? You just import a csv and you can explore, clean, manipulate data and make any sort of calculation using a real programming language. On top of that you can use something like seaborn and create visualizations. Then you click print pdf and you're ready. It almost feels like cheating. You can say all you want about how fast,optimized and superior SQL is, but the pyt…

I have a significant amount of experience with both of them. For pandas, it is fine for initial exploratory analysis (input, plot, reshape and export, etc). However, it's API has inconsistencies and subtle "features" around silent data coercion that make it hard to use in production. Seaborn is much nicer to work with than matplotlib and Jupyter is useful for making interactive presentations. So I believe Pandas/Jupyter have a place, but then there was a tendency to create a Pandas-like wrapper for all data retrieval such as:

https://github.com/ibis-project/ibis https://github.com/blaze/blaze

Re: Prisma Raises $12M Series A

#110

Post by hervelabas »

desmap wrote: post #73
nikolasburk wrote: post #47

Earlier quoted context omitted.

TypeGraphQL and Prisma are not really comparable though. Prisma is an open-source database toolkit (much like an ORM), TypeGraphQL is a GraphQL schema construction library (like `graphql-js` or `@nexus/schema`), they solve very different problems! You can even combine Prisma with TypeGraphQL if you're building a GraphQL server that needs to access a databases. In that case, you'd use Prisma Client inside your TypeGra…

They can be compared in terms of who dictates the model/is the leading source of truth. I saw that you integrate with type-graqhql but the integration hasn't convinced me yet, somehow type-graqhql loses its elegance with the resulting architecture. Besides, did you sponsor type-graqhql's maintainer to collaborate with Prisma 2?

> They can be compared in terms of who dictates the model/is the leading source of truth.

You can also use introspection to keep the database as the source of truth for the model, and lean on the Prisma schema for type safety if you prefer.

Post reply on HN