The fact that btrfs isn't stable after 15+ years for parity setups is, IMO, unreasonable.
192 karma · joined December 6, 2011
The fact that btrfs isn't stable after 15+ years for parity setups is, IMO, unreasonable.
If you never have to type something you're reading, I'm sure unique typing styles are just fine.
"not notable" is the cancer within wikipedia. You can't claim to be the sum of human knowledge but also arbitrarily remove articles to meet some imaginary criteria.
As part of a restoration, yes. As part of a remaster, no.
If the remaster is overseen by the primary creative (such as everything done to the Aliens UHD 4k release, which was overseen and approved by Cameron), then it's official -- and as an audience member, you have to examine how you feel about that. For example, some enthusiasts lament the removal of film grain in Aliens, but Cameron has said in interviews that he hated the grain in Aliens because he was forced to use a particular film stock and didn't like the result. So it was never the director's vision to have excessive grain in that movie, and the audience should accept the 4k UHD release as canonical and authorized.
These debates are colored (no pun intended) by nostalgia, much like the vinyl vs. digital debates.
In the 1990s, we frequently used the phrase "launch a website" to mean "navigate to the website", so your prompt could have been clearer than just three words.
There are more reasons to use an Oxford comma than not, and I remain continually surprised that it is not taught as the default.
The eye's response to changing color is slow, but the response to changing luminance is very fast.
You misinterpreted what he wrote. He wasn't saying that mode 13h didn't work; he meant that the optimizations in the mode 13h path of the executable weren't as good as the Mode Y path. It's the optimization that didn't work, not mode 13h itself.
It's not a great name and not very discoverable, but there's a lot of very useful ffmpeg-by-example snippets there with illustrated results, and an explanation of what each option in each example does.
In the early 1990s, QModem's workflow for offline inter-BBS email (in the QWK file format) allowed me to communicate several times weekly, much faster than physical mailed letters, to people all over the world that I would not have been able to do otherwise. It helped me curb depression, build my technical skills, and join a community whose members I am still in contact with over a third of a century later.
QModem was written in Turbo Pascal, and was noticeably faster than other terminal ("modem") programs on my aging 8086 hardware at the time. And knowing it was written in TP, and being a TP programmer myself, gave me hope for the possibility of writing fast code in a high-level language myself, which I eventually did.
I would not be as successful in my life today without the positive experiences made possible by QModem.
PS: Your father's choice of name for his shareware company, "The Forbin Project", was quite the hax0r flex at the time.
It's not how well the bear dances, but that the bear dances at all. That said, EMS and a solid-state hard drived do help a little.
- A full OOP tree to determine parents/traits of descendant objects
- The ability to edit, assemble, and trace through both inline and external assembler code
- A registers window that showed all registers and flags at any stage of runtime
...all while able to run on the first 4.77 MHz 8088 IBM PC, which was long in the tooth by the time TP 7.0 came out. (The OOP tree required a 286 as they only added it to the protected mode IDE.) This made the TP 7.0 IDE a complete development and debugging environment for assembler as well as Pascal.