HNHacker News
TopNewBestAskShowJobs

smasher164

1,521 karma · joined August 13, 2015

akhil.cc
submissionscomments
smasher164··on How E Ink developed full-color e-paper
Hey, if your phone let you suit the keyboard to the context, I think physical keyboards need to catch up too :)
smasher164··on How E Ink developed full-color e-paper
Those clear plastic key-caps do not look nice to type on. Also, this seems to be using a single E-ink screen underneath.
smasher164··on How E Ink developed full-color e-paper
Yeah, I'd love a mechanical keyboard where each individual keycap was its own E-ink display. This would let you change layouts on the fly and have it reflected on the keys.
smasher164··on My self-hosting infrastructure, fully automated
This is how I currently manage my RPi NAS on NixOS: https://github.com/smasher164/nas.

Exposing Home Assistant over it allows me to do things like turn my lights off when I'm away from home, without exposing stuff to the public internet. https://www.blog.akhil.cc/shelly-dimmer

smasher164··on Rnote – A note-taking application for drawing tablets, written in Rust and GTK4
All of those either require a paid subscription for syncing/storage, don't support mobile & linux, or are electron-based and take a long time to start up.

I'm not sure why they don't go the Syncthing route of offering peer-to-peer note syncing.

smasher164··on Rnote – A note-taking application for drawing tablets, written in Rust and GTK4
I’ve been using iCloud notes by pinning a tab, but the search is pretty slow. Does Simplenote fare better here?
smasher164··on Rnote – A note-taking application for drawing tablets, written in Rust and GTK4
It's not sarcasm. I've looked pretty hard for the right app and haven't found one that meets all of those requirements. If it's that saturated, then what would you suggest?
smasher164··on Rnote – A note-taking application for drawing tablets, written in Rust and GTK4
I'm still looking for an Apple Notes-equivalent that I can comfortably use on Linux. It's been the hardest part about switching away from MacOS. A cross-platform app that launches instantly, syncs notes, has search functionality, and works on mobile is something I think we're missing.
smasher164··on Open-Sourcing our Firmware
I haven't had any hardware issues tbh. The only thing I would say is that the fans kick in pretty loud when doing anything remotely intensive. Even battery life has been fine, compared to my old Macbook Air. I've had to put in some work configuring drivers, since they're so new that they haven't landed in the distros yet. But NixOS makes that easy, so that's about it.
smasher164··on Open-Sourcing our Firmware
I've been running NixOS on my Framework for the last few months, and I've been really happy with it. I initially got it so I'd have viable hardware to do osdev on, so learning that they are going to open-source its firmware makes me even more happy.
smasher164··on WebAssembly: The New Kubernetes?
Is the "syscall layer" for this distributed runtime also designed to be distributed? I don't think WASI and POSIX-like abstractions lend themselves to be scheduled across a cluster. For instance, there's no way to mark a newly launched thread as not requiring shared memory. I see a lot of benefit in designing a syscall interface from the ground up for a distributed context.
smasher164··on JetBrains Mono – the free and open-source typeface for developers
This is up there with Inconsolata as one of the best monospace fonts, IMO.
smasher164··on Sci Hub Injector
Is Wikidata the proper way to get the currently functioning mirror? I was under the impression that you had to get it from Elbakyan's VK or the SciHub Telegram. I've been assuming that the subreddit would update with accurate links, so I've just been scraping it from there: https://github.com/smasher164/search/blob/53ae11b52f158d1986...
smasher164··on Making Open Source software safer and more secure
> can't afford to upkeep it

Address the cause, not the symptom. Make it so these individuals are more capable of upkeeping their projects. Otherwise, over the long term, you'll end up with projects disincentivized to do the maintenance, leading to a weaker open-source community.

smasher164··on Making Open Source software safer and more secure
Hopefully, "support" and "investment" are code for "contributions" and "donations".
smasher164··on What NPM should do to stop a new colors attack
I agree that Go made the right call with MVS. It's a nice compromise between pinning and fetching the latest version of everything.
smasher164··on What NPM should do to stop a new colors attack
> Essentially every open source software license points out that the code is made available with no warranty at all. Modern package managers need to be designed to expect and mitigate this risk.

It's almost like the package manager's job has become to protect users from their dependencies.

smasher164··on Some people want to run their own servers
Not sure I agree. What's another hacked-together shell script to a software engineer or system administrator? We've made servers manageable for ourselves, but rarely do we step outside of the bubble to ask how much of it is accidental complexity.

The networking layer isn't gonna change. That's given. Any change at the ISP level needs to be driven by policy decisions. But at the hardware/software-level? All of that is made up, and we could build much easier systems for network administration and app deployment.

smasher164··on How programmers make sure that their software is correct
I'm not sure why the example used for formal verification is Z3, and not proof assistants like Coq or Agda. SMT solvers have made verification a lot more accessible, but Coq is strictly more expressive than Z3.
smasher164··on The weight of the clipboard
I've overwritten my clipboard multiple times by accident, so I think that weight is the fear of losing what I copied. To be honest, the clipboard bears the weight of so much productivity, even though by default, its functionality is pretty limited. It's the poor man's IPC, after all.
smasher164··on Using HTTP Basic Auth in 2022
I found that sites (like fb messenger) which block URLs to certain sites can be easily bypassed by using HTTP Basic Auth with empty credentials. I built a small service (https://rot13.akhil.cc) that takes in a rot 13'd URL and redirects it to the original with HTTP Basic Auth. The nice part is that the credentials are cached, so visiting it again won't show the dialog.
smasher164··on Go Fuzzing
> llvm already has instrumentation

The Go toolchain actually supports emitting instrumentation for LLVM's libFuzzer with -gcflags=all=-d=libfuzzer.

> therefor the language has to add more

Okay, and so? If this ends up making fuzzing more popular and easy-to-use, I frankly don't care if it was added as a library or deeply integrated into the toolchain.

smasher164··on Go Fuzzing
The Go fuzzing tool takes advantage of compiler instrumentation. It can also work with built-in Go types, in comparison to traditional fuzzing tools that just work with bytes. Additionally, integrating it into the testing tool allows it to be as easy to write as a unit test. This can help provide a batteries-included fuzzing experience.
smasher164··on Why Not Rust? (2020)
My heuristic nowadays is if the workload is I/O bound, use Go. Otherwise, use Rust.
smasher164··on I can read C++ and Java but I can’t read Smalltalk (2000) [pdf]
Git allows you to use a custom diff tool for a specific file format. The problem is that these centralized source hosting/review tools only let you do about half of what Git can do.
smasher164··on Show HN: JWEB (a modern implementation of the CWEB Literate Programming system)
This is similar to the approach I take in my markup language: https://github.com/smasher164/mexdown. Pipe the body of a code block to the command's stdin, and replace the code block with its output.
smasher164··on Log4j: Between a rock and a hard place
It'd be interesting to see a library versioning model where every release is a breaking release, where we accept that Hyrum's law is a fact of reality (like Nix I guess?).

Then, the release process of a new version is additionally required to provide some migration path from previous releases. For example, if the language-level API is the same, but the behavior is slightly different, provide a diagnostic message that shows up in the editor when the library's updated.

On the other hand, if the language-level API has changed, additionally provide a "go fix"-like program that can migrate the user's code to use the updated library. As long as a migration path is provided/automated, updating libraries would be as easy updating to use an API-compatible release.

smasher164··on Professional maintainers: a wake-up call
I agree that appropriate compensation is necessary, but I don't think it's sufficient. There's a lack of visibility and tooling for dependency management/auditing. I can't even find a proper list of critical OSS along with their donation links.

Moreover, there needs to be a fundamental re-thinking of the security model of languages and runtimes, i.e. even if I can eval() user input or load a plugin from the network, it should not be game over. There should be finer-grained access control in programs, both at the type-level and with how they interact with the OS. The global view of "your program can do anything unless said otherwise" needs to change.

smasher164··on GhOSt: Fast and Flexible User-Space Delegation of Linux Scheduling
This is pretty cool! If I'm understanding this correctly, this would make it possible for green thread implementations to call FFI code with low-overhead? What are the plans to upstream this?
smasher164··on Using Flutter to build a native-looking desktop app for macOS and Windows
And this is why I think the goal of a cross-platform toolkit is misleading. If your language/library/compiler make it really ergonomic to conditionally target code for a platform, then you get the benefit of keeping your business logic in one place, and the pain only with testing the application.

Usually this is not the case, since interfacing with Cocoa is so different from Win32, for example. However, one shouldn't conflate that difficulty with the difficulty of testing an app across platforms.

← PreviousPage 6 of 9Next →