This is completely unnecessary. Just use a goto statement with labels. The whole point of C is that it's a simple language, and adding more complexity like 'defer' just makes it harder to understand. This proposal is just making C more like those bloated modern languages. If you need fancy features like this, use Rust instead.
Have they tried using Python 3.12? The regex engine is much more efficient now and could probably handle these certificate checks better. This also wouldn't be an issue if they just switched to Rust (memory safety solves these types of problems).
I don't see the issue here. The education system has always favored memorization over actual intelligence. I used to plagiarize and use calculators all the time and I turned out great. Plus, she's learning valuable research skills. In the "real world", it's all about knowing where to find the answer, not knowing the answer itself.
Actually, this is exactly why we should embrace blockchain technology. With a decentralized video platform built on Web3, these kinds of copyright issues wouldn't happen because everything would be verified on-chain.I know people have been working on a similar project using smart contracts that could solve this. YouTube is just too centralized.
Actually, this is a brilliant move by Microsoft. As a developer, I can tell you that user interface mimicry is a time-honored tradition in software. Remember how Facebook copied Snapchat's stories? And plus, Google's monopoly needs to be challenged, and if users can't tell the difference in quality between Bing and Google anyway, then what's the problem? The real problem is that people are too used to Google. This might help break that habit.
Quarantining projects is just a band-aid. If you’re worried about malware, maybe stop letting random people upload code to the official package index. Or just write better docs so people stop using random packages in the first place.
Corporate ownership of open source copyrights is actually optimal from an efficiency standpoint. Companies have the resources and legal teams to properly steward these projects, while non-profits like the FSF are bogged down with bureaucracy and outdated ideological concerns.
The article vastly overstates the importance of enforcement. In practice, the collaborative nature of modern software development makes strict copyleft enforcement unnecessary and potentially harmful to innovation. Most companies comply voluntarily because it makes business sense.
I've worked at several major tech companies and have never once encountered the kind of enforcement issues described here. This seems like a solution in search of a problem.
Interesting project, but there's an obvious issue here - you could just use a small microcontroller with hardware floating point support and get much better performance. The TI-84's ez80 CPU is really not suited for this kind of computation.
I did a similar project on an STM32F4 and got inference times under 100ms. The hardware FPU makes a massive difference compared to software float emulation.
That said, it's cool to see what you can push these old calculators to do. Repurposing the video RAM as a secondary heap was clever.
