VS Code extremely slow

andyj713 said:

Was there a lot of clamoring for "recompile the whole project on every keystroke" and I just missed it?

Yeah actually, in the past, new CIQ devs have asked "where are the IDE language features for Monkey C / CIQ?" Now that Garmin has finally added these features, there are also complaints when they don't work.

In this very thread:

"I have no idea on how to navigate the code or see any code completion in the editor."

"I'm on v.1.2.2 and it does nothing like that.
It doesn't help me write the code. Today w/the APIs being so big I can't really keep everything in mind (except for general guidance). For API docs it simply opens a browser."

As another example, a few months ago - when the language features were only in a beta SDK - one poster said they would not start CIQ development until a stable SDK was released which supported those features.

So no, nobody literally said "I want my project to be recompiled on every keystroke so I can use my laptop as a space heater in the winter", but obviously there is a demand for IDE language features and It just so happens that background compiling is how Garmin implements these features.

andyj713 said:

What I would also like is for Garmin to spend less time on what they think we might want, and spend time on things we actually ask for, like bug fixes

It's the same strategy as introducing new features with new models of watches as opposed to focusing on fixing all the bugs on existing models.

1) They want to attract new users, not necessarily make things perfect for existing users

2) They will never drop everything else in order to focus on fixing bugs, no matter how much a minority of users may say they want that. New features sell products, not bug fixes

3) Some of the new things that are added are legit useful, for both existing and new users

I say this as a software dev who was always frustrated by rampant bugs at a company I used to work for (with a very old-school culture like Garmin's). I would constantly make a ruckus about bugs and design issues (both internal and external) that I thought we should be fixing. Sometimes I predicted bad situations arising from these bugs (or design decisions) years in advance.

A lot of managers just don't care. Their stance is typically "there will always be bugs", and honestly, they don't care about poor quality as long as it doesn't affect the bottom line.

We once had a feature listed on the spec sheet which did not work at all - rather than fix or remove the feature, one manager said to leave it in and see if any customer complains. Garmin is *almost* like this, where some of their features are either broken or impractical to use due to design or implementation issues, but it's ok because they have their marketing bullet points and ppl aren't complaining too loudly.

I've also worked in places which a much more modern culture, and the mindset with regards to quality isn't much better. In some ways it's worse at a startup, since the products and services being developed are seen as more ephemeral and disposable.

andyj713 said:

What I would like to be able to do is turn off background compiling, and just compile when I say.

You can do this indirectly by turning off type checking, as beva implied.

Ofc you will lose also lose the benefits of type checking, so it's not a perfect solution.

You could also open the current SDK's bin/ folder and rename LanguageServer.jar, which would disable Monkey C's IDE language features and turn off background compiling.

What I'd do is try installing the stuff for CIQ on a friend's computer,  If it runs fine (I expect it will) then there's a second computer right there that can be checked for differences.

I would really appreciate if you didn't try to intercept the thread...

That would be nice... If I did have a friend with a computer... :(

Saying 'man, it's your problem' today considered helpful?

Looks like Garmin just throws something to the market (like the watch with unclear specs) and then there's no support... except for this 'community' which I totally understand is 'free' and people don't even have to care about others (I completely recognize the fact you are doing this in your personal time. Exactly like I do. Which doesn't mean these kind of statements - about the issue being my own - need to be made).

Well... overall the situation is really discouraging...

I will try to find another box to do the same thing and see if the situation changes.

nskmda said:

Saying 'man, it's your problem' today considered helpful?

There is no evidence that it’s a general problem. So, yes, realizing it might be something odd/broken with your setup might be helpful. 

The problem certainly isn’t due to VS being “bad”.

nskmda said:

I would really appreciate if you didn't try to intercept the thread...

You managed to do that with your initial irrelevant rant. 

I’m using a 4th gen i7 and not experiencing the issues you are talking about. It doesn’t seem like anybody else is experiencing it either. 

nskmda said:

Looks like Garmin just throws something to the market (like the watch with unclear specs) and then there's no support... except for this 'community' which I totally understand is 'free' and people don't even have to care about others (I completely recognize the fact you are doing this in your personal time. Exactly like I do. Which doesn't mean these kind of statements - about the issue being my own - need to be made).

You typically don’t get more support than this from any company unless you pay (a lot) for it. So, your expectations aren’t realistic.

Your issue seems quite unusual.

jim_m_58 said:

What I'd do is try installing the stuff for CIQ on a friend's computer,  If it runs fine (I expect it will) then there's a second computer right there that can be checked for differences.

This is suggesting the problem is specifically with his computer. You aren’t allowed to suggest that.

From the start, he’s discounting the possibility that it’s an unusual issue with his setup. He should have just described his problem without the silly rant that goes against everybody else’s experience (not having his issue).

Is anybody else experiencing a similar issue?

jim_m_58 said:

What I'd do is try installing the stuff for CIQ on a friend's computer,  If it runs fine (I expect it will) then there's a second computer right there that can be checked for differences.

This is suggesting the problem is specifically with his computer. You aren’t allowed to suggest that.

From the start, he’s discounting the possibility that it’s an unusual issue with his setup. He should have just described his problem without the silly rant that goes against everybody else’s experience (not having his issue).

Is anybody else experiencing a similar issue?

His issue appears to be with the Java part. Nothing to do with VS code at all (even though he ranted prominently about VS code). Maybe, he’s still running some odd/old version of Java in his path.

dpawlyk said:

You managed to do that with your initial irrelevant rant. 

my very "initial irrelevant" rant was 1 - a P.S, 2 - in another message as a response to the suggestion.