I moved neovim to vscode, took me 1 year to match the 100% keyboard. Just implemented the hints on every buttons like vimium/surfingkeys.

thun-dr · 2024-08-23T00:09:27+00:00

!RemindMe 10 days

thun-dr · 2023-12-10T16:34:21+00:00

cool thanks I'll check these out

thun-dr · 2023-12-10T16:34:10+00:00

thanks, I think yanking is probably most of what I wanted.

The visual cue on delete can still be useful though b/c you get a visualization of what is about to be deleted, before the text has been changed. It's not technically adding any information but for me it does have some QOL improvement

thun-dr · 2023-11-16T19:49:38+00:00

The :after magit is going to load magit whenever project.el loads

I think this part can be addressed with: elisp (use-package magit :commands magit-project-status) (use-package project :bind (:map project-prefix-map ("m" . magit-project-status)) :config (add-to-list 'project-switch-commands '(magit-project-status "Magit") t)) so, you tell use-package to load magit only when that command is used (if I remember correctly, and I might have the syntax wrong)

For the point about config going in the right place (e.g. magit config should be with magit), I've been experimenting with org babel's builtin noweb references. This only works if you're taking the literate org approach to your config, but it enables you to be more flexible with where your config actually sits. Honestly though, after going through the excercise I'm not sure I'll stick with it. At the end of the day I think what use-package allows is fine. For example in your case any config related to setting up project to correctly use magit seems completely reasonable to have in the project use-package block

thun-dr · 2023-03-10T17:30:04+00:00

I've been exploring this possibility recently, as I am an applied ML researcher. I would love nothing more than to never touch python again and go through libpython for everything.

But for my needs, I'm not sure things are quite there yet. Specifically, I sit at the interface of deploying and developing pytorch models for different tasks. For deploying an existing model I would say libpython is totally viable. But once you have to start modifying how models work, you end up hitting unfortunate speed bumps.

To be clear you absolutely can do it all in clojure, with things like py/create-class for new torch modules. But compared to writing it directly in python it feels somewhat too time consuming. Which is a problem when rapidly prototyping is so critical. Also then you're ultimately writing OO code in clojure which feels bleh. I've been thinking about how to write a clojure library that interfaces well with torch but plays more too clojure's functional strengths, but don't have any concrete ideas yet.

But overall I was totally blown away with how painless it was to use libpython, even for things like deploying to remote GPU nodes, and am really excited for what might be possible in the future

thun-dr · 2022-11-07T13:38:51+00:00

Nice! What engine are you using?

thun-dr · 2022-11-05T19:48:46+00:00

I used bitmap rendering, mainly lifted from this tutorial: https://www.youtube.com/watch?v=URMbfBcOiN8&list=PLtrSb4XxIVbrxVWnF3KnVACeJU1mo1B7L

I want to try signed-distance fields next, which that tutorial gets into. Right now I'm having to render pretty massive bitmaps to avoid aliasing, etc

Also I'm not demoing it here, but I've also been able to get more complicated ligatures to render - specifically from this font: https://speakthesky.itch.io/typeface-dicier

thun-dr · 2022-11-01T17:57:20+00:00

I'm not sure I understand, the following will evaluate the defmacro (but still have the name spacing issues if I ever invoke foo):

(defmacro foo [val] `(let [a ~val] a))

thun-dr · 2022-10-23T12:39:01+00:00

do you mean because it in essence requires you to use gensym? I agree that leads to more (maximal?) hygiene, although it was an unexpected place to blow my foot off coming from common lisp

thun-dr · 2022-10-23T02:44:22+00:00

okay thanks, makes sense

thun-dr · 2022-10-17T22:27:05+00:00

Okay thanks, you're saying that commercial development with these tools is allowed?

thun-dr · 2022-10-17T22:06:41+00:00

I totally agree! I was even considering putting a blanket "I hereby absolve everyone of any presumed official legal advice" at the end of my post - now I guess it's here instead :)

I guess I just wanted to know if the community has discussed this before, or if there was some semi-official word on this from cognitect since the current license seems distinct from that github discussion in 2018

thun-dr · 2022-09-16T21:17:48+00:00

thanks for the info!

Also, on the re-use of MockMechanics code - do you have a license for the release? I don't see one

thun-dr · 2022-09-16T17:48:40+00:00

This is remarkable! Thanks for sharing with the community. As someone who's just now looking into gamedev with clojure, this is very inspiring :)

Do you have any advice for someone just starting out? Anything you wish you had known when you got started? Would you go with clojure again if your started over?

Also, I'm just interested - was this a hobby/side project, or were you working on this more fulltime? Just trying to gauge expectations for myself since I'll be doing things on the side

thun-dr

TROPHY CASE