Skip to content

Iteration Plan for May 2022 #149008

Closed
Closed

Description

@kieferrm

This plan captures our work in May. This is a 5-week iteration. We have several holidays across countries coming up which gives us a bit less than 5 weeks of work time. We will ship in early June.

Endgame

  • May 30, 2022: Endgame begins
  • June 3, 2022: Endgame done

The endgame details for this iteration are tracked here.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark Description
🏃 work in progress
✋ blocked task
💪 stretch goal for this iteration
🔴 missing issue reference
🔵 more investigation required to remove uncertainty
⚫ under discussion within the team
⬛ a large work item, larger than one iteration

Accessibility

UX

Workbench

Web

Code Editor

Notebook Editor

Jupyter Notebooks

Languages

AnyCode

Python

JavaScript/TypeScript

Markdown

CSS

JSON

Debug

js-debug

Testing

Terminal

Tasks

Source Control

API

Extensions

Extension Contributions

Install

Engineering

Electron

Documentation


Deferred

Activity

  1. changed the title [-]Iteration Plan for May 2022 [DRAFT][/-] [+]Iteration Plan for May 2022[/+] on May 9, 2022
  2. fisforfaheem commented on May 9, 2022

    @fisforfaheem

    Updating to latest ELECTRON version will also fix so many performance issues found in electron

  3. lorand-horvath commented on May 11, 2022

    @lorand-horvath

    Updating to latest ELECTRON version will also fix so many performance issues found in electron

    Do you mean from 17.4.1 to 17.4.3 (I've opened issue #149223) or the newer 18.x branch? https://github.com/electron/electron/releases/tag/v18.2.2

    I should mention the slowness and lag reported in #146737 which nobody seems to care about (ticket closed, merged with other issues, etc) - the problems have been obviously introduced with Electron 17 since VSCode 1.66

  4. praveer-k commented on May 11, 2022

    @praveer-k

    Any plan to include a toggle button to show/hide code section. Make it look like a report instead of showing code in jupyter notebook?

  5. vhscom commented on May 11, 2022

    @vhscom

    Do you mean from 17.4.1 to 17.4.3 (I've opened issue #149223) or the newer 18.x branch?

    Anything you can do to improve performance at this point would trump any more features in my perspective. I used to sing praises for VSCode telling people it didn't feel like Electron. Today, however, I would tell them it feels like an Electron app unless you're using bleeding edge hardware. A code editor should not heat up a 2019 MBP.

    Lorand Horvath (@lorand-horvath) I saw you added a confused emoji. Was there something in my feedback that confused you?

  6. lorand-horvath commented on May 11, 2022

    @lorand-horvath

    vhscom Sure... I'm just kind of tired of repeating the same performance issue reports without actually solving anything... You may check this one #146737 and see that I got nowhere with it. So I'm not sure how to proceed in order to ask the relevant developers to bring back at least some of the performance we had in VSCode before upgrading to Electron 17.

    In VSCode 1.65 we had Electron 13.5.2, which was fast and it was a pleasure to work with. However, since VSCode 1.66, based on Electron 17, all kinds of problems appeared and it's slow as a snail... Unfortunately.

  7. vhscom commented on May 11, 2022

    @vhscom

    Have you/we/anyone looked at moving to Tauri? That would be my suggestion to address the performance concerns. Otherwise I'd try and stay as up-to-date as possible on Electron and not fall behind. My 0.2 before I derail planning.

  8. lorand-horvath commented on May 11, 2022

    @lorand-horvath

    vhscom Well, I am really curious to see a proper explanation as to why Electron 17 was chosen for VSCode since April and not staying on 13.5.2 (which was quite good IMHO) or 15 or 16 or even the latest stable 18 for that matter?
    Electron 17 clearly has terrible performance issues.

    I've just checked out Tauri - it looks very interesting!

  9. isidorn commented on May 11, 2022

    @isidorn

    Thanks for providing feedback, but let's continue the discussion in #146737 or please file a new issue.
    The iteration plan is not intended for scoped discussions, I would hate to have to lock this issue.

  10. fisforfaheem commented on May 14, 2022

    @fisforfaheem
  11. mkurz commented on May 28, 2022

    @mkurz

    If it's possible, it would be nice if you could bump electron to version 19. Like mentioned in #145527 (comment) it contains a bug fix to make it work on Linux running on Apple Silicon. Thank you!

  12. fisforfaheem commented on Jun 6, 2022

    @fisforfaheem
  13. fisforfaheem commented on Jun 6, 2022

    @fisforfaheem
  14. fisforfaheem commented on Jun 13, 2022

    @fisforfaheem
  15. locked and limited conversation to collaborators on Jul 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

iteration-planVS Code - Upcoming iteration plan

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions