davidatbu

10 ms·

61.
by davidatbu 2y ago
¯\_(ツ)_/¯
62.
by davidatbu 2y ago
I don't know if it's due to my familiarity with Rust, but I find none of the examples cursed or surprising, except the "&* is useful" one. Even for that one, I think the use case of "turning a raw pointer to a r
63.
by davidatbu 2y ago
Than you so so much!
64.
by davidatbu 2y ago
How bad are the compile times? My understanding is that the compile times are currently bad, and they can't be improved without fundamental changes to the lang/type system.
65.
by davidatbu 2y ago
I'm working on an "offline first" Github client. The things I want to achieve are: 1. Background sync of repo state/PRs/issues/etc. 2. Ability to do "optimistically updates" when creating/editing
66.
by davidatbu 3y ago
That ranking of type systems matches my experience a 100% too.
67.
by davidatbu 3y ago
In my experience, in an RoR codebase, the dynamic-ness of rails severely reduces its utility to only enabling better auto-complete (as opposed to also helping out with writing logically correct code). In typescript, when I do a refactor, or
68.
by davidatbu 3y ago
> The plan is not to support macros. Gotcha. In every lang I've used a lot, I've found meta-programming (compile-time or dynamic) to be valuable (and often indespensible). I can imagine that a lang like Elm that is domain-speci
69.
by davidatbu 3y ago
We have a very similar taste in PLs :)
70.
by davidatbu 3y ago
I'm super keen to see how Roc pans out, because it sits at an (IMO) riveting spot in the space of PL design tradeoffs: 1. The typesystem will be sound, ML-like, and so simple that any code that doesn't interact with external data
71.
by davidatbu 3y ago
Like I said somewhere else "sledge-hammer" is _just as fast_ as Vanilla JS in those benchmarks (it's one of the "Vanilla Rust"/bare-bones entries to the benchmark).
72.
by davidatbu 3y ago
Thanks for providing your data point! If you're having another go, I'd recommend checking out sledge-hammer[0], a wasm-bindgen alternative that the folks behind Dioxus have been working on. It's a faster, but more limited ver
73.
by davidatbu 3y ago
Dioxus is also a vDOM based framework (like React). Leptos is a fine-grained-reactivity framework (like SolidJS/Svelte). They are both _way_ faster than React, and they are both faster than Vue and Svelte by a larger magnitude than Sol
74.
by davidatbu 3y ago
To me, the benchmarks you linked show that the fastest WASM web frameworks I know (leptos, dioxus, sycamore) are competitive with, or faster than, the JS frameworks most famously associated with speed, like SolidJS and Svelte; and that they
75.
by davidatbu 3y ago
I'd love to hear more about your experience, because it contradicts what the JS Framework Benchmarks[0] suggests. Leptos and Dioxus, Rust/WASM frameworks, are competitive with SolidJS, and right out destroy React, when it comes
76.
by davidatbu 3y ago
I def wanna try that out sometime! It does sound to me like that is not a consequence of the GUI-ness of VSCode, but just the man-hours that go into making it. In other words, it doesn't sound like that experience can't be replica
77.
by davidatbu 3y ago
A data point: I'm a plugin-heavy neovim user, and I wholeheartedly testify that familiarity with vi modal editing is incredibly useful when ssh-ing into remote systems, and I don't have my plugins.
78.
by davidatbu 3y ago
As a heavy user of neovim who's been curious about the "noun-verb" approach to modal editing, this link was an excellent read!
79.
by davidatbu 3y ago
I just skimmed the release blog post for Copilot Chat, and I don't see why it can't be implemented in a terminal based editor. Copilot itself was.
80.
by davidatbu 3y ago
No one has claimed that “most library libs are migrating to index based memory management”. I mentioned two crates that are DOM frontend frameworks, that also are based on fine grained reactivity (and not a virtual DOM). That’s an incredibl
81.
by davidatbu 3y ago
Because it's still HTML/CSS, just using Rust compiled to WASM instead of JS.
82.
by davidatbu 3y ago
I would say that it's a way to trade compile-time checks of reference validity for runtime-checks of reference validity.
83.
by davidatbu 3y ago
Here's the implementation of "remove a value" [1] from the popular Rust crate that implements this pattern. It completely sidesteps the issue you are describing because "deleting from array" does not mean "adju
84.
by davidatbu 3y ago
> array-bounds-checking bugs. Rust tries very very hard to avoid bounds-checking bugs, because it's central to the safety promise, maybe I'm misunderstanding you? > either "list was re-ordered, you now have the wrong it
85.
by davidatbu 3y ago
A great read! Might be worth pointing out: leptos, a Rust WASM UI library, uses the "store an index (or ID) into some central data structure" idea extensively. Sycamore, another Rust WASM UI library, has been using arena allocatio
86.
by davidatbu 3y ago
I haven't read your blog yet, but I'd be lying if the same thought hasn't crossed my mind :)
87.
by davidatbu 3y ago
As a regular consumer of pg docs, I vehemently agree that they are incredibly detailed, and at the same time, daunting to navigate.
88.
by davidatbu 3y ago
I THINK SO TOO! I'm 97% sure that just using static analysis to provide all the relevant type definitions and function signatures as context for code completion in LLMs alone will be a massive value-add. I'm literally doing that b
89.
by davidatbu 3y ago
Can you expound upon why Rust is having an identity crisis? Rust's current mission is: "empowering everyone to build reliable and efficient software." It seems like it's hitting that goal to me (for .e.g., it empowered m
90.
by davidatbu 3y ago
Did you actually shift careers those two times in the past (Ie, change companies/jobs/job focus)? And will you be doing the same when "calling a third" now?

More ›