One of the reasons might be that they realized that the absense of an official LSP for Kotlin will hinder its wide adoption by new developers who want to try Kotlin but don't want to move away from their favorite IDEs.
>I know it's a difficult spot because such effort will also indirectly compete with their main product which is an IDE, so I'm not very optimistic it'll last.
I would say this if this step was taking early while Kotlin is still a new language in the market, but I think their late decision to develop an official LSP for Kotlin is because of reasons you just mentioned, but maybe they changed their minds because they saw other benifits including a wide adoption of Kotlin.
This is horrible for people who learn languages using TV Shows and Movies. One of the most frustrating things I've encountered while learning German is the "paraphrase" thing, it makes practicing listening very hard, because my purpose wasn't to understand what was being said, but rather familiarizing my ear with spoken German.
So, knowing exactly the words being said is of utter importance.
Why did you assume that we would all work with just one tab?!
In my case, I am currently learning Go at the moment. So, a learning session will contain at least one browser tab for the website I'm using, a window for VS Code, and a third browser tab in case I need to look something up.
Just like "habit stacking" worked for the author, maybe you should try what might be called "interests or hobby stacking". Let them do what they love after completing something that they don't love doing.
- Be an active reader. Open to the page you need to read, get out some paper and a pencil.
- If notation is defined, make sure you know what it means. Your pencil and paper should come in handy here.
- Look up the definitions of all words that you do not understand.
- Read the statement of the theorem, corollary, lemma, or example. Can you work through the details of the proof by yourself? Try. Even if it feels like you are making no progress, you are gaining a better understanding of what you need to do.
- Once you truly understand the statement of what is to be proven, you may still have trouble reading the proof—even someone’s well-written, clear, concise proof. Try to get the overall idea of what the author is doing, and then try (again) to prove it yourself.
- If a theorem is quoted in a proof and you don’t know what it is, look it up. Check that the hypotheses apply, and that the conclusion is what the author claims it is.
- Don’t expect to go quickly. You need to get the overall idea as well as the details. This takes time.
- If you are reading a fairly long proof, try doing it in bits.
- If you can’t figure out what the author is doing, try to (if appropriate) choose a more specific case and work through the argument for that specific case.
- Draw a picture, if appropriate.
- If you really can’t get it, do what comes naturally—put the book down and come back to it later.
- You might want to take this time to read similar proofs or some examples.
- After reading a theorem, see if you can restate it. Make sure you know what the theorem says, what it applies to, and what it does not apply to.
- After you read the proof, try to outline the technique and main idea the author used. Try to explain it to a willing listener. If you can’t do this without looking back at the proof, you probably didn’t fully understand the proof. Read it again.
- Can you prove anything else using a similar proof? Does the proof remind you of something else? -
- What are the limits of this proof? This theorem?
- If your teacher is following a book, read over the proofs before you go to class. You’ll be glad you did.
[1] Reading, Writing, and Proving: A Closer Look at Mathematics By Ulrich Daepp and Pamela Gorkin.
I think in the modern era a very good piece of advice, particularly for those of us without gorilla-like stamina to comb through a math text, is to go on your favorite video website and watch through multiple videos on the topic.
