1. function trampolines, such as in libraries like ATL (Microsoft's COM template library);
2. hand-optimized encoders/decoders for things like ffmpeg;
3. niche applications such as Ben Eater's 6502 breadboard computer (using a modified WozMon and Microsoft BASIC);
4. reading ASM output from C/C++ code in things like the GodBolt site for performance comparisons/analysis;
5. reverse engineering old DOS games;
6. people working on things like compilers (generating optimized assembly), JIT engines, or other code generation -- though this will typically be machine code, possibly with assembly instruction comments;
and other performance critical places where assembly can speed up that part of the code.
ASM to a higher level language is a jump to a clearly defined higher level language through a deterministic compile step. The jump away to LLMs is something completely different.
That certainly couldn't be why they feel that threatened. But just think, using AI to build it will literally destroy Bambi's entire forest. Just that one prompt. Think about it.
Agree, isn't this precisely what credit-card companies promise to cover? I'd think I would just claim flight-interruption with the credit card insurance and it should cover all expenses.
I think after the AI crash the biggest winner will be Apple.
They will release MacBook Pro M10 or whatever that can comfortably run Opus5 levels of performance local model for software development/general ai that is baked in the MacOS for 7k USD.