[citation needed] for that assertion. Atari 2600 is extremely limited in the number of sprites available on-screen at the same time. If you've played Pac-Man then you know that 5 is too many, because all of the so-called "ghosts" are actually flickering. They're doing that not for a spooky effect, but because they can't be simultaneously displayed. That sort of sprite flicker doesn't happen in Pitfall!
Yes, but the limitation is per-scanline, not per frame. Thus, “racing the beam”. The tree branches are above all the other sprites besides the swinging vine.
I think we need to examine the definition of "pipe" in a POSIX context here. Pipelines feed the output of one program into the input of another one. You don't "pipe" files, you copy them.
This film resonated with 14-year-old me so profoundly that I became obsessed with it in every way. I managed to go see it in the theater at least 9 times, Mrs. Bueller. I was absolutely enthralled by Ferris' audacity and the overall thrill ride Hughes took me on. I had no particular love for any Hughes films before or after that; I was absolutely a Ferris Bueller boy and that's how it was for years. This favorite movie status was finally supplanted by Steve Martin in LA Story.
I remember liking this movie so much when I saw it in the theater when it came out that it became the first and only movie I ever snuck back in to watch a second time.
We rented this movie when I was a kid (probably the Beta version). It's one of 2 movies that me and my brother watched twice in 2 days. The other was Bill and Ted's Excellent Adventure. We watched that one the second time with my uncle who sat and watched the entire movie with us and then said it was the stupidest movie he's ever seen. We were so disappointed.
There are strange cases which may make this a logical choice. Since vi doesn't traditionally lock the file it's editing, another process could change the file on-disk while you have it in the editing buffer. I think you'll get a message in these situations, because it's usually not what you want. Then you'd have the choice of writing out the buffer, whether it's changed or not, to restore the contents of the file from when you began your vi session.
That's not obvious, because you don't necessarily own the code you're uploading. I can upload any sort of MIT-licensed, BSD-licensed, Apache-licensed, Creative-Commons-licensed, or GNU-copylefted works I want, anywhere within reason and compatible with those licenses, but if I didn't write them then I don't have the legal right to relicense, grant exclusive or restricted license to any specified parties.
So in a way this would void parts of many TOS agreements where you do relicense your User-Generated Content. If we're uploading memes to Facebook, they're gonna have to work out license terms with the copyright holders, not the uploaders.
Uploading someone else's code without permissions is, in itself, copyright infringement. Just like you can't take someone else's code and license it to GitHub without the copyright holder's permission, you can't take images off of someone's website and sell/license them to Getty Images for profit.
I'm not sure that's the case if the repo is private and the code is not shared/disseminated to others. If you buy a book, you are not allowed to distribute copies of it, but you can loan it or sell your copy, or store it wherever you like. Copilot does allegedly distribute copies of code that it doesn't have the copyright to.
But imagine Getty Images sells the stolen photo 10,000 times. They had no idea it was illegally stolen and fraudulently passed off as the fraudster's own work. If they get sued for infringement, they can just sue the actual fraudster for damages.
Same will be for GitHub: if people really didn't have the legal authority to bind someone else's code to GitHub's TOS, then GitHub can go after the $x million of users that have uploaded code they shouldn't have.
Technically, Jesus rose again and left Earth alive, without dying again.
The Blessed Virgin Mary is certainly mentioned in the New Testament, and her death is an open question, but her assumption into Heaven is a fact.
When I was homeless, I found a job with a "call center". Our training consisted of teaching us the cover story and how to handle reactions to it. We began with a joke involving alcohol. Then if they didn't hang up we launched into the pitch: "We just lost our lease on our warehouse, and we've got to move all these pens. You can get them imprinted with your name and phone number for a bargain. What do you say?"
Lying has been a source of controversy for Christians since the beginning. The Old Testament recounts at least two instances of righteous Gentiles: women who lied for the sake of Israel. The Egyptian midwives save the Hebrews' male progeny from death, and Rahab the harlot hides spies in the heart of Jericho. It's unambiguous that God deals kindly with them, and Rahab becomes an ancestor of Jesus.
The most frequently cited technique is that of mental reservation. If Nazis knock on your door and ask, "Are there any Jews here?" you can stand in your foyer and say "There are no Jews here." because "here" means the foyer, not your attic or closet.
Fast-forward to the present day. The Catechism of the Catholic Church revised a few paragraphs on lying: #2483 and #2508. While this doesn't constitute a change in teaching or doctrine, it makes the present stance stricter and less permissive, as well as obscuring the controversial history of the thing, and now we're unable to reconcile the OT pericopes with what the Catechism says.
"To lie is to speak or act against the truth in order to lead into error s̶o̶m̶e̶o̶n̶e̶ ̶w̶h̶o̶ ̶h̶a̶s̶ ̶t̶h̶e̶ ̶r̶i̶g̶h̶t̶ ̶t̶o̶ ̶k̶n̶o̶w̶ ̶t̶h̶e̶ ̶t̶r̶u̶t̶h̶."
That's a pretty major change. (and I would argue that while telling people who don't have a right to know "Mind Your Own Business" is the best course of action, in some power dynamics that is much riskier than lying. In the latter case, I was prepared to argue here that there is almost an affirmative obligation to lie, from the same "what if the behaviour was generalised" argument as TFA)
(idle query: are rationales for catechism changes public?)
[Edit: I am impressed that 2493-2499 cover "The Use of the Social Communications Media". and at least this change to 2483 and the blanket 2508 seem to be subordinate to 2510, which posits using the golden rule to discern whether or not it would be appropriate to reveal the truth to someone who asks. cf 2511
That’s a fascinating take, given that much of what Catholicism actually is is defined by the lies it’s routinely using for all kinds of purposes, from providing a safe heaven to child groomers to spreading the hate speech.
> If Nazis knock on your door and ask, "Are there any Jews here?" you can stand in your foyer and say "There are no Jews here." because "here" means the foyer, not your attic or closet.
That is some next level tortured reasoning. So if they first ask "Who lives here?" should the answer be "Nobody", because nobody lives in the foyer? Or does the meaning of "here" vary from second to second? If they say "To the best of your knowledge, do you know the location of any Jews or other minorities that the state considers unwelcome within this house or in a 100 meter radius around it?" should a devout Christian just give up the Jews hiding in the closet/cellar/shed because they couldn't find a way to twist the question, and lying would be wrong?
A tape drive actually led to my adoption of Linux.
Around 1999, I decided that a QIC tape was the best backup solution for my home network. At the time, I had a 486 running Windows, and two Apollo 425t running OpenBSD. The 486 may have also dual-booted into OpenBSD.
Anyway, I had a bare-bones 386 sitting around and I had upgraded the 486 so much that the spare parts were available to reconstitute the 386. I found a nice floppy tape drive, consumer grade, and wouldn't you know that OpenBSD didn't have floppy tape drivers. So I installed Linux on the 386 and it was a dedicated backup server.
At the same time I had a SyQuest EZ 135 that I was very fond of, and those 135MB cartridges could hold good stuff, like a complete complement of Windows updates. But its capacity was too low to be a backup solution, of course; it was storage on-the-go.