ajeetdsouza

10 ms·

1.
Parallel agents in Zed(zed.dev)
279 points by ajeetdsouza 5mo ago|164 comments
2.
by ajeetdsouza 2y ago
This is really well-written! Shameless plug: you may want to check out Loxcraft: https://github.com/ajeetdsouza/loxcraft I too followed the path of "ignore safe Rust for maximum performance". It got pretty cl
3.
Dgraph: New Funding Announcement(discuss.dgraph.io)
1 points by ajeetdsouza 4y ago|0 comments
4.
Regex Licensing(regexlicensing.org)
3 points by ajeetdsouza 4y ago|0 comments
5.
Show HN: Play Wordle over SSH(github.com)
6 points by ajeetdsouza 5y ago|1 comments
6.
Wordle-over-SSH(github.com)
3 points by ajeetdsouza 5y ago|0 comments
7.
Web Browser Engineering: How Web Browsers Work(browser.engineering)
1 points by ajeetdsouza 5y ago|0 comments
8.
by ajeetdsouza 5y ago
Shameless plug: zoxide recently added support for Nushell. It's a smarter cd command for your shell (similar to z or autojump). https://github.com/ajeetdsouza/zoxide
9.
What happens when you enter google.com into a browser?(github.com)
2 points by ajeetdsouza 6y ago|0 comments
10.
MuditaOS: An open-source, e-ink mobile OS(mudita.com)
211 points by ajeetdsouza 6y ago|94 comments
11.
A study of std::io::Error(matklad.github.io)
1 points by ajeetdsouza 6y ago|0 comments
12.
Playwright for Python: Reliable end-to-end testing for the web(devblogs.microsoft.com)
1 points by ajeetdsouza 6y ago|0 comments
13.
Ent by Facebook: Entity Framework for Go Now Supports GraphQL(entgo.io)
2 points by ajeetdsouza 6y ago|0 comments
14.
Optimization: Making Rust Code Go Brrrr(aspenuwu.me)
3 points by ajeetdsouza 6y ago|0 comments
15.
GNU Humor(gnu.org)
5 points by ajeetdsouza 6y ago|0 comments
16.
Rust: The Secret Life of Cows(deterministic.space)
9 points by ajeetdsouza 6y ago|0 comments
17.
Show HN: Zoxide, a new CD command written in Rust that learns your habits(github.com)
2 points by ajeetdsouza 7y ago|0 comments
18.
Type-Safe Raytracing in Modern C++(ajeetdsouza.github.io)
3 points by ajeetdsouza 7y ago|0 comments
19.
by ajeetdsouza 7y ago
Fixed, thank you!
20.
by ajeetdsouza 7y ago
The size of a compiled Hello World program is 2 MB on my machine, so you're probably right!
21.
by ajeetdsouza 7y ago
The tests were run 10 times, and I used the median value. There wasn't much variance between runs, so I don't think disk caching played much of a role here. Being a garbage collected language with a runtime, Go certainly cannot ma
22.
by ajeetdsouza 7y ago
Author here. I think you should go through the article again. I think it's quite readable, and there are no "hand-optimizations" as you say. Also, the single-core implementation was already faster than the C version - the mul
23.
by ajeetdsouza 7y ago
I tested this on a fresh install of Fedora 31, so I didn’t really see any benefit of running it on a LiveUSB. As I mentioned in the article, the wc implementation I used for comparison has been compiled locally with gcc 9.2.1 and -O3 optimi
24.
by ajeetdsouza 7y ago
Argument parsing is hardly the bottleneck when you're scanning 1 GB of data. The reason I didn't implement the rest of the features was to keep the implementation light and readable, and I don't think a fully compliant wc imp
25.
by ajeetdsouza 7y ago
Author here. I have addressed this in the article. The bufio-based implementation was the first one, and it was actually slower. In the second section, I was able to surpass the performance of the C implementation - by using a read call wit
26.
by ajeetdsouza 7y ago
This is not true, see my comment here: https://news.ycombinator.com/edit?id=21587907
27.
by ajeetdsouza 7y ago
Author here. This is not true - I included a link to the manpage ( https://ss64.com/osx/wc.html ) in the article to avoid this confusion. I did not use GNU wc; I used the OS X one, which, by default, counts single byte c
28.
by ajeetdsouza 7y ago
Author here. Why do you feel it is code golf? My primary focus when writing it was readability - I'm sure I could do it in much less than 70 lines if I had to. If you have any suggestions for improving the readability of my implementat
29.
by ajeetdsouza 7y ago
Author here. If you read the article carefully, you'll see that the 70 lines I used to outperform wc was a single-threaded implementation. I multi-threaded it later for overkill.
30.
by ajeetdsouza 7y ago
Hey, author here. You are absolutely right - Go would have a hard time outperforming finely tuned C. Rather, the article was more focused on exploring concurrency mechanisms in Go. The (admittedly clickbait) title was more of a reference to

More ›