haskell: “you submitted your math work instead of an essay”
javascript: “this is awful, but at least i can read it anywhere i like”
lisp: “it is not grammatically correct to nest brackets so much”
lua: “your vocabulary is too limited and you have the writing skills of a child”
rust: “omg. your essay is fast, safe, and perfect in every way! A+”
css: “this is beautiful, but it doesnt say anything”
Found the Rust programmer
Ha, such a loser. Real programmers use C.ԥ[��\�q��r��8-߿�ʱT�xd]�UG���S;���v�o������ՠ��N�iYts~fv���@ֿ��Qj�\�Q��“�$�:� �����0��y��G�6�K!{Ȯ������Z�n�˭s�\��ڣ�:J��1���e�k=�${�Z�3�k67D�����K���(�P.��v�0��a�����d���6e?=�v�)���a*��bF���R��4>�˕�G�=��v-�dP��O�3��+A�nw�|ъ�f۽b�oF�I`‘�#��:��̴g>�j:^���O�mu^U�l�A�oI�’�.��j>Dm\����y��2T��8w�D"1������ת«Q����l�”�C�{���*�����% ��A�߸�=t��� �X��m�9R�x��)�a�-���tbL�����Ǣs��d$oMZ��4I1jXD���
Segmentation fault
C#: did you just copy Java’s essay and put your name on it?
COBOL: why it looks like it’s from 16th century?
PHP: I did not ask for a spaghetti recipe
alternative Rust: it’s great, but I asked for an essay, not “🔥 Blazingly fast rust-based EssayOS”
C# is Java in good
C# is Java except from Microsoft, which means it’s designed and much more integrated with Windows. The official .net core even brings telemetry right out of the box. Using C# apps on Linux is a pain, which is very bad considering it’s supposed to be like Java - compile once, run anywhere - except Java actually achieves it.
Also, Minecraft runs on Java. Therefore, C# is useless. Boom, destroyed /s
Untiy games are programmed in C#
So point for Java
Rust v3: “It’s three hours and I’m still compiling dependencies”
EDIT: Also, “What does
Option[Arc[Mutex[BTreeMap[String, Box[RefCell[Box[amp mut F>>>>>>> where F : Fn(T) -> Uin your essay mean?” (srry, I didn’t come up with a better obscure data type, it’s probably gibberish)EDIT2: Lemmy deletes ‘less than’ sign for some damn reason (time to build Lemmy at home?)
I don’t think you should criticize a language that you clearly have not even learnt the syntax of. Dependencies are also a one-time compile and linking just your own program or library does not take very long, and if you’ve ever worked with C languages it’s all the same.
Just because you don’t know how to read a languages syntax doesn’t mean it’s bad, it’s just like how you have to learn anything else. Rust is quite self-explanatory afterwards.
rust: “You just translated someone else’s essay”
Unity: handing me over the essay is going to cost you extra.
Typescript: is this a declaration of war?
Unpopular opinion: Ruby is too widely used, because it’s the least performant language.
Sometimes even for stuff, where performance matters (Asciidoctor).
Ruby’s popularity in the early 10s thanks to Ruby on Rails feels like it happened by accident. The language is hard to read and low performance, but Rails is completely automagic. But this is also the worst thing about rails. You create your app fast, but then maintaining it is expensive because you can’t onboard new developers easily. Even if they’re familiar with rails’ automagicisms, it will take them quite some time to parse what the hell the code is doing.
Meanwhile I seem to recall Ruby’s creator finding the situation of his language being popular because he’d created it as an experiment and never thought it would be used in production grade environments
language is hard to read
for item in array do puts item[:name] endWhew, iterating and working with data in Ruby is so hard. How does anyone read this stuff.
low performance
Ruby is a syntax-sugar-loaded C-wrapper, just like Python and countless other languages that don’t compile straight to machine code. If anything other than C and Rust are slow to you, then sure, maybe Ruby isn’t a good fit for your project (but Crystal might be).
create your app fast
Damn right, I’m two or three times as productive as I ever was in C#/Razor, Java/Spring or kludging through the countless JS boilerplate-heavy web frameworks.
but then maintaining it is expensive
As with any app that grows into something successful and widely used, technical complexity becomes exponential. I’ve found once web applications grow to a certain number of models and controllers, the relationships between them start to grow exponentially as well. This means one small change can ripple throughout your application and have unintended consequences where you least expect.
This is not even remotely a unique problem to Ruby. It’s happened across every project I’ve seen that grows beyond 30 models and a couple of dozen controllers, regardless of language. This is why unit testing is so important.
But, specifically you mentioned you can’t “onboard new developers easily”. I don’t see how. I’ve taken two CS grads straight out of college and had them adding features with tests within a couple of days on Ruby projects. Ruby was designed to be most friendly to humans, not the compiler. If Rails is what is tripping you up, imagine trying to learn a new web framework on top of an even more complicated language than Ruby. I just don’t see this argument at all, from my experiences.
Ruby’s creator finding the situation of his language being popular because he’d created it as an experiment
Pretty sure most any language that was created by an individual and not by BigCorp™ is a feat in and of itself. This speaks more widely to a language’s capabilities and value if it can reach popularity without corporate backing. This argument seems to imply that because of it’s origin, it will always be some kind of experimental toy that was never intended for wide-use.
Meanwhile, Linus Torvalds:
I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones.
Things have to start somewhere, I guess?
I kindly ask you to be more constructive in your criticism of Ruby. It’s a great, powerful language with a low barrier to entry. There’s no reason to spread FUD about it.
for item in array do puts item[:name] endWhat’s with the weird syntax, isn’t idiomatic ruby
array.each do |item| puts item[:name] end(or the shorthand version)?
