meta VS bun

Remote GMT -8 to +2 | (i) Technical Writer (ii) Senior Developer | Full Time | Salaries all visible at posthog.com/handbook/compensation (location-dependent)

https://posthog.com - see handbook at posthog.com/handbook

Open source, 6x rev growth last year, heading for profitability soon, well paid experienced team of 37 today, 25k customers across free + paid products, 65k developers in community, 0 outbound sales - all inbound growth. Didn't raise a 2021 overpriced round - real (potential!) upside.

* Technical writer *

Looking to hire a developer who loves to write. We aim for each piece we produce to be the best on the internet for that topic.

Content marketing is huge for us - writing deep technical content is what we want! You'd be on our (small) marketing team, making a huge impact.

Previous blogging (especially personal/interesting!) and a few years of development experience needed.

If interested, james at posthog.com and charles at posthog.com for a chat.

* Full stack developer *

We are looking for someone to build the next generation of our analytics backbone. You'll be working on ClickHouse and Python to make sure all our queries are web scale and users are happy.

You will (probably) help us build HogQL https://github.com/PostHog/meta/issues/86 (our own wrapper around ClickHouse SQL), or whatever else you think makes sense to prioritize. We work in small teams of up to 6, and you'll have a lot of trust to pick what to work on.

You need experience building high performance data systems, must be an expert at Django with deep SQL/database skills. Ideally, but optionally, you'd have worked in a high growth SaaS company / analytics product and have extensive experience with TypeScript-based React. We need someone ideally that has both worked in a very scrappy / early stage way _and_ ideally has seen a company scale.

This work will potentially extend into providing a full warehouse to our customers. It's a chance to work on the next Snowflake, but open source and product led, working with new companies from day 1 and staying with them as they scale - so get here in the first 40 employees before we are 100x the size.

If interested, james at posthog.com + careers at posthog.com and please mention you saw us on HN.

It has a decent compatibility with both Jest and Vitest's APIs (you can track progress here so you can use it as almost a drop-in replacement for either. Just as Node's, it has describe/it, mock, test and others, but with the expect syntax (which I find more readable). For example:

In this third and final article in the series on HTML Streaming, we will explore the practical implementation of the Diff DOM Streaming library in web browsing. This approach will allow any website using web components to retain its state during browsing. We will discuss in detail how to achieve this step by step using VanillaJS and Bun.

At Node Conference 2023, Jarred Sumner (creator of Bun) showed a demo of server components in Bun, so there is at least partial support in that ecosystem. The Bun repo provides bun-plugin-server-components as the official plugin for server components. And while I haven’t looked at it in-depth, Marz claims to be a “React Server Components Framework for Bun”.

Continuously evolving, Bun is currently optimized for MacOS and Linux, with ongoing efforts towards Windows compatibility. Tailored for resource-constrained environments like serverless functions, it emerges as an ideal solution. The Bun team is committed to achieving comprehensive Node.js compatibility and seamless integration with prevalent frameworks. For those intrigued by Bun's potential and want to give it a try, more information is available on its website at https://bun.sh/.

Let’s say you are interested in learning more about Bun and probably give it a try. Bun has a website, where you can learn more about Bun and its features (including all the benchmark data captured in this issue), and here is the link.

Looks like it, it seems the 2% are mostly odd platform specific issues that the authors' did not deem very important (my assumption for the release happening anyway). AFAIK this[1] PR tries to fix them.

[1]: https://github.com/oven-sh/bun/pull/9729

Bun has a solution for it. First of all, it already has a list of trusted dependencies. For them, Bun will execute all necessary scripts by default. Otherwise, you can add it to trustedDependecies in your package.json file. In Bun community usage of trustedDependencies is a hot topic. There are several suggestions on how to improve it.

Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there

I think maybe I was unclear. I'm talking about writing libraries that abstract across these differences and provide a single API, as sibling describes. I already know it's possible. I made a simple filesystem abstraction here[0] and a very simple HTTP library that uses it here[1]. They both work in Node/Deno and the browser. Unfortunately I ran into issues with Bun's slice implementation[2]. But I suspect there's a much better way of detecting and using the different backends.

[0]: https://github.com/waygate-io/fs-js

[1]: https://github.com/waygate-io/http-js

[2]: https://github.com/oven-sh/bun/issues/7057