javierhonduco

6 ms·

1.
by javierhonduco 1mo ago
I agree it sounds inclusive but I find it to be in tension with some of his previous writings: - https://world.hey.com/dhh/as-i-remember-london-e7d38e64 - https://world.hey.com/dhh/wolves-sheep-and
2.
by javierhonduco 1mo ago
I am all in seeing more people run Linux and I think this might help the whole ecosystem and other distros long term. That being said I’m a bit concerned about videos like this https://xcancel.com/thestanduppod/status&#
3.
by javierhonduco 2mo ago
I really love Zed and I want them to really succeed. Unfortunately it seems that they are swamped with various things and the issue tracker is not a priority for the team, which fair enough. OSS is a gift and I take it as such. Wild proposa
4.
by javierhonduco 3mo ago
This is very sad. I bought a PS5 with disc precisely to “own” the games. End of an era, I guess.
5.
by javierhonduco 6mo ago
Great write-up. As a side note (not a Googler myself and this is 100% my opinion) Lalit’s team was hiring in London, UK. If you are interested in working in low level performance tools, this might be a very cool opportunity!
6.
Debunking Zswap and Zram Myths(chrisdown.name)
215 points by javierhonduco 6mo ago|61 comments
7.
by javierhonduco 7mo ago
Super cool project! Curious on how this compares to Meticulous in terms of functionality and approach. Thanks!
8.
by javierhonduco 10mo ago
Wondering to what degree this was done to support Anthropic’s web crawler. Would assume that having a whole JS runtime rather than just a HTTP client could be rather useful. Just hypothesising here, no clue what they use for their crawler.
9.
by javierhonduco 11mo ago
I am incredibly happy that Apple has added MTE support to the latest iPhones and perhaps the M5 chips as well (?). If that’s the case I don’t think any other personal computers have anything close to Apple machines in terms of memory safety
10.
At Google, the future is multiarch; AI and automation are helping us get there(cloud.google.com)
2 points by javierhonduco 1y ago|1 comments
11.
Making the Clang AST Leaner and Faster(cppalliance.org)
2 points by javierhonduco 1y ago|0 comments
12.
by javierhonduco 1y ago
Really enjoyed reading this. Thanks for writing it!
13.
by javierhonduco 2y ago
These metrics can be used in performance reviews at Facebook.
14.
by javierhonduco 2y ago
Zig 0.13 is required according to https://ghostty.org/docs/install/build
15.
by javierhonduco 2y ago
This is pretty cool work. Something that’s been on my mind recently is that there’s a need of a high-performance flame graph library for the web. Unfortunately the most popular flame graph as a library / component, basically the react
16.
by javierhonduco 2y ago
Axum + minijinja is quite close to this I would say. Been using it for a little while and I am very happy so far.
17.
by javierhonduco 2y ago
Haven’t had the chance to play with WezTerm just yet but wanted to share that the author is an incredibly smart, friendly, and humble. Had the opportunity to work on a project together at work some years back and I can only aspire to be 1&#
18.
Low Impact Website(jasonheppler.org)
1 points by javierhonduco 2y ago|0 comments
19.
by javierhonduco 2y ago
Or in other parts of the kernel. It's been the case in multiple occasions that buggy locking (or more generalised, missing 'resource' release) has caused problems for perfectly safe BPF programs. For example, see https:&#x2F
20.
by javierhonduco 2y ago
It is not, programs that are accepted are proved to terminate. Large and more complex programs are accepted by BPF as of now, which might give the impression that it's now Turing complete, when it is definitely not the case.
21.
by javierhonduco 2y ago
It’s easy to miss this in large codebases. Having to check every single struct initalisation whenever a field is added is not practical. Some folks have mentioned that linters exist to catch implicit initialisation but I would argue this sh
22.
by javierhonduco 2y ago
Personally I’m not a fan of Go’s default zero-initialisation. I’ve seen many bugs caused by adding a new field, forgetting to update constructors to intialise these fields to “non-zero” values which caused bugs. I prefer Rust’s approach whe
23.
Unexpected Profiling Use Cases Beyond Performance Optimization(blog.felixge.de)
2 points by javierhonduco 2y ago|0 comments
24.
by javierhonduco 3y ago
This looks incredibly comprehensive, thanks for sharing! Should have added that I read this book in 2016, and the first edition is even older, so there’s naturally been lots of new (and exciting) developments in this area!
25.
by javierhonduco 3y ago
For anybody interested in this topic, “Release it!” is a pretty good read. (Not affiliated in any way, just enjoyed reading it) https://www.oreilly.com/library/view/release-it/978168050026...
26.
by javierhonduco 3y ago
Overall, I am for frame pointers, but after some years working in this space, I thought I would share some thoughts: * Many frame pointer unwinders don't account for a problem they have that DWARF unwind info doesn't have: the fac
27.
by javierhonduco 3y ago
There's always room for improvement, for example, Samply [0] is a wonderful profiler that uses the same APIs that `perf` uses, but unwinds the stacks as they come rather than dumping them all to disk and then having to process them in
28.
by javierhonduco 3y ago
Inlined functions can be symbolized using DWARF line information[0] while unwinding requires DWARF unwind information (CFI), which the x86_64 ABI mandates in every single ELF in the `.eh_frame` section - [0] This line information might or m
29.
by javierhonduco 3y ago
Curious to hear more about this. Full disclosure: I designed and implemented .eh_frame unwinding when I worked at Polar Signals.
30.
by javierhonduco 3y ago
Had completely missed that line — great point!

More ›