m455
learning elixir! though not using the official mix tool, just fuckin with a single file lol. my first time using a language that is forcing me to put everything into modules and stuff lol
... okay i should go to bed. this is what happens when i go to the gym too late at night lol
edit: woops forgot to remove that extra trim after finding out that split can do it too
tech? no! man, see...
@m455 @dozens I wonder if part of the reason the syntax clicks is that the creator of elixir spent a lot of time maintaining rails and suffering from the way that ruby tries to be cute but ends up just being ambiguous and confusing, so he knew what not to do
there's still more cleverness there than I would like, but for a non-lisp it's much better than most
m455
@dozens i really like elixir
dozens
@m455 i bet you will really like elixir
tech? no! man, see...
@m455 @dozens yeah, method resolution rolls up to the class normally, so the method is only ever *stored* once, but there are a lot of places that the method can be overridden, so the method that comes from the class isn't always the one that runs
the problem is resolving which method should actually be called is a lot more complex than just "look up a field in a data structure" so yeah, that's a big part of why ruby is one of the slowest languages around
m455
@technomancy @dozens like i assume there are some kind of optimizations or type checking to see if a method can be called from an object and its not all just duplicate stuff stored in a million things. just my brain was trying to think too much with it. i just like being able to see what things return easily and deal with that as data
m455
@technomancy @dozens i honestly couldnt figure out ruby without tripping over myself several times. an example was like ... how the fuck do you get a length of an array in ruby, and then it clicked after struggling and realizing that everything is an object so i need to call a method from things, them my brain started to wander, wondering how many things store methods and how much extra memory and stuff is taken from having duplicate methods and stuff, and you can see where this is going lol
tech? no! man, see...
@m455 @dozens it's soooooo complicated: https://www.ruby-forum.com/t/method-name-resolution/223217
all this just to support inheritance, which is like ... I've only once ever run into a situation where inheritance was a good fit for the problem at hand, and even then the inheritance wasn't based around classes
you could just ... not do any of that, and you'd have a better language
m455
@technomancy @dozens oh right woops uh i just realized what i said might not make sense ( too lazy to check what i said again lol), i keep forgetting you make a class with methods and then make instances of that class by making objects of that class.
just never knew that the methods actually resolve to the class and not the object itself when doing the lookup! makes sense tho, because that would be a lot of extra duplicates
m455
@technomancy @dozens thats wild, i could see like memory hackers being able to fuck around and make objects call methods they werent designed to run then if the methods arent technically associated with the objects, just the object classes or some shit
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.