mwsherman

9 ms·

1.
by mwsherman 2mo ago
I recommend starting with SWAR [1] before SIMD. Our registers are typically 64 bits, and one can try out SIMD patterns without taking a dependency on particular hardware. This will only be effective if the data you’re working on is smaller
2.
by mwsherman 8mo ago
While this article is about perf — and trading off semantic precision by design — there is a Unicode standard for sentence boundaries, may be interesting: https://www.unicode.org/reports/tr29/#Sentence_Boundaries
3.
by mwsherman 9mo ago
Shameless plug, if one wishes to track down allocations in Go, an allocations explorer for VS Code: https://marketplace.visualstudio.com/items?itemName=Clipperh...
4.
by mwsherman 9mo ago
I’ve found C#’s frozen dictionary to be useful: https://learn.microsoft.com/en-us/dotnet/api/system.collecti... It’s optimized for fast reads in exchange for expensive creation.
5.
by mwsherman 11mo ago
That’s true, converting in either direction will typically allocate. Which it must, semantically. One can use unsafe for a zero-copy conversion, but now you are breaking the semantics: a string becomes mutable, because its underlying bytes
6.
by mwsherman 11mo ago
There is mention of how len() is bytes, not “characters”. A further subtlety: a rune (codepoint) is still not necessarily a “character” in terms of what is displayed for users — that would be a “grapheme”. A grapheme can be multiple codepoi
7.
by mwsherman 11mo ago
In Go, string effectively serves as a read-only slice, if we are talking about bytes. ReadOnlySpan<T> in C# is great! In my opinion, Go essentially designed in “span” from the start.
8.
Making Unicode things fast in Go(clipperhouse.com)
2 points by mwsherman 11mo ago|0 comments
9.
by mwsherman 11mo ago
A Go allocations explorer for VS Code. Extension: https://marketplace.visualstudio.com/items?itemName=Clipperh... Source: https://github.com/clipperhouse/go-allocations-vsix
10.
by mwsherman 11mo ago
Shameless plug, you may wish to do Lucene-style tokenizing using the Unicode standard: https://github.com/clipperhouse/uax29/tree/master/words
11.
by mwsherman 1y ago
I move between Go and C#. I wrote a zero-allocation package in Go [1] and then ported to C# — and the allocations exploded! I had forgotten, or perhaps never realized, that substrings in C# allocate. The solution was Spans. Notably, it caus
12.
Show HN: Go Allocations Explorer for VS Code(marketplace.visualstudio.com)
4 points by mwsherman 1y ago|0 comments
13.
Allocations Are a Dependency(clipperhouse.com)
1 points by mwsherman 1y ago|0 comments
14.
I deal with copyright claims [video](youtube.com)
2 points by mwsherman 1y ago|0 comments
15.
Yagni for Distributed Rate Limiting(clipperhouse.com)
1 points by mwsherman 1y ago|0 comments
16.
by mwsherman 1y ago
Putting on eng manager hat, the problem to solve is that this regression went undetected, not that Safari is slow. The solution is a test that fails when Chrome and Safari have substantially different render times.
17.
Show HN: A more composable rate limiter for Go(github.com)
1 points by mwsherman 1y ago|0 comments
18.
Casey Handmer on powering data centers [video](youtube.com)
4 points by mwsherman 1y ago|0 comments
19.
Is a "routing" LLM isomorphic with a single large model?(twitter.com)
2 points by mwsherman 1y ago|1 comments
20.
Designing a Composable Rate Limiter(clipperhouse.com)
4 points by mwsherman 1y ago|0 comments
21.
by mwsherman 1y ago
C# has implemented some SIMD for IndexOf: https://github.com/dotnet/runtime/pull/63285
22.
Self-Hosted x86 Back End Is Now Default in Debug Mode(ziglang.org)
1 points by mwsherman 1y ago|0 comments
23.
Poor spill decisions making code 14% slower(github.com)
8 points by mwsherman 2y ago|0 comments
24.
by mwsherman 2y ago
Here’s a way to write tests next to the code: https://clipperhouse.com/go-test-csharp/ (Whether I recommend it, not sure! I did it and then undid it, with suspicion that tests were taking longer due to, perhaps, worse
25.
The River, the Village, and the Fort: Nate Silver's New Book, "On the Edge"(statmodeling.stat.columbia.edu)
2 points by mwsherman 2y ago|0 comments
26.
C# almost has implicit interfaces(clipperhouse.com)
53 points by mwsherman 2y ago|71 comments
27.
Splitting Words Correctly in C#(github.com)
2 points by mwsherman 2y ago|0 comments
28.
Tips for moving between Go and C#(clipperhouse.com)
2 points by mwsherman 2y ago|1 comments
29.
Tips for moving between Go and C#(clipperhouse.com)
3 points by mwsherman 2y ago|0 comments
30.
A fast Unicode tokenizer for C#(github.com)
3 points by mwsherman 2y ago|0 comments

More ›