update @ Sun 9 Jan 15:17:46 EET 2022

This commit is contained in:
Ari Archer 2022-01-09 15:17:46 +02:00
parent a340fbb343
commit 51edd575f8

View file

@ -1,132 +1,184 @@
<!DOCTYPE html> <!DOCTYPE html>
<html lang="en"> <html lang="en">
<head> <head>
<meta charset="utf-8"/> <meta charset="utf-8" />
<meta content="IE=edge" http-equiv="X-UA-Compatible"/> <meta content="IE=edge" http-equiv="X-UA-Compatible" />
<meta content="width=device-width, initial-scale=1.0" name="viewport"/> <meta content="width=device-width, initial-scale=1.0" name="viewport" />
<title> <title>Ari::web -&gt; Blog</title>
Ari::web -&gt; Blog <meta
</title> content="website webdev linux programming ari terminal dark blog javascript opensource free"
<meta content="website webdev linux programming ari terminal dark blog javascript opensource free" name="keywords"/> name="keywords"
<meta content="Blog on 2021-11-07 05:03:56 EET - Rust bad" name="description"/> />
<meta content="follow" name="robots"/> <meta
</head> content="Blog on 2021-11-07 05:03:56 EET - Rust bad"
<body> name="description"
<div> />
<h1> <meta content="follow" name="robots" />
Rust bad </head>
</h1> <body>
<p> <div>
2021-11-07 05:03:56 EET | <h1>Rust bad</h1>
<a href=".."> <p>
back 2021-11-07 05:03:56 EET |
</a> <a href=".."> back </a>
| |
<a href="/"> <a href="/"> home </a>
home |
</a> <a href="/git"> git </a>
| </p>
<a href="/git"> <hr />
git <h2>Rust is solving an issue nobody has</h2>
</a> <p>
</p> Ah yes, memory safety, the only thing people use bruhst for, like it's
<hr/> so important to them, first up if you're allocating a lot of memory you
<h2> shouldn't be programming either way, allocating memory is slow and heavy
Rust is solving an issue nobody has so you should not do it if you can get away of not doing it, like ofc
</h2> it's necessary to allocate memory in
<p> <strong> some cases </strong>
Ah yes, memory safety, the only thing people use bruhst for, like it's so important to them, , but to unnecessarily allocate it and FORGET TO FREE IT is just on
first up if you're allocating a lot of memory you shouldn't be programming either way, allocating memory you...
is slow and heavy so you should not do it if you can get away of not doing it, like ofc it's necessary </p>
to allocate memory in <h2>Rust is painful to compile</h2>
<strong> <p>
some cases Rust is horribly heavy and slow to compile so if people start writing
</strong> software only in rust it will become a mess for users who compile their
, but to unnecessarily allocate it and FORGET TO FREE IT is just on you... software and it's already happening for me for example, I'm on gentoo
</p> and every time I compile rust I just want to kill myself because of how
<h2> painful and slow it is. Just bad...
Rust is painful to compile </p>
</h2> <h2>Less availability</h2>
<p> <p>
Rust is horribly heavy and slow to compile so if people start writing software only in rust Rust binaries are slower and larger so making the availability to people
it will become a mess for users who compile their software and it's already happening for me for example, bad. And for people who have lower spec computers and they still compile
I'm on gentoo and every time I compile rust I just want to kill myself because of how painful and slow it is. everything this will also make the compiling process painful so they
Just bad... might give up and not use your software, again making your software less
</p> available to less people. Even though it can make the development builds
<h2> faster, at the end it's the end user who's experience is more important.
Less availability </p>
</h2> <h2>Horrible ass syntax</h2>
<p> <p>
Rust binaries are slower and larger so making the availability to people bad. Rust's syntax is horrible and not a lot of developers know it and not a
And for people who have lower spec computers and they still compile everything this will also lot of jobs require it, so learning rust is just torturing with the
make the compiling process painful so they might give up and not use your software, again weird ass, shit(tm)++ syntax:
making your software less available to less people. Even though it can make the development builds faster, </p>
at the end it's the end user who's experience is more important. <p>
</p> <code>
<h2> fn~~~~~~~~~~~!@@!!!!! so(jauhg::sfduf!!!68768Jijuhe:;@@@@@@
Horrible ass syntax ufuheuwifh) { using
</h2> s:s:e:frg::gger:fwuhf::jfewhe::fweuhwueih:::fiehu9wehf::fhuewhf:::fiuuwehf::fhuwehufhwe::ewiuhfwuie;
<p> kfhuerh::fiufu::yufewy:fwgiwfuif::owiffhoiwefh::fehuhyew::wfiuguifg::3hw8w
Rust's syntax is horrible and not a lot of developers know it and not a lot of jobs require it, so &lt;&lt; "r23rj4r" &lt;&lt; 'wfefwhuwfhefhwe9fwhdhuhfweidu';;;;;;
learning rust is just torturing with the weird ass, shit(tm)++ syntax: 43twrugyj9ifj0fjfew(())))(()()()()()()()()()))()()()::g9hgergheeegu; }
</p> </code>
<p> </p>
<code> <p>
fn~~~~~~~~~~~!@@!!!!! so(jauhg::sfduf!!!68768Jijuhe:;@@@@@@ ufuheuwifh) { I wanted to exaggerate, but this actually feels and looks a bit like
using s:s:e:frg::gger:fwuhf::jfewhe::fweuhwueih:::fiehu9wehf::fhuewhf:::fiuuwehf::fhuwehufhwe::ewiuhfwuie; rust code LOL... Even though this also resembles C++ a bit, C++ is not
kfhuerh::fiufu::yufewy:fwgiwfuif::owiffhoiwefh::fehuhyew::wfiuguifg::3hw8w &lt;&lt; "r23rj4r" &lt;&lt; 'wfefwhuwfhefhwe9fwhdhuhfweidu';;;;;; as horrible as this.
43twrugyj9ifj0fjfew(())))(()()()()()()()()()))()()()::g9hgergheeegu; </p>
} <h2>Buggy</h2>
</code> <p>
</p> Even though rust has come a good way since like two years back it's
<p> still buggy and for production you can kinda expect it to break in one
I wanted to exaggerate, but this actually feels and looks a bit like rust code LOL... way or another.
Even though this also resembles C++ a bit, C++ is not as horrible as this. </p>
</p> <h2>In some ways, bad debugging experience</h2>
<h2> <p>
Buggy Disassembling rust binaries is a pain, so you lose some privilege to
</h2> debugging rust code, though that's just my experience, complete mess...
<p> </p>
Even though rust has come a good way since like two years back it's still buggy and for production <h2>Rust causes bloated software</h2>
you can kinda expect it to break in one way or another. <p>
</p> Rust projects usually require 3908948093 crates, even the simplest
<h2> projects require a lot of them so rust executables become large and
In some ways, bad debugging experience painful to compile quick. Rust dependencies also are a pain to manage
</h2> and you just get a LARGEEEEEEEEEEEEEEEEEEEEEEEEEEE cargo.toml file so
<p> again making it a pain to download for people with worse hardware, shit
Disassembling rust binaries is a pain, so you lose some privilege to debugging rust code, though internet and/or low storage.
that's just my experience, complete mess... </p>
</p> <h2>Rust has a bad community</h2>
<h2> <p>
Rust causes bloated software Rust's community consists of idiots calling C cringe, unsafe, slow and
</h2> in general bad and people who complain about CMake causing C software to
<p> be bloated when it's nowhere near as bloated as cargo and in general
Rust projects usually require 3908948093 crates, even the simplest projects require a lot of them rust. Sure they have good docs, but that's everything good about it...
so rust executables become large and painful to compile quick. </p>
Rust dependencies also are a pain to manage and you just get a LARGEEEEEEEEEEEEEEEEEEEEEEEEEEE cargo.toml file <p>
so again making it a pain to download for people with worse hardware, shit internet and/or low storage. Every project includes at least one rocket emoji and description is
</p> something like "XXX is a blazingly fast, configurable, lightweight
<h2> #rustrewrite, it introduces 69 new features and it's very very fast
Rust has a bad community trust me"
</h2> </p>
<p> <h2>More downsides than upsides</h2>
Rust's community consists of idiots calling C cringe, unsafe, slow and in general bad and people who complain <p>
about CMake causing C software to be bloated when it's nowhere near as bloated as cargo and in general People call rust good because it's modern and has useless memory safety
rust. Sure they have good docs, but that's everything good about it... when overlooking other flaws I mentioned before for example being
</p> bloated, less available and being slow to compile, making rust
<p> ultimately useless
Every project includes at least one rocket emoji and description is something like "XXX is a blazingly fast, </p>
configurable, lightweight #rustrewrite, it introduces 69 new features and it's very very fast trust me" <hr />
</p> <i>Updated points</i>
<h2> <hr />
More downsides than upsides <h2>Bad library support</h2>
</h2> <p>
<p> Even though rust has a bunch of libraries, it's missing a lot of them
People call rust good because it's modern and has useless memory safety when overlooking other and doing everything from scratch is a pain. Its libraries suck a lot
flaws I mentioned before for example being bloated, less available and being slow to compile, and most that are out there are buggy.
making rust ultimately useless </p>
</p> <h2>Bad IDE support</h2>
</div> <p>
</body> Rust with its popularity is getting more editing support, but either way
on a bunch of editors rust is not supported as language.
</p>
<h2>Overly backed by companies</h2>
<p>
I don't like companies and they usually ruin everything,
I see rust's future as a pile of garbage...
</p>
<hr />
<p>
Now, rust community, I know y'all don't like me, but please, I know
you're reading this, explain to me why rust is so good, make an issue on
github or something. I keep asking y'all and y'all just keep ignoring me
which is kinda stupid when you are trying to prove a point.
</p>
<br/>
<p>And some points y'all pointed out:</p>
<ul>
<li>"Ah yes, memory safety, such useless thing" (sarcasticly)</li>
<li>"Bad syntax, lisp totally does it better"</li>
<li>
"Obviously we call rust good because of memory safety and modernism"
</li>
</ul>
<i>tbh nothing else? fr?</i>
<br/>
<br/>
<p>
To debunk stuff y'all said. Memeory safety being useless is true imo,
most projects are not some high scale enterprise apps which are stupidly
made by allocating memory left and right and it being not closely
monitored. and the ones which are lower-scale usually don't allocate a
bunch of memory always and not free it, but if they do, just to make
sure, memory safety is good. A lot of people seem to think that when
programming in C you have to code like mallocing memory for everything
all the time. And bad syntax, yes, its syntax is bad worse than C++, I
can't believe how badly designed it is. And again, yes, you call it good
because of those things while ignoring all the downsides of it, you just
want to be "a part of a trend" and overly focused on modernism.
</p>
<br/>
<p>
Also to that one guy who said I'm a moron because I use gentoo,
sure, at least I don't need 1662 crates for a hello world <3
</p>
</div>
</body>
</html> </html>
<!-- this is automatically generated by scripts/add_blog --> <!-- this is automatically generated by scripts/add_blog -->