[dead]
CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
11–20 of 30 posts
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#12I want to see an Excel frontend to LLVM.
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#13How is the iteration triggered?
I don't think it is really, it must result in a single value, like an aggregate, at least that's what I understood from reading it.
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#14This is impressively cursed.
i now have a word to describe why i found this hilarious, thank you
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#15Wait'l people figure out Excel is thread safe and has no memory leaks. Every one will be rewriting things in that instead of Rust!
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#16Related to this, I recommend Felienne Hermans' talks on Excel as a functional programming language - https://www.youtube.com/watch?v=0yKf8TrLUOw .
Not related to this, excel has just introduced Python support and it's a pretty wild take on it all. You can have Python code in any cell, and all the cells share a namespace for their variables. GL HF everyone.
Ideal: Functional. Reality: Stateful spaghetti
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#17This is impressively cursed.
That's exactly how I felt when I first heard about node.js, and look what happened there.
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#18missed the chance to call this "CeLLVM"
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#19Wait'l people figure out Excel is thread safe and has no memory leaks. Every one will be rewriting things in that instead of Rust!
Too bad it has tons of memory leaks if you run even simple VBA using excel.
Re: CellLVM: A proof-of-concept LLVM to Excel spreadsheet compiler
#20For too long, web browsers have dominated the market for applications that are consumed by document readers, glad to see some competition at last.
Interesting dichotomy! Ultimately I see the browser as a document viewer. As someone who’s trying to kill desktop apps once and for all with the progressive web app revolution, I’m very curious: what excites you about getting this in excel instead of, idk, Excel.com? Do you think there’s a fundamental performance difference that matters?