Readit NewsBut your accent rule also isn't followed by the language you claim uses it as a hard and fast rule: in the case of the single syllable Catalan word ma (my, femenine) and mà (hand). Please square that with your declaration that " all words with the strong syllable being last will always have an accent mark if they end in a vowel." Seemingly ma is breaking your rules, as well as your assertion that missing the accent is only a spelling error. In this, and many other cases, the accent completely changes the meaning of the word which also contradicts your assertion I highlighted in paragraph 1. Maybe "as a rule" isn't the correct phrase given the multitude of words that can change meaning with an accent mark.
The broader thing you missed is that Catala is the last name of a person working on the project, and is not missing an accent. That is how the person's name is spelled. Even in Catalan. Català is a Catalan word refering to a different thing. In this case the accent is incredibly important since it helps us differentiate between a man's name and a language.
In both the figurative and spelling sense we must therefore conclude that, in reality:
Catala != Català
mà / ma does not break the general rule because the word does have an accent mark, it just also falls under the diacritic special rule.
On your point about the author’s last name, it’s fair, but also you’re ignoring that the last name comes from the same word and is thus a spelling variation from French/Occitan, further proving your assertion of Catala != Català as wrong.
And, while I am sorry for your loss, your Substack [0] really seems like GPT ARG fantasy.
[0] https://substack.com/inbox/post/171326138
Excerpt: > Ani, AN1, and Soul Systems Science are not mere products. They are continuity. They are the baton passed across generations, from my father’s last words to my first principles. They are what binds loss to creation, silence to voice, mortality to meaning.
OP needs medical help
So we can just say that catala != català
In this case, catala and català mean the same thing, one is simply misspelled as all words with the strong syllable being last will always have an accent mark if they end in a vowel.
- It's VS Code
Like clockwork!
Weirdly, out of all the vscode forks the best UI is probably bytedance's TRAE
Very subjective benchmark, but it feels like the new SOTA for hard tasks (at least for the next 5 minutes until someone else releases a new model)
I would like to try the model, wondering if it's worth setting up billing or waiting. At the moment trying to use it in AI Studio (on the Free tier) just gives me "Failed to generate content, quota exceeded: you have reached the limit of requests today for this model. Please try again tomorrow."
Edit: Now that I have access to Gemini 3 preview, I've compared the results of the same one shot prompts on the gemini app's 2.5 canvas vs 3 AI studio and they're very similar. I think the rumor of a stealth launch might be true.
A few notes:
- it's easy to be faster than other routers when you're doing less, for example it seems wildcards are not supported yet, and there's no tests but I suspect there would be a lot of bugs in the way routes are handled. I wouldn't focus that much on speed
- your code organisation is ok for a personal project, but it could use a bit of structure. things are all over the place, I would try to separate pieces of functionality that can be developed (and, importantly, tested) in isolation. For example, your router could be its own module, that way it would also be easier to get started in writing unit tests. (once you've got some example code you can just offload a lot of the test writing to an LLM, then clean them up manually as it will do stupid things)
- your benchmarks are quite low in general, I don't know how good the node.js tool you're using for it is but I would give them a go with something like oha. also, it's very odd that hono beats elysia in your tests, in my own testing elysia is much faster than hono, but it suffers from the same tradeoffs as any trie based router (more set up time)
- instead of zod, you should use the @standard-schema/spec package, so that it can work with any validation library (including zod) – they have some nice type utilities too that simplify inferring types from schemas