HNHacker News
TopNewBestAskShowJobs

smasher164

1,521 karma · joined August 13, 2015

akhil.cc
submissionscomments
smasher164··on macOS Monterey
Okay macOS, if you’re gonna deprecate kexts, please give us a VFS API that fulfills the role of macFUSE, not the syncthing-esque API of FileProvider.
smasher164··on Hrmpf rescue system, built on Void Linux
Currently dealing with a zfs cachefile issue on my nas, where hrmpf has been instrumental in letting me backup data and regenerate a cachefile from my macbook.
smasher164··on Mēris botnet, climbing to the record
An attack-resistant trust metric? Although I haven’t seen them used against denial of service attacks.
smasher164··on Maintain It with Zig
What I don’t understand is why Clang doesn’t do this? What’s stopping them from shipping libc’s for cross compilation? Given that they are a C and C++ compiler, surely this is in their domain.
smasher164··on What if JavaScript had a synchronous async flavor?
If you're interested by this, take a look at Stopify[1], which further adds first-class continuations to javascript.

[1] https://www.stopify.org/

smasher164··on Low level is easy (2008)
Anyone who becomes sufficiently experienced in a domain will inevitably learn and take advantage of their underlying platform's characteristics.

A web developer who wants an app to load and render quickly will take advantage of the browser's characteristics. For example, loading compressed assets in the right order to get a short time-to-first-paint, updating styles without reflowing the page, using requestAnimationFrame to render animations at a consistent frame rate and play nicely with the event loop, etc.

Likewise, a systems programmer ends up learning the quirks of their OS and hardware. For example, loop tiling to take advantage of cache locality, reducing data dependencies to reduce pipeline hazards, using splice() to copy data on Linux to avoid context switching, etc.

It's all just programming. Even if the distance from hardware is different, the concepts are consistent. Historically, hardware has been under-documented, which I think led to the community glorifying low-level programming. But under-documented and buggy platforms are essentially universal nowadays, so I think the low-level vs high-level distinction is not very useful.

smasher164··on macOS extensions are moving away from the kernel
There's the File Provider API [1], but I don't think it's a proper replacement for osxfuse yet.

[1]: https://developer.apple.com/documentation/fileprovider

smasher164··on Programming Language Memory Models
Even with that expressivity, someone who incorrectly relates or forgets to relate two variables could experience the same issues. It's still important to address what happens when the program has data races or when it is data-race-free but the memory model permits overreaching optimizations. The language and implementation should strive to make a program approximately correct.
smasher164··on GitHub Copilot
I wonder how much of this is OpenAI-based vs program synthesis techniques.
smasher164··on Unicode sorting is hard and why browsers added special emoji matching to regexp
> While WASM languages could shell out to JavaScript browser APIs for collation, I suspect they won’t due to the lack of guarantees around those APIs.

That's just it, right? Unicode support has always been a tradeoff between precise coverage/larger binaries and loose coverage/smaller binaries. I'd be excited to see the data size for collation+normalization get under 1MB.

smasher164··on Surreal numbers (2014)
I remember checking out a copy of “Surreal Numbers” in college, and being absolutely blown away by both the constructs and the storytelling.
smasher164··on Sir, Please Step Away from the ASR-33 (2010)
Supporting unicode doesn't mean you can't defend against homograph attacks. See http://www.unicode.org/reports/tr39/.
smasher164··on Why did we ever think a student's first programming language didn't matter?
This applies beyond introductory programming. We faced this in our university's Machine Learning course. The same course was taught both to students from the engineering school, which requires a certain number of math courses (Linear Algebra, Calculus, etc.), and in the general college, which had much fewer requirements.

The professor was forced to stay surface-level on the math, so the coursework was a task of glueing together code from scikit-learn. Unfortunately, the exams were much easier if you had the mathematical intuition.

smasher164··on Why did we ever think a student's first programming language didn't matter?
From the PL theory front, when confronted with the idea that languages shouldn't necessarily assume prior mathematical knowledge, even some well-known researchers simply shrug and say "I can't do anything about that." And those same people will also criticize more popular/accessible languages on the grounds that they lack features from their favorite pet language based in some mathematical footing.

The hypocrisy is real. It is definitely a real problem. If your field has confined itself in formalism without a consideration for HCI, you are doing yourself harm. Not only is the transfer of knowledge to industry and other domains harder, you miss out on equivalent but more accessible ways of expressing the same ideas.

smasher164··on Go 1.17 is deprecating the traditional use of 'go get'
If the author or anyone feels really strongly about `go get`'s deprecation, the issue for it is http://golang.org/issue/43684.
smasher164··on A quest for safe text formatting API
Should mention type-safe printf in dependently-typed languages like Idris[0] or F*[1]:

[0]: https://zgcoder.net/ramblings/typesafe-printf/ [1]: https://fstarlang.github.io/general/2017/11/23/sprintfstar.h...

smasher164··on Multicore OCaml: May 2021
I think this might be for social reasons instead of technical.

You'd need an overlap of

1. An appreciation of ML and its extensions.

2. A relatively deep understanding of Go's semantics, performance hacks w/ GC, type system quirks, etc.

3. Belief that this would be useful.

4. Knowledge of compilers.

5. Time on your hands. This is a blocker for me :(

smasher164··on Multicore OCaml: May 2021
I would love to see a Concurrent ML variant that compiles down to Go as the target language. Get the advantages of a great type system, while standing on the shoulders of Go's compiler and runtime.
smasher164··on iPadOS 15
Why was my comment downvoted? I said that I'm looking forward to trying a feature. It seems that if a comment doesn't fit under someone's narrative of "iPad is useless," it'll get egregiously downvoted nowadays. Goodness gracious people, please be more mindful.
smasher164··on iPadOS 15
Looking forward to trying out the new multitasking features. They seem to be an improvement of iPadOS 14, and require fewer gestures. The window management looks a little confusing, so I’ll have to give it a shot to see if it was just the presentation that made it seem that way.
smasher164··on If someone’s having to read your docs, it’s not “simple”
Same. I'm often surprised as to how far programmers will go to disparage the quality of docs, as opposed to just reading them. Like I get that there are factors affecting their accessibility, e.g. internationalization, but it is your literal job to read this information.

Meanwhile, for reverse engineers, it's a dream come true to be granted any information whatsoever on the product they're reverse engineering. For some reason, programmers want to operate in the context?

smasher164··on Counterexamples in Type Systems
The notation really isn't as bad as it originally looks, trust me. I was in the same boat recently, but after cracking open TAPL, on page 26 you basically get all the notation you need for the rest of the book.

Inference rules just transform the traditional format of

    (A && B) -> C
into

    A B
    ---
     C
This format allows you to stack rules on top of each other when writing out the derivation of some term, without running out of page space.
smasher164··on Why Decentralised Applications Don’t Work
To centralize is to share rules and information. Without shared information, humans cannot work with and communicate with one other. The goal of decentralization should be to fix the power imbalance embedded in our current central structures, whether it's Google with email or Github with git.

People should instead be incentivized to centralize in their own local communities, i.e. their family, friends, coworkers, local businesses, community centers, etc... Accomplishing this will likely require effort on multiple fronts, from increased regulation over the tech sector, to creating products that empower communities to run these services themselves.

smasher164··on Cosmopolitan Libc 1.0
Would you not get the same effect by statically linking to MUSL? I could see some problems with NSS, but there are workarounds there as well with nsss.
smasher164··on Cosmopolitan Libc 1.0
Gotcha. That still runs counter to the comment:

> I do not wish to install Python or Java on every computer. I have small form factor computers where I need to conserve space.

Now you have to install QEMU on every computer, in which case your options for portability dramatically increase.

smasher164··on Cosmopolitan Libc 1.0
> One use case is where the source and target are different architectures, and either the target does not have a compiler installed or the source does not have a cross-compiler installed.

Do you mean different OSes? AFAIK, Cosmopolitan isn't cross-architecture.

smasher164··on Building an efficient and portable programming language with Zig
Yeah, I'm unaware of any push to bring flow-sensitive typing, or a mechanism that affords flow-sensitive analysis, to Zig.
smasher164··on Building an efficient and portable programming language with Zig
Not sure, but I became optimistic of there being some solution after I saw someone implement affine typing using stateful template metaprogramming: https://godbolt.org/z/PnPPrnPjY.
smasher164··on Building an efficient and portable programming language with Zig
The question is if this should be done at the language-level or library-level. With sufficient metaprogramming capabilities, an enterprising programmer could write safe resource management abstractions for Zig. However, this wouldn't make the language "safe by default," which seems to be what Rust programmers are bringing with this criticism.

Even if Zig doesn't bring safety by default to the language, however, I think you could get it in practice by making the standard library enforce safety. Then, unless someone goes out of their way to write their own libraries from scratch and eschew all of the safety mechanisms, they would likely live in this safety bubble.

smasher164··on The compiler will optimize that away
Impedance mismatch. Languages don't give the compiler enough semantic information to work with, and some require heavy runtimes. Compilers, on top of having to infer semantic information about the above, aren't able to sufficiently utilize the hardware, either due to constraints on the types of analyses done, or lack of control. The hardware exposes an API too high-level or too unfamiliar to existing compilers.

IMO, the future is bright, because all these layers are being re-thought. However, phrasing this as a debate over programming paradigms is a red herring. If coupling data and behavior is a useful mental model, we ought to accommodate that while giving the compiler more to work with.

← PreviousPage 7 of 9Next →