saba2008

I've done this even with CDs.

50% figure for vinyl sounds plausible to me, considering cost of turntable and hassle of actually using it (unless you enjoy the ritual and experience of physical media). And vinyl makes great merch.

Single file + CUE sheet solves lead-in thingie problem, by storing both timestamps (time when player should start showing 'Track 2', and time which servers as zero for track-relative timestamps)

It pretty much mirrors actual CD structure of TOC (containing all necessary timestamps and metadata) and continuous sequence of frames with audio data

At least globbing should return fully qualified paths (not sure there is an established term for `(<directory>/)+<file>' paths, as opposed to `<file>` ones).

>Some things you need to hide from the end user. De-emphasize - maybe, hide - no. Garbage pile that is average Linux home directory is pretty much result of 'out of sight - out of mind' practice, enabled by dotfiles being hidden. I wish Linux settled on single `~/System/` directory, mirroring `/` structure.

On the other hand, dotfiles convention is useful for meta/"parallel" data, `.git` being prime example - something tighly linked with abitrary file structure.

Intelligence (in a metric, "this is intelligent way to do X", sense) implies some purpose. But life is just one big 'systems that survive and grow - grow and survive' tautology.

Only if you are designing another TempleOS. Thing for it's own sake, unaffected by any external requirements and completely specified, designed and implemented by one person.

GIF compression is lossless, codecs used in WebM and MP4 are not.

>These days

HashCash is older than Bitcoin, and Bitcoin sybil-attack protection is basically HashCash.

It can be also tied to bespoke equipment, hard-to-transfer expertise and experience. If consumption grows relatively slow, it makes sense to expand single installation, rather than duplicate it with 'copy exactly (which might take too long to pay off).

Promise is not disputed. There are no signed papers - there is no promise.

Whenever it was discussed at all is 1% a purely academic dispute and 99% demagogy.

You can exploit it do distinguish whenever script is `curl | bash`'ed.

Add `sleep 1`, and detect pause on server. Then, if pause detected - serve attack payload. If not - somebody is careful enough to download and audit, so serve just the script.

Most other languages would require `eval` and having incorrect code as syntactically correct string literal.

But because Perl is parsed as it is executed, incorrect code raises syntax error only when it is reached by execution.

News at 11: greater fool pyramid scheme collapses.

Putting Unicode everywhere is great.

Turning Unicode into clipart collection is not.