This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-05
Channels
- # babashka (14)
- # beginners (62)
- # calva (1)
- # cider (54)
- # clj-kondo (3)
- # cljdoc (15)
- # cljs-dev (2)
- # clojure (180)
- # clojure-europe (5)
- # clojure-italy (4)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (39)
- # clojurescript (85)
- # core-async (9)
- # core-logic (1)
- # core-typed (5)
- # data-science (27)
- # datomic (2)
- # emacs (15)
- # figwheel-main (98)
- # fulcro (26)
- # graphql (15)
- # helix (1)
- # jobs-discuss (26)
- # kaocha (1)
- # off-topic (54)
- # other-lisps (1)
- # re-frame (21)
- # reagent (1)
- # reitit (3)
- # shadow-cljs (49)
- # spacemacs (12)
- # specter (5)
- # xtdb (2)
in haskell, how does one translate {:lines [] :pictures []}
as a composite type, ala class Page { lines; pictures;}
I’ve been writing java all week, refactoring some configs that are parsed from files to java classes, since some subset of configs is shared between different services
a week of juggling stupid class hierarchies when in clojure it would have been just loading config as data T_T
@vlaaad socially: don't know, technically: https://clojure.github.io/clojure/javadoc/clojure/java/api/package-summary.html
@danieltanfh95 That would be something like data Page = Page { lines :: [Line], pictures :: [Picture] }
what’s good in types vs schemas? technically type classes are just schemas?
@danieltanfh95 type classes are more like protocols in Clojure
im just trying to understand why use spec over types/protocols
Talking as someone who likes Haskell and clojure.spec. Haskells type system is less expressive, but gives you compile time guarantees. clojure.spec is very expressive (its just arbitrary predicates, right), but because it is, usually is only offering runtime checking
that makes spec a good fit for clojure, it does not impose the rigidity of a type system on a language that aims to be flexible
If that makes any sense
any thoughts on this?
The question "does this meet specification" or "is this provable" isn't just useful at compile time concern imo. I predict more modern languages will blurr this dynamic even further.
if you head over to future of coding slack people discuss lanagues that seem to do just this. But it takes decades for the changes to seep in. I predicate some big company will promote a language that will do this by 2030. But i have also just randomly been predicting things in hopes of getting one right for the last couple years. I predicate ill get at least one prediction right by 2025. see how easy that is...
Any recommendations on best practices for setting up authentication for web apps? I want something that will works both on-prem and “in the cloud”, and I’ll probably want to set up Oauth2 and 2FA eventually.
Dont roll your own auth server. Everything past that depends on your budget, plateform, etc...
we use keycloak which has a ton of authorization stuff that we ignore and just use auth through the tokens/claims/jwts
I’ll take a look at Keycloak, thanks 🙂
is there a way to save the state on a ssh agent between idk computer restarts? in particular it seems i have to start the agent and add a key:
e.g $(ssh-agent -s) && ssh-add -k some_key
I'm working on an emacs-like editor. I have a similar windowing system to emacs with "windows" (the rectangles that divide up a screen) and "buffers": the things that go in the windows and basically provide all ui/functionality. "Buffers" in my app aren't necessarily just for displaying text and could be anything. Trying to think of a better name for "buffers" which doesn't feel right. Any ideas for a good alternative name for "buffer"? I've been using "app" but not in love with that either. Thinking about "mApp" ("mini app", implemented as clojure map), not sure how I feel about that either.
“frame” is related concept
similarly, “viewport”
I believe a frame in emacs is what most OSes refer to as "windows", ie the thing you drag around in main OS gui
i mean, there are only so many good words. I wouldn’t depart from historical usage unnecessarily, but it might be better to use a good descriptive word than inventing a new one or using a less apropos word
I was looking at other jargon from architecture, “metope” is interesting.
this is other jargon from architecture, just because you are not familiar with it, doesn't mean it's non-existent or invalid 😛 😄
I know someone who is working on a windowing GUI library which is going to get that name probably 😉
treasure