An AI editor, a competitor to Cursor but written from scratch and not a VS Code fork. They recently announced a funding round from Sequoia. https://news.ycombinator.com/item?id=44961172
This may be the case, but as a Helsinki resident I am always surprised when visiting either Stockholm or Tallinn, because their drivers always seem more likely to honor zebra crossings than drivers in Helsinki.
I don't know about German law, but in Finnish law you can only appeal to the trial period if you have an acceptable reason related to the trial period. For example, if the employee isn't performing well, that is a legal reason to annul the work agreement during the trial period. But selling the business to investors or having financial difficulties because of the economy are not acceptable reasons, since they are not related to the specific recently-hired employee.
It cuts both ways: the employee can walk out during the trial period for reasons such as feeling like they didn't fit in, or the work being different from what they imagined. But if they merely find a better-paying job elsewhere, they cannot invoke the trial period but have to give notice in the usual way.
I have the "Relax & Sleep" pair. I got mine from a Finnish reseller, and thought they were a global company but they seem to list only European locations. I believe thomann.de delivers to the U.S., but that's little help since the point of these would be to get them made individually.
I would assume that your local audiologist or music instrument store will know what the U.S. equivalent to these is. It seems to me that Elacin's biggest market is musicians who want a comfortable pair of earplugs with a flat frequency response.
Not a full solution, but one thing I've learned not to do is tell Cursor "you got that wrong, fix it like this". Instead, I go back to the previous prompt and click "Restore Checkpoint", edit the prompt and possibly the Cursor rules to steer it in the right direction.
When the model has the wrong solution in its context, it will use it when generating new code, and my feeling is that it doesn't handle the idea of "negative example" very well. Instead, delete the bad code and give it positive examples of the right approach.
You probably mean the USAMO 2025 paper. They updated their comparison with Gemini 2.5 Pro, which did get a nontrivial score. That Gemini version was released five days after USAMO, so while it's not entirely impossible for the data to be in its training set, it would seem kind of unlikely.
I've seen Greek computer scientists write Omega as an underlined O. Much easier than trying to approximate the printed letter Ω but still unambiguous, unless you use underlining to denote something in your formulas.
Doesn't seem to be updated for Tahoe yet, and even the Sequoia version isn't notarized, so it's not really clear if it has a future.