Re:Generating a full-stack application from a database
by eatonphil on Tuesday June 16, 2020 @05:12PM
(#23544196)
> First the server is written in Haskell using the Warp HTTP server (aka a compiled language with lightweight threads).
From the PostgREST readme. Even if you generated the controllers with openapi, I'm not aware that openapi will generate you an entire application already hooked up to the db?
> guess this is only as true as saying that you have to deal with Erlang because you use RabbitMQ. Or you have to deal with C because you use PostgreSQL. Same applies with PostgREST, you don't have to write Haskell to use it, only SQL.
In my experience you will undoubtedly end up dealing with the oddities of it as some point. Would you rather deal with oddities in Haskell or in C? For most of the world, for better or worse, C (or Go or Java) is probably more pragmatic.
From the PostgREST readme. Even if you generated the controllers with openapi, I'm not aware that openapi will generate you an entire application already hooked up to the db?
> guess this is only as true as saying that you have to deal with Erlang because you use RabbitMQ. Or you have to deal with C because you use PostgreSQL. Same applies with PostgREST, you don't have to write Haskell to use it, only SQL.
In my experience you will undoubtedly end up dealing with the oddities of it as some point. Would you rather deal with oddities in Haskell or in C? For most of the world, for better or worse, C (or Go or Java) is probably more pragmatic.