If you look at the standard equipment used in healthcare you'll notice that everyone wears mask and eye protection (goggles or face shields), because the virus can also transmit through the eye.
I'm not saying that masks are not effective, but I would be very careful with certain affirmations, such as: "going in public without a mask in a pandemic is like riding a motorcycle without a helmet", it's more like: "going in public with a mask only covering your mouth and nose is like walking through a fire while wearing a fire proximity suit and sandals".
I don't like using underscore or lodash for methods that are parts of the EcmaScript specifications. I prefer using native methods (i.e. `forEach`, `map`, etc..) and including a JS shim (like https://github.com/es-shims/es5-shim) to monkey-patch legacy browsers.
And I know that these are just examples, but what is the point of writing:
Yeah, it's verbose because you have to cast the lambda expression before executing it, but honestly I don't know any case where a self executing function can be useful in C#.
Not too bad. Actions return null though. How about a self-executing function that returns a value? This is useful for assigning values to variables. IIRC it's going to start getting more ugly from here.
"PC" has been appropriated numerous times by vendors to mean a specific platform. In the times were personal computers were less-standardised "IBM PC" and later "PC Clones" referred to the platform and not "personal computer" specifically. This naturally led to Macintosh computer being referred to as Macs, even though they too are "personal computers".
The problem is that many people today don't understand the history of personal computing and that "PC" has an established history of meaning a specific mainstream platform. I think some mistakenly poke fun at Apple, as if they had invented the label 'PC' for their ad campaign. When actually Apple merely took advantage of this convenient, existing differentiator for their PC vs Mac ads.
Apple have been working references to other platforms out of their marketing materials for years. Comparisons are no longer needed when a company has found their publicly-held niche.
just asking seriously.. aren't Macs x86 now? Doesn't that distinction comes from the time when Macs used a totally different architecture (risc) based on something called Ironically "PowerPC"? I still can't see the difference now. Why then don't call Linux-PC or BSD-PC to others if based on the platform? I may be wrong, but the way I see it its just something anachronistic with an historical basis, but now just used for marketing purposes.
The early intel macs were "x86". The current line up is x86_64. Depending on who you ask in the industry this is called AMD64, Intel64, EM64T, IA-32e. This is the 64 bit platform as developed by AMD, it's not to be confused with Intels IA-64 as sold in "Itanium" chips.
No, in the context we are discussing, a PC is not a "personal computer", but what was called an "IBM PC compatible" (and subsequently by some a Wintel machine).
Few people use "PC" to mean personal computers in general, especially since for 99% of the people personal computers are all they know and encounter anyway, so no need to distinguish both Mac and PCs from, say, Mainframes and embedded systems....
That's why nobody got confused by the 3 year running "-I'm a Mac, -And I am a PC" ad campaign.
I think the only difference now is that Macs use EFI boot, and not BIOS boot and hence will only boot software with a EFI-boot compatible bootloader.
Once you get past that step a Mac works exactly like a "PC". Just like a "PC" works exactly like a Mac if you fake the EFI-boot via a custom BIOS-to-EFI bootloader on a USB-stick.
EFI is not exclusive to Macs. It was developed by Intel and has been deprecated in favor of UEFI.
Most UEFI images will have legacy support for BIOS services.
There is basically no difference between a modern Mac and a PC - except for Mac OS X, which can be run on "Hackintoshes".
Not if your (U)EFI firmware is capable of booting BIOS-booted operating systems as well as (U)EFI operating systems (like IBM System x Server Firmware).
So they appear to be moving over to "not being IBM PC compatible". Which is perfectly valid.
I never said that PCs are called PCs because they ARE IBM PC compatible, only said they are called PCs because in the past "IBM PC compatible" defined their category.
I have a floppy drive and my PC will run some old PC games that ran bare-metal (i.e. booted off the floppy). Macs by design, can't boot those.
Also it's a bit freaky that my disk from 1987 still works in a machine I built last-year. Some games assumed a 4.77MHz clock though, and I there's no turbo button, so they don't really work :(
Technically, since they don't use a PC BIOS. Plus, the "IBM PC compatible" as a specification hasn't been important since 199x.
The PC moniker for Wintel machines, while heralding from the "IBM PC compatible" era, it's used as a designator of the category of, well, PC-derived machines now, not as a technical spec. We mostly use the word Wintel for the respective thing now.
I'm not saying that masks are not effective, but I would be very careful with certain affirmations, such as: "going in public without a mask in a pandemic is like riding a motorcycle without a helmet", it's more like: "going in public with a mask only covering your mouth and nose is like walking through a fire while wearing a fire proximity suit and sandals".