Why? about quine-relay HOT 81 OPEN

Why not? Why not? Why not?

from quine-relay.

Source

^{Was the first thing I thought of. Love this project}

from quine-relay.

not because it is easy but because it is hard

from quine-relay.

It's awesome and inspired.

Computer Scientists and generally-terrific engineers often choose to do examples that are largely academic in nature because that engineer (or maybe -any- engineer) hasn't yet encountered that class of problem. They do this because the question can present a challenge to efficiency or elegance, or even defy a solution completely.

Often times, the journey produces lessons along the way that can be applied to other problems. On occasiona, it's a trainwreck that produces little fruit. However, when the answer is found, you might find new ways to do old things. If the answer is elegant, you can put another star next to your name attesting to the fact that there is one more question that you've never backed-down from, and answered beautifully.

I, for one, was astounded to find that, not only could he loop through fifty different languages, but that he ended up at the same code with which he began. This is a testament to how fundamental/efficient that each transient result was: there was no additional gibberish was produced by any specific one, which would likely produce more gibberish at one or more downstream steps.

As far as practicality is concerned, there is often a need to produce any number of libraries for programmers to develop against. The best of us find a way to define a structure that we can then permute to whatever language is required. Apache Thrift produces such a mechanism for client-libraries.

Thanks for doing this, Gabriel.

from quine-relay.

Autism.

from quine-relay.

Sheldon Cooper would say "Because we can"

from quine-relay.

George Mallory would say: "Because it was there"

from quine-relay.

Source
_{Just found this and immediately thought of this project}

from quine-relay.

from quine-relay.

Because a quine is itself a fundamental problem type. Try writing one sometime -- a program in any language that prints its own source code. The most basic quine type prints a single line to stdout. Level 2 is to output source code to a .png file or some other format requiring additional processing. Level 3 is to build a mutual quine -- two programs that output each other's source code, in different languages.

Somewhere out there, there is level N. This is where the practitioner has achieved an unimaginably high level of mastery, so high that those who are still on early levels can't yet imagine the types of problems the master has not only met, but solved. Those who understand the difficulty of levels 1 and 2 can only stand back and gape at the incredible demonstration of mastery that is before them. That's what this project is.

Why should the top jiu jitsu master or world-renowned musician give a public performance? The answer is the same -- because mastery ought to be seen and appreciated.

from quine-relay.

mengzhuo, i would a button "like" for the comments.

from quine-relay.

"Why?" Because it's beautiful and funny. It's "nerd art" :-)

from quine-relay.

— Why, Mr. Anderson? Why, why, why? Why do you do it? Why? Why get up? Why keep fighting? Do you believe you're fighting for something? For more than your survival? Can you tell me what it is? Do you even know?

Is it freedom or truth?! Perhaps peace?! Could it be for love?! Illusions, Mr. Anderson, vagaries of perception! Temporary constructs of a feeble human intellect trying desperately to justify an existence that is without meaning or purpose! And all of them as artificial as the Matrix itself, although only a human mind could invent something as insipid as love! You must be able to see it, Mr. Anderson! You must know it by now! You can't win! It's pointless to keep fighting!

Why, Mr. Anderson?! Why?! WHY DO YOU PERSIST?!

— Because I choose to.

from quine-relay.

ultimate derping.

from quine-relay.

from quine-relay.

🌷 🐢

from quine-relay.

this is a piece of art!

from quine-relay.

Amazing achievement truly.
The next logical step of course would be to make this into a 100-step loop performing also some calculation like adding up from 1 to 100. That would be enough of a proof for the existence of Quine Combinators!

from quine-relay.

So naïve...

from quine-relay.

"Because I can, bitches!" 🍪

from quine-relay.

👍

from quine-relay.

After 6 years, this is still an open issue.

from quine-relay.

The skill required to accomplish this task is moderately high. And once you've done it yourself a few times, you will finally know the answer why:

Because it is immediately satisfying to gaze into ones navel and see the entire universe.

from quine-relay.

Either you die an Engineer or, you live long enough to see yourself become an academic .

from quine-relay.

Be cause

from quine-relay.

One of the applications can be to encrypt a program
Let's say someone writes program in X and quine it and convert it to Y which can't be used to give back the original code untill run through some kind of custom compiler

from quine-relay.

“The reason anyone would, which they can't, is because they could, which they can't.” - Rick Sanchez

from quine-relay.

we do what we must because we can

from quine-relay.

Because:

Programming is all about knowing when to boil the orange sponge donkey across the phillipines with an orangutang gorilla crossed with a ham sandwich to the fourth power of twelve across the nile with an awful headache from the previous night when all of alfred's naughty jalapeno peppers frog-marched the nordic elves across the loom-lined geronimo induced swamp donkey over and above the fortran fortified kilomanjaro fence past the meticulously crafted anti disgusting sponge cake scenario where all the hats doth quoteth the milk which is not unlike the super werewolf from the infinite realm of ninja-step. it's hard to define, really.

source: https://discourse.codinghorror.com/t/why-im-the-best-programmer-in-the-world/1341/20

from quine-relay.

We do what we must because we can

from quine-relay.

Shit happens

from quine-relay.

Because why not have an issue that questions why or why not why or why not, "Why or why not should we have the repo?"

from quine-relay.

to sell more RAM 🐏💴💴💴💴💴💴

from quine-relay.

Why? Because. Because why? Because why because.

from quine-relay.

Beacuse it ...:feelsgood:!

from quine-relay.

So why? 🤔

from quine-relay.

goddammit! I love it!!!!

from quine-relay.

We don't ask why, we ask why not.

from quine-relay.

This is the craziest issue I have ever found on Github. I love it

from quine-relay.

I love the fact that this issue is still opened for no apparent reason.

from quine-relay.

Because the chicken wanted to cross the road.

from quine-relay.

Now if we add text-to-speech, it could recite it's own source code to Google Home and ask Amazon Alexa to compile and run it.

from quine-relay.

This is honestly a beautiful thing. I look forward to learning a new language by looking at the language I know now and seeing what's different! 👌👌

from quine-relay.

Why not? Maybe this could be useful for showing off all open source lanauges? 😄

from quine-relay.

"Because I can!"

from quine-relay.

Because the essence of programming is repeating.

from quine-relay.

"Actions are according to intentions, and everyone will get what was intended. " (Muhammad, pbuh)

Author has his own intention, implicit or explicit. He already get what he wants.

from quine-relay.

from quine-relay.

Why? Why? Why?

To get sweet internet karma of course

from quine-relay.

Because we can test those bazillions of compilers out there that we can never have time to test in the rest of our life.

from quine-relay.

Science isn't about why, it's about why not?

from quine-relay.

from quine-relay.

@dreamyguy

Be cause

So poetic. "Be the cause". Create a new branch in the infinite set of possible timelines where we didn't do what we wanted, because we were afraid of failure, or because we underestimated ourselves. Be the cause of this timeline being the one where you succeed

from quine-relay.

@jeffli678

Because the essence of programming is repeating.

Because_the_essence_of_programming_is_repeating = "Because the essence of programming is repeating".split()
while True:
  for word in Because_the_essence_of_programming_is_repeating:
    for _ in range(len(Because_the_essence_of_programming_is_repeating)):
      print(word)

Gist

from quine-relay.

This is so awesome!

from quine-relay.

Oh.

from quine-relay.

Love it! I was creating a program that generates a quine java code, and found this piece of art. Good job! 👍

from quine-relay.

For the hell of it of course!

from quine-relay.

Great Work :-)

from quine-relay.

I was going to ask the same question... WHY

from quine-relay.

Just came here from wikipedia, and I just can't stop laughing.

from quine-relay.

Why? Because we like you.

Em oh you ess eeeeeeee.

from quine-relay.

Why? Because why the fuck not?

from quine-relay.

I think taking this a step further would be resolving calling protocols between all language versions of the code so you can call any language version of a function from any language. I guess with 100 languages trying to call 99 other languages that would be 100*99 = 9900 functional binding to verify. Kind of like doing 100,00 prostrations for Tibetan Budhism.

from quine-relay.

Because it is possible!

from quine-relay.

why don't you compile it to mc an turn it back!

from quine-relay.

damn it @lemontghe, why have you summoned us here today? Let us sleep.

from quine-relay.

Art!

from quine-relay.

https://i.kym-cdn.com/entries/icons/original/000/027/869/Screen_Shot_2018-12-14_at_2.09.02_PM.png (although quining is certainly more worthwhile than what the image refers to)

from quine-relay.

I love it!

from quine-relay.

because it had to be done I guess

from quine-relay.

because it had to be done I guess

but why?

from quine-relay.

To be the first.

from quine-relay.

Because they are still there.

from quine-relay.

yes

from quine-relay.

quality assurance

from quine-relay.

Love it

from quine-relay.

@prijindal

to encrypt a program

I once had the idea of an esolang where the program is allowed to modify itself, and the interpreter, at runtime. A lang where you can mutate a table of opcodes to make the interpreter execute an entirely different opcode when it finds it (basically, runtime operator overloading, with absolutely no constraints). The funniest thing is that you can mutate the table directly, or mutate via a pointer table where each pointer points to an opcode. So you can swap, delete, and shadow opcodes by value AND/OR by reference, because the interpreter only accesses the op-table via the pointer-table.

There's built-in multithreading, but no built-in mutexes, so you must implement it yourself. You can use GoTos to jump into arbitrary threads (I'm so evil!!). Actually, there are no gotos, you must mutate the instruction-pointer just like any other register (this lang has many registers, each one special, but there's no special handling, and there's no way to distinguish between them unless you've read the docs)

But hell doesn't stop there! Each thread has its own op and ptr tables, copied (inherited) from the parent thread. ALL THREADS CAN MUTATE THE CODE AND TABLES OF ANY OTHER THREAD!! At any time!

The lang is typeless, so you're always dealing with raw binary data. And each byte is 11 bits wide just for the sake of triggering OCD

from quine-relay.

@infinitygamer404

To get sweet internet karma of course

Found the redditor (I know because I'm a redditor myself)

from quine-relay.

@chapmanjacobd

to sell more RAM 🐏💴💴💴💴💴💴

I prefer to download RAM

from quine-relay.

YEET

from quine-relay.