Hacker News .hnnew | past | comments | ask | show | jobs | submit | helloycombinat's commentslogin

I don't think it's the comment.

Usually variable names in a loop is the object being manipulated not the address of that pointer which means p isn't a pointer to the object which makes it completely confusing.

If the article used pp which is the typical way you describe a pointer to pointer it'd help


If NES didn't have locks it would have went the way of atari (99% of games being utter crap with 0 quality control)


Obviously that's a matter of opinion; and the Atari Flashback consoles sold quite well...

And, of course, not having a licenser did little to harm PC Gaming.


I believe they're referring to loss of publishing control often cited as a reason for the video game crash of 1983 that the NES helped carry the industry out of.

https://en.wikipedia.org/wiki/Video_game_crash_of_1983#Loss_...


What's wrong with zip? It's fine. Maybe more than fine if it managed to be this popular for so many applications. From my understanding it's very good on floppy disk too


Consider a use case where you need high concurrent write performance and you don't want the things you are writing to be accidentally dissociated from the file. If you have to write to a zip file there will be overhead every time you append a new "file" because you have to rewrite the central registry at the end of the file.

Basically there is no way to say to you operating system "hey, can I get a no-nonsense, don't what to have to come up with some other conventions that will be broken, way to have some additional storage and file system paths that are just for this file so I don't have to worry about name collisions?" I already have a perfectly good unique name under which I could stash information, but the posix standard basically prevents me from using that name as a way to safely namespace things that I need per file.

However, to your original point I have partially implemented this [0] using zip files on the read side. I treat the internal paths inside the zip file as if they are rooted at the zip file itself. I haven't implemented rewriting though.

0. https://github.com/tgbugs/augpathlib/blob/master/augpathlib/...


You clearly missed his point


I never had facebook on my phone and I dropped whatapp for signal. IG is the last piece I need to get rid of besides those apps I don't care about with the "sign in with facebook" crap.

I'm trying to quit IG so my next phone will be fb free but does anyone have any recommendations on how to make dropping IG easier? So far I made a group with friends so we can spam pics but it's not the same (probably cause not enough of us is spamming it)

Does anyone know of a IG replacement?


Whatsapp (haha). But seriously the answer for me to de-social media myself in general was to focus on the few relationships that matter to me and message them directly. Phone calls, facetime, direct messages.

Whatsapp is the primary way I do this because of it's global reach, but you could get away with sms too.


you don’t replace drinking with smoking.


because you replace it with bath salts, McAfee style.


hah. still waiting on BTC to hit 500K. McAfee told us it’s gonna happen!


No, he said it would happen or else he would...


imho this is the reason he allowed the authorities to catch him. it was between getting caught or keeping his promise


What does this mean? M1 isn't an ARM64? Is it saying there's extra opcodes and this takes advantage of them?


I assume this means it’s compiling with Xcode targeting the M1. Firefox has never had to target aarch64 on macOS before.


It's long since targeted aarch64 on Linux though, so it's not too surprising to me that they have it ready so quickly.


Apple ARM dev kits have been available for a few months, also.

https://9to5mac.com/2020/06/22/apple-arm-developer-kit/


It means they recompiled Firefox for macOS/ARM64.


Correct. Just installed it on my Intel Mac running Big Sur (had to put it in my home directory; I already had non-beta Firefox in /Applications):

    file ~/Applications/Firefox.app/Contents/MacOS/firefox-bin   

    ~/Applications/Firefox.app/Contents/MacOS/firefox-bin: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable arm64]

    ~/Applications/Firefox.app/Contents/MacOS/firefox-bin (for architecture x86_64): Mach-O 64-bit executable x86_64

    ~/Applications/Firefox.app/Contents/MacOS/firefox-bin (for architecture arm64): Mach-O 64-bit executable arm64


It means that M1 Mac's will not be translating x86 opcodes. Apple has done a very good job of making the transition (relatively) painless, but it's still not entirely trivial for many large projects, so seeing this many native binaries is quite nice.


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

Search: