3⅓ bpc linear RGB sales pitch oughtta be as close as we get to selling time to a clock before the markets collapse
169 karma · joined December 17, 2017
I guess 5 years ago (around the time when Intel stopped making SSE-only chips) is technically "older", but I wouldn't prioritize avx2 when devices intended for consuming media definitely experience much less pressure to upgrade than workstations…
That's why you usually want a userspace early oom service. Most preconfigured distros ship one by default. Linux is mostly focused on embedded targets, not servers or workstations. There is not a notion of mobile-style app lifecycle either, not in freedesktop environments that is, but XDG portals are working on addressing that sometime in the near future.
> In contrast, the other day the Force Quit window showed up on my Mac Studio because the OS was running low on memory
Windows does that at since like XP and likely earlier. BeOS did that before Darwin based macOS was a thing. On Linux, I don't know which distros do that, but you're definitely much more likely to see an app die rather than be asked whether to kill it. Freezing, once again, is a result of not having a [working] early oom service.
Linux is not that bad, but traditional freedesktop model kind of is.
It's still much better than mac OS.
Also those replies just look like bots, they were really fast and not providing any value, that's what I meant.
Either way, I find it hard to believe memory management would vary so much between those two CPU architectures on a single-codebase OS.
Well, that assumes descriptions are extremely accurate down to the last seam, which is not true. You'd be better off considering reviews and photos, esp. user provided photos, you also need to take into account the model/s in the photos are not necessarily shaped the same as you, so you need to somehow counter that bias in training. This is simply not a task achievable with current ml techniques, however again, feel free to prove otherwise.
(and ftr, I'm of course making a basic assumption that we're past the topic of markov chain/'llm' based chat bots at this point? Those are completely irrelevant to the goal of categorizing clothes based on some characteristics [i.e. the so-called 'vibes'])
(I mean honestly the project idea[?] they posted sounds like daydreaming some science fiction scenarios, otherwise with all the hype and investment around chat bots, this way of shopping would definitely be mainstream already. If it weren't daydreams, that is. But if my grandma had wheels, she would've been a bicycle, no…?)
I'm genuinely curious, whatever you're doing sounds cool, but more details beyond the buzzword pitch you'd tell your manager would be welcome on a hard technical site like hn?
(ftr, I'm skeptical of all applications of machine learning, but I keep experimenting with all the various kinds of it, generally with no good result; last real-world useful [to any extent] ml model I tried was BASnet, but whatever you tinkered out sounds cool and if it actually scrapes and filters clothes the way you describe, that'd be quite cool [perhaps even product worthy…?], cuz there are way too many clothes online to look at all of them manually and then esp. on fast fashion sites, there are oftentimes reviews you want to be wary for that indicate low quality products… anyway, that just sounds impossible to automate in my experience, but feel free to prove otherwise)
Honestly though, the argument against systemd is that it moves too much stuff into init, but I don't think it does enough of that, it's still extremely conservative, like, SD-DBus should be using binder x-port IMO.
Basically all I'm saying is that a syscall "ABI" is but a red herring for everyone but the [mainline] Linux devs themselves.
I think the real problem is GNU libc devs' unwillingness to stabilize it (not sure why, perhaps the menace of HURD still haunting them?)