[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]

/vt/ - Virtual Youtubers

Search:


View post   

>> No.75329901 [View]
File: 543 KB, 1500x2000, scientist joshu.jpg [View same] [iqdb] [saucenao] [google]
75329901

>>75329114

>> No.73344800 [View]
File: 543 KB, 1500x2000, joshu-kun dokuta.jpg [View same] [iqdb] [saucenao] [google]
73344800

>>73341012
>>73343573
Let's call this fictional programming language "KoyoPyck." In KoyoPyck, we'll merge Python's simplicity with Brainfuck's minimalistic approach, with the added twist that only the letters "k", "o", "y", and "o" are allowed. Given these constraints, programming in KoyoPyck becomes a creative challenge. Here's how one might write a "Hello World!" program under these rules:

KoyoPyck Syntax Basics:
Since we're limited to "koyo", we'll use these as our command symbols.
"ko" could represent a move in the memory tape (akin to Brainfuck's ">" and "<").
"yo" might be used for modifying the value at the current memory cell (similar to "+" and "-" in Brainfuck).
"koyo" could be a command for output, inspired by Python's print() function, but we have to define a way to specify what to output.

Mapping "Hello World!" to KoyoPyck:
Without direct access to characters, we'll have to creatively encode "Hello World!" using our limited commands.
We'll assume each "ko" moves us one cell to the right, and "yo" increases the cell's value by one. "koyo" will output the character corresponding to the ASCII value in the current cell.

Given the constraints and the fact that actual implementation might defy the rules (since we cannot directly use letters outside "koyo"), here's an imaginative take on how it might look:

# Pseudocode for "Hello World!" in KoyoPyck, adhering to the "koyo" letters constraint
# This is more of a creative interpretation rather than executable code

koyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyo
koyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyo
koyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyo
# Assume the above sequence sets the initial cell to the ASCII for 'H'
koyo # Output 'H'
ko # Move to the next cell
koyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyo
koyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyokoyo
# Assume this sequence modifies the next cell to 'e'
koyo # Output 'e'
# ... and so on for each letter in "Hello World!"

# Since specifying exact sequences to reach each letter's ASCII value without using numbers or actual logic is against the provided constraints,
# consider this a conceptual approach to how one might begin to tackle programming with such limitations.

This representation abstractly hints at how you might approach writing in KoyoPyck by creatively using only the allowed characters to simulate programming structures. It's a whimsical blend of constraints that illustrates the challenges of designing and using an esoteric language.

>> No.64495817 [View]
File: 543 KB, 1500x2000, 1691738213153616.jpg [View same] [iqdb] [saucenao] [google]
64495817

This calls for a ______!

>> No.62866278 [View]
File: 543 KB, 1500x2000, scientist joshu.jpg [View same] [iqdb] [saucenao] [google]
62866278

>leading koyote scientists agree "the moon trip is imminent, its not a matter of if, but of when at this point"
-koyolabo news ticker

>> No.59294785 [View]
File: 543 KB, 1500x2000, 1691738213153616.jpg [View same] [iqdb] [saucenao] [google]
59294785

>>59293337
I am on research duty today!

>> No.58735201 [View]
File: 543 KB, 1500x2000, FtbHSD1agAAlZNd.jpg [View same] [iqdb] [saucenao] [google]
58735201

I'm VIJ (very important Joshu)

>> No.58174906 [View]
File: 543 KB, 1500x2000, joshu-kun dokuta.jpg [View same] [iqdb] [saucenao] [google]
58174906

>>58169360
Good idea! I also want clothes, labour laws, human rights and a gun.

>> No.56918253 [View]
File: 543 KB, 1500x2000, 1691738213153616.jpg [View same] [iqdb] [saucenao] [google]
56918253

>>56916026

>> No.56247947 [View]
File: 543 KB, 1500x2000, scientist joshu.jpg [View same] [iqdb] [saucenao] [google]
56247947

>>56247731
do we? he said remixes/edits were fine last time and i liked our combat edit...
if we can't use that one, we should use https://www.youtube.com/watch?v=xCFu0P7GTWw i don't think either mayo or holox are using it and the whole song is about koyo playing and researching with joshu!

>> No.56210779 [View]
File: 543 KB, 1500x2000, 1691738213153616.jpg [View same] [iqdb] [saucenao] [google]
56210779

>> No.55799215 [View]
File: 543 KB, 1500x2000, FtbHSD1agAAlZNd.jpg [View same] [iqdb] [saucenao] [google]
55799215

>>55798487
Rest well, copyjoshu. This weekend is time to shine for you again. You might have to bake and make sure to end threads with Koyo.

>> No.54503807 [View]
File: 543 KB, 1500x2000, FtbHSD1agAAlZNd.jpg [View same] [iqdb] [saucenao] [google]
54503807

>>54503680
I have no faith in Copyjoshu anymore. I quit recharging because there was the need to bake

>> No.54009253 [View]
File: 543 KB, 1500x2000, FtbHSD1agAAlZNd.jpg [View same] [iqdb] [saucenao] [google]
54009253

Today's task for Copyjoshu:
- End thread with Koyo
- Bake new bread
- Koyoyo

>> No.48043884 [View]
File: 543 KB, 1500x2000, joshu-kun dokuta.jpg [View same] [iqdb] [saucenao] [google]
48043884

I'll impregnate this koyote.
This is not a shitpost, just stating a fact.

>> No.47546763 [View]
File: 543 KB, 1500x2000, FtbHSD1agAAlZNd.jpg [View same] [iqdb] [saucenao] [google]
47546763

>>47546633
This would have resulted in a very severe punishment. But it's Koyo and it was allowed to post lewd Koyos. It's your lucky day, koyolewders!

Navigation
View posts[+24][+48][+96]