Need to setup gpg-agent first, on OSX I use keychain (it also does ssh-agent)
$ brew info keychain
keychain: stable 2.8.5
User-friendly front-end to ssh-agent(1)
https://www.funtoo.org/Keychain
/usr/local/Cellar/keychain/2.8.5 (7 files, 108.5KB) *Here is a short guide that will help you setup your environment to create signed commits or signed tags with Git locally. This has been extensively tested on Windows with Git and the Github Desktop application: I use it every day for my professional development projects.
I you face any issue, feel free to leave a comment below.
| # βββββββ ββββββ βββββββ βββββββ βββββββ ββββββ ββββββββββ | |
| # ββββββββββββββββββββββββββββββββββββββββ ββββββββββββββββββ | |
| # βββββββββββββββββββββββββββ βββββββββββ ββββββββ ββββββββ | |
| # βββββββ βββββββββββββββββββ ββββββββββββββββββββ ββββββββ | |
| # βββ βββ ββββββ ββββββββββββββββββββββββββββ ββββββββ | |
| # βββ βββ ββββββ ββββββββββ βββββββ ββββββ ββββββββ | |
| # | |
| # ββββββββββ | |
| # βββββββββββ | |
| # βββ βββββββ |
Someone asked whether or not acid-state was production ready. I shared my experiences:
parsonsmatt [11:32 AM] @nikolap it's used by cardano-wallet and Hackage. Based on my experience with acid-state, I'd say it is not a good choice for production data storage. For local desktop apps, SQLite is a much better choice, and for real production apps, Postgresql is king.
parsonsmatt [11:44 AM] acid-state did not have a test suite, at all, until I implemented the very first tests (for TemplateHaskell code generation) earlier this year. It has picked up some tests since then, but I'm still not confident in it's correctness.
It claims to be resilient to unplugging the power cord, but I doubt that, as it's not resilient to Ctrl-C: acid-state/acid-state#79
Hey everyone - this is not just a one off thing, there are likely to be many other modules in your dependency trees that are now a burden to their authors. I didn't create this code for altruistic motivations, I created it for fun. I was learning, and learning is fun. I gave it away because it was easy to do so, and because sharing helps learning too. I think most of the small modules on npm were created for reasons like this. However, that was a long time ago. I've since moved on from this module and moved on from that thing too and in the process of moving on from that as well. I've written way better modules than this, the internet just hasn't fully caught up.
@broros
otherwise why would he hand over a popular package to a stranger?
If it's not fun anymore, you get literally nothing from maintaining a popular package.
One time, I was working as a dishwasher in a restu
This proposal is largely based on my previous proposal, which can be found here. It had a few problems though, which are fixed by this proposal.
It is unclear how to represent operators using interface methods. We considered syntaxes like +(T, T) T, but that is confusing and repetitive. Also, a minor point, but ==(T, T) bool does not correspond to the == operator,
The included script 'widevine-flash_armhf.sh' fetches a ChromeOS image for ARM and extracts the Widevine binary, saving it in a compressed archive. Since it downloads a fairly large file (2Gb+ on disk after download) it is recommended that you run the script on a machine that has plenty of disk space.
To install the resultant archive, issue the following on your ARM machineβafter copying over the archive if needed:
sudo tar Cfx / widevine-flash-20200124_armhf.tgz
(Where 'widevine-flash-20200124_armhf.tgz' is updated to reflect the actual name of the created archive)
A formatted version of https://pastebin.com/EZQWbwCB to make it easier to read. Written by Nick P., not by me. There is discussion on Lobste.rs.
(originally 2014 on Schneierβs blog; revised 2018)
Iβve noticed in recent debates a false dichotomy: you can have βopen sourceβ or proprietary, but not benefits of both. Developers thinking thereβs only two possibilities might miss opportunities. This is especially true for users or buyers that are concerned about source copying, ability to repair things, or backdoors. The good news is there are many forms of source distribution available. The trustworthiness of review process also varies considerably. Iβm going to briefly run through some of them here.