foundationdb VS PowerToys

Actually, Apple does this for iCloud! They use FoundationDB[1] to store billions of databases, one for each user (plus shared or global databases).

See: https://read.engineerscodex.com/p/how-apple-built-icloud-to-...

Discussed on HN at the time: https://news.ycombinator.com/item?id=39028672

[1]: https://github.com/apple/foundationdb https://en.wikipedia.org/wiki/FoundationDB

Is this the language in question? https://github.com/apple/foundationdb/blob/main/flow/README....

> I wondered if perhaps this WASM use case for a cross-language library was already just as possible and ergonomic using language bindings and maybe thats why this use case doesnt seem like a big deal to people.

Yeah that’s the reason. You don’t notice it a lot of the time, but FFIs are everywhere already. The most common foreign function interface is basically the ability to call C code, or have functions made available to C code. C is used because everyone knows it and it’s simple. And most languages either compile to native code (eg rust) - which makes linking to C code easy. Or the runtime is implemented in C or C++ (eg V8, Ruby). In languages like that, the standard library is already basically implemented via a FFI to C/C++ code.

I’ve got an iOS app I’m working on that’s half rust and half swift, with a touch of C in the middle. The bindings work great - the whole thing links together into one binary, even with link time optimizations. But the glue code is gross, and when I want to fiddle with the rust to Swift API I need to change my code in about 4 different places.

Most FFIs are a one to many relationship in that if you write a clean C API, you can probably write bindings in every language. But you don’t actually want to call naked C code from Ruby or Javascript. Good bindings will make you forget everything is done via ffi. Eg numpy. I haven’t looked at the wasm component model proposal - I assume it’s trying to make this process cleaner, which sounds lovely.

I maintain the nodejs bindings for foundationdb. Foundationdb bindings are all done via ffi linking to their C code. And the API is complex, using promises and things. I find it really interesting browsing their official bindings to go, Java, Python and Ruby. Same bindings. Same wrapped api. Same team of authors. Just different languages. And that’s enough to make the wrapper wildly different in every language. From memory the Java ffi wrapper is 4x as much code as it is in Ruby.

https://github.com/apple/foundationdb/tree/main/bindings

Isn’t apple server on C/C++?

They have their own db in that

https://github.com/apple/foundationdb

> Any meaningful technology is open source.

Clearly untrue, however FoundationDB is open source, with a permissive license.

https://github.com/apple/foundationdb

So is much of the operational tooling for it:

https://github.com/FoundationDB/fdb-kubernetes-operator

I don't recall any of those details but the test involved injecting a bogus block device that always returns garbage, and noting that this results in garbage records returned from client queries. And I don't think those kinds of issues have been eradicated, browsing through their github issues there are people trying to recover corrupted clusters. https://github.com/apple/foundationdb/issues/2480

For my current job, I have to install FoundationDB (they have a github repo) as a dependency for the project's code.

To clarify, FoundationDB has some documented multi-region features, but it's not at all clear that anybody who runs it at scale relies on those multi-region features [1]. Even if they do, it's not obvious they run this Fearless DR mode at any appreciable latency.

Geo-replication is an area where Anna really shines, and foundation pays severe costs. All of the concurrency control problems have contention footprints on the order of round-trips. Fully optimistic concurrency control needs to expose backoffs quite a few round-trips to be live. Even pessimistic concurrency control requires some number of round trips, probably at least 1.5 optimally, but in practice in most tuned systems, probably 3. A heck of a lot of use cases make sense at 0 global RTTs and don't at 1+. The ability to tell the database how to manage concurrency, and then providing causal is ultimately the best you can do. That's awesome.

At the end of the day, I have to believe that there's a whole big mess of applications we'll build this, on systems in the portion of the design space Anna is choosing, one day. This is only recently not cutting edge research, but it's definitely still research. We don't know how to model these concepts at a high-level and in a composable way where the masses of software developers can engage with them.

It's interesting to think about how long ago we were graced with BAYOU [2], that thing was ahead of its time. I suspect it's going to take a little while longer before these sorts of techniques make their way into data storage primitives we think of as part of the standard vernacular, but I believe we'll get there eventually.

Databases are fun!

[1] https://github.com/apple/foundationdb/wiki/Multi-Region-Repl...

Windows PowerToys GitHub Repo

RunFlow is a cross-platform productivity tool which can launch apps and search files and more, that similar to Wox and PowerToys on Windows, and also similar like Alfred and Raycast on macOS. But we have differences with these tools, and we have our own unique new features. Right now, at the below, we will introduce you what features of RunFlow have been implemented in more details. It's an amazing journey, let's start.

I'm curious - when you were doing research into the mechanics of hinting options, did you stumble onto any relevant discussion around allowing custom pixel geometries to be defined, to enable hinting on modern OLED / WRBG displays? There's a good thread on the topic here[0], with some people referring to it as 'ClearType 2' on the MS side [1]. On the oss side I know FreeType theoretically supports this[2], but I can't quite figure out how relevant the FreeType backend is to this most recent work.

This is great work btw.

[0]: https://github.com/snowie2000/mactype/issues/932

[1]: https://github.com/microsoft/PowerToys/issues/25595

[2]: https://freetype.org/freetype2/docs/reference/ft2-lcd_render...

Thank you all for the informative advices. Here is the summary for those who are in the same situation:

1. Run Windows on Linux by using VM

for the applications you can’t run on Linux

Risks:

* some softwares may attempt to detect VMs and refuse running

* Anything what needs to touch hardware may not work.

2. separate "data" partition on D:

3. back up %APPDATA% and %USERPROFILE%

4. learn chocolatey, scoop or winget

Winget should be good enough

5. Don’t worry about C:\Program Files

6. (Mixed) Use/Don’t use Ansible (or saltstack/salt)

Use:

* Allows you to setup a new machine quickly and consistently when one breaks, get stolen, or lost in an inconvenient time.

* You can get a clean and consistent development environment so that you do not depend on anything accidentally installed on the machine.

* If you define specialised roles, create test playbooks for those individual roles, use these roles to compose more complex playbooks, and offload logic to custom ansible modules that are written in python, you won't wrestle with heavy logic in the template or playbook layer.

* installing software and pulling some configs and scripts down is fine

Don’t use:

* You will spend your days fighting a mix of yaml and Jinja.

* You will end up looking at Python errors because there are no static types.

* errors are cryptic.

7. Use WSL2

You need 32gb of ram, but ram is cheap so choose a good thinkpad

8. Debloat with Recommended Tweaks

Run

irm christitus.com/win | iex

from Administrator Terminal (Powershell)

The link leads to https://raw.githubusercontent.com/ChrisTitusTech/winutil/mai...

VirusTotal

https://www.virustotal.com/gui/file/709834b0e003b6bb546cf16e...

9. Get [PowerToys](https://github.com/microsoft/PowerToys)

10. Use Devbox for containered environment

https://www.jetpack.io/devbox

11. Dual-Booting Linux and Windows

If you use physically separated drives, you don’t need partitioning.

12. Dedicated Windows machine for class

Yes it sure would be the cleanest solution but I prefer one device for everything

13. keep a git repository with all dot files in it

Many people suggested me to use virtualization, otherwise just let Windows be Windows.

Also, backing up seems to be a good practice.

I’m planning to write a blog about this, if it worked.

Again, thank you all for the helps!

Powertoys Run (https://github.com/microsoft/powertoys) can do this. There are not that many plugins as Alfred but Window Switcher is built-in.

For sharing a mouse/keyboard between Windows PCs, there is Mouse Without Borders. It's included in PowerToys nowadays.

https://github.com/microsoft/PowerToys

- https://github.com/microsoft/PowerToys

If you’re on Windows, download PowerToys. It’s an app published by Microsoft officially. Then enable Quick Accent in the settings of PowerToys. Now all you have to do is hold down the key you want accented until the switch shows up, then add an accent with your arrow keys.

microsoft/PowerToys: Windows system utilities to maximize productivity (github.com)