dropofwill

They do actually admit that about constrained decoding somewhere in the docs. They argue it’s useless in practice because when the constraints actually kick in it harms the output too much and that it’s better to just error and retry in those cases.

That does align with my experience, though we’re not using anything close to frontier for these sort of tasks.

I am interested if it can actually improve on that. As an engineer i like the elegance of guaranteed output, but the retry works pretty well in practice.

Cursor has a terminal based app that’s just as good as any of the other mainstream ones…

Just use scopes in the API key the agent uses? If you’re exposing something publicly that should be a requirement anyways.

That’s how I use gh, aws, etc. No need to modify any of the code in the cli, they’re just wrappers.

BERT came out in 2018 and that’s a pretty important inflection point. It didn’t cause a pop culture frenzy, but in NLP circles it was a ‘magical’ improvement.

In linguistics this sort of thinking comes from 'basic color term' theory, which lays out heuristics for deciding if a word for a color in a given language is 'basic'. 2 things going against these blue-green terms are:

* They refer to specific objects (a duck and a stone), eventually these referents can be transcended though, like with the case of orange. * Their frequency is roughly similar to each other (along with cyan, aqua, etc.), so there's no one term for this range (e.g. there's no doubt in a corpus of English that red is the basic color term for its spectrum).

This is exactly the process happening in the music space with Suno. Go to their subreddit, they all talk about how they only listen to ‘their’ songs, for the exact reasons you list.

Its bleak out there.

Pontevedra is at least 100 times smaller then NYC, it's more comparable to the suburbs that you're moving your family to.

Generally what people are talking about are his universal grammar or generative syntax theories/approaches, which are foundational to how you approach many topics. Because you build your academic career based on specialization they are hotly contested (for the material reasons of jobs, funding, tenure, etc.).

This leads to people who agree hiring each other and departments ‘circling the wagon’ on these issues. You’ll see this referred to as east vs west coast, but it’s not actually that clearly geographically delineated.

So anyways, these are open questions that people do seriously discuss and study, but the politics of academia make it difficult and unfortunately this often trickles down to students.

Spotify makes over 80% of revenue off of paid subscribers, even though over 60% of users are on the free, ad-supported subscription.

Now that's not some optional donation scheme, there are real tangible benefits to being a paid subscriber, so idk how that could fit into something like Firefox.

Spotify is mostly Java, with some Scala and Node.

The concepts here apply to any client-server networking setup. Monoliths could still have web clients, native apps, IOT sensors, third party APIs, databases, etc.