This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-03
Channels
- # aleph (2)
- # announcements (13)
- # babashka (7)
- # beginners (36)
- # calva (26)
- # cider (11)
- # circleci (13)
- # clj-kondo (15)
- # clojure (105)
- # clojure-europe (79)
- # clojure-nl (3)
- # clojure-uk (6)
- # clojurescript (17)
- # conjure (4)
- # core-logic (2)
- # cursive (10)
- # data-science (5)
- # datalevin (11)
- # datalog (14)
- # eastwood (6)
- # emacs (2)
- # figwheel-main (1)
- # fulcro (34)
- # google-cloud (1)
- # graphql (3)
- # introduce-yourself (7)
- # jobs (1)
- # leiningen (17)
- # lsp (46)
- # malli (2)
- # minecraft (3)
- # missionary (19)
- # off-topic (31)
- # other-languages (49)
- # polylith (2)
- # portal (5)
- # practicalli (1)
- # quil (77)
- # releases (1)
- # remote-jobs (1)
Morning!
Good luck going back to the battlefield !
HNY everyone, hope you all had some time off and got to spend it with family/loved ones etc.
If you're on macOS you might enjoy this: https://github.com/babashka/obb
I’m in the target audience, I think, but I don’t know exactly what I could do with it.
Excellent. This seems very useful. Do you happen to know where Apple documents their own “standard library”? I.e. what is the MDN for Apple’s JS.
I suggest joining #obb - I think @U050CT4HR is most knowledgable about this API :)
The most authoritative resource is the release notes: https://developer.apple.com/library/archive/releasenotes/InterapplicationCommunication/RN-JavaScriptForAutomation/Articles/OSX10-11.html
There’s also a community-run cookbook: https://github.com/JXA-Cookbook/JXA-Cookbook/wiki
@U050CT4HR Perhaps we can put these links in the README
@U050CT4HR great that there is already an examples folder. I think it’d be really nice with one or more examples in the README, though; really helps fast comprehension of any project, I find. Perhaps even using a .gif showing the visual result of running a script? That’d be really effective in conveying the power of the library, I think.
Just ideas 🙂
@U0AQ3HP9U I totally agree, and plan to. I had hoped to make things more presentable before this got any attention but here we are. 
hahaha thwarted by your own success @U050CT4HR
I’ll let you get to it, then! 😄
If anyone is already taking it for a spin you should probably pull again; I just pushed an important fix.
I’m looking forward to see what can be done with this!
See also examples/gui.cljs. Can you create a GUI using this? Yes! Should you? Probably not!
@U050CT4HR I'm getting:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'NSGetSizeAndAlignment(): unsupported type encoding spec 'G' at 'GPoint}"size"{CGSize}}' in '{CGPoint}"size"{CGSize}}''btw @U050CT4HR if something isn't working we'll blame it on me, if it is working you get the credits ;)
@U04V15CAJ Interesting! That’s for the GUI example?
Reminds me slightly of https://github.com/slipset/applescript
@U04V5VAUN You can now run that script straight with obb without using the CLJS compiler.
Apparently some guy named @U04V15CAJ retweeted something at some point in time.
I donated the account after I didn't have time to post an example each day (the bar I had for myself)
@U04V5VAUN Perhaps write a blog post: following up to the blog post from 8 years earlier, you can now use obb. ;)
Morning! Happy new year!
so, you may get garbage from the backend and your TS client will happily continue onwards (until it blows up)
@dharrigan type systems don't usually span network hops. Though Gary Bernhardt is trying to have a unified Type system across Frontend/Backend so that the type checker works across the whole stack.
Yeah, but I thought (mistakeningly) that if you define a type in typescript, then pull it in via fetch (and declare what the fetch promise returns), then, if it tries to then coerce the information from the network into the type, it would complain at runtime
i.e., if I declare interface Foo { age: number }, then do Promise<Foo> => (await fetch(....)).json(), then if age comes back as age: "foo bar baz" it would blow up when trying to shove the json data into the Foo type.
Ah no, Typescript types go away entirely after compilation, as far as I know. I think there's libraries to try and make these assertions from TS types.
Yup, TIL 🙂 I'm teaching myself some frontend dev during this holiday period, so first time trying out typescript (with solid-js).... 🙂 So, just something I learnt today 😉 Thanks for the heads up on the erasure of the types at compilation - I'll investigate further.
I last had a proper look at TS a few years back and gave up on it after a project since I found out that the only addition over ES6 was a type system, no fixing of JS foot guns or additional data structures/standard library. Perhaps things changed since then.
I think they think that the type system protects you from JS footguns, by Maybe(!) protecting you from nulls, etc.
Our IT department used to leave Mac users alone, but recently they started becoming just as intrusive as they are on Windows, forcing sudden restarts in the middle of our workday giving us no option to cancel.
Like, they will literally initiate a 60 second countdown with no cancel button, force quit everything once it has run out and restart the computer. Then you get to sit there for however long the forced updates take to install and wonder how to recreate your state.
I once privately bought a Macbook Air for my work because the provided laptops by the institute were too slow (downloaded a profile when you logged in from some network drive) and managed by the IT department.
I was a lecturer and when you started your class and logged in you wasted 5-10 minutes of your class
Yeah, many of my colleagues have run into that issue (I work at a university). Also, lots of them do machine learning and will leave computers on overnight only to have all of those hours wasted.