202 karma · joined July 16, 2014
I think you may be living in a bubble.
Hash: SHA512
Yeah!
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE1cv7ESh+CzooffWR/YGUxUpj29UFAmM107cACgkQ/YGUxUpj
29Walw//fdfXCWWkD7P3fOraYrZw2zKDwJqFtvn4jznGga8MSGzllPfZiWSZtBnI
wAPGLwMwrpzV5wJyP+JUB4/vwZ7Eh7mzDUZuuxvLalVEwkqkTwqM+rhp44YeXVL6
HJnN52pknmuko7R0tHjKOVYz66VAyWaVJLIbLUqP3UWo4O35nttYlUxTBky8fIHs
z3p7ZMDf44AymOozBmRdeG++1VgXS2CQGemZqbSSqgqTa6RFJYAzaz7sBYd14ZgG
pwoPEe/JV7QfxdRwotQgFdyhbwDY7J7dvn/p6pj0eU3HiuHHi4TDMHA7xpuocrku
jWC4CuQ6fVrnsBtSJuZ2H/SvwDCY2cV1FPwO6blzSJ7t+JymCpCj6uwmLnd4S/Pr
twMisrEP6x9V992D8Q9gfMymilNW9wlTdyWVTpzMxjj/tGdYsSqXTJrXnTPqdlnD
jdq3g3YlC8fZQeatdhy2aofbnUr8esvnlu/JwD5dby9tDKBQwGoAenupl+ZY6uEb
2/93tDHsJTmXfhbJ8ndfPNMWL0zEtULpokgM9EUXPgJxM5QcnTf+GtlW6GH/uZlq
Z00GdKW9tF6MC0SKoqW1IQJcq/MQAcDaTr4hwHAVnonXjzTTBpq1r6zSSP4AgqMg
TZ58dM9HPpSWEv7RM3Bp93UPp1M+z761BC0WWkG2PenJu/vw3Fc=
=9+Ii
-----END PGP SIGNATURE-----
While there is value in discrete and planned releases, we value responding to change more.
Users should be aware and make a conscious decision about where their keys are kept, however this is usually something that doesn't matter until they either lose their phone or law enforcement freezes/seizes their money. It's pretty high up on Maslow's hierarchy of financial freedom.
It is a badge of pride to have blue underlined hyperlinks that turn purple if you've been to them before.
I think Next.js does this very well, although I'll admit that their "getting started for total beginners" documentation spends way too much time explaining the magic. If I were to throw someone into the deep end to make their own mistakes, as I assume we all did with PHP, I would tell them to git clone https://github.com/vercel/next-learn/tree/master/basics/lear..., and then experiment with "pages/index.js".
Hot reloading that you get out-of-the-box with most JS frameworks is a massive improvement over static HTML, or PHP.
SSI still works, and you can turn it on with Nginx. It's still quite limiting and fragile.
PHP still works, but as your project grows, unless you have equally experienced PHP developers, you'll see things get out of hand quickly with scope issues.
CGI will still work, but similar to PHP, it's a headache to setup the sandbox so a malicious or naive committer doesn't clobber the environment. At least PHP's defaults were pretty sane until someone does something cute and bypasses magic quotes and introduces some SQL injection.
Let's give AWS Lambda some credit though, it's virtualized and containerized CGI and can scale to handle loads that you'd think your backend was written in Elixir.
The issue is really around having multiple handles for writing (not just reading or appending), and the number of times you actually have this problem here is vanishingly rare.
(2) If not, what app was this?
They're stored in the Arctic Code Vault, as well as more replicas than you can imagine, because git, so I could imagine there's very little risk of data corruption, and because of the amount of knowledge stored in this standard format of static HTML, there's strong incentive for people to preserve it and keep hosting it if Microsoft becomes evil again and decides its not profitable. Moreover, if you PGP-sign your git commits with a 4096-but RSA key, you can be fairly sure nobody will edit your commits (perhaps for at least for the first 200 years). I believe the key here is lumping your data in with other high-value data.
There does exist a hub that has 2 USB-As and 2 USB-Cs for 50 USD, but it does not pass through video or power.