Burj

My guess is that their books are cooked to hell and back

In truth, the alleged $200k lego collection is meaningless. The real smoke is that the previous owners were strong armed out at random.

It honestly would just be franchise infighting if it werent for the fact that the ceo is explicitly running interference at every step

It seems like there is deep, deep fraud. The knee jerk reaction to run legal defense seems to me like they are hiding WAY worse

If you insist on not watching the "really long youtube videos" youll unfortunately have to settle for taking our word for it

There were 10x small claims cases against i believe the single franchise (L2 Bricks LLC iirc) which were won by default and might not stick due to them going chapter 11

Yeah, this tracks! The steps are basically 1) determine user facing elements 2) determine strings 3) map user facing elements to the string. (We use the ast and no llms for this)

The upside of this approach is that we get a lot of context for accurate translation. The other upside is that down the line we can pull off fully automatic translation, but as others have pointed out, this is more of a gimmick. We think it's cool but it's more like the cherry on top

Also, yeah, that pattern would make life infinitely easier. Most develors really should think like this already, and not mix user facing strings with strings for other logic. But from what ive seen, pre i18n, devs dont think like this. Someday...

Svelte should be supported soon, alongside the other major js frameworks we don't support yet. I hope it's ready in time for what you're building!

Vue tooling should be ready soon, but it's not supported yet. All major js frameworks are high up on the roadmap

Which language? Our site/dashboard supports 15 or so languages, as do our accessory apps/tools. Still working on our docs though, which are only in 2 languages...

It's a huge pet peeve of mine when translation services aren't themselves fully translated, and I see it a surprising amount ahaha

Yeah, we've noticed that companies in the early stage ignore i10n completely and then eventually realize it's going to be a huge lift to retroactively support it

So, for the build time translation-

Yeah, I would say it's not reliable yet =p

But, it's not that far off. It's not magic- the idea is that we inject the t functions at build time so that they don't need to be in your code. The vscode extension is a good visual for this- for many patterns, it correctly notices what does or doesn't need to be translated.

But, the real problem is that if a process like this goes awry (a strange pattern leads to text being erroneously translated/untranslated) then it is next to impossible for someone to debug.

Glad you think this is cool. We think this is absolutely on the horizon, and we hope to be the first to get people using it... but in the meantime, we don't want to be responsible for issues on prod...

The computer kicked my ass. I had forgotten why I disliked othello...

As for the UI/UX tests, we're looking to integrate with PostHog and work with another company in our batch (PathPilot) which focus on analyzing user experience

Once we work these analytics in, the theory is we can better predict UI issues and resolve them retroactively. A full UI testing suite is something people have asked for, and we aren't there yet, but the tools are here