Clojurians Log v2

For example: Could not find artifact org.clojure:clojure:jar:1.12.4 in central ()

Yes, I have also had Maven problems and not sure they are solved yet.

Yep, me too https://clojurians.slack.com/archives/C03S1KBA2/p1778497669446349

yep CI

but all good here I guess ;) https://status.maven.org/

It would be very helpful to see the full exception report for one of these linked in your tmp dir

One CI test failed for me like this (disclaimer: I might be using a very old tools.deps in there)

ERROR in (re-frame-athens-lint-test) (maven.clj:167)
Uncaught exception, not in assertion.
expected: nil
  actual: clojure.lang.ExceptionInfo: Could not find artifact org.apache.maven:maven-plugin-api:jar:3.6.3 in central ()
{:lib org.apache.maven/maven-plugin-api, :coord {:mvn/version "3.6.3", :deps/manifest :mvn, :dependents [org.apache.maven/maven-core], :parents #{[com.github.athensresearch/athens io.github.nextjournal/clerk org.clojure/tools.deps.alpha org.apache.maven/maven-core]}}}
 at clojure.tools.deps.extensions.maven$get_artifact.invokeStatic (maven.clj:167)
    clojure.tools.deps.extensions.maven$get_artifact.invoke (maven.clj:155)
    clojure.tools.deps.extensions.maven$eval22277$fn__22280.invoke (maven.clj:178)
    clojure.lang.MultiFn.invoke (MultiFn.java:244)
    clojure.tools.deps$download_libs$fn__21854$fn__21855.invoke (deps.clj:477)
    clojure.lang.AFn.applyToHelper (AFn.java:152)
    clojure.lang.AFn.applyTo (AFn.java:144)
    clojure.core$apply.invokeStatic (core.clj:667)
    clojure.core$with_bindings_STAR_.invokeStatic (core.clj:1990)
    clojure.core$with_bindings_STAR_.doInvoke (core.clj:1990)
    clojure.lang.RestFn.invoke (RestFn.java:428)
    clojure.lang.AFn.applyToHelper (AFn.java:156)
    clojure.lang.RestFn.applyTo (RestFn.java:135)
    clojure.core$apply.invokeStatic (core.clj:671)
    clojure.core$bound_fn_STAR_$fn__5839.doInvoke (core.clj:2020)
    clojure.lang.RestFn.invoke (RestFn.java:400)
    clojure.lang.AFn.call (AFn.java:18)
    java.util.concurrent.FutureTask.run (FutureTask.java:264)
    java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)
    java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)
    java.lang.Thread.run (Thread.java:829)

more failures here: https://github.com/clj-kondo/clj-kondo/actions/runs/25666680557/job/75340852345?pr=2837 tbh I think it's an intermittent failure with one of mvn's services?

or clojars?

> Error building classpath. Could not find artifact com.pngencoder:pngencoder:jar:0.13.1 in central

For me, It seems that the problem occurs only on Github action

When I run a Docker build (that create the uberjar) locally, I have any issues related to maven

I also had circleci failures

FYI: https://clojurians.slack.com/archives/C03S1KBA2/p1778503009933099?thread_ts=1778497669.446349&cid=C03S1KBA2

I think the most sensible approach here would be to first come up with an interesting project that seems reasonable at the first glance, and then attempt to implement it. You can try building pure knowledge all you want, via whatever means, but it won't stick if you don't practice it. And people are very unlikely to practice anything they don't find interesting, so the project has to be interesting to you. Then it's just looking up stuff on the need-to-know basis that will organically grow your knowledge in this domain.

And it seems to be pretty much exactly how the author of the video did it. Come up with a project, decide on what's necessary at the conceptual level, look things up to see what already exists, read about those components, choose specific ones, experiment.

Just in case - try not to care about novelty or utility at all. So what if you can buy a proximity-based light switch for 3 €, so what if you don't have a way to use it - try to make it yourself if you think it's something interesting. And if nothing comes up at all in terms of a project, just look up something like "esp32 starter kit" on Temu/AliExpress/whatever, spend 50 €, tinker to your heart's content. At some point, you'll stumble upon some barrier that cannot be solved effectively without new hardware - then you simply figure out what you need, buy it, and continue. It's all like Lego, unless you start delving into "high" stuff - high frequencies, high voltage, high current, high density, high precision.

@ben.sless It's one of the greatest single player games I've ever played and I highly recommend you go into it knowing as little as possible because it's one of those rare games that will stay with you long after you've stopped playing.

Also that's exactly what happened to me. I was watching a play through and I stopped and said "no, I'm buying this right now".

That's why I shut down the let's play

Doubt my rtx 980 can handle it

It can. I played it on a 1080 and it looked great and performed great.

Unlike other Unreal games, this one is actually well optimized. You might have to bump settings down but it'll run well.

It's at least worth a try. If the 980 isn't quite up to the task, you'll know within two hours of game play, which is Steam's refund window.

E33 is a wonderful game. imo one of the best, most impacting first 30min of any game ever?

it and cyberpunk are games that stick in your head

and @ben.sless I second the recommendation to go in completely and utterly blind

I'm keeping myself as blind as possible

Maybe ask in #music? There's some fairly esoteric stuff posted there from time to time...

I started watching a play through and stopped when I realized I want to play it because it looks like an amazing game

Lol now that I think about it, Sean, it DOES sound like a band name!! 😆

Yeah it's fascinating. Those devs are my damn heroes. They proved you don't need to be a behemoth company to create a masterpiece.

Here's a fantastic talk on some juicy details on how they pulled it off. Absolutely fascinating. https://youtu.be/t1CrbTx6O6w?si=JpPF4LI6wV3P39IX

THEY LEARNED FROM YOUTUBE TUTORIALS ON THE JOB!

They also used some visual programming framework

it's an amazing achievement

Watching this thread play out, I'm amused (and a little embarrassed) that I thought Expedition 33 was a band 🙂 Spot the complete non-gamer! 😄

It's an interesting meta story of how a small independent team manages to eat AAA's launch

You see, I don't have time to sit down and invest in an RPG. For now, at least. So I'm optimizing for fast and short game play loops. Diving into Mortal Sin.

that's so funny, i much prefer typescript over javascript. js has so many gotchas, the type system helps me fight against it

True, but when I just wanna check something really quickly, TS requires a lot more work up-front so I also tend to dislike this default 🥲.

Thing is, for the problems I usually have with JS, I can't see "typing" solving them. But disregarding that, if I search for Javascript, I'm expected to find "Javascript". Not TS. Especially not when I'm coding something and the LLM starts to spit TS out of nowhere.

I have never tried writing TS functionally, but I'd imagine the proliferation of types to become an unnecessary headache unless any is leveraged maximally.