No, you were given a piece of a worthless token by the mining pool. If you ever want to get anything with that worthless token somebody else has to lose money. That somebody makes the bet that another somebody will be an idiot and lose more money so he can get his back.
And that money came from someone. You can’t win in crypto unless someone else loses. Typically it’s vulnerable people wishing for a get rich quick hack who lose.
It was until the authorities learned how easy it is to connect transactions to actual people.
13700k seems to be similarly priced now compared to 7900x.
AMD slashed prices due to poor sales of zen4, 7700x used to be more aligned to 13700k pricing than 13600k. Before that Intel was actually usually the better choice between the two.
Yes, the benefit of RISC-V I can see is that if a large company, let’s say intel, designs a high performance CPU, a small company can also create a compatible alternative CPU. I don’t think the small companies can really compete in performance with the large ones, even if you manage to create a good CPU once it’s not simply feasible to keep up with hundred times larger r&d teams in long term, but there is a place for the smaller CPUs filling specific niche use cases.
Now, let’s be clear, RISC-V is a loose definition of an instruction set. It’s free in the sense that you don’t need a license to design a CPU that uses it. However the actual CPU designs are no more free than any other ISA, they will be closely guarded IP of the companies that design them.
Also, since RISC-V includes a minimal base set (truly minimal of like 50 instructions that doesn’t even implement multiplication and division) and a large number of optional extensions and freedom to create new extensions, software compiled to one RISC-V processor doesn’t necessarily run on another. Hence, “ecosystem” people talk about might not happen.
In this case it really seems this windows convention is bad though. It is uninformative. And abbreviations mandate understanding more file extensions for no good reason. And I say this as primarily a windows user. Hiding file extensions was always a bad idea. It tries to make a simple reduced UI in a place where simple UI is not desirable. If you want a lean UI you should not be handling files directly in the first place.
Example.zip from the other comment is not a compressed .exe file, it’s a compressed archive containing the exe file and some metadata. Windows standard tools would be in real trouble trying to understand unarchived compressed files many programs might want to use for logging or other data dumps. And that means a lot of software use their own custom extensions that neither the system nor the user knows what to do with without the original software. Using standard system tools and conventions is generally preferable.