You’re not a novice, there are a lot of us who know exactly what we are doing and see this as a huge downside. We are just being told to go faster, faster, faster lest we miss out on… something?
Both ahead of time compilers and JIT compilers often perform autovectorization of tight loops. The problem is that lots of hot loops are not necessarily simple loops, and in particular a lot of source code is written in a way which uses sequential dependencies that can’t be modeled in SIMD code. Aside from undefined behavior in C/C++, most compilers will fail to autovectorize because doing so would very slightly change the behavior of your code in a very hard to understand way.
I feel like this can be explained in part by “I like using it for myself, but I hate when others use it.”
When you use ChatGPT for yourself, you may have a sense that what you see is made up; when someone else that you trust uses it and pronounces the output in a way that suggests it is their own, you are left doing much more complex social math to figure out if your trust in this person or entity can hold. It gets exhausting, personally.
When AI produces those meaningful advances in those fields, great, we can start having meaningful discussions about them. The greatest medical advancement of the 21st century is likely mRNA, or maybe GLP-1 for some. Neither were LLM assisted in any meaningful way as far as I know (they predate ChatGPT, perhaps more primitive models were involved in ways I’m not familiar with). Until those advances come, this argument is fanfic.
Plus, in the most morbid way possible: who gives a shit about living longer if they are stripped of their career, are inundated with slop at every angle, and can’t trust any information. These are real problems that AI has already created, unlike the fanfic of ridding cancer.
I have no advice to offer, I only wish you good luck. I am still lucky enough to be employed, but when this whole parade ends, I have no idea what comes next - my only skill is programming and related knowledge work. I think the only path forward is to try to jump ship to another white or blue collar industry…
Have you considered just… writing code? Like we used to in the good old days? If the tool drives you to that point of frustration, maybe it’s time to give the tool a break.
> when the author is an AI and the consumer is a compiler, and no human needs to read the output at all.
This seems like a big bet on the assumption that fully autonomous codegen without humans in the loop is imminent if not already present - frankly, I hope you are wrong.
Even if that comes to pass in some cases, I also find it hard to believe that an LLM will ever be able to generate code in any new language at the same level with which it can generate stack overflow-shaped JavaScript and python, because it’ll never have as robust of a training set for new languages.
That seems correct, but it also doesn’t account for managed languages with runtimes like JavaScript or Java or .NET, which probably have a lot of interesting runtime info they could use to influence caching behavior. There’s an amount of “who caches the cacher” if you go down this path (who manages cache lines for the V8 native code that is in turn managing cache lines for jitted JavaScript code), but it still seems like there is opportunity there?
Sure, but this is based on a fundamental trust in governments ability to spend money effectively. The ineffective spending has been in the news way more than the effective spending, so some people take this to mean all of the spending is ineffective.
I don’t know how to square this skepticism of government against very vocal “patriotism” coming from the trump camp, but humans can contain multitudes, I guess?
In C#, you would normally implement rules like this with a custom Roslyn Analyzer or with https://github.com/dotnet/roslyn/blob/main/src/RoslynAnalyze.... It’s fair to say C# projects tend to have smaller denylists than mature C++ projects, but banned APIs definitely exist in mature C# projects.
I didn’t know this, but there are also security downsides to being ahead of chrome — namely, all chrome releases take dependencies on “known good” v8 release versions which have at least passed normal tests and minimal fuzzing, but also v8 releases go through much more public review and fuzzing by the time they reach chrome stable channel. I expect if you want to be as secure as possible, you’d want to stay aligned with “whatever v8 is in chrome stable.”
If people aren't getting their work done, then they should be having discussions with their manager that eventually lead to pip or firing if not resolved. If they are getting their work done... Who cares if I do a "non work thing" at a "work time"?
Saying that Microsoft is "Rewriting Windows in rust" suggests you might not be as informed as you think... Very specific components with history of performance or security issues are getting ported in a very uncoordinated effort. Windows will be primarily C, C++, and C# for a very long time to come
But, it's also a reasonable response to prevent bloat. Not asking that question is how anything with backwards compatibility guarantees, especially languages, get too complex over time. Asking the question doesn't mean you've hit a wall; the maintainers may just be going through a mental checklist to try to keep this from being a major pain for them in 10 years.