they rewrote c parts of ffmpeg in rust and it was 35% slower
@Inginsub They didn't even rewrite it. Someone from the ffmpeg team claimed they just transpiled it, probably with LLMs. And then made a bounty for figuring out why it's slower, because according to the Rust "porters" it should have been much faster.
@dcc @Inginsub This angers the "No memory leaks in Rust" evangelists: https://doc.rust-lang.org/std/mem/fn.forget.html
@dcc @Inginsub I also like that the documentation says that you have to write unsafe code in some specific ways to ensure that it won't leak and that it will even work.
Meanwhile in C land you malloc and then you free when you need. Or in C++ land, you can use smart pointers and do all the memory work in constructors/destructors and everything will get magically cleaned up. No need for memory management in actual program logic when its done properly.
Meanwhile in C land you malloc and then you free when you need. Or in C++ land, you can use smart pointers and do all the memory work in constructors/destructors and everything will get magically cleaned up. No need for memory management in actual program logic when its done properly.
@Suiseiseki @Inginsub @dcc @phnt Sounds even less portable.
Looks like it is: https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html
Looks like it even says it's less portable.
Looks like it is: https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html
Looks like it even says it's less portable.
@dcc @Inginsub @phnt @Suiseiseki Even 
doesn't use HURD. Last I heard, he was suggesting Gentoo or Trisquel. If you're posting from a HURD machine, let me know. In the mean time, this post was written on a full GPL system, built with God's own kencc. 
doesn't use HURD. Last I heard, he was suggesting Gentoo or Trisquel. If you're posting from a HURD machine, let me know. In the mean time, this post was written on a full GPL system, built with God's own kencc.
+bonifartius 𒂼𒄄
@p @dcc @Inginsub @phnt @Suiseiseki joe has an emacs style config and is made for porting 💁
@bonifartius @dcc @Inginsub @phnt @Suiseiseki acme has no configuration files. If you want it to do something different, the source code is right in /sys/src/cmd/acme and is only 13k lines and it only takes 30 seconds to find the behavior you want to change.
@bonifartius @p @dcc @Inginsub @Suiseiseki I like acme as an editor. It has interesting ideas just like many aspects of Plan 9. It's probably the only "IDE" I don't hate using.
BUT the same thing kills Plan 9 without hacking on it a lot, which is something I'm planning on doing, is the mouse-centric UI kills acme for me. I already have issues with my wrist and constantly switching from my mouse to keyboard and back hurts after like an hour. Which is why I mainly use nvim for everything and only use editors that support some kind of vi-mode.
BUT the same thing kills Plan 9 without hacking on it a lot, which is something I'm planning on doing, is the mouse-centric UI kills acme for me. I already have issues with my wrist and constantly switching from my mouse to keyboard and back hurts after like an hour. Which is why I mainly use nvim for everything and only use editors that support some kind of vi-mode.
> unfortunately the whole acme idea works best on a real plan 9, not on unix.
Well, /sys is something dumber on non-Plan 9 machines.
I just use ed and nvi or sometimes busybox's vi.