squash looks lovely. I'm building something simil...

# server

[evanchooly]

squash looks lovely. I'm building something similar for mongodb

[orangy]

I’m not receiving any complaints, bug reports, doc requests, nothing… I can’t believe it “just works”, so it all looks strange to me 😄

[evanchooly]

if i wrote sql apps i'd use this. or jooq.

[indyfromoz]

Using Squash in a project at the moment, really loving it!

[orangy]

Nice! Feel free to give feedback in #squash 🙂

[dave]

@orangy If you want bugs and complaints, you should definitely take Squashy "full ORM" 😉

[orangy]

Well, that’s exactly what I’d like to avoid. ORM is not async-server-friendly.

[dudleyf]

@orangy Since you're asking, how about some docs on squash-graph? :)

[orangy]

PRs are welcome! 😄 Seriously though, my priority right now is #ktor

[roberto.guerra]

how do exposed and squash differ? Their APIs look very similar.

[noone]

I'm new to kotlin and learning spring. Can I use squash with spring?

[dudleyf]

If I knew what the hell was going on, I’d be happy to, that’s why I’m asking 😄 Seriously though, I know you’re focusing elsewhere.

[orangy]

@roberto.guerra squash was my attempt to fix exposed’s API issues that I perceived as important, especially in the area of dialects, but since I didn’t have enough time to work on it, it’s what it is – a working experiment. It lacks ORM, but introduces graph-fetching system.

[orangy]

@noone Though you can, I don’t think squash & spring will be good fit for each other. But if someone wants to work on integration, I’d be happy to guide through the stuff.

[qwert_ukg]

@orangy it should be included into #ktor. Kara reborn 🙂

[orangy]

Kara didn't have anything for sql either

[qwert_ukg]

just mean what kara was a "web framework", any web framework have a DB layer

[orangy]

why would a web framework have a DB layer? There is basically no need to do it, as far as I understand. May be I don’t understand something important…

[dudleyf]

Because “web framework” sometimes means “database backed web application framework” a la Ruby on Rails.

[orangy]

Or it can mean “microservices backed application framework”? 🙂

[orangy]

I believe these two concepts should be independent, so that you can get any web framework you like, any db framework you like and use them in a single app. together with microservices, and what not.

[dudleyf]

There’s something to be said for an integrated stack where all the pieces are tested and designed to work together. On the other hand, Spring.

[roberto.guerra]

I prefer the web frameworks and DB layer to be separate. 🙂

[qwert_ukg]

i guess modern web app have this layer, and web FW should have it too for fastest development, one point of documentation, one dependency etc like as Spring Boot or Laravel or RoR. in over side .NET separate it too e.g. MVC and EntityFramework

[qwert_ukg]

it will be really cool to have one FW for all (all-in-one), and int this time nobody can't stop u too use another DB FW instead of included