@jitbit If they found these vulnerabilities only after Mythos found them, my question will be.. Why only now? Why didn't they try to find them earlier? Instead of the big news that Mythos is the one that found them!
@adamwathan It seems the older ones are more convenient. Whatever weight you want, you have it in a second. Instead of keep adjusting the new one. In terms of space, you already had ve the extra space. Now, what are you doing to do with extra empty space that's only good for dumbbells
@dev_maims That means one or more of these. You're single shoting big features. Your prompt is not clear enough. You're not good at debugging. BTW, you wouldn't have known if you didn't try first anyway!
@RickStrahl Try opus 4.6. Give it examples and edge cases and tell it to go in a loop testing them and to have them all working. The more of them the better. Use a cli and yolo mode. This might go through a good amount of tokens.
@burkeholland In the future, the 1M context will work like today's 100k. I am guessing this will happen with newer models. So keep experimenting until you know we reached the effective 1M context.
@mkristensen I would like to see something like VS Code's workspaces so that Copilot and agents can work across different repos. Instead of creating a temporary solution.
@adamwathan Things you can pivot to. An AI service like Lovable, but it specialises in producing highly polished UI components using Tailwind. Video tutorials on Tailwind based UI components.
@theo_albers@RickStrahl@mkristensen@VisualStudio There are options to save and load configurations in the installer. I haven't used them. I assume it's maybe for it to know your previous workloads.
Anyway this is all to save a few clicks once every like 4 years!?
@jasonfried As a customer I like roadmaps. It gets me excited to know what's coming. I know they're promises and I don't plan now for all of them to happen. It's ok.
@hhrvoje@RickStrahl@danroth27 Blazor needs to get better, for it to get more adapted. Not the other way round. Blazor might be the future and therefore needs more attention. Just like WinForms is a mature and done technology, MVC Razor is heading that way. WinForms is also widespread but gets little updates