omneity

10 ms·

151.
by omneity 1y ago
International operations? Is DoorDash entering new markets?
152.
by omneity 1y ago
No idea about SOTA but naively it doesn't seem like a very difficult problem: - Ensure all TLA+ specs produced have the same inputs/outputs (domains, mostly a prompting problem and can solved with retries) - That all TLA+ produce
153.
by omneity 1y ago
A fascinating thought. But then who verifies that the TLA+ specification does indeed match the human specification? I’m guessing using an LLM as a translator narrows the gap, and better LLMs will make it narrower eventually, but is there a
154.
by omneity 1y ago
I always found Kufi to be a form of space-filling curves[0], which was the original purpose: a form of decoration that can fill a surface such as edges around a building[1, 2], without depicting humans in stone, a form of art historically f
155.
by omneity 1y ago
Worth noting that Kufi writing originates from the region of Kufa in modern-day Iraq, also the source of the Kufiyyeh headdress. https://en.wikipedia.org/wiki/Kufa
156.
by omneity 1y ago
Interesting. Maybe a new product line will come out of this.
157.
by omneity 1y ago
Serverless in the context of Postgres means to decouple storage and compute, so you could scale compute "infinitely" without setting up replica servers. This is what Neon offers, where you can just keep hitting their endpoints wit
158.
by omneity 1y ago
Supabase, while a great product, does not offer serverless Postgress.
159.
by omneity 1y ago
Despite the tone this is excellent advice! I had similar impressions reading the article and was wondering if I missed something.
160.
by omneity 1y ago
Great job, congrats for the release! A little feedback, it could be nice to auto-generate a unique url on page load (the one you generate after clicking on "share"). Bonus is that it gives the user a certain confidence to reload t
161.
by omneity 1y ago
True in principle. Looking at it from Apple’s side, they are selling an ecosystem of clients to digital (or physical) service providers with certain guarantees on how that ecosystem operates. Opening up automation is a double whammy for App
162.
by omneity 1y ago
Thank you! Adding support for `additionalProperties`[0] (and perhaps `patternProperties` too) would be particularly great! Happy to provide test cases as well if helpful. 0: https://datatracker.ietf.org/doc/html/dr
163.
by omneity 1y ago
It does! I do use CT2! On a decent CPU I found the translation to take anywhere between 15-30 seconds depending on the sentence’s length, very unnerving to me as a user. But it’s definitely worth revisiting that. Thanks!
164.
by omneity 1y ago
Many languages (with a sizable speaker population) do not have machine translation to or from any other language. The technique makes sense though, but in the training data stage mostly. BART-style translation models already represent conce
165.
by omneity 1y ago
JSONSchema support on Google's OpenAI-compatible API is very lackluster and limiting. My biggest gripe really.
166.
by omneity 1y ago
Yes. There's a scoring and filtering pipeline first, whereby I try to automatically check for the quality of the correction using a custom multilingual embedding model, madmon[0] and language identification model, gherbal[1]. Above a c
167.
by omneity 1y ago
Being alone in this vast city gave me a certain feeling of unease. Reminds me of Stargate episodes where they would find an advanced civilization devoid of life, only to discover they got wiped out in a mysteriously terrible fashion.
168.
by omneity 1y ago
Thanks for the tip and cool project! The model I trained is relatively large, as it's a single model that supports all language pairs (to leverage transfer learning). With that said while running it client-side is indeed an option, ope
169.
by omneity 1y ago
Pandoc can be painful (mostly due to the complexity of all the tools it orchestrates in my opinion), but I find it very hard to beat once you get in non-trivial publishing territory and you refuse to use TeX/LaTeX-style processors. The
170.
by omneity 1y ago
Marian was a good starting point and allowed me to iterate faster when I first started, but I quickly found it a bit limiting as it performs better for single pairs. My goal was a google translate style multilingual translation model, and f
171.
by omneity 1y ago
I started seeing results as early as 5-10k pairs, but you want something closer to 100k, especially if the language has a lot of variations (aka morphologically rich, agglutinative, or written in a non-standardized way). Manual proof-readin
172.
by omneity 1y ago
Do you have a recommendation for a better incarnation of the principle?
173.
by omneity 1y ago
Tangential but I noticed a certain common conflation between pre-rendering and server-side rendering. Very often plain SSR is all it takes for good SEO performance, SSR in this case simply being rendering the page on-demand before serving i
174.
by omneity 1y ago
Related: I built a translation app[0]* for language pairs that are not traditionally supported by Google Translate or DeepL (Moroccan Arabic with a dozen of other major languages), and also trained a custom translation model for it - a BART
175.
by omneity 1y ago
I used the seamless attribute extensively in the past, it still doesn't work the way GP intended, which is to fit in the layout flow, for example to take the full width provided by the parent, or automatically resize the height (the pa
176.
by omneity 1y ago
I think that's very smart, thanks for sharing! With the prevalence of coding agents currently the cost of context/language switching is much lower and these best-of-breed multilang setups are likely to become more prevalent in the
177.
by omneity 1y ago
Seconding this use case! I see pipask helping greatly as another safety net when using coding agents.
178.
by omneity 1y ago
Thank you for the answers. Sounds reasonable in my book (what's one more internet stranger to trust, hah). I'll give it a try!
179.
by omneity 1y ago
What makes Rails stand out is the focus on convention-over-configuration as a guiding principle in the ecosystem which results in a lot less code (have you seen these relatively thin models and controllers?), as well as established dependen
180.
by omneity 1y ago
I switched from Rails to the node.js ecosystem back in the 3.2 to 4 transition, however looking back I share a similar sentiment as the OP. I recently initiated the backmigration and my approach thus far however has been to take out the &qu

More ›