Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mananaysiempre
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
mananaysiempre
5d ago
No need for image gen to get this kind of problem; to me that skin look just reads as really aggressive denoising. And there is no escaping physics, a tiny high-res sensor will need a whole lot of denoising for this really challenging sce
2.
▲
by
mananaysiempre
19d ago
It’s partly by design—the word senate shares its root with the word senex “old man” (whence also senile , etc.) because it’s literally a council of elders. That’s what the Roman one was and what the US constitution (among others) was a
3.
▲
by
mananaysiempre
23d ago
An ASCII-friendly way to spell ℞, an R with a crossed right leg, shorthand for the Latin singular imperative recipe! “take (the following)!”, which is the conventional start of a prescription; by extension, something necessitating a presc
4.
▲
by
mananaysiempre
24d ago
Depending on the effort you’re willing to put in, you don’t have to: gzip has a specific provision for concatenated files and tar is a flat array of (file) records each followed by file data, terminated by a sentinel record, so what you nee
5.
▲
by
mananaysiempre
25d ago
> Rust's critical invention was "what if we modeled heap ownership and borrowing with linear types". Rust did not invent this (and I don’t believe Rust’s creators claim it did), see e.g. “Linear regions are all you need”[1
6.
▲
by
mananaysiempre
26d ago
None of the sequelae of that have really improved since then, at least as far as the first world is concerned. The foundations of universal surveillance were being laid down, but it wasn’t yet feasible. Police (transport security, border pa
7.
▲
by
mananaysiempre
26d ago
Here’s a larger stash: https://github.com/timvieira/justified-variables (via https://news.ycombinator.com/item?id=31138306 ).
8.
▲
by
mananaysiempre
26d ago
Judging by the lowercase “m” it’s the 8x16 variation[1] and not the 9x16 one you linked, but otherwise yes, looks like the plain old VGA font? (Incorrectly displayed, as the site points out: the VGA didn’t have square pixels in either of th
9.
▲
by
mananaysiempre
27d ago
Muratori et al. like comparing speeds to (single-core) memory bandwidth (dozens of GB/s) and that’s a reasonable upper bound, but generally it seems to me that, unless you operate on huge elements and don’t do very much with them, you
10.
▲
by
mananaysiempre
27d ago
> I/O is inherently very slow compared to computation. Not anymore, no. Your SSD, before any caching, does gigabytes per second of sequential reads. For any bytewise processing, except the most trivial of tasks, you’ll struggle to
11.
▲
by
mananaysiempre
27d ago
> Don’t think TeX ever did that, that was a “simple” Pascal program. Not exactly the entire process image, no, but essentially all of its data in a single chunk. It’s a peculiar Pascal program because it bypasses basically all of Pascal’
12.
▲
by
mananaysiempre
28d ago
Related: previous article in the series, https://news.ycombinator.com/item?id=49308685 (103 points, 47 comments)
13.
▲
by
mananaysiempre
29d ago
Some time ago, I’ve come across an Asahi patch to I think Pipewire that tied system volume to a Macbook-specific loudness compensation filter, but I couldn’t figure out how to actually make use of it outside of their environment.
14.
▲
by
mananaysiempre
29d ago
Not Black Mirror, 2013 vintage 4chan.
15.
▲
by
mananaysiempre
1mo ago
Kinda. There are also the 32-bit bits on top, not (AFAIU) that different from their NT4 counterparts, such as the shell, COM/OLE2, TrueType, OpenGL, etc.; the core Win16 stuff (KERNEL/USER), which the Win32 layer thunks down to an
16.
▲
by
mananaysiempre
1mo ago
I mean, a plain JPEG can tolerate up to I think 2^16 × 2^16 pixels, and already that you don’t really want to decode from a single unseekable bitstream with no index and no effort to improve locality of data required to fill a rectangular v
17.
▲
by
mananaysiempre
1mo ago
Likely 32-bit file access[1] and the caching it included? The arrangement where Windows calls 16-bit MS-DOS entry points to do I/O (including from 32-bit programs) to respect preexisting DOS drivers, network redirectors, etc., but then
18.
▲
by
mananaysiempre
1mo ago
It’s not correct to say it was “really 16-bit”, no, but as Unauthorized Windows 95 [1] eloquently demonstrates, neither was Windows 3.1 or 3.11, especially with Win32s, and Windows 95 was much more of a direct descendant of that environmen
19.
▲
by
mananaysiempre
1mo ago
> [JPEG XL can] display much larger images than AVIF can Does it do tiles? What about pyramids (i.e. precomputed downscaled images, think mipmaps)? Right now the state of the art for truly large images (medical, geospatial, scanned artwo
20.
▲
by
mananaysiempre
1mo ago
It was around 1/96" on a conventional PC screen because that was the conventional pixel density for PC screens; it was 1/72" (i.e. 1pt) on a conventional Mac screen for the same reason. That was something to deal with al
21.
▲
by
mananaysiempre
1mo ago
Nixpkgs has 11k open PRs at the moment (a lot of them routine version bumps and such), so no. But then Nixpkgs isn’t a piece of software in the conventional sense: the monorepo does contain a few of those, but most of it is a giant collecti
22.
▲
by
mananaysiempre
1mo ago
Less of a commodity at this point than a few years ago, what with Minio immolating itself to be reborn as, excuse my French, AIStor. Which is not to say that TFA’s approach is invalid or uninteresting, but the mechanics of how “an S3” works
23.
▲
by
mananaysiempre
1mo ago
“Software forge” is an established[1] term by this point: a piece of software providing a full set of features for collaborative development, usually at least code hosting with a web interface, tickets, and webpage hosting, and these days o
24.
▲
by
mananaysiempre
1mo ago
For me (not GP), this lives in the recreational-mathematics part of my brain rather than the useful-things part of my brain: John Conway called this invention of his the “Doomsday rule”[1] and I suppose the memorable name helps. But I admit
25.
▲
by
mananaysiempre
1mo ago
I don’t imagine that you’re unaware of any of this, but: ld.so and libc.so are heavily interdependent in deliberately undocumented ways with Glibc and outright the same file with shared Musl. And while you might usually get away with using
26.
▲
by
mananaysiempre
1mo ago
If you want to load the OpenGL/Vulkan vendor driver then unfortunately you don’t have much of a choice: those are linked against glibc, and I believe generally also against libwayland so screw off if you want a different protocol libra
27.
▲
by
mananaysiempre
1mo ago
It appears that Framework contracted out the development of their (Insyde-based) firmware to somebody who, to put it mildly, does not treat them as a priority. Either way, Framework’s firmware is really bad, and that’s entirely on Framewo
28.
▲
by
mananaysiempre
1mo ago
IIRC the only Frameworks that have a coin cell in them are the 13-inch 11th-gen Intel ones (i.e. the OG model), and it should be right there staring you in the face as you lift the keyboard. There’s indeed a known design flaw[1] around that
29.
▲
by
mananaysiempre
1mo ago
C++ bundles together a way to write functions inline in an expression (what I’d call “lambdas” in general) and a way to create closures with strictly nested lifetimes, but there’s no law of nature tying the two together. Even in C++ the ess
30.
▲
by
mananaysiempre
1mo ago
Good C style is that every function that accepts a callback should also accept an opaque context pointer it then passes through unchanged to the callback. Usually the caller will allocate a structure on the stack or the heap, stash some of
More ›