Friday Blast #56
16 ways to measure network effects (2018) - a company has network effects when users benefit from new users coming into the platform. Think of Facebook, Twitter or Uber as canonical examples of these sorts of businesses in the tech space. This article is a rundown of no less than 16 metrics to describe such companies. Obviously useful for insiders, though some of these are reported by public companies as well.
Things UNIX can do atomically (2010) - I recently needed to do some inter-process synchronization from Java and thought about using file-system methods for locking. This turned into a goose chase of “thing I can actually” lock on, and turns out just linking and file/directory creation (in certain modes) are OK.
Lock on existance of file in Java (2014) - a SO thread where I started my search and which lead to the previous article. What I ended up using was picked up from here, namely File.createFile
.
A tale of two standards (2005) - a comparison of POSIX and the Win32 files API. I kind of missed the boat on Windows as a target for programs, so I have only the fuzziest knowledge of what it is all about. Save for ASP.NET work, which is far removed from anything system level. So I’m always impressed at the tech chops of the folks who built the system, and the somewhat unwarranted flak the business side has drawn on the solid technology part. Still reading on locking at this point.
Addendum on the Brokenness of File Locking - more woes of file-locking. But in the presence of NFS. Which we all knew was kind of borked to begin with, cause it couldn’t offer POSIX compliance well. OTOH, you never know if the disk you’re writing to is a local or remote one in some cloud providers. So “this won’t happen to me” is not a valid excuse to try the file locking in POSIX.