409 karma · joined December 6, 2014
GitHub: https://github.com/molszanski
Locking env version is important.
Double points for using experimental / POC technology like gatsby or nextjs. They are expected to burn and fail
How many machines this migrator was running on? One? :D Sounds absurdly amazing!
We’ve recently moved one service from next to Astro and it was just removing a ton of boilerplate and “dance around” code.
Is it? I feel that there is a stark difference between what you say and what I remember what was written in the book.
> We don’t know how human intelligence works.
I think it was addressed in the first half of the book. About research and progress in the subject. Both with the tissue scanning resolution, emulation attempts like human brain project and advances in 1:1 simulations on primitive nervous systems like worms that simulate 1 second in 1 real hour or something.
While primitive, we are doing exponential progress.
> Yet, the Bostrom view is that our greatest invention will just suddenly "emerge"
I think it is quite the contrary. There was nothing sudden in the reasoning. It was all about slow progress in various areas that gets us closer to advanced intelligence.
The path from a worm to a village idiot is million times longer than from a village idiot to the smartest person on earth.
> an entity able to create new knowledge at astounding rates yet completely lacking in other human qualities.
This subject was also explored IMO in the depth...
Maybe my memory is cloudy, I've read the book 5+ years ago, but it feels like we've understood it very (very) differently.
That said, for anyone reading, I am not convinced by the presented argument and suggest reading the book.
I highly, highly recommend this book "Superintelligence" by Nick Bostrom
https://en.wikipedia.org/wiki/Superintelligence:_Paths,_Dang...
It has one of the highest information and idea density per paragraph I've read.
And it is full good ideas. Honestly, reading any discussion or reasoning about AGI / Safe AGI is kinda pointless after that.
Author has described all possible decisions and paths and we will follow just one of them. Could find a single flaw in his reasoning in any history branch.
I would rather have a more examples. And kinda _advanced_ and complex, rather than trivial we see in the docs.
Even though I had a working V1 configs and had a know-how about lingo / architecture like routes / services I still struggled for a day or two to properly configure a pretty simple workflows in v2 like:
* add TLS with LetsEncrypt
* configure multiple domains
* configure multiple services
* add Basic Auth for some domains
That said, more detailed and extensive docs would be much better.
I also remember finding things in github issue comments that worked as bugfix/workaround of something from the docs.
PS. For now I've moved to Caddy for simplicity and better Caddy DSL compared to yaml/label verbose config.
https://www.prometheusfuels.com/news/dude-wheres-my-fuel
I am curious how do they compare
Same. React as a UI library is great. React as a state manager (hooks) or a framework is (hooks or hooks+next) is not good. Writing and fusing business logic to a framework is always a bad idea