Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
chungy
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
81 ms
·
781.
▲
by
chungy
4y ago
> Oh and it's cost me money in fines from taking me the wrong way down streets I was not allowed to drive on. It is your responsibility to drive legally. Even if Google Maps is suggesting a route that's illegal, you made the ac
782.
▲
by
chungy
4y ago
Seems a nice way to bury a lede :) No links back to GCC including the languages, and a look at https://gcc.gnu.org/ doesn't reveal it either, even if you click on changes for GCC 13.
783.
▲
by
chungy
4y ago
Actually it was Windows Me that had a USB Mass Storage driver. Windows 98SE still didn't include one.
784.
▲
by
chungy
4y ago
Pick something you're willing to maintain. Stable releases tend to reduce maintenance and surprises.
785.
▲
by
chungy
4y ago
It was the best of times, it was the blurst of times.
786.
▲
by
chungy
4y ago
Should be worth noting that NetBSD is its own thing; FreeBSD and OpenBSD haven't had problems getting the newest GNOME versions for the entire lifetime of 3.0 and higher. Unlike Linux, the BSDs aren't distributions of some "u
787.
▲
by
chungy
4y ago
Changing out the hashing algorithm in Git is a very difficult thing to do.
788.
▲
by
chungy
4y ago
GNOME and KDE both work fine on Linux and FreeBSD. In addition, OpenBSD usually gets the newest GNOMEs.
789.
▲
by
chungy
4y ago
If you run a ZFS file system where this is a huge deal to you, then don't set utf8only. If it's set on a parent dataset, then explicitly do utf8only=off.
790.
▲
by
chungy
4y ago
This is why "convmv" exists :) and also why my /tmp is a normal tmpfs where file names can be any byte sequence. I can, for instance, extract random archives there, use convmv to make them UTF-8 (if not already), and then it
791.
▲
by
chungy
4y ago
> I wouldn't be too put out if either "won". AVIF sort of makes sense in how easy it is to support with the support of AV1 in the first place, but it is one of a long line of still-image codecs based on video codecs (comin
792.
▲
by
chungy
4y ago
NTFS disallows 0x002F as well; it is possible to use the entire set even from Windows (installing Interix, for instance). Windows NT was designed around UCS-2, the file system didn't have to do much but be a dumb bag of bytes for file
793.
▲
by
chungy
4y ago
Seems it uses ffmpeg on the backend anyway :) Best tool for the job. I'll probably keep using ffmpeg to clip out a single segment, but it gets hairy when you have more complicated edits.
794.
▲
by
chungy
4y ago
On most Linux distributions, it's basically the same. Your package manager tends to make no distinction between OS files and installed program files. FreeBSD does another approach, where user-installed packages go to /usr/loc
795.
▲
by
chungy
4y ago
Better link: https://lkml.org/lkml/2022/12/4/120
796.
▲
by
chungy
4y ago
It's similar in the US. The police could ask nicely to come in without a warrant, but anyone can (and should!) decline.
797.
▲
by
chungy
4y ago
> So what's the distinction between JPEG XL and AVIF? On a tecnical level, it's hard to find a way that AVIF is preferrable. AVIF support comes nearly for free with AV1 already supported for video.
798.
▲
by
chungy
4y ago
I'm probably part of the group you'd call "WebP haters", especially if you look at my comment history[1]. I would rather describe myself as extremely disappointed in WebP. It's a clear win over PNG in the lossless u
799.
▲
by
chungy
4y ago
> In fact, it could be that the test was successful and now Chrome is waiting on something else before it adds proper support. Waiting for libjxl 1.0 is reasonable. Though I can't help but to think it would be less work to just keep
800.
▲
by
chungy
4y ago
The link styling is inconsistent with basically every other web page; underlines haven't been "everywhere" since the late 1990s (for better or worse), but distinguishing links has usually been done via the use of color, maybe
801.
▲
by
chungy
4y ago
Yes, the convention is not at all obvious. I also thought it was a link-free page and closed it the first time thinking there wasn't really much to show.
802.
▲
by
chungy
4y ago
It's sort of funny the paragraph about a custom title bar, that is always the first feature I disable whenever I deal with a new install of Chrom(ium|e). Don't really know why it tries to do it, but a right click and "Use sys
803.
▲
by
chungy
4y ago
It's pretty much already happened. Tor Browser is little more than stock Firefox with some of the settings changed.
804.
▲
by
chungy
4y ago
WebP's lossy codec is based on VP8 intraframes; the lossless codec is original. Either mode of which is contained in a RIFF file, which is where the dimension limits happen (RIFF's headers have enough space to represent 2^14-1). W
805.
▲
by
chungy
4y ago
WebP is recent enough that it shouldn't have even been a real concern. 16383×16383 even in 2010 was an absurdly small size. I've had PNGs and JPEGs with larger dimensions for longer than WebP has even existed.
806.
▲
by
chungy
4y ago
JPEG should be fine with those dimensions (did you try mozjpeg's cjpeg?), but WebP is contained in a RIFF format and has a limit of 16383 pixels in either of its dimensions. Don't know the technicals of AVIF, but being derived fro
807.
▲
by
chungy
4y ago
Flatpak exists; Nix exists; Guix exists. All of them make it easy to have newer software without caring about your Debian package versions.
808.
▲
by
chungy
4y ago
AsciiDoctor is a second implementation that doesn't even fully compatibly implement the original specification. The original AsciiDoc is pretty well-specified, and it's mostly the plaintext markup of stuff that was intended to go
809.
▲
by
chungy
4y ago
I honestly don't get why Markdown became preferred in most projects over AsciiDoc.
810.
▲
OpenZFS 2.1.7 Released
(github.com)
10 points
by
chungy
4y ago
|
1 comments
More ›