You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For those who prefer to avoid solutions like iCloud Photos and Dropbox for
backing up photos, you can sync your iPhone photos with Syncthing. To do this,
you'll need two things:
Möbius Sync is, to my knowledge, the only
actively-maintained Syncthing client for iOS. It's free to sync up to 20 MB,
and only $4.99 (one-time) to remove that limit.
PhotoSync is a nifty iOS app for syncing
photos to a number of different destinations. It's free for low-quality
I'm going to do something that I don't normally do, which is to say I'm going to talk about comparative benchmarks. In general, I try to confine performance discussion to absolute metrics as much as possible, or comparisons to other well-defined neutral reference points. This is precisely why Cats Effect's readme mentions a comparison to a fixed thread pool, rather doing comparisons with other asynchronous runtimes like Akka or ZIO. Comparisons in general devolve very quickly into emotional marketing.
But, just once, today we're going to talk about the emotional marketing. In particular, we're going to look at Cats Effect 3 and ZIO 2. Now, for context, as of this writing ZIO 2 has released their first milestone; they have not released a final 2.0 version. This implies straight off the bat that we're comparing apples to oranges a bit, since Cats Effect 3 has been out and in production for months. However, there has been a post going around which cites various compar
As an exercise, I started to design and implement a database in some of my free time.
As I started working through some of the details, there were a few things that I knew I wanted to work with and a few things I wanted to evaluate.
Since I'm looking at more of a CP system, my mind immediately jumped to Raft.
But which implemenation to use?
And what storage mechanism?
Since I had more familiarity with Hashicorps implemenation, I started there.
The first thing I wanted to do was consider the performance characteristics of the underlying data stores.
One of the nice features of the hashicorp implementation is it allows callers to plugin in different stores for logs, stable, and snapshots.
There's a whole slew of community implementations.
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
Use ESM yourself. (preferred)
Use import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.
Macro hygiene is the concept of macros that work in all contexts; they don't affect and aren't
affected by anything around them. Ideally all macros would be fully hygienic, but there are lots
of pitfalls and traps that make it all too easy to accidentally write unhygienic macros. This guide
attempts to provide a comprehensive resource for writing the most hygienic macros.
Understanding the Module System
First, a little aside on the details of Rust's module system, and specifically paths; it is
Demonstrating the effect of JVM arg -XX:-MaxFDLimit on OSX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters