correct, i saw that too. the outage returned 500/nginx. no version number either on footer. @jgrahamc thought that was strange too as few commenters last night were caught off guard trying to determine if it was their systems or cloudflare. supposedly its been forwarded along.
One aspect that I haven't seen considered is how useful increasing the brightness for folks who are disabled like myself. I have a rare eye condition where the amount of light omitted really matters to me. It's one reason why I look at nit brightness each year on phones and monitors. I can say it really helps the more light these devices can output and how it impacts my vision. It's why I try to upgrade more frequently.
night and day. it's the reason I sought out something like multipass. I first started with a license for Parallels Desktop and noticed the disk performance to be way better. Once I came around to multipass, I ditched Parallels Desktop because I liked having cloud-init support, so all my workstations can easily spin that up when setting them up on a fresh-install or a new machine. I have my own dotfiles so automating all of that was a win. Also the auto-mounting of the home directory was a nice touch so I could bind volumes like Docker Desktop does out of the box for you. I would say if you aren't doing heavy i/o across binded volumes you might not notice. But for a client of mine I was having Docker do some large C++ compiles of a project that even after bumping up the cores + memory of Docker Desktop, still felt slow. When trying Parallels Desktop and multipass it felt way snappier and compile times were heavily reduced.
I've been running multipass for awhile now to host Docker on macOS, especially on M1. I ended up writing a guide/docs on how to easily get it setup with cloud-init to replace Docker Desktop. Hope this helps anyone.
i agree they are definitely getting better though. i have memberships to both and have been watching how they have improved quite a lot in last few months. the big reason why i got a membership to walmart+ was due to Amazon going from (1 day shipping for last 3 years) to (4+ days!) in the Louisville market, which makes no sense. We have multiple warehouses in the area. Tons of articles/forums discussing it, so definitely im not an edge case. Strangely enough when testing out the membership types (personal vs business) of amazon they are now just finally giving me 1-day shipping on my business account but not personal (verified using both items). Walmart+ has them completely beat on some items that are usually essentials that you can get at the local store. Plus they are offering same-day shipping for free, since they are coming from the store. I've had multiple times where I ordered something from Walmart+ where it said 2-3 day shipping and within hours, it turned into 'Oh we found it local' and delivered it that day.
I went ahead and created vscode-readme it takes the templates used on readme.so and creates a snippet per section and if you use the readme snippet it combines all the sections https://github.com/ThreeCommaIO/vscode-readme. I just published to the extensions marketplace too.
I can speak from experience on this, home made cache can be much better depending on your avg object sizes. Letting the OS make decisions usually in databases is the wrong choice. The data is cached at page level (4k), if you have many objects randomly spread across your working set it's not going to be as efficient as object caching. Usually the more control you desire the better for the performance of your database. One technique that is used if you want to just let the OS deal with cache/paging of data is you have a dedicated commit log that is written with fsync on every update or periodically depending on your durability requirements.
The OS usually does a pretty good job, but remember it's designed to be generic not for a specific use case. When you really care about performance of a database you tend to bypass what the OS does, and take control bypassing things like the scheduler, cache, etc.
Yes, I think the article got that wrong. You are right that Gizzard is eventually consistent. The storage engine for Gizzard is mySQL, so in the event you want to do some node-local indexing, you at least have mySQL's strong consistency, but you won't achieve it in the overall system across keys.
When Manhattan first started, our first use case was this. To support batch (something we talk about in our blog post). Similar to ElephantDB, the biggest difference was we wrote our own storage engine (seadb), instead of using BDBJE. We built the hadoop pipeline service so developers only needed to supply us with sequence files and we did the work for them by watching.
Over time, Manhattan evolved into a fully fledged read/write database that is able to support batch + read/write in the same system. Batch is great for some use cases, but sometimes the cost is too expensive when you factor in how much processing power, storage, etc is needed for that model. We support both of course still we want developers to have the freedom to increase their productivity.
Because in-house we have a custom version of memcache. We rewrote memcache's slab allocator, and for some use cases, is better at memory efficiency than Redis.