I'd recommend NixOS instead. Trying different desktops is easy as changing the config and doing a `sudo nixos-rebuild test`.
Arch with its rolling release model is prone to breakage. Every upgrade gets you closer to having to reinstall everything from scratch. On contrast, NixOS is transactional and if something breaks you can switch to a previous version easily.
(I actually went from Arch to NixOS, after using Arch for about 3 years).
To be fair, some of those are full database engines; they have lots of inherent complexity to tackle.
Hasura provides an interface to a database(/s) engine. GraphQL was supposed to solve the interface problem but it looks like it has created a lot of accidental complexity to tackle.
Q: Regarding multi-cloud. Say if AWS has an outage will Timescale cloud fallback to use GCP or Azure?
Can something like this be provided? Not sure if the network latency between different cloud providers would allow doing a multi-master replication scheme.
Billy's mommy had ties with IBM CEO John Opel, this is often overlooked but it's the key to MS success. Don't overestimate the philantropist , he always had a rich family.
I was thinking for a while now that a license like this was needed, the redistribution of copies seemed to me the main problem. It makes so much sense to tie the code to a physical medium.
I plan to use physical source on a future project. Thank you so much for sharing.
For me the rolling release model of Arch makes it not the most suitable distro for development, lately I had to fight with the openssl upgrade to 1.1.0 because some rust libs I used no longer worked. Downgrading is not an option for pacman, so I had to resort to compiling on docker containers and that's not the most comfortable dev environment. I'm gonna migrate to NixOS or GuixSD this weekend, the package managers they have are really a breakthrough to package management.
There's a similar "canned procedure" a guy posted in python, why he wasn't judged with the same severity, is there some kind of bias against Haskell around here?
I've read somewhere that for BeOS demos they used to play a bunch of videos and music and then unplug/plug and after boot everything was playing again from where it left. I guess they were using the same design for process persistence.
I was waiting for their Linux client.. I liked the charts and the feature to export them, anyway it was an awesome app with a great UX, really sad to see that go.
I read about this a long time ago in the form of a conspiracy theory, I always see people(even well educated ones) dismiss those and label it as false right away, but seeing that many conspiracy theories have proven to be true I think is time to recognize that this kind of thinking is a fallacy of the form X, X is a conspiracy theory => X is false. So I think conspiracy theories should be taken as what they are: hypotheses.
I somehow understood the same thing(a graph is a collection of points that makes a function true..) a year ago through Gilbert Strang Big picture of derivatives: https://www.youtube.com/watch?v=T_I-CUOc_bk
It's not human nature, even the etymology and history for the word "assassin"(hashish eater) says it, in most of the cases humans have needed drugs to bypass his default nature and kill another human.
I've tried to switch my workflow from vim + tmux + tmuxinator to spacemacs a few months ago, and I must say that it easily could replace my Vim environment, there was evil-surround, evil-nerd-commenter, etc. even neotree, and plus I got org-mode, other really great packages and the power of emacs, however I didn't find a replacement for the tmuxinator part, I need it since I usually have projects with several shells in different windows and panes aside from vim, so in the end that detained me from doing the switch and continued with vim.