This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # babashka (16)
- # beginners (182)
- # calva (13)
- # chlorine-clover (43)
- # clj-kondo (17)
- # cljs-dev (14)
- # cljsrn (19)
- # clojure (97)
- # clojure-argentina (7)
- # clojure-dev (45)
- # clojure-europe (7)
- # clojure-germany (5)
- # clojure-nl (4)
- # clojure-portugal (4)
- # clojure-romania (5)
- # clojure-spec (46)
- # clojure-uk (21)
- # clojuredesign-podcast (2)
- # clojurescript (159)
- # conjure (28)
- # core-async (7)
- # cursive (13)
- # datomic (17)
- # defnpodcast (9)
- # duct (1)
- # fulcro (45)
- # graphql (6)
- # jobs (7)
- # jobs-discuss (1)
- # juxt (3)
- # kaocha (4)
- # leiningen (12)
- # malli (5)
- # observability (1)
- # off-topic (50)
- # pathom (15)
- # re-frame (16)
- # reitit (5)
- # remote-jobs (21)
- # ring (7)
- # shadow-cljs (166)
- # test-check (6)
- # tools-deps (27)
- # xtdb (2)
Perhaps this is one path towards Clojure on WASM
@ashnur What would that solve? In my mind it would make it more confusing than anything else.
@jayzawrotny it would solve the problem of having only one license
personally, i think the whole idea of licensing is a solution of a problem that only exists because we, as a civilization as a whole, have really bad ideas that we do not want to let go in fear of confusion, but because people with money who act in a serious manner do not allow heterodox thinking in this manner in any other way than multi-licensing, i will choose what is allowed.
I never encountered the word "heterodox" before so thanks for that. Could you please elaborate? I'd like to understand your argument better.
I am not sure if you want to understand what I said in relation to licensing, or in relation to the way humans think and how our thinking (especially the shared part of it) has very old errors in them.
Can't do both 🙂 But if you are curious, I think https://libcom.org/files/__Debt__The_First_5_000_Years.pdf this can give a good overall view of what I think how many opportunities we miss at the moment socially to do what licensing solves in part. As far as I understand, licensing is the way we can monetize directly or indirectly software (and not just software).
And the other is perhaps best explained by Thomas Kuhn in https://en.wikipedia.org/wiki/The_Structure_of_Scientific_Revolutions
My personal take on this is that our brain doesn't care about truth, it cares about utility. It takes a lot of small truths and integrates it into a big lie, which we then share via communication and create society. Hence my point about the 50000 year old mistake, that's how old historians and archeologists and paleontologists say that language is.
I kind of see what you're getting at with licensing. It's a bit inconvenient, especially when my GH already shows I wrote the spacemacs anakondo layer but also who gives a shit who wrote the spacemacs anakondo layer? How about the relation to the way humans think then?
Then in our society we have these nice bubbles where lots of people have a relatively cushioned life where they don't have to think about survival and they don't really have much in the way of negative feedbacks so ideas that are useful are literally ideas that spread the most, not even nice or correct, not to mention true.
Is licensing one of those ideas?
I wouldn't say so, licensing to me by itself is just a tool, I need to see what it is used for to see if it's good or bad.
But the idea that we can own ideas is very much seems like a bad and to be honest, quite a nonsensical idea
Kind of. I think the intention was to protect people who have worked really hard to discover or invent something from an idea, and a more popular entity taking that idea making a worse version of it and being credited for discovering it.
I know licensing isn’t a perfect solution for that, but I see some benefit of having a common or standardized way of communicating the ownership or protection of said ideas.
again, ownership is the bad idea in my opinion. If you have decided that you have such a thing, especially ownership of ideas, then licensing might seem like proper way to go about it. That book from Graeber has a lot to say about ownership, it's also available on audible if you like audiobooks more.
Haha ok, I’ll check out those links.
@jayzawrotny https://www.youtube.com/watch?v=pETCs9Mktus 🙂 very succint way to talk about this, although I am not sure I subscribe to everything the same way Eric does.
i mean stuff like wholesale demeaning anyone who doesn't adhere to the norm "any code with no license should be considered a red flag"
you might be right, but that doesn’t change the reality of what Sean said — in the environment in which we normally work, any code without a clear license is a red flag
What's an example of a bad idea that we do not want to let go in fear of confusion?
maybe this should be moved to #i-am-richard-stallman
see, any hint of criticism and all I get is doubt and mockery, because that's what is engraved into everyone's behavior
it's not that I don't see your point, it's that there are only so many things I can worry about in life, and I'm full
that's perfectly understandable, I am no less full but should we start mocking each other if we are full?
apologies on the mocking
“The reasonable person adapts themself to the world: the unreasonable one persists in trying to adapt the world to themself. Therefore all progress depends on the unreasonable person.”
😮 hey guys, clojure rs is mine ^^ didn't expect to see that. I was hoping to unveil it later, but its definitely exciting to see it posted here
Indeed, the plan is to provide some sort of FFI or interop. I don't get the impression there's really some sort of rust runtime reflection I can tap into, so the plan is to experiment with parsing rust code ahead of time and generating the appropriate wrapper code. I have no idea what kinds of roadblocks I'll run into there, especially as I try to generalize this, so even now I want to be careful speaking on it, but that's the direction I want to head. I'm really glad to see you comment on this, aha
@U2M723H42 I think the joker folks do a similar thing for Go libraries.
I've recently started learning Rust and creating something like this certainly crossed my mind, but nothing more than that
No pressure or anything 😈 😄 @UBCSS6NGK
>:) right now its just very simple, naive reference counting. This will change, and I've got lots of ideas there, but I did not want to make the mistake I've made before of designing everything up front instead of iterating (especially when its harder to really see the eventual shape and bottlenecks of the program), and getting stuck into an endless cycle of designing and not creating. You don't need to manage lifetimes, as this is supposed to be Clojure -- although I'm not opposed to including a lower level, Rust-Clojure you can also drop into and embed, I think that would be cool.
Note, reference counting behind the scenes -- from the Clojure end, its just Clojure, not a lower level programming language (although I assume that's known)
@UBCSS6NGK looks amazing. would be cool to have this in https://github.com/chr15m/awesome-clojure-likes when you're ready!
Ahh that's awesome, I'm so glad! Its pretty young right now, I'm currently implementing Clojure RS's first programs (and, in doing so, beginning on its
clojure.core), but otherwise the version on github has no such core yet with which to build a program. I don't mind when it gets added though