Mind boggling to me that I can make a thing faster and there's always people that ask "but why?" What kind of mentality is that? The pursuit of excellence does not need justification. Also, I find in so many cases, we can't know the impact of an improvement until we do it.
For example, one I've talked about before: Ghostty's high IO throughput has enabled terminal program (emulator and TUI) fuzzing at a speed thats incomparably fast to prior solutions. This has resulted in upstream patches to resolve issues in popular projects like btop, tmux, and more.
Speed enabled that anecdotally example that lifted the tides of adjacent communities that don't rely on Ghostty technology at all. I didn't predict this.
Make things better because they can be better and let the results naturally play out.
Episode 107: Language Design Deep Dive with @josevalim! 🎉
I tried something different in this episode: we were both using @zeddotdev to write example code in realtime in shared buffers, Google Docs-style, as we talked about language design. It was really fun!
Just finished the day 1 of Advent of Code 2024. And, for the first time ever, I wrote it in ReasonML & OCaml. For the frustration of immediately coming up with a solution, but then painfully coding it in 5-6 hours I thank @teej_dv and @dillon_mulroy.
O Caml, my Caml #aoc2024
This speaks to me: it’s the essence of building hard things that take time to have impact, but then matter in a big way - you have to love the process, not just the outcome!
It was super fun talking with @ThePrimeagen and @teej_dv last week: relived the social side of launching Swift at Apple, lessons learned building scale projects, what Mojo🔥 is and how (yes) progress is still being made in systems, and more.
Thanks both!
https://t.co/6GS0G0O9Hs
No hate though, I'm occasionally using both. And sometimes IntelliJ. But, for the most part, it's Helix as I find it's editing model the most appealing to me. Clever combo of modal editing and multiple cursors/visual editing, as well as structured editing via Tree-sitter
I'm very pro using GDScript in Godot over anything else, and I feel the same for Vim (VimScript) or Neovim (Lua). DSLs like these are very close to the underlying system, and in the end one needs to learn the system, which takes much more time than learning language syntax itself
With DSL you're not only learning the system, but the concepts of the domain you're applying it too, thereby removing major points of friction and accelerating your learning process like crazy. It's very worth to learn those than to try to apply your favorite language everywhere.
I'd just like to interject for a moment. What you're referring to as Flutter, is in fact, Dart/Flutter, or as I've recently taken to calling it, Dart+Flutter. Flutter is not a complete system unto itself, but rather another free component of a fully functioning Dart language.