🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆.
𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍
Ah, a youngling.
My first programming language was Basic; my second, assembly; third, C. I didn’t get to new-fangled languages like Pascal until i was in college, long after I’d learned the only really useful fundamentals of programming and computer software.
Everything else is just gloss, convenience, and bloat.
I agree; it probably didn’t occur to them. But it was a fairly common job in IT in the 90’s. Not a career or job description, maybe, but a duty you got saddled with.
What they really got wrong was the clothing: so much anime/hentai.
This is a techno-goth.
A studio should be able to afford a good LTO tape drive for at least one backup copy; LTO tapes last over 30 years and suffer less from random bitrot than spinning disks. Just pay someone to spend a month duplicating the entire archive every couple of decades. And every decade you can also consolidate a bunch of tapes since the capacity has kept increasing; 18TB tapes are now available: $/MB it’s always far cheaper to use tape.
They could have done that with the drives, but today you’d have to go find an ATA IDE or old SCSI card (of you’re lucky) that’ll work on a modern motherboard.
But I’d guess their problem is more not having a process for maintaining the archives than the technology. Duplicating and consolidating hard drives once a year would have been relatively cheap, and as long as they verified checksums and kept duplicates, HDs would have been fine too.
Github is full of lists of things. There are even several lists of “awesome lists”. Far more than I can list here, and it starts to get painfully recursive (an awesome list of awesome lists of awesome lists?). Just search for “awesome list” on github; some live outside of github, so you could search for “awesome list” in Ecosia, or DDG, or whatever you use.
It sucks the same way Python sucks. Some people just really don’t like indentation-based syntax. I’m one of them, so I dislike both formats. However, if you groove on that sort of thing, I don’t think YAML is any worse than any other markup.
Oddly, I get along with Haskell, which also used indentation for scoping/delimiting; I can’t explain that, except that, somehow, indentation-based syntax seems to fit better with functional languages. But I have no clear argument about why; it’s just an oddity in my aesthetics.
djot for text markup. It addresses a lot of the issues in Common mark (and of course far more of the issues of Markdown).
I love that there’s someone out there who’s that passionate about JSON.
Love, love, opus. It’s a fantastic format.
Minnesotan here. Can confirm that 32 is still long-sleeve shirt weather.
I regularly see people here walking into a store from the parking lot in T-shirts, in 32° weather. Wind chill makes a far greater difference. 38° from wind chill is far colder than 32° with no wind.
The week-of-year is far more relevant in Western Europe, and is used quite a bit in business. I have a Junghans watch that has a week complication.
It’s an important format outside of the US, and gives ISO-8601 an edge as a standard of conformance.
I may know someone who used an fmovies site to watch something last night, so some are still up.
Dead.
Pirate streaming is a Hydra. Cut off one head, two more grow.
We’re gonna put creatives out of work, we’re gonna sell a unified product to replace them, and we’re gonna use their own labor to build their replacements.
Yes, but: it’s short sighted, and wrong. Until we have a sea change in the LLM/AGI space, “creatives” will be needed for seed data. LLMs that are recursively trained on their own output degrade and produce worse output over time.
The “yes” part is that companies looking to replace paying people for their work, but still hoping that Creative Commons types are still posting online for free harvesting.
There are already quantum resistant algorithms available as open source libraries, and some tools which already use them. It’s nice to see some standards emerging, although I’ll be more confident after external reviews pronounce them “clear.”
And then this article showed up today on EFF’s site; things are getting worse, not better 😠 🏴☠️
Since when? There was a ruling in the 80’s that it was. I admit laws may have changed and I didn’t notice, but I also believe corporations are perfectly capable of lying - or using half-truths - to convince people they don’t have rights that they really do.
I just grabbed the first search result, but:
https://legalbeagle.com/12719016-copyright-law-making-personal-copies.html
DRM & DCMA. Well, I don’t know whether this has yet been tested in court, and with the current Supreme Court it might not be wise to risk it, but eventually with a more moderate court I would expect a similar ruling as the original ruling was meant for. A corporation suing an individual for circumventing DRM with no proof of redistribution, I think, would result in a ruling DCMA would not like to have on the books. But, that’s just me, and we don’t have a moderate higher court, and you’re right.
I do it for all books I’ve purchased because Fair Use has ruled that I have a right to make copies of media I’ve purchased, for my own personal use.
Calibre & DeDRM. If these are the tutorials you’ve tried and have failed with, I can’t help you. It’s even harder with Linux, but somehow I’ve managed. You might have more luck if you say how it’s failing.
I’m with you; I prefer date versioning for many things. Semver does work really well for things with exposed APIs; it’s a stretch to justify using them with user tools, and especially GUI tools. Semver is used to great effect in Go - which is how it should be use: mainly by the language’s module management system. Outside of that, it’s human readable, but like XML, its main value is to machines, and only secondarily to humans.
Calendar versioning is far more human-oriented, and so more useful for things without exposed APIs or module tooling.
How did you get your invite?