This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (99)
- # announcements (2)
- # babashka (37)
- # beginners (111)
- # cider (4)
- # cljsrn (5)
- # clojure (51)
- # clojure-australia (2)
- # clojure-chicago (3)
- # clojure-europe (141)
- # clojure-nl (2)
- # clojure-provo (2)
- # clojure-spec (48)
- # clojure-sweden (2)
- # clojure-uk (26)
- # clojurescript (34)
- # conjure (1)
- # core-logic (5)
- # cursive (16)
- # datomic (2)
- # events (2)
- # fulcro (54)
- # graphql (13)
- # jobs-discuss (116)
- # kaocha (14)
- # meander (101)
- # off-topic (41)
- # pathom (6)
- # planck (3)
- # re-frame (53)
- # reagent (10)
- # reitit (1)
- # reveal (13)
- # shadow-cljs (35)
- # spacemacs (22)
The quicktime player (or the built-in screen capture thing in later version) produces huge files and takes very long to process. I’m curious to see if there’s better alternatives.
Oskar Wickstrom, of haskell fame, has this: https://owickstrom.github.io/komposition/
Maybe not Haskell fame, but he’s used this project as a vehicle for talks on property based testing and stuff.
The reason I want to do this is that I’d like in our remote team to be able to share snippets of work in the same way we’d do if we were in the office. From editor shortcuts to workflow tips to bug reports etc.
Re yesterdays Google outage. I just read that the Auth service went down and took everything with it. Surely that is actually a good thing in the sense that now we really know that Auth is used and anything that kept on working at Google doesn't depend on Auth. just my 2 cents.
so many people on here sponsored by Cognitect I'm worried that if I congratulate them all individually that I'll miss someone out. 🙂
I'm happy to be sponsored. But I also feel a bit sorry for the folks who are not yet sponsored but perhaps should be. Then again, anyone can sponsor anyone.
I realize that my sponsorship application at github was stuck at this docusign process somewhere. This was a nice reminder for me today to finalize it.
The possibility of making a living from open source is becoming more and more a reality if things keep moving in this direction.
without needing to freemium it > we depend on an open source product who is now rewriting to Rust and will charge heavily for some features we're using
I prefer to keep my "products" without freemium, since I will have to do no additional work for this and it's more accessible to those who can't afford sponsoring or don't want to decide yet
I was super surprised to get sponsored. There are so many people in the community that put in a lot of time on stuff that the community benefits from. I guess I need to think about this as a recognition that the work I do through clj-commons is valuable to the community.
@slipset I was going to suggest that you could consider writing a proposal for Clojurists Together to put more organizational work into clj-commons, since I do think that's valuable.
I could also see Clojurists Together sponsoring onboarding of new developers on existing vital clj-commons projects
The “problem” is that the sponsoring doesn’t really change much for me. Since I have a full-time day job, more money doesn’t necessarily give me more time.
I thought that was true for me with Clojurists Together, but I have found that the sponsoring motivates me to finish tedious tasks that I would not do for free without sponsoring.
I have a 4 day workweek which gives me more time for OSS. But if things keep moving in the right direction, I could see myself taking on a sabbatical of 2 days critical support for the company and the rest of the week OSS. And then see from there.
The last two years it's been mostly 4 days commercial work and 3 days OSS "work" (out of free will)
But currently the income from OSS is not yet at a level where I'm courageous enough to take this step, although it's growing significantly and I could probably feed myself from it at a bare minimum level.
What’s certain is that the sponsorship definitively tells me that the work that I do is important and that it should be continued and improved.
@slipset Maybe OpenCollective is a good model for clj-commons. People can donate and you decide how the money is distributed to developers. Fully transparent.
And that I now actually have some motivation/tool/whatever to go to my employer and ask/demand for more time to work on this.
Or better, “The community is willing to pay me this much for the work, how much are you willing to chip in in terms of hours”
One thing I'm currently trying to find out is how to view this money: is it a gift and should it be treated like this for taxes? should I pay income taxes over it?
Even gifts can be relevant to taxation.
yes, the question is: which category does this belong to. OpenCollective is pretty clear: I send an invoice for services, they pay me out and I pay income taxes like any other company I do business with
At least in german tax law it does not depend on an invoice. That would be nice to tell my client “just send money!” if there is no invoice - no taxes 😛
But it can make a difference regarding VAT. Still I think any tax administration would assume this is a business if you’re not carefule and then the paymount would due for VAT.
That’s actually true.
(Should have known as my main client is in the US cough)
But assumed you get a sponsorship by a european found this could be a problem.
I'm getting this money from Github, I can't track where all the individual donations are coming from.
I mean, I could go on every profile on Github but this doesn't give me the legal info of every individual sponsor / company
With OpenCollective this is way easier since I get paid by OpenCollective, not from the sponsors directly
Paying taxes is good. It shows that there is income 🙂
I wonder if the money comes from github it basically them paying you. 🤷
Btw. I can see how some sponsorship would allow me to address all the accumulated issues with liberator without the preassure of “I’m doing that for free. I could have charged my client five thousand million bucks for the same time!”
Exactly. This is what I mean with: finishing the tedious stuff because someone is paying for it.
@ordnungswidrig thanks for liberator btw. Using it at work, and interacting with it daily 🙂
You would be surprised what my backlog for “liberator2” looks like. It’s huge. But there is no time
yes, that’s on of the things. And getting rid of the cumbesome multimethod response generation which makes me add some “util” functions to all project where I’m using it.
@slipset Also non-local-returns, e.g. be able to return a “412” from any decision.
the multimethods are not a pain-point for us I think. It just sits there and does its job.
@slipset if you need to add custom headers and stuff it can be tricky
@borkdude well, @malcolmsparks contributed substantially to liberator (not only the name) before he created yada.
A couple of things that have shot us severly in the foot:
1. non-ns’d kw, as we returned maps from our fns that had
:status which was string.
2. deep merge. We happened to return our
system as the truthy value for some of the decision points. That was rather slow.
One think I don’t like about liberator is that it ties the idea of a “decision graph” to the specific implementation. This prevents async or good integration in servers like pedestal. (Although most run ring handler functions, which liberator creates, well)
So, since liberator doesn’t have namespaced-kws, we add stuff to the context under namespaced keys
@slipset yes, these are on my list. To my defence, this was basically the first clojure project I’ve every created. It suffers from a lot of bad design decisions. But I need to stick with it because compatibility. That’s why there will be no “liberator 2” but a spiritual successofr.
@ordnungswidrig oh yes, apex is going to be swagger-centric I think
@slipset I am! But when people suddenly using it in production 😱 You inherited a lot of reposibility 😛
@borkdude Juxt was hit by the requirements of real world software development 😉
@ordnungswidrig Now imagine taking on aleph and manifold…
I just realize I even did a talk about this topic https://www.youtube.com/watch?v=fTBEMpmFFmw
Holy cow, that’s already 5 years ago?
I still had boring hair.
Re using it in production. That was our choice. And, since it’s OSS we’re free to fix things.
It's interesting to see how many libs are "not perfect" , and while there are in some regards, more "perfect" or "optimized" solutions, the "not perfect" libraries remain useful and popular because they work well for the majority of use cases they were initially designed for.
And often the libs that are available first, stick in a community. There is a price to pay for migration, not only in a project, but also in a community. Leiningen is great but boot never left the niche.
deps.edn however took over quicky. I think because the price to pay was lower than migration to boot.
(Which says exactly nothing about the quality of boot, btw.)
I think deps.edn adoption is also pushed by that it is the "official" tool brought forward by Cognitect
We're leaving boot at work, although it has served us well. We have the impression it's no longer maintained really
Yes, this is all about the “perceived price”. Official tool by cognitect reduces the “price”.
on that. I’ve been thinking about switching from compojure to something else ever since I started at ardoq three years ago, for no other reason than that I thought a datadriven router would be “better” for some measure of better. But the cost of switching out compojure was always to high, and it wasn’t really a pain point for us.
And even though I do have a reason now for changing from http-kit to aleph, that’s probably never gonna happen.
http-kit is also one of this libs that I deem "not perfect" but still useful and popular. since I adopted it in babashka (both server and client) I had on-going doubts if I made the right decision because it has limitations: 1) blows the heap with big requests/responses, 2) no http2 support, ... I've come up with alternatives that are "better" but for bb usage http-kit may actually fit very well: people aren't going to write "big" apps with it and the binary size it yields is as small as it gets for the functionality it provides
it's clearly not for advanced usage, I guess for testing and simple uses it might be ok
it's in http://com.sun.net so maybe it's not available everywhere, not sure
should be ok: https://github.com/openjdk/jdk/blob/master/src/jdk.httpserver/share/classes/com/sun/net/httpserver/HttpServer.java
it's risky as in implementation detail, but maybe it's a risk worth taking. I also use some of this in babashka
They've been in there for proverbial (or literal) decades now, pretty sure the oracle/open jdk won't drop them. But if you're on other implementations they may not be available. Then again not sure who's still really maintaining a jvm that can compete. Is IBM's still a thing? IcedTea?
It used to be that they at least tried to keep the details of these sun classes secret, but the implementation is open now so not really that secret any more.
com.sun can disappear w/o Snorcle telling you about it whereas the main language should be much more stable. I know from some other libraries that the disappearance of some com.sun things caused a real problem for them