This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-21
Channels
- # announcements (4)
- # aws (29)
- # aws-lambda (1)
- # babashka (21)
- # beginners (143)
- # calva (47)
- # cider (31)
- # clj-kondo (24)
- # cljsrn (4)
- # clojure (70)
- # clojure-australia (3)
- # clojure-czech (1)
- # clojure-europe (97)
- # clojure-greece (4)
- # clojure-nl (3)
- # clojure-uk (45)
- # clojurescript (70)
- # code-reviews (1)
- # conjure (7)
- # cursive (10)
- # datomic (13)
- # duct (5)
- # emacs (1)
- # fulcro (38)
- # graalvm (1)
- # graphql (9)
- # honeysql (13)
- # integrant (33)
- # jobs (14)
- # jobs-rus (1)
- # malli (7)
- # off-topic (72)
- # pathom (1)
- # re-frame (11)
- # reitit (9)
- # remote-jobs (2)
- # sci (11)
- # shadow-cljs (9)
- # sql (5)
- # tools-deps (5)
- # xtdb (6)
Would people pay for commercial licenses for Clojure libraries that deal with things such as SAML, emails, etc? All the boring bits and plumbing that you have to wade through just to get to something useful.
Iām not talking about low level stuff, more like solving high level problems including eg email validation, monitoring, throttling, etc etc
For me, licensing valuable libraries is okay, as long as the licensing process is not too heavy, I can evaluate before buying and the licensing does not bind me for 20 years. I prefer buying support for open source libraries, but thatās a business model that is easily exploited (as we heard this week)
Guten morgen!
(forgot: Morning)
Thatās a good one. For closed source libraries, bankruptcy of the vendor is a huge concern for companies, this would address that
I like the pricing of jOOQ. Itās free with Open Source databases, and the enterprisier the DBs you use get, the more expensive the license gets, too: http://www.jooq.org/download/
What does it even do? JPA but better?
I've used jOOQ. It's quite nice, but I didn't ever manage to make complex queries not look horrible
Well, SQL is quite optimized for what it does.
And when trying to extract stuff into methods, you can end up with crazy return types like SelectConditionStep<Record4<Long, Integer, Integer, Integer>>
Oh, yes. These times where I had to build a domain model User extends Entity<UserKey>>
and so on. God bless persitent datastructuresā¦
āThese timesā are still relevant for me š«. Searching a way out of those Enterprise-Big-Company projects
Morning. Does anyone have a Raspberry Pi (64bit) here? There is now a non-official binary for babashka: https://github.com/babashka/babashka/issues/241#issuecomment-764009022
I thought about getting an RPi 4, but it sounded like the power consumption was quite a lot higher
magnumDslContext
.select(POI_TYPE.POI_TYPE_ID, POI_TYPE.UUID, POI_TYPE.NAME, POI_TYPE.ICON)
.from(POI_TYPE)
.where(POI_TYPE.UUID.eq(UUID.fromString(uuid)))
.and(POI_TYPE.TENANT_ID.eq(tenantId))
.fetchOne { (poiTypeId, uuid, name, icon) ->
PoiType(_id = poiTypeId, id = uuid.toString(), name = PoiType.Type.valueOf(name), icon = icon)
}
If you're interested, when trying to do something vaguely complex, we ended up with http://djm.blinkenshell.org/jooq_repository_example1.txt , which we refactored to use CTEs to try to make more readable, and ended up with http://djm.blinkenshell.org/jooq_repository_example2.txt I'm not sure if Kotlin has anything that would help with that
We needed to pull out data for the first of the year, and the last day for each month that actually had any data
Plain SQL is hard to beat, but we wanted the type safety of jOOQ... which did come in handy as the database was outside of our control, and kept changing, a lot!
Using Kotlin for the tests also helped for that, val expected = FooRecord.apply { id = 1, foo = 2, bar = 3, ... }
, meant that our tests didn't keep breaking when the database changed
I share your pain, I have a db that is not under my control too, so yes, having JOOQ is superdoopar handy
Does Kotlin support something like dynamic languageās āad hocā datastructures? Oh do you still need to define a static language model (classes) to hold data?
I recently played with golang. I expected it to be hard to do dynamically typed things, but it's incredibly easy just by casting everything to interface{}
:)
but with the Kotlin Dataclass, it takes default's, so I can just do var foo = Foo()
and it'll prepopulate it with name = "" and age = 0
tbh, it's a very nice language, and when I'm working with my fellow co-workers, and in Kotlin lang, I'm quite happy
I think Iād be happy to pay for libs to solve auth etc, but I would want to have the source available to me.
I wonder if it makes economic sense via Patreon/GH sponsors etc to take on this role in a community.
I think what I would want is a system like the one used for Cursive, albeit a bit more complicated in some way, because Iād need access to the source code (at least once I started paying, or when I went into some agreement/NDA with them).
I'm happy (and do) contribute to open source. I'm always very nervous about anything proprietary in my stack
@slipset one of my biggest concerns, too.
The thing I hope my company would be happy to pay for is a security lib that was, well secure.
@slipset how would you know when itās open source?
that itās secure
Iām not sure I understand the question, but any how. Say that https://www.pac4j.org was delivered by a company who sold pac4j licenses to companies. I would probably be willing to pay for that, given that I also had access to the source code of the lib(s) I licensed.
Basically, I want to out-source security and the responsibility for fixing bugs in security libraries to a (knowledgeable) third party.
I guess something like https://www.pac4j.org/commercial-support.html is offering.
@slipset I was refering to the access to source code.
Security evaluation is kind of a social thing, right? I trust latacora based on their reputation and because Iāve met lvh and heās wicked smart, and spending all his time in security. I have no means to evaluate objectively if theyāre actually good at security or not.
So paying a company to deal with security and releasing libraries that I could use, is helping them make such a reputation for themselves and hire good people etc etc. Much better than using a library that some company developed in-house and released after.
Thereās a limit on how much auditing of 3rd-party dependencies on can reasonably do.
It is also nice as a consumer of a security lib to be in a somewhat more formalized contract situation than āIāll fix it wheneverā.
and I'm not sure most commercial companies would have an SLA that would bind them to fixing something in a particular time frame
most companies, like most organisations (and people!) will only be pushed into changing things if their largest donors threaten to abandon them