You have no clue what SQL or ACIDity is. For 99% of the cases SQL/RDBMS is the right choice. You probably think you belong in that 1%, but from your comment, I suspect you do not.
> I choose to use NoSQL for virtually all my projects
That's because you have no important data to store.
When you get to store data that are important to your customers you're gonna have a big revelation.
"NOSQL" doesn't mean "no ACID". There are plenty of NOSQL DBs that are ACID compliant. And SQL is not the only way to write your queries. There are a lot more QLs.
In that case, the Ethereum hard fork doesn't sound very controversial - even if the devs decided to hard fork for bad reasons later on, no one would be forced to adopt it. They would be "voting with their feet" by sticking to the old chain.
[1]: https://github.com/google/seesaw/blob/master/common/conn/con... [2]: https://github.com/google/seesaw/blob/master/common/conn/ipc... [3]: https://github.com/google/seesaw/blob/master/common/conn/rpc...
Though according to the feedback online, Freenom to domains is not what Letsencrypt is to SSL. Their business model (cancel domain name registration then ask $xxxx to register it again) looks like fraud to me [1].
Location: Central Asia
Remote: Yes
Willing to relocate: Yes
Technologies: Proficient in Go (Golang), MySQL, RethinkDB; Git; HTML, CSS; Web, HTTP; GNU/Linux; Continuous Integration (CI), Test Driven Development (TDD); Have experience of PHP, JavaScript, MongoDB.
Resume/CV: https://bit.ly/2dCmzWH
Email: hn2016@protonmail.com
~~~
I am a security conscious software engineer mainly focusing on back-end; B.S.E.; looking for a position that requires a self starter with can do attitude. Work on open-source projects and communication with other developers as part of responsibilities is a plus. Both remote work (in any timezone) and relocation are OK. I am, however, not authorized to work in the US or EU.