It doesn't take being bad with money to get hit by insufficent funds fees. If you're poor, you don't have cushion. If anything goes wrong (fraud transaction, runup phone bill, spouse makes purchase same day) and you get overdrafted. Then the bank sees you bought a sticke of gum earlier that day and decides to order transactions high to low so you get hit by another overdraft fee.
This problem is easily solvable; banks don't want to because it's the only way they can make good money on low banances.
That's really just hidden merchant fees though. And worse, those hidden fees get paid whether or not you use cash or credit, because the fees have already been priced in.
This is why we need to support Bitcoin. Technical hurdles have mostly been leapt at this stage. Time to solve some of the design hurdles, then get everyone moving into the new era.
This is the great Bitcoin Miner's Fallacy. So many do not understand the basics of what they're doing.
I talk to people all the time who talk about buying a GPU rig and finding a coin to mine. I always tell them the same thing: buy BTC instead. None of them do. None of them get much farther than "I can print money like a real hacker!"
The ones who make it a few steps farther end up paying for losing mining rigs.
We're far from the tipping point. The institutional operators have different classes of hardware. They shut down the inefficient ones, but have plenty of newer ones to handle the network until the next difficulty adjustment. The price would have to fall far and fast (even for BTC) for a mining difficulty network collapse to take hold.
The allure for me as a developer is the fact that I can setup payments for an app using open standards. As many have said before, payments are a protocol that has been long missing from the Internet.
OS X Terminal is easily one the best terminal apps in existance. Linux is only starting to catch up to some features (reflow is sick). Most definitely not an afterthought.
GitKracken is great, but I'm skeptical if it's worth an annual subscription. I use it primarily to stage parts of files, but I still end up on the command line a lot. Especially because I work on lots of small projects (Node.js), the slow startup time is a killer.
I installed OpenSSH server on Windows over a decade ago. It was almost painless. Would it be nice to have it installed out of the box like OS X and most Linux distros? Sure. But that's hardly a significant difference between platforms.
Windows CLI has supported history and tab completion for decades, at least. If that's your selling point, may I suggest you periodically (say, once every decade) check out the alternatives.
I call bullshit on "full intellisense". I wrote a three-line ps1 script the other day with several inline evaluations and property references and not a goddamn thing came up from intellisense.
Maybe there's intellisense, but nowhere near "full" intellisense.
As devops engineer, I've never felt the desire to have a Python REPL available. Frankly, no REPL is signicantly better than Bash with readline, and nothing beats pipes for interoperability. Pipes are the one form of IPC anyone can easily get to work with Bash, Python, Javascript, Perl, Ruby, C, C++, Go, Rust, etc.
OS X learned this lesson well. Simple GUIs, with advanced features only available from CLI. Windows tries to keep dumping more and more crap into the GUIs, until they are bloated and nigh unusable.
GUIs don't intrinsically make things more discoverable. Only GUIs specifically designed for discoverability.
If you think making edits in the registry or through Group Policy are discoverable, you're crazy. Even having different apps for different things (essentially all admin tools except MMC) tanks discoverability. Add to that a schemaless registry and scattered policy docs, and your GUI discoverability is going to essentially rely on Google to perform the discovery.
Slashdot Mirror
If a truck delivers to ten houses, that's better than ten people traveling to the store.
Fucking morons.
It doesn't take being bad with money to get hit by insufficent funds fees. If you're poor, you don't have cushion. If anything goes wrong (fraud transaction, runup phone bill, spouse makes purchase same day) and you get overdrafted. Then the bank sees you bought a sticke of gum earlier that day and decides to order transactions high to low so you get hit by another overdraft fee.
This problem is easily solvable; banks don't want to because it's the only way they can make good money on low banances.
That's really just hidden merchant fees though. And worse, those hidden fees get paid whether or not you use cash or credit, because the fees have already been priced in.
I feel like most banks that operate primarily online refund those charges. Ally and Navy credit union both do this.
This is why we need to support Bitcoin. Technical hurdles have mostly been leapt at this stage. Time to solve some of the design hurdles, then get everyone moving into the new era.
Did you miss the part where it says, "can make it hard for them to stay organized or focused"?
This is the great Bitcoin Miner's Fallacy. So many do not understand the basics of what they're doing.
I talk to people all the time who talk about buying a GPU rig and finding a coin to mine. I always tell them the same thing: buy BTC instead. None of them do. None of them get much farther than "I can print money like a real hacker!"
The ones who make it a few steps farther end up paying for losing mining rigs.
We're far from the tipping point. The institutional operators have different classes of hardware. They shut down the inefficient ones, but have plenty of newer ones to handle the network until the next difficulty adjustment. The price would have to fall far and fast (even for BTC) for a mining difficulty network collapse to take hold.
It would hurt, but it would not fail. That's the power of a decentralized platform. Most platforms die with their corporate sponsors.
The allure for me as a developer is the fact that I can setup payments for an app using open standards. As many have said before, payments are a protocol that has been long missing from the Internet.
But enough talk! Have at you!
As long as you can recover from the stall before you hit elevation 0, you're good.
OS X Terminal is easily one the best terminal apps in existance. Linux is only starting to catch up to some features (reflow is sick). Most definitely not an afterthought.
GitKracken is great, but I'm skeptical if it's worth an annual subscription. I use it primarily to stage parts of files, but I still end up on the command line a lot. Especially because I work on lots of small projects (Node.js), the slow startup time is a killer.
I installed OpenSSH server on Windows over a decade ago. It was almost painless. Would it be nice to have it installed out of the box like OS X and most Linux distros? Sure. But that's hardly a significant difference between platforms.
Windows CLI has supported history and tab completion for decades, at least. If that's your selling point, may I suggest you periodically (say, once every decade) check out the alternatives.
I call bullshit on "full intellisense". I wrote a three-line ps1 script the other day with several inline evaluations and property references and not a goddamn thing came up from intellisense.
Maybe there's intellisense, but nowhere near "full" intellisense.
PowerShell has always come with built-in aliases to make the environment usable for Unix/GNU users.
Until MS abandons this paradigm in a couple years when CLI is no longer the "new" hotness.
As devops engineer, I've never felt the desire to have a Python REPL available. Frankly, no REPL is signicantly better than Bash with readline, and nothing beats pipes for interoperability. Pipes are the one form of IPC anyone can easily get to work with Bash, Python, Javascript, Perl, Ruby, C, C++, Go, Rust, etc.
You may want to stear clear of Linux, where there are hundreds more ways to do everything.
PowerShell has all the same problems as every other CLI Windows app.
OS X learned this lesson well. Simple GUIs, with advanced features only available from CLI. Windows tries to keep dumping more and more crap into the GUIs, until they are bloated and nigh unusable.
GUIs don't intrinsically make things more discoverable. Only GUIs specifically designed for discoverability.
If you think making edits in the registry or through Group Policy are discoverable, you're crazy. Even having different apps for different things (essentially all admin tools except MMC) tanks discoverability. Add to that a schemaless registry and scattered policy docs, and your GUI discoverability is going to essentially rely on Google to perform the discovery.
Maybe, but piping objects between scripts is fucking amazing.