People... Please stop using foreign alphabets like that! It's a nightmare for those of us who know the alphabets. It took me a good 20 seconds to read the title. And it's magnitudes worse when someone uses cyrillic for instance and it's native to me.
αcτµαlly pδrταblε εxεcµταblε
301–309 of 309 posts
Re: αcτµαlly pδrταblε εxεcµταblε
#302Earlier quoted context omitted.
https://www.blopeur.com/2020/04/08/Intel-x86-patent-never-en...
> Transmeta tried it and failed Author has clearly not heard about NexGen! They implemented a RISC architecture that code morphed x86 i586 design. They were then bought out by AMD who shortly thereafter adopted the design for their own architecture. Then Intel had no choice but to adopt NexGen architecture as well lool. We all use NexGen Architecture now. The most famous microprocessor no one's heard of. I only know…
Re: αcτµαlly pδrταblε εxεcµταblε
#303Earlier quoted context omitted.
On Windows, though, there's C# compiler out of the box on every OS since Vista. And C# has a bunch of rarely-used syntax for things like raw pointers, that can work on more or less the same level as C, and even look pretty similar. It might be possible to do something with that.
Huh, I never knew this. For anyone else who didn't know, it's in the C:\Windows\Microsoft.NET\Framework64\ folders, it's the CSC.exe file included with each version of the .NET framework. Edit: Good grief, there's even vbc.exe, which is a command line Visual Basic 2012 compiler. Also JSC.exe for Jscript, aspnet_compiler.exe for ASP and MSBuild. Kinda embarrassed that I didn't know this.
https://docs.microsoft.com/en-us/dotnet/api/system.codedom
If you look at the functionality provided there, it includes ability to compile generated code. This is implemented using those command-line compilers.
Re: αcτµαlly pδrταblε εxεcµταblε
#304Earlier quoted context omitted.
Author here. I considered doing that. Then I learned about things like how MSVC 2017 would wrap the main() function of C programs with telemetry. The push for code signing, retpoline, aslr, etc. worries me too, from a software freedom standpoint, and the same goes for how difficult it's become to build native software from scratch, thanks to the shift from autotools to a whole new set of competitors like bazel, cmake…
Then I learned about things like how MSVC 2017 would wrap the main() function of C programs with telemetry. Could you provide a link to learn more? This seems bad.
If that's true, it's just further proof that once people learn something, they never think to check if it's still true later. This entire industry churns over and over so quickly. To me, it's borderline negligence in public forums like this one to make statements which could no longer be true without a quick verification that they are still true, especially for particularly egregious statements, because of the scaling factor.
The 1000 people reading the comments can do the checking, or the one person making the statement can do the checking. To me, it's a moral failure to get one person's jimmies in a rustle over something that isn't true anymore, nevermind 1000 people.
Re: αcτµαlly pδrταblε εxεcµταblε
#305Earlier quoted context omitted.
Yes, being x64 compatible but not supporting SSE4 or AVX is basically useless.
Rosetta won't support this, it's far from "useless". Good programs should detect the lack of support and fall back to earlier extensions.
Besides, where did you hear that Rosetta wont have to at least support SSE4? I think there are Mac apps that assume presence of these instructions since all of Apples macs since 2008 or so has had them.
Re: αcτµαlly pδrταblε εxεcµταblε
#306Earlier quoted context omitted.
So ISAs are patentable? Even if you reimplement them from scratch, it's covered? Can anyone ELI5 that in the light of the Oracle vs Google "APIs are not copyrightable" battle? Seems like an ISA (sans implementation) is comparable to an API, so is the difference patents versus copyright? Are APIs patentable?
I haven't investigated it in detail personally, but my understanding is that Intel has or had troll patents on the obvious (and therefore not legitimately patentable) way to go about implementing various x86 features. So if you reimplement it from scratch, the way you naturally go about implementing it will just happen to match 'Intel's' supposed 'inventions' which they have patents on. (Eg, I think they had a patent…
If Intel had a patent on this, it must have been on some (possibly tiny) variation, though, as IBM had register renaming in hardware in 1967 (See https://en.wikipedia.org/wiki/Tomasulo_algorithm) and the POWER1 had it in 1990.
Re: αcτµαlly pδrταblε εxεcµταblε
#307Earlier quoted context omitted.
What's the deal with the uncommon font of the post title? I saw it here on HN too and was wondering if it's just aestetics, of if there's something else.
It is using (abusing?) Greek letters. I actually kind of hate that as those letters don't necessarily sound anything like what they look like to English speakers. It is effectively gibberish.
Re: αcτµαlly pδrταblε εxεcµταblε
#308Earlier quoted context omitted.
Oh, cool! I thought this file was just prefixed with some random garbage. Unrelated: I used this to verify that my daily scheduled full scan of my Linux laptop works. This is required by compliance at $WORK. It reports found viruses via the i3-nagbar.
Cool. How many viruses has it picked up? (Presumably ClamAV?)
None besides this example file.
I use this laptop for $WORK and web browsing, and my warez times are behind me now that the software I want to run is typically open source, and the content I consume can be bought.
Re: αcτµαlly pδrταblε εxεcµταblε
#309Earlier quoted context omitted.
Play stupid games, win stupid prizes.
Please explain your reasoning for this.
Thus, the stupid game led to a stupid prize, where major thread (in fact, one that felt like drowning any other discussion) was about the title technicalities, but not about content.