Conversation
Notices
-
Of course they'll probably try to redo everything in Rust.
cc: @p
- matrix07012 :thotpatrol: :cunnyEmpire: likes this.
-
@ins0mniak @p There's a very common misconception that "all code written in Rust is correct" when in reality, the only people who bother writing Rust will also take the time to get it right. The only reason Rust has even been able to stick around as a language is because of autistic trannies who do it for free.
Forcing Rust on paid developers is a recipe for disaster.
-
@ins0mniak @p @vic
So it's just backdoored C.
-
@vic @p Absolutely.
The NSA has been pushing the White House to push it as a "safer" language.
-
@p @ins0mniak @lanodan @vic
I wonder if there were any successful attempts in creating a successor for C that is reasonably simple 🤔
-
@lonelyowl13 @p @ins0mniak @vic Plan9 C :DDD:
I'd more put Rust as a C++ successor, but well most people can't do the difference between C and C++ while for me it's kind of like not doing the difference between Unix Shell and Perl.
And well I don't think "successor" really makes sense in (programming) languages.
Like is Ruby a successor to Perl? Depends on the person/projects really, I guess do things the weird way so Perl ended up being a successor to Python3 due to me wanting a more boring language.
Meaning you could pick Fortran as a C successor.
But it could be D, or Zig, or Hare, or Forth, or Go, …
-
@lanodan @ins0mniak @vic
> I wish Rust would crumble under it's own weight but sadly software culture doesn't seems to work this way.
"Look, the big ball of mud *must* be important. Look how big it is!"
-
@p @ins0mniak @vic Best about Rust is trivial programs which could often just be purely ISO C, not even POSIX, then end up with absolute hundreds of direct dependencies (of course lot of them vendoring non-Rust code because they can't do package management) upon a Rust rewrite.
It's not just mere JS fetishism, it's NPM fetishism. And I feel like it's more like enterprise Java than C++.
Want to bootstrap Rust from source? Hope you like dealing with 5+ versions of LLVM…
I wish Rust would crumble under it's own weight but sadly software culture doesn't seems to work this way.
-
@vic @ins0mniak
i_do_not_care_for_rust.png
-
@churkia @lonelyowl13 @get @p @ins0mniak @lanodan @vic Beat the cum out of him.
-
@lanodan @lonelyowl13 @p @ins0mniak @vic ruby is the smalltalk successor
-
@get @lonelyowl13 @p @ins0mniak @lanodan @vic i will beat u to death
-
@Forestofenchantment @lonelyowl13 @get @p @ins0mniak @lanodan @vic u r DUMB! export pleroma db objects table as csv and contact me for furhther details 😠😠😠😠!!!!!!!!!!
-
@Yoruka @ins0mniak Only if your model of writing a makefile is based on the GNU toolchain and autotools. Ten or fifteen lines of build targets versus an entire terrible rubygems-like monster, and then dependency hell? I mean, I had to uninstall Rust and reinstall it because the new version couldn't cope with the old version being installed at build-time and if I didn't have the new version, cargo fucked itself, and if I couldn't get cargo to stop fucking itself, then I couldn't get Firefox to build. It's like an ouroboros combined with the human centipede.
-
@p @ins0mniak its definitely more convenient then manually writing makefiles and manually installing libraries
-
@Yoruka @ins0mniak
> its cargo system which is very convenient
I must have been using a different cargo system for Rust.
-
@ins0mniak @p the only thing I'd credit rust for is its cargo system which is very convenient but still nothing new...
-
@p @ins0mniak I really don't like writing makefile, cargo always worked fine for me. But I guess it is bloated shit yes.
ins0mniak
vic
w0rm
Haelwenn /элвэн/ :triskell:
Forest of Enchantment
You Get Glee
夜化
All ０７６萌ＳＮＳ content and data are available under the 