Alternative: create a .ignore folder for stuff that doesn't belong to repo at all, like your personal notes. Of course, .env shouldn't be there, because it's expected by your code, put it in .gitignore as usual. And stuff like .DS_Store should be in your global gitignore via core.excludesfile config.

There, problem solved. This covers all cases I think.

Interestingly, they plan to make a multiplayer mode:

> I hope that Fontra can develop into a fully online collaborative tool, under a sustainable business model. We like to say: “like Figma for fonts”, or “like Google Docs for fonts”.

https://typeparis.com/news/q-a-fontra

Idiocracy's society didn't have a movie about Idiocracy. So, no, we're not in Idiocracy.

Am I the only one who finds this writing style hard to read?

I stumbled upon this page a few years back and was very confused by the language. It took me some time to parse it and realize that all the comments are actually sarcastic. Overall, the general style feels like I'm reading comments on TikTok.

It's not that I'm against this style; it's just that you don't expect it in a technical article.

I'm on Safari, and it seems you can open your local LaTeX file to use the tool. It's an “Open file” button at the top.

Although I agree that it would be cool to have some hello-world example pre-opened.

The hello-world example sounds like a good idea, I'll try to add that as well, so that the user lands on a working document.

Ooh. That worked. Thanks.

Finally, a periodic table of labs

> Presenting at first nothing but an input box to the user, they constituted a deliberate break in habits for many

No, users were used to it because that's how Google works.

Just 6 month ago they were on HN: https://news.ycombinator.com/item?id=46889703

Okay, but then why not make this a new sort of fuzzy language, rather than building a new app with it's own UI?

I think having to open a web interface is a big entry barrier.

Imagine if those pseudocode files could live in your codebase, and the CLI tool would just “build” the actual code, with sourcemaps. You could edit the code in your favorite editor and run “build” commands in your favorite shell.

(TBH, I haven't looked deeply inside the repo and maybe it's exactly how it works. I just saw that demo and readme tell you to open a http://localhost:5173 as if you can use it only via custom UI.)

I'm not sure how to do syntax highlighting for this pseudocode in any IDE, but you could start with supporting something like Alabaster theme, the whole point of which is to highlight as little as possible.

I say this because I really think that if the setup was simpler lots of people would use it. It's a kind of concept that when you read about it, you think “Wait, how did I not came up with this”. Finally some interesting concept in this endless stream of skills, MCPs, loops etc.

I mentioned it was an experimental proof of concept, but I didn't specify what that means. Right now it's just a web app, but yes exactly as you said, the goal is to turn it into a desktop application where the files live alongside your code (somehow) and can write to a file system. That's the natural spot for it, I think.

As for why it needs a dedicated UI, there's a few reasons. First, the syntax highlighting as you mentioned is a wickedly difficult problem. I'm super stoked that it even works at all, tbh. Another reason (which I didn't showcase) is that the editor builds source maps from your pseudocode to the real code. So you'll be able to uniquely trace each part of your prompt to the line it generated.

That kind of thing might be able to be implemented in a plugin, but at the moment it's way easier if I just control the entire environment. I'm not opposed to it, though - this could go in lots of different directions and I'm open minded.

> It turns out (pun intended!)

Thanks, I was waiting for this pun the moment turns were introduced in the article.