> Those people usually go for the low hanging fruit that appeals to most people like preventing the mentally ill to buy firearms. However it is important to note some unpleasant facts like the fact that 11% of Americans are on some antidepressant and probably many more were on some anti depression medication in the past [0].
I'm not a doctor, but I doubt that, say, "mild depression" or "previous history of depression" is enough to be considered mentally incapacitated. Is every person on anti-depressants mentally incapacitated?
The article highlights suicide rates.
> In 2014, Veterans accounted for 18% of all deaths from suicide among U.S. adults, while Veterans constituted 8.5% of the US population. In 2010, Veterans accounted for 22% of all deaths from suicide and 9.7% of the population.
> Approximately 66% of all Veteran deaths from suicide were the result of firearm injuries.
You can't get a drivers license if your vision falls below 20/40. That's a "slight hint of incapacitation".
Edit to clarify: ...without also requiring eye correction. Of course you can wear glasses to drive, but it becomes mandatory, and without that eye correction you cannot get a license.
I have given it a solid try and I've contributed to the hyperline package. But I've had panes crash/go unresponsive kind of frequently. This isn't to say I won't use it, just that I think I still prefer Terminal. One person's opinion is all. :)
I also gave Hyper a solid go but found the native Terminal and tmux/tmuxinator gives me all the same (worthwhile) utility without some bugs related to pane management and history preservation. With Hyper I regularly experienced history being cleared and lost even in the same pane/window, but I couldn't force replication which made it more frustrating. Also, it has some strange feature (?) that can spawn a browser window inside the terminal but I can never figure out how to escape it.
I agree that my terminal shouldn't crash. I handle so many fundamental parts of my workflow in terminal so it has to be stable and efficient.
> Stressing the "deliver quickly" aspect of any language, if you're actually trying to deliver for a business or with a team of people, is extremely destructive short term thinking. And yes, sometimes, in rare cases, it may be a necessary evil, but I think it's become the norm with words like "agile" being thrown around as synonyms for "don't have to write anything down".
Unfortunately, this is pervasive in the "real world", especially with regard to client-driven (agency) work. Deadlines beat developers almost without fail. I agree that it is destructive short term thinking. Entire weeks of programming can be destroyed in a 15-minute phone call that (re)highlights a limitation clients either didn't account for in their specification (if you can call it that) or just chose to ignore.
This isn't to say that using a language or framework a developer is familiar with is baseless, but I've heard this advice before and see it reinforced often:
I built the Chrome extension [0] for Pesticide[1]. It toggles the Pesticide CSS in the current tab making it easier to visualize the placement of elements in the DOM. Useful for front end debugging.
The extensions first implementation was basically just a ternary operator! Now it's got a little more to it, but it's still super simple.
I use `git add . -p` which allows me to 1) selectively create my commit, and 2) re-read what I've changed to understand it all better. I agree about wholesale adding, but of course there are exceptions when you already did `git diff` Or something.
Side note: `git status` is not a good means of "knowing what was changed". I see others use it constantly (doing git status -> git add . -> git commit) and it'a sloppy IMO.
I was just looking at your pricing. :) All in all Netlify does offer a compelling service for this scope. I'm also interested in the Pro tier being free for OSS, that's fantastic!
To be fair, setting up AWS for the first time is a real PITA and I happen to have had it all set up (IAM, buckets, command line, etc) already, so my barrier to entry was low. Had I known of Netlify when I first moved my site to AWS I probably would have gone with Netlify for the convenience and free HTTPS cert.
Nice guide. I have my personal site on the same AWS S3/Cloudfront combo and I effectively only pay for the domain name ($12/yr) and certificate (~$35 for a 2 year?). AWS invoices me monthly for ~$0.05/month in fees with a credit that erases the charge, so I'm not actually paying for hosting. If you're unfamiliar with AWS it can be daunting, but it's mostly initial setup to get it working then uploading changed files whenever you update the site, which was a better choice for me than $5/$10/whatever each month for little or no additional benefit. I'd recommend it for anyone with a static site. I think you'd need a lot of traffic and/or updates to the site to incur $10/month in fees on AWS.
AR content creation tools will likely be desktop apps similar to video editing software. Not that web-based is impossible, but these are probably going to want stand alone apps.
Also, enterprise AR ad placement, buying, and management software could be desktop software.
Apply a max threshold to check if a client is reasonably close to potential "co-located" clients.
You can't shrink physical distance. Pinging a server in a nearby US city is 13ms. Hong Kong is 232ms.