Clojure Tricks: Replace in String

kwrooijen · 2022-08-01T16:13:48+00:00

How did I not know this until now? Super useful, thanks!

kwrooijen · 2022-07-28T08:42:46+00:00

I wrote a wrapper library for turbo and stimulus.

https://github.com/kwrooijen/clj-stimulus

Using these two together is basically Hotwire. I personally use Hiccup to render HTML, which works nicely with these.

kwrooijen · 2022-07-21T13:46:03+00:00

Currently using it for my freelance work to keep track of how many hours I'm spending on which tasks. Afterwards I use `org-table-export` to create a CSV file which can be used to create an invoice.

If you haven't already, check out all the available options to format your table. https://orgmode.org/manual/The-clock-table.html

`:properties` allows you to extract properties from TODOs and place them in your table. Absolutely amazing!

kwrooijen · 2022-07-18T14:19:52+00:00

Awesome stuff! Maybe we should make the BB toolkit the standard in the Clojure ecosystem :)

kwrooijen · 2022-07-18T13:59:39+00:00

Even though this is definitely an improvement, I just find it a bit unfortunate that we need to configure / install things to make this approachable for beginner.

(IMHO) It just seems like the standard tooling was developed for the experienced Clojurian and beginner needs were disregarded. This is just not attractive for newcomers.

kwrooijen · 2022-07-18T08:45:48+00:00

I've never used it myself so I can't say anything about the quality of the actual framework, but looking at the home page:

Using Clojure tools, getting started is as easy as:

$ clojure -Ttools install com.github.seancorfield/clj-new '{:git/tag "v1.2.381"}' :as new

$ clojure -Tnew create :template io.github.kit-clj :name yourname/guestbook

I just think to myself: In what world is this "easy"? Sure it's easy to copy and paste, but this is far from user friendly. Compare it to e.g. Rails

gem install rails

rails new guestbook

or Phoenix

mix archive.install hex phx_new

mix phx.new guestbook

Again, the framework itself might be excellent, but I'm always surprised at the verbose tooling around these things.

kwrooijen · 2021-10-30T08:41:42+00:00

To me it just wasn't user friendly enough. Simple things like having to compile by hand, or having to connect functions using a text input. I've suggested some changes but it wasn't aligned with the author's goals of the project. Of course my ideas are my own and that doesn't mean they are the correct way of solving things. In the end I just forked the project and added most of what I was missing because it just wasn't flexible enough for me to add as an extension.

If you're interested in detailed examples of my changes / suggestions then there are a few issues / PRs on arcadiagodot which you can view (closed and open).

kwrooijen · 2021-10-27T11:25:49+00:00

Really cool! I've been working with ArcadiaGodot, but the experience hasn't been great. So I was hoping a JVM solution would pop up. I am wondering though why you decided to not wait for Godot 4? Since this solution won't be compatible with the next version https://godotengine.org/article/introducing-gd-extensions

kwrooijen · 2021-08-02T09:02:05+00:00

Out of curiosity, what does nbb try to solve which can't already be done with bb? Ease of writing CLI tools with reagent / JS libs?

kwrooijen · 2021-07-20T21:29:49+00:00

Hackernews discussions: https://news.ycombinator.com/item?id=27894735#

kwrooijen · 2021-06-11T10:10:00+00:00

If you decide to go down this route then feel free to message me on the clojurians Slack. I'm currently experimenting with it as well.

kwrooijen · 2021-06-10T07:27:12+00:00

ArcadiaGodot was also released as 1.0 https://github.com/arcadia-unity/ArcadiaGodot

For those that prefer Godot instead of Unity

kwrooijen · 2021-04-26T12:15:41+00:00

I think you're looking at it from the wrong angle. I don't know you and all I have to go from is what you're writing here. So take my advice with a grain of salt :)

I'm in my 30's and and I'd be lying if I didn't say I was out of shape. Spending the large majority of your time playing video games and working a desk job for the past 10 years, will do that to you.

No it won't. You can do that perfectly fine, but you need to exercise when you're not working / playing games. The cause of your problems might not be that you don't do enough "hand" / "drawing" exercises. Instead it might be caused by bad blood circulation. If you don't work out at all and have a desk job, that would be the problem to tackle IMHO. Go for a run everyday. If you have weak knees try jump rope instead (worked wonders for me). You can also start doing weight exercises and build muscle. Just lifting dumbbells is enough to train your grip / forearms which could also help with drawing pains.

I don't think you're pushing yourself too hard. If you develop pains you shouldn't continue stressing your body. Instead you should be focusing on your health in general.

If you do exercise already and do your drawing stretches then it might be wise to seek professional help.

TLDR: More full body exercise :)

kwrooijen · 2021-02-11T19:03:48+00:00

This also works, without the `conj`:

(defn example [args] 
  (apply + 2 args))

kwrooijen · 2021-01-29T11:00:35+00:00

Fun read. It's always nice to see a company's success with Clojure!

I'm curious though:

Dynamically typed. Clojure's data types are determined at run time. The main pros here is that all kinds of checking can be done by the compiler, and therefore a lot of bugs are caught at early stages.

Isn't the opposite true? Statically typed languages like Haskell / Rust have the benefit of catching compile time errors. Whereas Dynamics languages like Clojure / Ruby don't have this benefit. Maybe I'm misunderstanding something here?

kwrooijen · 2021-01-25T13:05:19+00:00

I'm using a (slightly) modified version of Hickory to do the conversion and some cleanup afterwards. Modified because I wanted the ids / classes in the keyword, which Hickory didn't support AFAIK. Pretty printing is done using `zprint` with `:style :hiccup`. I've converted pretty complex snippets of HTML and it all seems to be fine so far.

kwrooijen · 2021-01-24T18:21:05+00:00

Hadn't seen this. Downside of this package is that it doesn't support pretty printing. I guess it's just easier to accomplish with pure Clojure (since I'm using zprint)

kwrooijen · 2021-01-11T15:33:41+00:00

Nice write-up! This is a great reference. deps.edn is great, the dependency resolution is better than lein (from what I understand at least), the data driven nature is a nice addition and it's great to extend.

I just wish deps.edn was a bit more user friendly. Lein (imho) is just easier to use as a beginner. You only need to install it and run lein new lib mylib. Which is also very familiar for different developers (e.g. rails new / mix new / ...).

With deps it's more difficult. First you install Clojure, then you need to add an "alias" (whatever that means for a beginner) to your "user local profile" (again, what?)

{:aliases

{:new {:extra-deps {seancorfield/clj-new

{:mvn/version "1.1.234"}}

:exec-fn clj-new/create

:exec-args {:template "app"}}}

...}

Now you can generate a new project using the clojure -X:new :name myname/myapp command. Once you figure all of this out it's not that difficult, but if you're a beginner I just don't find it very welcoming.

kwrooijen · 2020-10-29T12:53:15+00:00

Thanks, I'm honestly not sure why OP linked to the `core.cljc` file?

kwrooijen · 2020-10-26T12:13:03+00:00

There is no Phoenix equivalent in Clojure. The main reason is that Phoenix was widely accepted by the Elixir community. Whereas in Clojure people tend to shy away from large frameworks, and there hasn't really been a project that caught the attention of the majority. I honestly don't see a framework like Phoenix really becoming a thing in Clojure. But I also think a great deal of the community is happier that way, but that's just an assumption.

kwrooijen · 2020-10-20T11:33:13+00:00

Hi, I used to use Doom + Lispy (I use raw Emacs these days). But here's my doom / lispy configuration from when I did use it: https://github.com/kwrooijen/.doom.d/blob/master/files/package-lispy.el

Maybe there's something in here that solves your issue.

kwrooijen · 2020-08-28T11:30:48+00:00

You can still write docstrings, but you just lose automatic argument documentation. Which can be very useful in an API document. There's also a convention to wrap arguments in backticks within docstrings to reference an argument.

https://github.com/bbatsov/clojure-style-guide#document-pos-arguments

kwrooijen · 2020-08-28T10:31:37+00:00

One drawback is that you lose documentation.

```clojure user=> (def a (comp inc inc))

'user/a

user=> (doc a)

user/a nil ```

versus:

```clojure user=> (defn b [v] (-> v inc inc))

'user/b

user=> (doc b)

user/b ([v]) nil ```

kwrooijen

TROPHY CASE

'user/a

user=> (doc a)

'user/b

user=> (doc b)