The Most Absurd Thing You've Ever Coded/Built
-
@Mason_Wheeler said in The Most Absurd Thing You've Ever Coded/Built:
Because what we're talking about here is not just archives, but compressed archives. TGZ takes a TAR archive and applies compression on top of it, which means that the entire thing has to be decompressed before you can extract single files. Modern disk-oriented archival formats apply compression to individual files and then join the results together into an archive, so extracting subsets of the archive is trivial.
Yet another problem that's mostly a problem in someone's imagination.
-
@Vixen said in The Most Absurd Thing You've Ever Coded/Built:
sitting at 95% full
that's unhealthy...
-
@Tsaukpaetra said in The Most Absurd Thing You've Ever Coded/Built:
@Vixen said in The Most Absurd Thing You've Ever Coded/Built:
sitting at 95% full
that's unhealthy...
i know!
but do i grow the array or shrink the data?
-
@Vixen said in The Most Absurd Thing You've Ever Coded/Built:
@Tsaukpaetra said in The Most Absurd Thing You've Ever Coded/Built:
@Vixen said in The Most Absurd Thing You've Ever Coded/Built:
sitting at 95% full
that's unhealthy...
i know!
but do i grow the array or shrink the data?
Yes!
-
@Vixen said in The Most Absurd Thing You've Ever Coded/Built:
but do i grow the array or shrink the data?
Grow the array, natch.
My NAS needs an increase but as it requires buying 4 larger drives (from different suppliers) and then increasing the volume 1 disk rebuild at a time, it's waiting until it gets a little higher up the priority list.
For now, I shuffled some stuff onto different storage to keep it over 10% free.
-
@topspin said in The Most Absurd Thing You've Ever Coded/Built:
I guess you’re getting to the point where you’ve had 95% of forum memes thrown at you
Luckily these are ageless.
-
@Vixen said in The Most Absurd Thing You've Ever Coded/Built:
shrink the data?
For me personally I recompressed security footage older than three months of any clips with no motion to 21 percent bitrate and deleted the originals.
In your case, raw footage is not desirable compressed unless lossless... Maybe remove any interim renders? Though I find it unlikely you keep temp shit on your NAS...
-
@topspin said in The Most Absurd Thing You've Ever Coded/Built:
Yes!
thrown at me, yes, i think so
Understood....... not even close.
-
@Tsaukpaetra said in The Most Absurd Thing You've Ever Coded/Built:
older than three months of any clips with no motion
Why not recompress to .tif? You don't lose any resolution that way, and a single frame of a video with no motion in it has got to be smaller than a video of it.
-
@Vixen said in The Most Absurd Thing You've Ever Coded/Built:
@topspin said in The Most Absurd Thing You've Ever Coded/Built:
Yes!
thrown at me, yes, i think so
Understood....... not even close.
It relies on the double meaning of "or", whether it's expecting a boolean or an enum in response. It was funny the first 100 million times.
-
@AyGeePlus said in The Most Absurd Thing You've Ever Coded/Built:
@Tsaukpaetra said in The Most Absurd Thing You've Ever Coded/Built:
older than three months of any clips with no motion
Why not recompress to .tif? You don't lose any resolution that way, and a single frame of a video with no motion in it has got to be smaller than a video of it.
But how do you replicate the timestamp changing per frame with a .tiff?
This is an excellent question candidate for SO!
-
@Tsaukpaetra Replace the video with a
.zipdirectory compressed( or not )in the manner of your choosing containing a .tiff and a short program that turns a .tiff into a video file by writing timestamps into successive frames.We're basically reimplementing a compression codec for 'videos with no movement', so i guess we're back on topic again.
Seriously what do you even need the timestamp for? A video with no movement has the same content all the way through.
-
@AyGeePlus Zip topic is :arr.... wait, which topic was that in again?!
-
@loopback0 said in The Most Absurd Thing You've Ever Coded/Built:
@AyGeePlus Zip topic is :arr.... wait, which topic was that in again?!
That one over yonder
-
@loopback0 said in The Most Absurd Thing You've Ever Coded/Built:
@topspin said in The Most Absurd Thing You've Ever Coded/Built:
I guess you’re getting to the point where you’ve had 95% of forum memes thrown at you
Luckily these are ageless.
Except for .
-
@jinpa said in The Most Absurd Thing You've Ever Coded/Built:
It was funny the first 100 million times.
Just like Mason downvoting jokes.
-
@boomzilla said in The Most Absurd Thing You've Ever Coded/Built:
@Mason_Wheeler said in The Most Absurd Thing You've Ever Coded/Built:
Because what we're talking about here is not just archives, but compressed archives. TGZ takes a TAR archive and applies compression on top of it, which means that the entire thing has to be decompressed before you can extract single files. Modern disk-oriented archival formats apply compression to individual files and then join the results together into an archive, so extracting subsets of the archive is trivial.
Yet another problem that's mostly a problem in someone's imagination.
Just because you've never had to do a thing doesn't make it irrelevant.
Having to wait an extra minute to get a file isn't the end of the world, but it's still better not to have to. Plus it completely disqualifies the format from certain uses where you may need fast access to individual components (like the MS Office .docx files).
-
@levicki said in The Most Absurd Thing You've Ever Coded/Built:
I haven't heard of a single file system which doesn't come with a warning saying "don't fill me up above 90% or bad things may happen (even without disks failing)".
Sounds like they should make 90% the new 100%
-
@levicki said in The Most Absurd Thing You've Ever Coded/Built:
Liar! There is no such thing as a big enough disk.
The Off-by-One Thread is
-
@anonymous234 said in The Most Absurd Thing You've Ever Coded/Built:
@boomzilla said in The Most Absurd Thing You've Ever Coded/Built:
@Mason_Wheeler said in The Most Absurd Thing You've Ever Coded/Built:
Because what we're talking about here is not just archives, but compressed archives. TGZ takes a TAR archive and applies compression on top of it, which means that the entire thing has to be decompressed before you can extract single files. Modern disk-oriented archival formats apply compression to individual files and then join the results together into an archive, so extracting subsets of the archive is trivial.
Yet another problem that's mostly a problem in someone's imagination.
Just because you've never had to do a thing doesn't make it irrelevant.
I never said that.
Having to wait an extra minute to get a file isn't the end of the world, but it's still better not to have to. Plus it completely disqualifies the format from certain uses where you may need fast access to individual components (like the MS Office .docx files).
I don't recall having such a problem, was my point. Mason is a tiresome concern troll about stuff he kind of understands.
-
@Coldflare
the more i look at this the less sense it makes
-
@anonymous234 said in The Most Absurd Thing You've Ever Coded/Built:
@levicki said in The Most Absurd Thing You've Ever Coded/Built:
I haven't heard of a single file system which doesn't come with a warning saying "don't fill me up above 90% or bad things may happen (even without disks failing)".
Sounds like they should make 90% the new 100%
I'm pretty sure 100% is the real 100%. I've never seen such a warning, or any bad things (besides running out of space, of course) on NTFS or any FAT file systems. The closest I've seen to what he's describing is that Android used to throw a shit fit if it had less than 10% free, but I'm pretty sure that's an Android thing, not a filesystem issue.
-
@AyGeePlus
Replace the video with a directory containing a .tiff and write a short program that generates additional hardlinks all named after the timestamp and whatever other metadata you want to record.security camera footage front porch nothing happening 2019090614274314
-
@hungrier said in The Most Absurd Thing You've Ever Coded/Built:
@anonymous234 said in The Most Absurd Thing You've Ever Coded/Built:
@levicki said in The Most Absurd Thing You've Ever Coded/Built:
I haven't heard of a single file system which doesn't come with a warning saying "don't fill me up above 90% or bad things may happen (even without disks failing)".
Sounds like they should make 90% the new 100%
I'm pretty sure 100% is the real 100%. I've never seen such a warning, or any bad things (besides running out of space, of course) on NTFS or any FAT file systems. The closest I've seen to what he's describing is that Android used to throw a shit fit if it had less than 10% free, but I'm pretty sure that's an Android thing, not a filesystem issue.
If your filesystem is filling up that much it might be due to lots of small files, and once that starts happening the NTFS master file table might have grown so much entries that it needed extra space allocated outside of its initially reserved space. That in turn means the master file table is now fragmented all over your disk, and no Microsoft tool is ever going to fix that situation (those move file data but do not touch the master file table). If you're dealing with a spinning rust drive you'll notice the speed penalty whenever the head needs to skip over your drive just to read the master file table; if you're using an SSD you might see less read impact but writing might still not be as zippy as before due to more flash blocks having to be moved when touched.
-
@anonymous234 said in The Most Absurd Thing You've Ever Coded/Built:
@levicki said in The Most Absurd Thing You've Ever Coded/Built:
I haven't heard of a single file system which doesn't come with a warning saying "don't fill me up above 90% or bad things may happen (even without disks failing)".
Sounds like they should make 90% the new 100%
Some SSDs let you do that intentionally, supposedly it's better for health...
-
@Tsaukpaetra AFAICT all SSD and spinning disks these days have more sectors physically available than they present to you and do internal remapping. The SSDs probably have bigger reserve as they need to remap on almost every write to avoid erasing while spinning discs only remap if a block becomes bad. But even the spinning ones do, because at current densities the plates almost always have some faults.
-
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
Salmiakki is an aquired taste, but once you've aquired it, its bloody wonderful.
I still sorta wish I'd have pilfered that bag of raw salmiakki powder I found in a semi-abandoned house, but I am at the same time also glad I didn't. I remember the kitchen of that house having some interesting bags of ingredients that made me go , as it was stuff I expected to find in a chemistry lab rather than a kitchen.
-
@Atazhaia said in The Most Absurd Thing You've Ever Coded/Built:
stuff I expected to find in a chemistry lab rather than a kitchen.
At least not an apothecary or perhaps witch's hut?
-
@jinpa said in The Most Absurd Thing You've Ever Coded/Built:
It was funny the first 100 million times.
Yes!
-
@Atazhaia said in The Most Absurd Thing You've Ever Coded/Built:
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
Salmiakki is an aquired taste, but once you've aquired it, its bloody wonderful.
I still sorta wish I'd have pilfered that bag of raw salmiakki powder I found in a semi-abandoned house, but I am at the same time also glad I didn't. I remember the kitchen of that house having some interesting bags of ingredients that made me go , as it was stuff I expected to find in a chemistry lab rather than a kitchen.
My chemist teacher in högstadiet actually pulled out a 10L bucket of pure ammonium chloride and let the class taste some. Yummy!
You can also order a bucket of it here: https://allt-fraktfritt.se/salmiak-ammoniumklorid-1400-gram.html
(that'd actually be an interesting thing to send to Alex for http://www.salmiyuck.com/ )
-
@AyGeePlus said in The Most Absurd Thing You've Ever Coded/Built:
Seriously what do you even need the timestamp for? A video with no movement has the same content all the way through.
Long file names fixes this. You just need to jam your noodles
-
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
that'd actually be an interesting thing to send to Alex for http://www.salmiyuck.com/
Don’t get me wrong, I’m not like one of those crazy people who rub peppers in my eyes, but I can handle the heat
Funny, Alex even included a link to @anotherusername.
-
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
pure ammonium chloride
Sounds disgusting...
-
@Tsaukpaetra said in The Most Absurd Thing You've Ever Coded/Built:
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
pure ammonium chloride
Sounds disgusting...
It has a really sharp salty taste. I think only the Scandinavians and Belgians actually eat and like it. (apart from the odd case in other countries)
-
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
My chemist teacher in högstadiet actually pulled out a 10L bucket of pure ammonium chloride and let the class taste some. Yummy!
Yeah, we had that too. Along with citric acid and other such things.
-
@Atazhaia said in The Most Absurd Thing You've Ever Coded/Built:
citric acid
This also sounds unappealing...
-
@Tsaukpaetra said in The Most Absurd Thing You've Ever Coded/Built:
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
pure ammonium chloride
Sounds disgusting...
Better than ammonium chloride and licorice
-
@Carnage said in The Most Absurd Thing You've Ever Coded/Built:
I think only the Scandinavians and Belgians actually eat and like it.
Some of the Dutch like it too (e.g., one of my coworkers).
-
@levicki said in The Most Absurd Thing You've Ever Coded/Built:
@Mason_Wheeler said in The Most Absurd Thing You've Ever Coded/Built:
Modern disk-oriented archival formats apply compression to individual files and then join the results together into an archive, so extracting subsets of the archive is trivial.
Those that are worth using don't, because storing individual files is reducing the compression ratio for no good reason.
(snip picture)
Solid archiving is a thing, if your computer isn't manly enough to handle it then I guess you can keep using that crap called ZIP and I'll stick to using LZMA2 compression and solid archives with large dictionary sizes to actually, you know, compress things.On the other hand, I don't think modern solid archivers compress the file list along with the rest, so unlike compressed tarballs you don't need to read and decompress the whole file to get the file list.
-
Apropos of this whole compression thing--
one of my biggest annoyances with MacOS is that the built-in Archive Utility won't let you look inside a zip file without decompressing it. Which even the brain-dead Windows ZipFolder implementation does without an issue.
-
@Coldflare It's very on-topic.
I especially like that it seems normal and sane and gets stranger and stranger the more you think about it.
-
@PleegWat said in The Most Absurd Thing You've Ever Coded/Built:
@PleegWat And it's
Netherlands' only real one
With old-fashioned spelling.
-
@Benjamin-Hall said in The Most Absurd Thing You've Ever Coded/Built:
one of my biggest annoyances with MacOS is that the built-in Archive Utility won't let you look inside a zip file without decompressing it.
Install BetterZip, then (assuming the Archive Utility works for you) delete it again but be sure to keep its Quick Look generator.
-
@dkf
Even more then Belgians.
-
@Benjamin-Hall said in The Most Absurd Thing You've Ever Coded/Built:
one of my biggest annoyances with MacOS is that the built-in Archive Utility won't let you look inside a zip file without decompressing it.
unzip -l filename
-
@loopback0 said in The Most Absurd Thing You've Ever Coded/Built:
@Benjamin-Hall said in The Most Absurd Thing You've Ever Coded/Built:
one of my biggest annoyances with MacOS is that the built-in Archive Utility won't let you look inside a zip file without decompressing it.
unzip -l filename
Thank $deity MacOS has no use for a command line!
-
@loopback0 said in The Most Absurd Thing You've Ever Coded/Built:
@topspin said in The Most Absurd Thing You've Ever Coded/Built:
I guess you’re getting to the point where you’ve had 95% of forum memes thrown at you
Luckily these are ageless.
They only look like they're 17 years old.
-
@djls45 TDWTF was born in 2004.
-
@loopback0 said in The Most Absurd Thing You've Ever Coded/Built:
@Benjamin-Hall said in The Most Absurd Thing You've Ever Coded/Built:
one of my biggest annoyances with MacOS is that the built-in Archive Utility won't let you look inside a zip file without decompressing it.
unzip -l filename
Let's compare windows and macOS here:
Windows can, in the GUI, trivially,
- let me view the directory structure in the zip file
- let me open individual files (in read-only mode) and look at whats' inside of them
- selectively unpack the zip file to any location I choose
macOS can:
- In Finder, only unzip the whole archive. Can't let me peek inside, and especially not into files. And unzipping always takes place in the current directory.
- from the console can let me see the file list, but not do anything with them. And requires arcane commands to do anything other than just unzip it, although unzipping it to other locations is easy...if annoying due to having to navigate.
Windows wins, by a light-year. And Windows's implementation is (as admitted by Raymond Chen), moronic and archaic. What does that say that macOS can't even do that?
-
@Benjamin-Hall said in The Most Absurd Thing You've Ever Coded/Built:
Windows wins, by a light-year. And Windows's implementation is (as admitted by Raymond Chen), moronic and archaic. What does that say that macOS can't even do that?
It’s clean and intuitive, obviously. Why would you ever want to do anything other than the default action?
Filed under: from the “whats’s a right click” people