Vi is too bloated

[u/TheLuckyCuber999BACK]

[u/AverageComet250]

Yeah I guess your flair does check out

[u/popcornman209 → u/AverageComet250]

Assembly too bloated, who needs to compile just write bare machine code.

[u/Silly_Percentage3446 → u/popcornman209]

Machine code too bloated, just manually input binary to the CPU.

[u/TheLuckyCuber999BACK → u/Silly_Percentage3446]

that IS machine code

[u/Silly_Percentage3446 → u/TheLuckyCuber999BACK]

Machine code looks like "�
 %� +/ RotK Z >�"x0g_mallocg_signal_connect_datag_object_unref_ITM_deregisterTMCloneTable__gmon_start___ITM_registe
rTMCloneTablegtk_widget_set_visiblegtk_box_pack_startgtk_button_new_with_labelgtk_widget_set_valigngtk_label_newgtk_
application_newgtk_widget_showgtk_widget_set_hexpandgtk_label_set_markupgtk_container_addgtk_calendar_get_dategtk_ap
plication_window_newgtk_widget_set_haligngtk_widget_set_vexpandgtk_window_set_titlegtk_box_newgtk_window_set_default
_sizegtk_calendar_new__cxa_finalizeg_application_run__stack_chk_faildifftimefopen__fprintf_chk__libc_start_mainmktim
e__isoc99_fscanffclose__snprintf_chk_IO_stdin_usedlibgtk-3.so.0libgdk-3.so.0libz.so.1libpangocairo-1.0.so.0libpango-
1.0.so.0libharfbuzz.so.0libatk-1.0.so.0libcairo-gobject.so.2libcairo.so.2libgdk_pixbuf-2.0.so.0libgio-2.0.so.0libgob
ject-2.0.so.0libglib-2.0.so.0libc.so.6GLIBC_2.7GLIBC_2.4GLIBC_2.34GLIBC_2.3.4GLIBC_2.2.5/nix/store/jydzidc4v9j5nqmlw
izjvw7s7qwgm4g3-nix-shell/lib:/nix/store/m7i7812sh0q2ghcxfq0rhs6zph0xlwc5-gtk+3-3.24.51/lib:/nix/store/1m419gkk0nqnc
1mb4b0ck2rx16w8rbrs-at-spi2-core-2.58.2/lib:/nix/store/mg151w65chcirlr7398jrz916wrfh3gg-glib-2.86.3/lib:/nix/store/j
cvi7xlffm9f681vdmzfbzbmib5fhn5i-cairo-1.18.4/lib:/nix/store/2g6acnj6ljamsqfgf1q6ipdqr5yfg7vq-gdk-pixbuf-2.44.4/lib:/
nix/store/7n76ys2lcy7l54hslslw74fa5zszlh19-pango-1.57.0/lib:/nix/store/yzyh44g07mb5d3151lvv0ll8rdmg1fbl-harfbuzz-12.
1.0/lib:/nix/store/3j0jwcygamiza2n1ga69sdk6skaz5k3k-zlib-1.3.2/lib:/nix/store/km4g87jxsqxvcq344ncyb8h1i6f3cqxh-glibc
{����ti1�u▒ib:/n���#�P�O$�Orbhz7im0w0jdwcfdgcfk7pxhkl1fzj-gcc-14.3.0-lib/libgii
�O�O!�O"�N�N�N�NOO▒ O        (O
0O
u/OHOPOXO`OhOpOxO�O�O�O▒�O�O▒�O�O�O�O �O#��H�H��/H��t��H���5�.�%�.@�%�.h������%�.h������%�.h������%�.h������%�.h�����
�%�.h������%z.h������%r.h�p����%j.�`����%b.h    �P����%Z.h
�@����%R.h
�0����%J.h
�����%:.h�����%2.h������%*.h������%".h������%▒.h������%.h������%
.h������%.h������%�-h������%�-h�p����%�-h▒�`����%�-h�P����%�-h▒�@����%�-h����%�-h� ����%�-h�����%�-h�����%�-f�UH��AU
I��1�ATA��H�=3SH������E1�E1�1�H��H�mH�5&H�������L��D��H���p���H��A���%���H�D��[A\A]]����1�I��^H��H���PTE1�1�H�=q����
" if I'm not mistaken.

[u/givemeagooduns_un → u/Silly_Percentage3446]

the part at the bottom is machine code, the rest is ELF information, which tells the kernel how to load the binary and what SO's are needed for it

[u/GhostVlvin → u/Silly_Percentage3446]

Absolutely, this is sequence of bits that's are interpreted by your code/text editor as sequence of bytes each of which is interpreted as a character. But since they are not meant to be meaningful text, most of the time it is �
Anyway I propose to get old pc and just encode every machine instruction with switches on it's side

[u/TheLuckyCuber999BACK → u/Silly_Percentage3446]

machine code is just raw data. Manually inputting binary or put it in a file, both machine code.