We are currently working on new rules for what content should and shouldn't be allowed on this website, and are looking for feedback! See Esolang:2026 topicality proposal to view and give feedback on the current draft.

User:RaiseAfloppaFan3925

From Esolang
Jump to navigation Jump to search
My preferred username is raiseafloppafan3925 however because of the User: prefix, I prefer RaiseAfloppaFan3925. Although I still prefer raiseafloppafan3925

Codeberg | GitHub | Scratch | Sandbox

▼(°v°)▼ ▼(^v^)▼ 3.1415926535897932... ▼(^v^)▼ ▼(°v°)▼

RE-ADD KASANE AND SKILSAW

Time: 17:39 (reload to see the time?) RaiseAfloppaFan3925 【mag-usap tayo (talk)・投稿】【▼(°v°)▼】

Esolangs of the time period: pythOwO and Permission denied

Why not join us on IRC?

YES MATH WORKS NOW

I

On Special:LongPages, Minim is the largest at freaking 270,024 bytes!!! That's around 1/4 the way to a megabyte! Good luck making a page larger than that! (unless you consider JavaScript as an esolang, which in my opinion it absolutely is, since it has a ton of strange stuff and a lot of implementations)

Wouldn't it be cool to have an esolang compiler collection? and for those that can't be compiled because of how they work (like Usernames or Malbolge) then just make in interpreter and the compiler is a bundler instead. Would be cool to have an optimizing compiler too. If it were retargetable as well then we could FINALLY make esolang compilers in themselves, possibly use some of the "less esoteric" languages (like LOLCODE) and INTERCAL (or C-INTERCAL, CLC-INTERCAL, or CLCLC-INTERCAL) for some parts of the compiler, then we can FINALLY write an operating system using LOLCODE and INTERCAL. Don't forget great-grandpa COBOL though.

my esolangs

golden era

flop era

renaissance II

  • 🍡Dango - Now Turing-complete. Isn't it wonderful?

mesmerizer

There are language families now.

???

  • Some language

The Double free family

The Double free family is a language family based on Double free, which itself is based on Malloc. 

       C
       |
 +-----+-----+
 |           |
C++          |
 |     Malloc (None1)
 |           |
 +-----+-----+
       |
  Double free
       |
       +----------------+
       |                |
Mixed allocators        |
                  Use-after-free
  • Double free - What if you turned every undefined behavior into a programming language?
  • Mixed allocators - I actually had to search if that was UB and it is (just can't find it tho)
  • Use-after-free - Forced the other two to fix their logic

Conway's game of life is mesmerizing

esolang of the time period

Time period Esolangs Reason
12 August 2026 – present Conway's Game of Life and Double free The reason is obvious
26 July 2026 – 12 August 2026 Lambda calculus with named variables Obtw why MathML not work at all? It just shows as dollar sign. (λx.x x)(λx.x x) or I guess in better form, SII(SII).
18 July 2026 – 26 July 2026 pythOwO and Permission denied very obvious (see history of Permission denied)
14 June 2026 – 18 July 2026 pythOwO and Bussin (X) i like pythowo and i severely disrespected Bussin (X) when I made the page lol
4 April 2026 – 14 June 2026 pythOwO i like pythowo
26 May 2026 – 4 April 2026 LOLCODE i like lolcode
22 May 2026 – 26 May 2026 pythOwO i love pythowo

sino ba ako

i like raise a floppa and i loved playing it while it was popular (why do you think is my username "raiseafloppafan")

I mostly only edit my user page.

If it wasn't obvious by now, I like Undertale OST 054 - Hotel (and vocaloid)

news?

Some strange questions and thoughts and ideas

  • Is it best to have your personal stuff before the languages or after?
  • C is technically self-modifying since you can make a byte array of instructions (and depending on your platform, change the memory protection of that region to allow executing) then call it using a function pointer. This also means that C++ is self-modifying, and that Rust is self-modifying. This also makes C3 self-modifying.
    • Adding onto this idea, what if you linked a C compiler to your program (say, TinyCC or chibicc) and made an eval function? Then, you could just write this.
#include "raiseafloppafan7741/crt.h"

static const char* program =
"#include <stdio.h>\n"
"void proc_main(){puts(\"Hello, world!\");}";

int main() {
    rcrt_code_t code;
    if (!rcrt_compile(&code, program)) return 1;
    void (*proc_main)() = rcrt_find_proc(&code, "proc_main");
    proc_main();
    rcrt_release_code(&code);
    return 0;
}
  • With the above knowledge in mind, you can maybe make an actual C shell that actually uses C instead of a C imitation!
    • If it works with C# and Roslyn in Unity, it should work for C with a C compiler like chibicc or TinyCC.
  • What exactly makes a language esoteric? If I just make a verbose, COBOL-looking (Common Business Oriented Language, not the COBOL we have here) language, then is that esoteric? And if it is esoteric, then wouldn't that make COBOL esoteric by modern standards? Same with SOL? Maybe esoteric just means not mainstream and very unusual, so COBOL isn't that esoteric compared to GolfScript but is in the same place as LOLCODE?
  • A language that ragebaits you.
  • What if we tried to use a Markov text generator to generate code? Can even run on a cheap microcontroller!
  • If the wiki were to gain a style guide or manual, what would it look like and what if a page doesn't follow it?
  • What if we had an operating system (or a kernel, like Linux or GNU Hurd) that's usable like a normal one (Windows, Linux distros, macOS, RedoxOS, Multics, UNIX, Darwin, TempleOS, ZealOS, etc.) but it's written in esolangs? For example, some numeric computation parts could be written in brainfuck, the assembler-needing parts could use hex1/hex2, and everything else uses variants of INTERCAL, LOLCODE, Piet, and Whitespace designed for bare-metal programming? Also, the parts that cannot be written in esolangs (hex1/hex2 would probably cover them, but) we can just use normal C.
    • The problem is we would need an established ABI for INTERCAL and LOLCODE, plus a compiler for brainfuck and Piet that can generate non-standalone code. Then, we'd need an esolang compiler collection with a unified ABI and dedicated language dialects, since INTERCAL is kinda high-level and LOLCODE was not at all intended for bare metal.
    • Would be pretty cool though.
  • INTERCAL should really have a compiler written in INTERCAL.
  • Adding onto the question of esoteric-ness earlier, what if a language that "isn't esoteric enough" is added to the wiki? Not going to name examples but this has happened thrice to my knowledge. If they are not esoteric at all is obvious, but what if it's kinda esoteric? Like a COBOL-like language?
  • What if we make a compiler collection for esolangs, then we use the esolangs to write the compiler collection? For example, we could have a brainfuck, LOLCODE and INTERCAL compiler, and rewrite the meat of it in INTERCAL and LOLCODE, and use brainfuck for some of the numeric stuff.
    • Adding onto this, some languages can't be compiled and so must be interpreted. (or you can just make an interpreter and the compiler is a bundler, I think I've said this already here) So what do we do about those? (make. a. bundler. like. pyinstaller or something.)
    • Would it be better for the "compiler collection" to use a shared backend like LLVM or how the GNU compilers (C, C++, Ada, Go, Rust, Objective-C, Fortran, Forth, etc.) all target the same IR?
      • I suppose if an IR were to be used, it'd have to be very general-purpose since some languages (cough cough cough cough) can't be compiled "normally" and would require a runtime, so something like LLVM IR would be good.
  • If the Esolang:2026 topicality proposal takes too long, will it be renamed to Esolang:2026-2027 topicality proposal?
  • What if we made compilers for LOLCODE and INTERCAL? We could have dialects of LOLCODE and INTERCAL (or C-INTERCAL, CLC-INTERCAL, or CLCLC-INTERCAL) with FFI functionality so we could have library bindings for them!
    • I know that LOLCODE has that ability, but it's an interpreter. I would like to be able to write an operating system kernel in LOLCODE.
  • What if we use LOLCODE's lollm for an IRC bot in #esolangs?
  • Is there anyone who has been actively working on an esolang compiler collection? If so, how's it going? Something I'd like to ask is, is it more of a collection of different separate esolang compilers or is it like GCC where they are all unified?
  • What would actually happen if you somehow did eat 562 metric tons of air? Obviously you probably wouldn't start floating up into the sky like that, but I still wonder what would happen. (other than the obvious "you die")

observation about page size

The gap between Minim and the second largest page, SELECT./Hello World, is around 7,000 bytes. Then the gap between that (SELECT./Hello World) and the third largest page, PRINT/Concept Interpreter, is around 70,000 to 80,000 bytes. Then the first page below 100,000 bytes is BunnyBell at place 14, with the first below 75,000 being UserEdited in 23rd place. First one below 50,000 is Siterip at 44th place, and the first one below 25,000 being Computable at 157th place. First one below 10,000 bytes is Parse this sic: Revised at 805th place. Below 5,000 is Rail (data structure) at 2,247th place. Below or equal to 2,500 bytes are Remove Line Numbers, Total LISTP, and Container starting at 4,555th place. Below 1,250 bytes is JS-- at 6,827th place. Below 500 bytes are ™¥÷¶÷™÷ ~¦¢\¶\ ¶^\, Halting problem (language) and Deutsch, starting at 8,510th place. 250 bytes is Not a brainfuck derivative at 9,018th place, and around 300 places later are the zero-sized pages.

Based on this, we can hypothesize that the distribution of pages is most heavily concentrated in the range of 500 bytes to 10,000 bytes, with the density in that range being shifted more to the lower end somewhere between 5,000 and 1,250 bytes.

TODO: proper data analysis

CLCLC-INTERCAL is a documentary about rizzlers set in sigma town
Retrieved from "https://esolangs.org/w/index.php?title=User:RaiseAfloppaFan3925&oldid=189393"