You don't need dryer sheets if you're hang drying your clothes, which reduces wear on the clothes and uses less energy, along with requiring one less appliance, unless you have a combo washer/dryer.
I started hang drying my clothes maybe 4 years ago and I'm definitely not going back
No, they are changing the .sln-format, which is only used by Visual Studio itself
This has nothing to do with EEE.
I remember running some J2ME-stuff on the Sony Ericsson-phones, but it was generally quite incapable. Maybe it was a lack of creativity on my part, but then again, I was in my teens at this point
I thought the cutoff for Smartphones was Android/iOS/(Windows Phone)?
It becomes hard to draw a line otherwise. I had a few various Sony Ericsson non-Android phones back in the day, but the first phone I would call a smartphone was a ZTE Blade. It put me down the path of developing apps for Android, which is what I do for a living now, so that's a little interesting.
A few not yet mentioned:
And a vote for previously mentioned podcasts:
I don't think DeepSeek has the capability of generating code and executing it inline in the context window to support its answers, in the way that ChatGPT does - the "used"-part of that answer is likely a hallucination, while "or would use" more accurately represents reality.
The concern is that the model doesn't actually see the world in terms of distinct hexadecimals, but instead as tokens of variable size - you can see this using the tiktokenizer-webapp: enter some text and it will split it into the series of tokens the model actually will process.
It's not impossible for the model to work it out anyway, but it is a reason for this type of task to be a bit harder on LLMs.
It's not out of the question that we get emergent behaviour where the model can connect non-optimally mapped tokens and still translate them correctly, yeah.
It is a concern.
Check out https://tiktokenizer.vercel.app/?model=deepseek-ai%2FDeepSeek-R1 and try entering some freeform hexadecimal data - you'll notice that it does not cleanly segment the hexadecimal numbers into individual tokens.
Still, this does not quite address the issue of tokenization making it difficult for most models to accurately distinguish between the hexadecimals here.
Having the model write code to solve an issue and then ask it to execute it is an established technique to circumvent this issue, but all of the model interfaces I know of with this capability are very explicit about when they are making use of this tool.
What a pathetic loser move