Don't get me wrong, I really like the device but it needs a few more years to be easy to use and maybe a new hardware revision to get better performance. I get about 9 hours standby time (wifi on, modem off), at least the screen on time is pretty good.
And maybe for creating playlists? And maybe for modifying playlists? And maybe for searching for songs/albums/artists? And maybe for modifying metadata?
Considering all these features that needs to be supported it makes sense IMO that it's a specific protocol.
Well, since you've only worked for 3 years I bet you haven't seen many different workplaces either. I've been a professional developer for 3 years and 80% of the people I know use either vim or emacs. The difference between you and me however is that I'm aware that I have been to very few workplaces and don't assume that most people use vim or emacs because of my limited experience.
Which is why Result and Error types exist. With those you get both the context of the error as well as making it clear that the code you are entering needs error handling to be safe. Much less of an issue than calling code that unexpectedly raises exceptions.
And they do have their uses but they are not good enough by their own. Having both exceptions, result types and maybes is a lot better to have and to use appropriately than only have one or the other.
Any half-decent VIM user knows that there are no good vim emulators, only ones which do the absolute basics right. That includes vim mode for vscode which last time I used it even lagged when using it.
The only vim mode that didn't make me rage quit was evil mode in emacs. I use mostly vanilla vim, and there's always something that isn't implemented or isn't implemented properly.
Well, yeah, not sure why you even wrote this except to get some snark in. The point is the trade off of having the basic if imperfect operation of vi/vim, along with what vscode offers. That includes connecting with the large community of vscode users.
Ironic, the most complicated thing for me to understand when I started writing rust was borrowing and lifetimes. The rest of the common features of Rust isn't too complicated to understand.
Understanding the concepts is not the issue with me (as of now). It is the hard to read syntax (my personal opinion!). It puts a lot strain on my mind. Same is the case with C++ with extreme use of STL. I have difficulty in reading that, although with clear mind, I will eventually get the code, it is not fun.
No great battery life on ultrabooks? Have you ever even used one? The XPS has one of the best battery life on the market and other thin laptops like chromebooks have great batterylife while still being thin. The reason why 11-14" ultrabooks have good battery life is very simple: SSDs take up less space and are more efficient, iGPUs take up no space and are more efficient and no DVD drive taking up space.
I love my Chromebook with coreboot and archlinux, but I need a upgrade to a 1080p screen and more than 4gb of ram without having to pay $1000 for a overpriced laptop with a dual-core i7.
I only got about 4 hours on an older ultrabook (about 5 years ago) with an SSD. I'm not sure what you get these days but under in the 3.5-4.5 hour range isn't very good IMO.
For isolating your database from your host OS.