@lnxw48a1 I have specifically resisted linking paypal to my bank account for this reason. In the past, when I had my personal paypal linked to my account not only would I be on the hook often for transactions I didn't authorise (often because unscrupulous online merchants like to set the transations as reoccuring), I'd also be on the hook for NSF fees from my bank. Thankfully, my bank would forgive the charges when I would claim them as unauthorised, but paypal eventually froze the personal account. I actually have the HLA account in a business name with someone else who deals with that BS for me so I don't have to, at this point. I would not use paypal if there was an alternative in Canada.
Verius (verius@community.highlandarrow.com)'s status on Monday, 29-Oct-2018 14:44:20 EDT
Veriushttps://blog.regehr .org/archives/1393 I kinda disagree with Rust being the obvious choice to replace C. It's not a bad choice in many respects but I feel that Rust lacks something often overlooked but very important in C: pragmatism. Now C is a bit too pragmatic at some points but I doubt that working programmers with deadlines will be itching to learn Rust and fight with the borrow checker. Sure, you learn, but let's not forget that most Rust programmers at this point do so voluntarily meaning they're already way ahead of the pack in terms of skill (mediocre programmers rarely go out of their way to learn a new language). Though it's a bit of a long shot at this point I expect D with the BetterC flag to match the mindset of a C programmer better. Looking at https://dlang .org/spec/betterc.html the things that are removed are not in C anyway (so C programmers won't miss them) but there are still a lot of things that make programming easier _without_ requiring a D runtime lib (only a libc, which isn't different from C of couse). And unlike Rust D is pragmatic, it doesn't force you to adapt your code to fit a borrow checker. Ok, to be fair D also doesn't force you to write memory safe code, it only gives you tools to write better code (e.g. array slices which help avoid silly array bugs).