One example: I asked it to explain continue.dev, the kind of thing I’d asked it previously.
Before I got a proper summary and an arch diagram. It felt like its own work. Now it spun in circles for a good while and then it regurgitated the continue.dev website in weird topic boxes and that wasn’t helpful at all.
It does seem that it’s SOTA for LLMs to take forever to respond. In that sense it’s in good company. More and more, lately, I send a prompt to an LLM and switch tabs because it’s likely to be 20-60 seconds at best.
As someone who never used Phind, how was it better than copilot? Did it integrate data from broader sources or just do a better job of presenting it? Was it faster?
I want a simple CRUD mobile app that talks to a website. Like a website where you GET and POST to read and write data. Something that copies the submission forms of a website and gives me the website as a mobile app. Something that identifies all endpoints in a website and gives me access to these endpoints as a mobile app.
A hypothesis here is that well-crafted UI helps you understand/see options for what you don't yet know.
For example, here's an example for a "day trip plan in Bristol" that contains a canonical example (directly based on the query), but also a customization widget that presents some options that you might not have already thought about if you were just doing a text-based followup.
reply