bjpbakker
Joined 10 years ago
Joined 10 years ago
Like parent mentions, this is about scoping. My rule about short variables is that I have to see their _full_ use (including declaration) in only a few lines on the screen.
Personally I prefer single letter variables especially in lambdas for consistency (x, y, z).
The argument that there might be some end-users unable to renew their prescription seems mostly used to gain sympathy. Also this will most probably not be “a large swath of internet users”.
I do hope Actalis step up their game and regain some trust. Or it may become the next symantec.
Either way, that has absolutely nothing to do with the security issues of html email. Eg phishing and tracking still works when you decrypt the message and open it.
Encrypting the data transfer doesn’t improve any of the HTML email security issues. So I fail to see how that would be “real improved security”.
But I do share the authors sentiment on the failure to not using open standards of both Protonmail and Tutanota. So maybe I’m biased.
Right is actually a synonym for Ok.. besides, Either is useful for _much_ more than error handling. That is exactly why I dislike Error for the left side; often it's just not an error.
This is no different than with windows. Except that more vendors sell you windows compatible pre-built systems. With macos the situation is far worse.
If you want more Linux enables hardware it will help to vote with your wallet and buy hardware from manufacturers that do provide support for Linux.
And yet I fearlessly upgrade my Linux system at any time. With OSX you first have to check if the software you use is at all compatible, especially if you use proprietary software..
Also Apple does not embed icons in their binaries. Their app bundles are not binaries, they are a directory structure. The icon is just another file, just like the _actual_ executable(s).
> you could publish a binary containing native versions for all existing architectures
This sort of ignores the hardest part of shipping binaries; linked libraries. Dynamic linking everything is simply not always feasible. Not to mention libc.
Also I don't really understand why anyone on Linux would want this. The fact that I can recompile all of the software I use, is a really important feature to me and not a distribution problem. I can see why Apple wanted this to simplify distribution via their Appstore, but IMO that's mostly to work-around their specific distribution problems. I don't see any of those problems on Linux.
(edit: wording, see below)
Microsoft proves over and over again that they are not trust worthy. I agree you shouldn't be using their OS, but sadly many people don't consider this a choice since it comes pre-installed on most PCs.
For a hobby computer it can be interesting to write your own driver. For a professional laptop not so much :)
In fact my own 15" MBP late 2013 has a GFX750, which is no longer supported according to Apple Support [1].
The worst for me is that this didn't withold Apple from pushing the update, so running Mojave with an external monitor is hardly possible now.
> Nvidia is not a "good" company.
Agreed. Neither is Apple.
Another approach could be to use an effect system like PureScript does. The main problem with Node.js packages is that any function you use can execute arbitrary code (such as wiping systems with an IP that is from the Russian region). Having an effect system in place the library author has no other means than to come forward with the side-effect, or code won't compile.