movfuscator
sycamore
movfuscator | sycamore | |
---|---|---|
82 | 70 | |
9,013 | 2,681 | |
- | 2.0% | |
0.0 | 7.3 | |
about 1 year ago | 18 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
movfuscator
- M/o/Vfuscator: The single instruction C compiler (2020)
-
controversialOpinion
Everything can be reduced to assignments. https://github.com/xoreaxeaxeax/movfuscator
- M/o/Vfuscator: The single instruction C compiler
-
Subtraction Is Functionally Complete
However, the movfuscator as implemented does still require a sigaction(2) syscall to set up a signal handler, under the justifications that "it is not actually part of the program" and that "if we were in ring 0, we wouldn't need help from the kernel" [0]. However, the latter part seems a little dubious to me: without the help of the kernel running non-MOV instructions, you'd never be able to escape from 16-bit real mode into 32-bit protected mode, since you wouldn't be able to load a valid GDT with the LGDT instruction (as far as I am aware).
[0] https://github.com/xoreaxeaxeax/movfuscator/blob/90a49f31219...
-
The bigger the interface, the weaker the abstraction
I _think_ the idea is thinking of an "interface" as "something that you use as a way to interact with something from outside an abstraction". I'd summarize their argument as reasoning that if the goal of an abstraction is to avoid having to care about the internal details of something, an interface is a way to expose a subset of ways to interact with it, and the more you expand it, the more it exposes the internals of the thing being abstracted. I don't think they necessarily mean this only in terms of programming, but you could apply this argument to a programming language interface; if you use an interface for interacting with something instead of its direct functionality, each additional method you add to the interface exposes more details of the inner value, which makes it less of an abstraction.
Assuming my interpretation is correct, I'm not sure I totally buy this argument because there doesn't seem to be an obvious way to define the "size" of an interface where it holds true. The naive way to define the size would be number of methods, but I'd argue that methods can vary so much in terms of the amount of cognitive overhead they "expose" to the user that it's not very meaningful. Consider the Movfuscator compiler[0], which compiles code into binaries only using MOV x86 instructions because it happens to be Turing complete; as complex as it might be to learn x86 assembly as a whole and start writing programs directly in it, I'm dubious that trying to do so only with MOV would somehow be easier. Put another way, an x86 instruction set that only contains the MOV instruction is not a "stronger" abstraction than the actual one because it _introduces_ complexity that doesn't exist in the original. Does adding an ADD instruction alongside MOV increase the strength of the abstraction, or weaken it? I don't think there's an answer that we'd immediately all agree on for this sort of thing.
Ultimately, I think trying to measure interfaces through the number of methods they expose is similar to trying to measure code by the number of lines in it; while there are some extreme cases where we'd likely all agree (e.g. for a fizzbuzz implementation, having 10 lines of code is probably better than thousands of lines of code[1]), we can't really come up with a good objective metric because the "target" number is based on the complexity of what you're trying to define, and we don't have a way of quantifying that complexity. I think the ideas here are still super interesting though, not because they have definitive right or wrong answers, but because thinking about stuff like this overall improves one's ability to write good software for usage by other programmers.
[0]: https://github.com/xoreaxeaxeax/movfuscator
- The M/o/Vfuscator contains a complete mov-only floating point emulator. Since it is approximately 500,000 instructions, you must explicitly link to it if you need it
-
Can the RISC instruction set be simplified even further?
The mov instruction in x86-64 is Turing complete. Someone even made a C compiler using only mov.
-
This is definitely not the best way to initialize an array
Are you sure they didn't use the MOVFUSCATOR?
-
Can every function defined in popular libraries/frameworks be traced back to primitive data types, conditional statements and loops?
Yep. In fact you can reduce everything to just one simple assembly instruction.
- I am going to learn goto
sycamore
-
Building a Rust app with Perseus
Perseus is a fast frontend web development framework for Rust with built-in support for reactivity using Sycamore, server-side rendering, and much more. Sycamore is a frontend library that allows you to build interactive user interfaces with Rust. I’d say that Perseus is to Sycamore as Next.js is to React, so it’ll be helpful for you to have a fair understanding of Sycamore before jumping into using Perseus — although it’s not necessary to follow along in this article.
-
Announcing samba – a Rust full-stack assistant for ballroom dancers
Now, I considered whether to spend more time fixing everything that now failed in sycamore 0.9. But there are major changes ahead which would require yet another major refactoring, to the point where I am not sure whether it would not be more of a rewrite than a refactoring, given my previous experiences with sycamore.
-
Rust Tauri (inspired by Electron) 1.3: Getting started to build apps
Sycamore.
-
Want a web app to respond to local file changes. Is Tauri the solution here?
Sycamore, Yew, or Seed if you want a full-stack solution. (Or Leptos if you want something that's faster but less mature.)
-
Hey Rustaceans! Got a question? Ask here (16/2023)!
There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.
-
Sycamore -a library for creating web apps in Rust and WebAssembly
Sycamore is a reactive library for creating web apps in Rust and WebAssembly. https://github.com/sycamore-rs/sycamore
-
Yew | What’s been your experience?
I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.
-
Rust tech stack
If you want to do fullstack/SPA stuff, check out Sycamore, Seed, and Yew.
-
rust web dev??
If you want to do front-end SPA development, take a look at Yew, Seed, or Sycamore.
-
How Discord Stores Trillions of Messages
I have written a front-end (website) application in Rust that is used internally in production. I wouldn't recommend to use something like sycamore, leptos, dioxus, yew for you next puplic web-app now but i can absolutely see how this is used in the future as those libs mature.
What are some alternatives?
demovfuscator - A work-in-progress deobfuscator for movfuscated binaries [Moved to: https://github.com/leetonidas/demovfuscator]
yew - Rust / Wasm framework for creating reliable and efficient web applications
obfuscator
dioxus - Fullstack GUI library for web, desktop, mobile, and more.
Molebox - MoleBox lets you convert your application into an all-sufficient stand-alone executable, containing everything needed: components, media assets, registry entries.
leptos - Build fast web applications with Rust.
onelinerizer - Shamelessly convert any Python 2 script into a terrible single line of code
perseus - A state-driven web development framework for Rust with full support for server-side rendering and static generation.
sectorlisp - Bootstrapping LISP in a Boot Sector
rust-dominator - Zero-cost ultra-high-performance declarative DOM library using FRP signals for Rust!
Unity-game-hacking - A guide for hacking unity games
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.