HNHacker News
TopNewBestAskShowJobs

ben0x539

4,454 karma · joined September 23, 2010

submissionscomments
ben0x539··on Response to “Developers are lazy, thus Flatpak”
I generally trust the applications that I run natively to not be malicious, but I don't always trust them to not step on each other's toes, or make a well-intentioned mess of things.
ben0x539··on Response to “Developers are lazy, thus Flatpak”
> The traditional approach forces all packages to make do with one version of a library,

Yeah, and that means a bunch of them don't work properly. It's unrealistic to expect app developers to support that one version that each particular distro ships.

ben0x539··on Response to “Developers are lazy, thus Flatpak”
There's still some reuse between flatpak apps, and not everything one might depend on necessarily is of the shape of a statically linkable library.
ben0x539··on Response to “Developers are lazy, thus Flatpak”
As ever, I wish I lived in the world the distro packagers are packaging software for, but in practice, I frequently do want to use the apps that make the distro packagers throw up their hands and go "we can't ship it like that".
ben0x539··on Rising number of lithium battery incidents on airplanes worry crew
Maybe you have the causation the wrong way around--about every time there is a lithium battery fire on a plane, someone has to buy a new phone, after all.
ben0x539··on Get a Tesla if you want to learn about AI trying to kill you, says Steve Wozniak
Surely nuance doesn't always make for a better argument!
ben0x539··on Millions snap up new Germany-wide public transit ticket
> there is (was?) a huge lag between adding value and posting the value depending on how you added value.

There is months worth of "pending" passes on my clipper card and neither some Clipper support number I called nor the poor guy in the booth at the local BART station could tell me how to activate them (and also not some people on Reddit and my public transit using friends, of course). It's obviously not done by using either BART or buses or SF Muni, or tagging the card against the insert-coin machines at the station, because, you know, I've done all of that a bunch of times since this started being an issue. Most of the pending passes expired by now. I'd be more upset about this if I had paid for them with actual money and not some employer based commute benefit since I haven't exactly commuted regularly since the pandemic started.

ben0x539··on A 1.5GB string
Wonder if it's worth putting special logic into json serialization libraries that politely raises some alarms when writing like a few hundred \ in a row.
ben0x539··on Microsoft's Software Is Malware
While it'd take many hours to figure out how to make some random FOSS code to do what I want if what I want is anything particularly interesting, finding out where to comment out the code that eg phones home, or makes annoying noises, and then sharing that patch with everybody else is much easier and more realistic. Sure, it doesn't entirely remove the power of the developers and particularly the people who control the official releases page, but it feels like a real, meaningful check on their power. It becomes even more meaningful if you're not just some rando but maybe the "user" in question is an org who can actually devote resources to maintain changes to some FOSS code, saving you from having to enter into some sort of partnership with the developer.
ben0x539··on Zig and Rust
Yeah, that's what my second gripe was meant to complain about. Really,

    withFile :: FilePath -> IOMode -> (Handle -> IO r) -> IO r 
is just a more general way of writing

    withFile :: FilePath -> IOMode -> (Handle -> IO Handle) -> IO Handle
;)

I've also heard about the ResourceT monad transformer but as of right now I don't think I could explain what it does or judge how well it does it, maybe that's also a sufficient solution.

ben0x539··on Apple introduces Apple Pay Later
> At what point is a situation so convoluted that it can be considered an edge case?

People have edge cases all the time! Failing gracefully in edge cases is a critical feature for anything that's so deeply wired into your life like a payment processor or a cloud account!

ben0x539··on Zig and Rust
I know this is facile, and it's speaking as someone with a lot more enthusiasm about than expertise with Haskell, but whenever I write some toy Haskell code and have to think about "remember to close this file handle before the end of this block" or "make sure not to use this file handle outside this block (because we just used a combinator to close it)", I'm baffled that Rust has mostly figured out that whole class of problem before Haskell
ben0x539··on Disney begins laying off 7k employees
It's, like, using active voice. Like it's a thing the employees are actively, purposefully, doing or perpetrating. Of course it doesn't actually unambiguously say "and they've fully consciously decided they would like to no longer work to", but it's definitely language that's designed to, however ineffectively, not draw attention to the blatant fact that the company has chosen to fire people.
ben0x539··on The Unix process API is unreliable and unsafe (2021)
Oh, good question, I have been running some stuff as systemd user services but I don't actually know if they get real cgroups.
ben0x539··on Practical Libc-free threading on Linux
Yeah, and the particular old-school UNIX I had in mind was Win32. :)
ben0x539··on Practical Libc-free threading on Linux
I think competing products define their interface in terms of calling a provided C library, and leave the entirely of the system call mechanics as an implementation detail.
ben0x539··on The Unix process API is unreliable and unsafe (2021)
Simply use systemd/cgroups they tell me and now I'm trying to figure out how my systemd service somehow ended up controlling processes for another service.
ben0x539··on Bard is much worse at puzzle solving than ChatGPT
I mean, English spelling certainly doesn't free you from the need to figure rhyming out from context.
ben0x539··on Windows Snipping Tool is vulnerable to Acropalypse too
(As a non web-dev, maybe, )I don't think I've cared about the file size of cropped images in the past couple years. When I crop stuff it's because I want to send it to someone, not because I'm gonna archive it or anything.
ben0x539··on Sci-fi becomes real as renowned magazine closes submissions due to AI writers
Librarians might give you a funny look if you show up at a library and start printing out books?
ben0x539··on Is it time to replace TCP in data centers?
We've all heard of the law. It's a cute observation but everybody is capable of making it independently and commenting with a reminder on every article with a yes/no question as the title is just noise.
ben0x539··on Amazon employees push CEO Andy Jassy to drop return-to-office mandate
Why would you assume the remainder is OK with this? Joining a slack channel isn't a referendum.
ben0x539··on There Are Only Four Billion Floats–So Test Them All (2014)
A while back for some videogame related data processing I ended up writing a "regular number to roman numeral" (or maybe the other way around) function in idk ruby or something. Not super convinced that I had gotten it right, I sat down to write a few tests, and then I realized I only needed it to work for numbers up to like 16. So I deleted the actual code, extended the table of test cases to cover 1 through 20 just in case, and just did a lookup in that.
ben0x539··on Tell HN: GitHub will delete your private repo if you lose access to the original
> At the same time this situation points up an important issue: if you don't own/control the infrastructure where your data lives, you don't own that data. Full stop.

We've known about this for many years!! And yet we for many varied reasons choose to make use of services anyway!! That doesn't mean we shouldn't get to complain about those services and giving people shit for that is really weird!!

ben0x539··on Rust's Ugly Syntax
I haven't really been keeping up, sorry.
ben0x539··on Rust's Ugly Syntax
Yeah, I think that's very cool and reads nicely in a lot of cases. D is definitely always a language that comes to mind thinking about "has lots of important features" + "doesn't look crufty".
ben0x539··on Rust's Ugly Syntax
That's wild actually, I've been aware that ML languages exist and had a rough idea what they look like but I never realized they do postfix generics. I'm going to have to let that bake in my brain.
ben0x539··on Rust's Ugly Syntax
Like, all the syntax does something that contributes to being safe and fast, but that doesn't mean there couldn't be a completely different notation for all of that. Maybe there is nothing that would make everybody happier, but for any given person unhappy with Rust syntax, there's probably a bunch of tweaks you could do to make it nicer for them.

For example, in

    pub fn read<P: AsRef<Path>>(path: P) -> io::Result<Vec<u8>> {
for me it's really unpleasant that there is so much stuff between the function name and the names of the parameters. It's a bit nicer with already-a-Rust-feature where-clauses like

    pub fn read<P>(path: P) -> io::Result<Vec<u8>> where P: AsRef<Path> {
but if nothing else I think that makes a mess of the indentation if you linebreak anywhere in that line.

C++ avoids this by just yanking all the extra bits at the very start of the declaration, so we could copy that (without going all the way into C++ caricature):

    for<P: AsRef<Path>>
    pub fn read(path: P) -> io::Result<Vec<u8>> {
This addresses my specific complaint, but is probably worse for other people. Who knows.

As another example, the whole business with explicit Result types and the early-return question mark is basically isomorphic to checked exceptions, which may or may not be syntactically lighter/more pleasant. Would Rust enthusiasts prefer that? Probably not. Would it make the language more approachable to people coming from some Java ecosystem? Maybe? Would it be worth it? No idea.

ben0x539··on Rust's Ugly Syntax
I keep thinking Rust should allow you to skip the < > if there's only one generic argument. Like just say io::Result Vec u8. Much more lightweight and not ambiguous (but breaks macros people write). You can keep the angle brackets for multiple arguments like idk Vec HashMap<Option String, Result<i32, ()>>.
ben0x539··on Directly access your physical memory (dev/mem)
Take that, memory-safe programming languages!
← PreviousPage 7 of 34Next →