Jarred

9 ms·

1. 61.▲
   by Jarred 2y ago

   there have been discussions about this
2. 62.▲
   by Jarred 2y ago

   > Does `bun foobar` translate to `bunx bun-foobar` as well? No.
3. 63.▲
   by Jarred 2y ago

   We are a team, but Dave wrote the code for this project so "I" makes sense
4. 64.▲
   by Jarred 2y ago

   Currently, the REPL is an alias of `bunx bun-repl`, and bun-repl is a community-maintained npm package. We haven't had the time to do our own REPL. Honestly, we really need to hire more engineers. We're a small team and there&#x27
5. 65.▲
   by Jarred 2y ago

   We haven’t prioritized implementing a repl yet. The current repl is a community-implemented bun-repl npm package. `bun repl` internally does the equivalent of `bunx bun-repl`
6. 66.▲
   by Jarred 2y ago

   Try simdutf. You’ll get a performance boost too.
7. 67.▲
   by Jarred 2y ago

   If you like writing Zig, Bun is hiring systems engineers in San Francisco. We are one of the largest Zig projects. https://bun.sh/careers
8. 68.▲
   by Jarred 2y ago

   The timer heap currently lives on a different thread instead of the main thread, which means timers have to be allocated and scheduled separately for each one. Scheduling things to other threads is expensive. The reason it works this way is
9. 69.▲
   by Jarred 2y ago

   We copied libxev's code for the timer heap implementation in Bun for setTimeout & setInterval, and it was a ~6x throughput improvement[0] on Linux compared to our previous implementation. [0]: https://twitter.com/ja
10. 70.▲
    by Jarred 3y ago

    What does the code do? 30-45 seconds to parse a 5k line text file into JSON sounds like something is going very wrong
11. 71.▲
    by Jarred 3y ago

    We'll add cross-compilation support and Windows arm64 eventually. I don't expect much difficulty from Windows ARM once we figure out how to get JSC to compile on that platform. We support Linux ARM64 and macOS arm64.
12. 72.▲
    by Jarred 3y ago

    I’m pretty sure issue #6842 was fixed in Bun v1.0.32 or so and we forgot to mark the issue as fixed Will check once I get to my computer Edit: was not fixed. We made other changes to fs.readSync to improve Node compatibility, but missed thi
13. 73.▲
    by Jarred 3y ago

    This is dead code from before Bun 1.0. This code exists but is not run and probably stripped from the final executable (Zig is great at dead code elimination). We do get the Linux kernel version to detect if syscalls like pidfd_open are sup
14. 74.▲
    by Jarred 3y ago

    We’ll add the uncaught exceptions handler likely before Bun 1.2 and fix the issue with sourcemaps. Sourcemaps do work (with some rough edges) at runtime when running TS/JSX/JS files, but are in a worse state with “bun build” right
15. 75.▲
    by Jarred 3y ago

    Ship an open-source Discord alternative that more people want to use than Discord and we’ll happily switch.
16. 76.▲
    by Jarred 3y ago

    We need to do some form of this but I’m not exactly sure what yet. I suspect same process but multiple globals might work well. A lot of tests spend time sleeping or waiting for things. They might benefit from that kind of paralellism (like
17. 77.▲
    by Jarred 3y ago

    Bun transpiles Typescript to JavaScript before execution, removing types and doing some dead code elimination
18. 78.▲
    by Jarred 3y ago

    That is unrelated. This is a code signing / notarization issue because we don’t distribute Bun via the Mac App Store and likely the way it was installed was via npm or something other than .zip file we distribute. Code signing is neces
19. 79.▲
    by Jarred 3y ago

    Note that we do not currently send telemetry anywhere. The extent of what we track right now is a bitset of what builtin modules were imported and a count of how many http requests were sent with fetch(), and a few things like that. This is
20. 80.▲
    by Jarred 3y ago

    I work on Bun and happy to answer any questions. Note that Bun v1.1 is still compiling at the time of writing (probably for another 20 minutes)
21. 81.▲
    by Jarred 3y ago

    Node.js Readable and Web API's ReadableStream both implement [Symbol.asyncIterator], which means you can usually use `for await` without extra code nowadays
22. 82.▲
    The Fil-C Manifesto: Garbage In, Memory Safety Out(github.com)

    13 points by Jarred 3y ago|17 comments
23. 83.▲
    by Jarred 3y ago

    Is this for all of WebKit or the non-Cocoa/Apple builds? It reads like WebKit on Mac (Safari) will not be impacted by this change
24. 84.▲
    by Jarred 3y ago

    Bun Shell implements a cross-platform bash-like shell, using builtins for popular commands like `rm`, `cd`, `which`, `ls` etc which support the same flags on Linux, macOS, and Windows. A lot of why we made it was for `bun install` to work o
25. 85.▲
    by Jarred 3y ago

    Bun (YC S19) | https://bun.sh | San Francisco | ONSITE | Full-time Bun is an incredibly fast JavaScript runtime, package manager, test runner, and bundler. Our 2024 goal is to replace Node.js as the default server-side JavaScrip
26. 86.▲
    by Jarred 3y ago

    The -N flag tells hyperfine to not run it in a shell, which means it is not nested.
27. 87.▲
    by Jarred 3y ago

    It’s nearly all in Zig. The parser, lexer, interpreter, process execution and builtin commands are all implemented in Zig. There’s a JS wrapper that extends Promise but JS doesn’t do much else. The performance of the interpreter probably is
28. 88.▲
    by Jarred 3y ago

    We implement a handful of the most common commands like cd, rm, ls, which, pwd, mv. Instead of using the system-provided ones, it uses ours. Unlike zx/execa, we have our own shell instead of relying on a system-installed one.
29. 89.▲
    by Jarred 3y ago

    I work on Bun - happy to answer any questions/feedback
30. 90.▲
    by Jarred 3y ago

    I work on Bun (though I did not work on this feature much outside of reviewing the PR), happy to answer any questions