Clojurians Log v2

I would not buy an Apple either. The M1 CPU sounds awesome but their OS has become too much of a walled garden.

I don't any of us would have expected Microsoft to become so much more open and supportive of OSS while Apple became more and more hostile to developers... I remember when Microsoft turned up at one of the MongoDB conferences and everyone was like "wut?" and they gave a keynote talk about all their OSS work and how supportive they were about MongoDB and Azure...

I've been using a Surface Pro X (Win10/aarch64) for a while, so I hear your JavaFX pain. One thing I've used to work around it is https://github.com/djblue/portal if you haven't tried it yet. In my case portal is usually running in a JVM process in WSL2 and I connect to its localhost port manually from a native Windows browser or vscode webview.

I'm going for a workstation this time around. Right now my biggest problem is graphics card availability / price.

Although I'm still cautious and can't really see myself using their products that aren't fully OSS in a serious way any time soon with their EEE approach that can still be seen today.

Not to hear one of my friends going through it... He's written off about a working week trying to get productive and decided to stop for now...

I'm waiting for the 16 inch model that can drive two screens 🙂. My 2012 MBP has been in need of replacement for years now but I've held off doing so due to a) butterfly keyboard and b) impending transition to ARM. So it's really great to hear that the M1 model works well for folks (with some of the tools that I like to use) and I can't wait to get one for myself later this year.

https://twitter.com/msexcel/status/1356965673784795143

)) coincidentally in my toy language that mimics excel LAMBDA already available as FN with the same syntax ) oh… and LET is available as WITH (syntax is the same as well), cool

https://twitter.com/onbeyondlambda/status/1358614009906417666?s=09

Hello, @eval2020 and I are looking for 2 more people to mob program with, so we can work together on our programming skills. Clojure, functional programming, data oriented programming, refactoring, test driven development, etc. The method: Weekly session of remote mob programming. We might call it gang programming. Sounds more bad-ass, being part of a gang. Also, there will be 4 of us, so it’s kind of like the gang of 4, isn’t it? When: Tuesday, 12:00 UTC. PM me if you are interested.

that's true, and they introduce their own tradeoffs - they are not appropriate for the kind of high throughput app that clojure excells with

eg. you can use cljs instead of clj in an aws lambda, but it only saves you total time if your job is short and computationally simple

Web people. I want to GET information from a web server. SO I'm thinking I want a GET, but I need to send data that will determine what information comes back. A little 3 property json object

{
   "ropeId": 25,
   "firstSegment": 1000,
   "lastSegment": 1350
}

And relaly I should change my WEB API web method to be a POST.

Is there a reason you don't want to just send these vars in a query string? So ?ropeId=25&firstSegment=1000&lastSegment=1350

in this case since their is only 3, I think I will do that

but what would you do if say I had 10 ? And the URI gets a bit cumbersome?

or had a complex object

Cumbersome in what way? You can express arbitrary nesting in a query string with square brackets:

?parent[daughter]=A&parent[son]=B&grandparent[child][grandchild]=xyz

oh, i wasn't aware of that!

thanks

for sure!

also flat arrays with [] e.g. x[]=1&x[]=2

There are times when it might be reasonable to require a POST, e.g. for consistency with endpoints in a larger API. But you should weigh it carefully against benefits of GET, like being able to leverage caching and share URLs easily.

you cannot send a body with GET, the "normal" thing is that the URI is structured to include the information that your object carries (as path and/or query params)

are the nestings with [] part of the HTTP spec, or a convention that's widely used?

Yeah, I've changed it to put the params in teh URL. So what was Postman doing somethign funky then? My web method was marked [HttpGet]

hmm, I was wrong - a GET can contain a body, but the spec says the body can't be meaningful

weird

Convention, the spec allows you to repeat any names, so really all query parameters should be multivalued, but to make it easy most libraries treat them as single values, which then caused people to go back and invent this new marker for parameters they want to be multivalue

it seems like grandparent[child][grandchild]=xyz would be simpler as grandparent.child.grandchild=xyz

it would be simpler as a request body

the initial question was about GET, and the content of a GET body isn't supposed to influence the result (if I understand correctly)

and switching to POST just so you can use a request body for parameters also seems less than ideal

it seems complicated

https://stackoverflow.com/questions/978061/http-get-with-request-body/983458#983458 you can see the UPDATE at the end