Why not integrate Exposed with the Spring Data instead? You’re suggesting essentially forking DSLs a...

# spring

[orangy]

Why not integrate Exposed with the Spring Data instead? You’re suggesting essentially forking DSLs and fragmenting community

[oshai]

I am pro to not fragmenting community, what about squash?

[sdeleuze]

1) Exposed seems not an officially supported project.

2) It is mainly based on Active Records pattern which I don't like and don't want to use, so I am not talking about doing what Exposed does, just I like the SQL DSL without code generation idea. Also I think there is also things I would implement differently to make people with Spring background confortable with it.

3) I think it should be possible to use SQL DSL independently of the underlying engine that perform the request.

[sdeleuze]

Like there is various opinions on Kotlin web frameworks, there could be different opinions on Kotlin idiomatic SQL persistence.

[sdeleuze]

Even if they model the same domain

[nfrankel]

@orangy i believe competition is good
people should have choice so they can decide what fit best their context
(i don’t know about exposed, i don’t judge it in any way)