Fluture VS myria

My name is Aldwin. I'm back-end-leaning full-stack (web-) developer with over 13 years of full time professional experience at various software development agencies. Besides that, I have years of hobby-programming and open-source experience, with Fluture[1] being my most well-received.

I've been leading small teams for the last eight years, focusing on developer enabling work such as process management, devops, software architecture, and coaching.

I'm very passionately in particular about functional programming, and I'm hoping to coach teams when it comes to the cross-over between functional programming and software architecture - something a lot of developers who are new to FP struggle with.

Although I have been involved in a huge variety of software types, I'm particularly well-experienced when it comes to real-time, offline-first web-applications and real-time data processing.

[1]: https://github.com/fluture-js/Fluture

I think that it is fine to code perfectly functional apps using TypeScript with React Native and React. You will have a huge community to support you with documentation, libraries, and available labor. Yes, the language has a lot of soundness holes and misses a lot of useful features like pattern matching or type classes but, for me, it is a valid trade-off. There are libraries for better FP programming in TypeScript like fp-ts, io-ts, and fluture.

Fortunately, as it has been shown in this article, it’s definitely possible to use functional programming with plain JavaScript. However, if you really want to dive deeper into this paradigm while using JavaScript, you’ll probably want to use some already existing functional libraries such as Sanctuary, Fluture, Ramda and others.

This is great news for functionally-minded libraries such as Ramda, Sanctuary, Fluture, and many more. But it also makes some vanilla JavaScript nicer, for example:

Location: Seattle area

Remote: Yes

Willing to relocate: No

Technologies: C/C++, Python, Java, SQL, Linux, DB engines, systems programming

Résumé/CV: https://www.linkedin.com/in/tobinbaker/, https://www.dropbox.com/scl/fi/0ai2g6loja08p90hwj6zq/TobinBa..., https://github.com/senderista/, https://senderista.github.io/atomik-website/

Email: [email protected]

I've been working for the last 3 years on an in-memory MVCC DB engine in C++, built from scratch. The engine incorporates several innovative design features. It has completely nonblocking transaction open and commit; incremental, concurrent, and nonblocking GC; and direct shared-memory access to data from client processes with zero-copy reads. All critical paths are lock-free and some are wait-free (e.g., transaction validation). Scalability is a work in progress but single-thread update throughput is ~5M TPS. I've also designed and partially implemented a high-level API over this database to expose transactional programming to C++ developers who would never normally use a database: https://senderista.github.io/atomik-website/.

Before starting this project, I worked on a distributed analytical database, supporting multiple scientific users:

https://myria.cs.washington.edu/