Very nice project!
Thanks for making it open-source and very easy to use. I hope you'll find contributors and be able to get a nice collection of animations!
I'm starting a new project, I may have to use this tool in the next few months.
Readit Newslaurentlb commented on Mesh2Motion – Open-source web application to animate 3D models mesh2motion.org/... · Posted by u/Splizard
What's the downside of open sourcing it?
laurentlb commented on An opinionated critique of Duolingo isomorphism.xyz/blog/2025... · Posted by u/agnishom
Each time I read this kind of feedback, I wonder if there should be a free, community driven, alternative to Duolingo.
- Content may be provided by contributors (like Duolingo did for many years)
- It could be supported by donations (I believe the costs can be kept low)
My feeling is that lots of problems with Duolingo are caused by monetization (and many things were better in Duolingo a few years ago).
I'm still not sure of how it should be designed and what we need exactly. One of the problems is also to get enough contributors. I'd be interested in hearing more thoughts on this.
As a hobby, I started building an alternative to the Duolingo Stories feature (https://lingostories.org), but it's still fairly limited.
laurentlb commented on A WebGL game where you deliver messages on a tiny planet messenger.abeto.co/... · Posted by u/thecupisblue
I appreciate what seems like an attempt to make a "smart camera" that gets out of the way of the player and unburdens them from having to control both a player and the perspective of the camera. That burden, of controlling two entities (player and camera) is large for people who are unused to playing video games.
Was this dynamic on your radar when building the game and camera system? Would love to hear your thoughts.
I'd rather have the choice to control the camera (the "smart" camera could be used only if I don't control it), because it didn't work well for me.
Nice game otherwise.
laurentlb commented on Static sites enable a good time travel experience hamatti.org/posts/static-... · Posted by u/speckx
I don't get this? I can checkout an old commit of my dynamic server rendered blog written in go and do the same thing.
Sure I won't have the actual content, but I can see the pages and designs with dummy data. But then I can also load up one of several backups of the sqlite file and most likely everything will still work.
Building old code and getting the same result is not always trivial to do.
Potential issues:
- If you have content in a database, can you able to restore the database at any point in time?
- If you code has dependencies, were all the dependencies checked in the repository? If not, can you still find the same version you were using.
- What about your tools, compilers, etc.? Sure some of them like Go are pretty good with backward compatibility, but not all of them. Maybe you used a beta version of a tool? You might need to find the same version of the tools you were using. By the way, did you keep track of the versions of your tools, or do you need to guess?
Even with static websites, you can get into trouble if you referenced e.g. a JS file stored somewhere else. But the point is: going back in time is often much easier with static websites.
(Related topic: reproducible builds.)
Is |> actually an operator in F#? I think it's just a regular function in the standard library but maybe I'm remembering incorrectly.
It's defined in the standard library and can be redefined by anyone.
It's usually called operator because it uses an infix notation.
laurentlb commented on Show HN: A 'Choose Your Own Adventure' written in Emacs Org Mode tendollaradventure.com/sa... · Posted by u/dskhatri
Interesting project!
When I looked into CYOA, I opted for Ink. It's using a nice text-based language, a bit like markdown. It worked well for me, and I think it's a good option if you want to use a text editor.
I wrote about my experiments here: https://laurent.le-brun.eu/blog/my-adventures-with-narrative...
But I find this kind of presentation much harder to read than a classic blog post. It's difficult to skim through the text to see how far it goes (and the article structure is not apparent); instead, I was kind of forced to read the text sentence by sentence (since I was familiar with the topic, I wanted to skip over the basics).