I think you mean pineapple quality . Bah dum tisss
I think you mean pineapple quality . Bah dum tisss
By using the AST? Do you really not know how languages work? I mean seriously, this is incredibly basic stuff. You don’t need to know the type to jump to the ast node location. Do you think that formatters for dynamic languages need to know the type in order to format them properly? Then why in the world would you need it to know where to jump to in a type definition!?!
Edit: also in the case of Ruby, the entire thing runs on a VM which used to be YARV but I think might have changed recently. So there’s literally bytecode providing all the information needed to run it. I highly recommend reading a book about how the Ruby internals work since you seem to think you understand but it’s quite clear you don’t, or for some reason think “jump to” is this magical thing that requires types.
Jump to declarations or usages has absolutely nothing to do with types so I have no clue why you think type annotations to make jump to useful.
I’m still looking for the glasses to show op is a professional.
Depends on your reference frame
Ligatures make code way easier to read, especially if you’re using lambdas or a language with different comparison operators than “normal”.
It says 2023, not 24. Commenter typo’d. and the top number is correct. Bottom one is probably custom filled out, not based on actual work history.
There’s not even an e after the l
Just use asdf or the alternative that works on windows. You can specify all your languages in the file even for maven or gradle or any thing else as well. No more managing installs.
Just in case you don’t actually know, it’s Looks Good To Me. It’s very commonly used when software devs review each other’s code.
Maybe other Ruby code is better, but people always say Rails is the killer app of Ruby so…
I’ve literally never heard anyone say that…
That only works if you have static type annotations, which seems to be very rare in the Ruby world.
no. it literally works for any ruby code in any project. you do not need static type annotations at all. I can tell you’ve literally never even tried this…
Well, I agree you shouldn’t use Ruby for large projects like Gitlab. But why use it for anything?
because it’s a fantastic scripting language with a runtime that is available on almost every platform on the planet by default (yes most linux distributions include it, compared to something like python which is hardly ever included and if it is it’s 2.x instead of 3.x). It’s also much more readable than bash, python, javascript, etc. so writing a readable (and runnable everywhere) script is dead simple. Writing CLIs with it is also dead simple, while I think Python has a few better libraries for this like Click, Ruby is much more portable than Python (this isn’t my opinion, this is experience from shipping both ruby and python clis for years).
You’re talking about rails. That’s like saying Kotlin is a terrible language because your only exposure to it is with something that decided to use Glassfish Webfly Swarm and Camel.
type annotations
You can literally follow code perfectly fine in an IDE like RubyMine. It actually works much better than Python because Ruby is incredibly consistent in its language design, while Python is an absolute mess (same with JS. Try opening a large Python or JS project in PyCharm or WebStorm).
No clue what you’re talking about with grepping though. Use an IDE like I said and you can literally just “Find all usages” or “Jump to declaration”, etc.
In any case, you shouldn’t be using any of these for large projects like gitlab, so it’s completely inconsequential. Saying something like “Java is terrible, have you ever used it for a CLI? It’s so slow it’s impossible to do anything!” is idiotic because of course it is. That’s not what it’s built for. Ruby is a scripting language. Use it for scripting. It kicks Python’s ass for many reasons, JS is terrible for scripting, and while you can use something like bash or rust, the situation is incredibly painful for both.
None of this has absolutely anything to do with the language design. You’re talking about language design and equating it to being terrible and then saying it’s because you don’t use any sort of tools to actually make it work.
You can count Ruby out immediately. Terrible language.
wow.
They didn’t do anything “with Apple”. The NSA added splitters to fiber optic lines to steal information. Apple never collaborated with the NSA, nor gave them information willingly.
I miss why… he was what everyone really needed, and the industry destroyed him. I haven’t seen anyone like him since.
Also, yeah that’s literally how recycling works… do you think they recycle the labels on glass bottles? no they burn them off to get the glass. Then they make a new bottle, then they put new labels on it. literally doing exactly what you’re saying “isn’t recycling”.
Still, that’s not at all what happens when recycling concrete.
That’s literally not what’s happening. Did you even read the article you posted? Or did you just google, find something that you thought supported your position, then cherry picked that bit out not realizing that the entire article completely disagrees with you?
formatting does depend on the type of variables. Go look at ktfmt’s codebase and come back after you’ve done so…
Lol, nice try with the insult there. I code in Kotlin, my intellisense works just fine. I just think you’re quite ignorant and have no clue what you’re actually talking about.
it gives you an option, just like if it was an interface. Did you actually try this out before commenting? Guessing not. And how often are you naming functions the exact same thing across two different classes without using an interface? And if you were using an interface intellisense would work the exact same way, giving you the option to jump to any of the implementations.
I’m sorry, but you clearly haven’t thought this out, or you’re really quite ignorant as to how intellisense works in all languages (including Ruby, and including statically typed languages).