What’s the problem? It makes perfect sense to me that a const object cannot be moved from, since it violates the constness. Since constness goes hand in hand with thread safety you really don’t want that violation.
There are cases where you would not want to reject such code, though. For example, if std::move() is called inside a template function where the type in some instantiations resolves to const T, and the intent is indeed for the value to be copied. If move may in some cases cause a compiler error, then you would need to write specializations that don't call it.
It's weird that they made a mistake of allowing this after having so many years to learn from their mistake about copies already being non-obvious (by that I mean that references and copies look identical at the call sites)
On servers I prefer Debian, but my experience on Debian hasn't been as smooth as Ubuntu for gaming, even when activating Debian nonfree repositories with proprietary NVIDIA drivers. I've had some trouble with the Wayland transition, but now everything works fine.
Also, the Steam client is officially supported only on Ubuntu. Probably SteamOS too, implicitly.
That makes little sense, notepad.exe already exists. The only development required on it would be to add AI shit to it. They could just leave it alone.
That means you have to work on the original code, and modern entry-mid level devs can't do that. It's probably in C++. Your expensive senior and staff level devs are on more important projects.
Make it a web app and your cheap entry level grads can do it.
My first entry-level job just freshly coming out of the University was writing C++ with Qt for a computer vision app. And that was my actual first contact with C++ (had seen C and Java in Uni).
It was no biggie, just joining the low level of C with the class notions from Java. Pair that with the C++FAQ website, and it was easy.
Are entry-level devs generally not able to do that nowadays? I do not believe people are generally more stupid or less capable, so, is education so much worse or what's going on?
But does any junior want to learn C++ Win32? You want to learn something that leads to a long-term career development path, not a sunsetting technology.
They would want to learn Winforms/WPF/WinUI/whatever if microsoft could settle on one and use it. I suppose part of the react native stuff is that Microsoft hasn’t done a good job of making people, even in Microsoft, bet the farm on any of their “native” toolkits.
I'm pretty sure Microsoft can pay them enough to be happy to learn it.
> You want to learn something that leads to a long-term career development path, not a sunsetting technology.
This seems like such an odd take when web frameworks seem to be obsolete almost as soon as you start using them. C++ has and will continue to be around for a very long time.
This is just the result of bad leadership at Microsoft.
The previous version would have been written in C rather than C++ since as someone else has said it's a very basic Windows application, more of a wrapper around the edit control than anything more complicated.
These days it would have to be written in some other language that has those Windows Runtime bindings available for it. So could be C++ but if I were to guess I'd say it's written in Typescript and compiled to a native or .Net binary.
> That means you have to work on the original code, and modern entry-mid level devs can't do that. It's probably in C++.
As far as I remember, Notepad was the reference implementation for a Microsoft widget. Nothing more. If "modern entry-mid level devs can't do that" you really have a much bigger problem.
I don’t think you understand. Notepad was literally one of the examples that comes with the SDK. It doesn’t need any maintenance. As long as windows has a native SDK, notepad exists because it is basically the simplest GUI application, provided as a sample.
I not too long ago received an ad on YouTube that was an entire episode of the UK reality TV program 'Made In Chelsea'. I think it was skippable but I couldn't believe that a) someone set up an ad campaign to do this, and b) YouTube didn't detect it.
We can't. I don't think the LLMs themselves can recognize when an answer is stale. They could if contradicting data was available, but their very existence suppresses the contradictory data.
LLMs don't experience the world, so they have no reason a priori to know what is or isn't truthful in the training data.
(Not to mention the confabulation. Making up API method names is natural when your model of the world is that the method names you've seen are examples and you have no reason to consider them an exhaustive listing.)
They will, but model updates and competition help solve the problem. If people find that Claude consistently gives better/more relevant answers over GPT, for example, people will choose the better model.
The worst thing with Q/A sites isn't they don't work. It's that they there are no alternatives to stackoverflow. Some of the most upvoted answers on stackoverflow prove that it can work well in many cases, but too bad most other times it doesn't.
They still use the official documentation/examples, public Github Repos, and your own code which are all more likely to be evergreen. SO was definitely a massive training advantage before LLMs matured though.
Latency and throughput from a multi-thousand (literally, in the age of IOT and M2M) user network, massive MIMO and beamforming that LTE doesn't support, etc.
reply