Hacker Newsnew | past | comments | ask | show | jobs | submit | secondcoming's commentslogin

UK energy consumers cry

I think the concern is around fans getting into the country, not players.

Nobody wants to just hear US citizens chanting 'Defence, Defence' all the time.


I need to chug more coffee, you're absolutely right.

This pause does not apply to visitor visas

The WC has already been ruined by pausing games for commercial breaks.

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.

Maybe a compiler error that a const object cannot be “moved”?

That would force the programmer to remove the std::move, making it clear that its a copy.


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.

I didn’t think of that, but you are right. At some point I thought I understood templates r-value references work but now I’ve forgotten.

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)

clang-tidy has a check for this case

To be honest I agree that it makes sense, at least if we put our hats of puritanism on the conceptual and semantical way of seeing it.

But having std::move silently fall back to a copy constructor is not a good solution.


It's kind of concerning to me that Ubuntu has started paywalling some package updates behind Ubuntu Pro. Thinking of switching to Debian.

Ubuntu pro and snap sure are obnoxious.

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.


The people working on the windows kernel must be gutted to see their hard work destroyed by sub-standard devs elsewhere in MS.

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.


Notepad was basically the "Hello world" of win32 apps. A kid in highschool could have "maintained" 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 there's no need to change it, that's the point. It's a finished product pretty much. Just ship it as is.

If a PM needs NotepadAI for their career progression then start it from scratch.


Shouldn’t the AI technology that Microsoft is spending billions on make this trivial?

Microsoft has the resources to train people.

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.

For money, anything is possible. That’s the employment contract, trade money for time doing things you would rather not.

Indeed but if the pay needs to be high, you may as well pay someone experienced.

The delulu who think C/C++ is "sunsetting". Hilarious.

> But does any junior want to learn C++ Win32?

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.


> But does any junior want to learn C++ Win32?

That's why they got the job, didn't they ? /s


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.

How can we be sure that LLMs won't start giving stale answers?

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.

LLMs are just statistics, eventually they kill themselves with feedback loop by consuming their own farts (literally)

My min spec requirements for a phone are 5G, physical dual SIM support, and a 3.5mm audio jack


I'm curious as to why 5G is on the requirements list.

3G made web browsing viable. 4G made streaming video viable. I haven't seen any new applications enabled by 5G on end-user smartphones.


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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: