4 ms·
>I hope Electron/CEF die soon, and people get back to building applications that don't consume hundreds of megabytes of RAM to render a hello world. Yes, so we
by ramesh31 3y ago
>I hope Electron/CEF die soon, and people get back to building applications that don't consume hundreds of megabytes of RAM to render a hello world.
Yes, so we can go back to writing a hundred lines of imperative code to render hello world.
- lylejantzi3rd 3y ago4 in c. 11 in assembly. Not so bad, really. https://i.imgur.com/r2WRnZk.png https://i.imgur.com/r2WRnZk.png
- dijit 3y agoI was about to make a joke about how many lines are required for an electron hello world but it was even more than I expected. 11 for the HTML document template 7 for the boilerplate package.json 3 more for the scripts addition to package.json 3 more for the “devdependencies” 20 for main.js from: https://electronjs.org/docs/latest/tutorial/quick-start https://electronjs.org/docs/latest/tutorial/quick-start A fairer assessment would be C++ with Qt to be honest though.
- SubjectToChange 3y agowrite a hello world application in gtk or qt and see how much assembly you get.
- GhostWhisperer 3y agolet's move the goal posts to doing it in brainfuck since we're at it
- SubjectToChange 3y agoWhat goalpost did I supposedly move?
- 5- 3y agox86_64 assembly, gtk3, 21 lines / 19 instructions build with e.g. gcc hw.s `pkg-config --libs gtk+-3.0` .globl main;main: push %rbx xor %esi, %esi xor %edi, %edi call gtk_init@PLT lea .HW(%rip), %r8 xor %edx, %edx xor %esi, %esi mov $2, %ecx xor %edi, %edi xor %eax, %eax call gtk_message_dialog_new@PLT mov %rax, %rbx mov %rax, %rdi call gtk_dialog_run@PLT mov %rbx, %rdi call gtk_widget_destroy@PLT xor %eax, %eax pop %rbx ret .HW:.string "Hello World!"
- SubjectToChange 3y agoAre you sure you couldn’t wrap that up in another library and just do everything in a single call?
- 5- 3y agoyou jest, but in fact you could. https://wiki.libsdl.org/SDL2/SDL_ShowSimpleMessageBox https://wiki.libsdl.org/SDL2/SDL_ShowSimpleMessageBox
- wiseowise 3y agoThat’s super ironic that you’ve shown screenshot from a web application.
- lylejantzi3rd 3y agoWhy, thank you!
- johnnyworker 3y agoTo the CPU it always boils down to sequences of instructions operating on data, so the syntax sugar put on top has be undone first, the abbreviations have to be unrolled, some way or another. But more importantly it's really not about the lines you code write once, or very few times in comparison -- it's about the computer does any time the application starts up on any machine, or any user does something. Obviously, to an extent. You wouldn't write a thousand lines of code instead of 100 to make something that is already very fast 10% faster. But I certainly would write 10 line instead of 1 if it meant the code is 10 times faster. It's just typing after all.
- ramesh31 3y agoMy point was that CPU cycles mean nothing now. Compared to programmer cycles they are effectively free. So stuff it into RAM and forget about it. Why not? Complexity is bad, and being able to hide it (effectively) is good. I shouldn't be thinking about pointer allocation when building a a text input box for a UI.