My favorite VS code extension is remote containers extension because
it allows me to have access to any languages or
toolsets without having to install them locally.
Super convenient for working on new projects.
My favorite V is code extension is called tab out.
Might not have heard of it and this is what
it does.
Let's you literally tab out of quotes and brackets and
braces of her press tab.
I'm outside the quotes if I press it again.
I'm outside the braces, tab out.
Hi, my favorite extension is Kate graph since it allows
me to manage commit history.
In an easy and intuitive way.
Hi, my name is Harold and my favorite is code
extension is markdown and mochi because I want my documents
on GitHub for planning.
Look the best with all the emojis.
Pull requests and issues because most of my work code
is on GitHub and I like having all of that
integrated also inside VS code favorite extension is multiple cursor
case preserve which does just as it sounds.
You have a bunch of different selections and they'll have
different cases and I can type normal text and it
will preserve the case in the text that I typed
my favorite extension right now is called conventional commits.
It'll guides me through creating a conventional commit message all
the way from.
Picking your category, picking a reason calling out,
breaking changes, etc. So it comes really handy if you're
using semantic release in your project.
I'm Matt Burner and one of my favorite extensions
is the issue notebook extension.
This extension saves GitHub issue queries to a notebook inside
of VS code.
It's really helpful for managing larger projects.
I
enjoy the theme generator exception which allows
you to do just that.
Generate
themes and with just a click of a button,
shuffle the colors and what they're used for.
My favorite extension is error lens and what this allows
you to do is to make your errors and warnings
a lot more visible.
You know when you're writing your code and you run
into any errors instead of hovering over each item to
see what the error is.
Error lens will print out the message directly in the
editor,
which saves you a ton of time.
This is also fully customizable,
so you can change the icons,
the font, the delay, and much more.
Hey y'all, my favorite vscode extension is called prettier,
which is great for format your code.
Check it out so this code here.
That's absolutely hideous, but as soon as I hit save.
We got much nicer that looks with prettier.
I like the Excalibur extensions at most,
which gives me a scratchpad to explore.
Ideas writing VS code. My favorite extension is Git lens
for its current line blaming hovers capabilities,
which allows me to see a lot of context behind
each line.
My favorite VS code extension code runner.
Use it with almost any language to get clean output
to your console.
This right here is in Python,
this right here. C++ consistent clean my favorite VS code
extension is template string converter.
Sometimes I'm typing in normal string in JavaScript and TypeScript
and then I realized I want it to be a
template string with backticks instead.
This extension automatically converts the quotes to backticks as soon
as I type a dollar sign and opening Curly Brace.
My favorite VS. Code extension has to be live share,
which lets you collaborate together from different devices in real
time.
It's made working from home the last two years and
working on code together way easier.
One of my favorites is indent rainbow.
Check this out. It helps me keep track of the
indentation level with color,
and as I hit tab here,
more colors get added.
Hi everyone, welcome to VS code day.
We thought it'd be fun to kick off the event
by doing a little retrospective on how far vis code
has come along in the past year.
So let's start by looking at some numbers.
We closed out 2021 with about 19 and a half
million people using the tool every month.
As of today, we're up to just over 20 million.
It's an amazing number. It's up almost 6 million from
just last year.
And one way we gauge satisfaction of the product is
through the concept of a Net Promoter score NPS.
So if you've ever responded to a survey where you're
asked to scale of 1 to 10,
how likely you are to recommend this code refriend?
Your response is reflected in this number.
So the higher the number,
the better, and I believe the creators of NPS say
that anything over 50 is excellent and 80 is world
class,
so it's 67. We're doing pretty well.
So thank you very much for recommending these code.
And we gauge interest in satisfaction with the project by
looking at the number of GitHub stars in the VS
code repository and according to the Git Star ranking site
with 128,000 stars voice codes,
the 20th most popular repo in GitHub and it's the
top Microsoft repository.
The way we look at the health of the extension
ecosystems by looking at the number of extensions published to
the marketplace now today,
there are more than 29,000 extension authors and you can
find more than 34,000 extensions and themes in the marketplace,
including new categories of extensions we added in 2200 2020.
One such as machine learning and data science.
Now the last number in the lower right hand corner
is the one I'm personally most proud of.
We want everyone to be able to program using VS
code.
We've worked alongside the community over the past year to
identify ways which we can make these code more and
more accessible to everyone.
For example, we've recently added audio cues to the editor,
making it easier to know when code has been folded
or collapsed,
or probably more importantly, when it breakpoints been hit in
2021,
the number of users who rely on screen reader support
grew to more than 100,000.
Up from about 40,000 at the end of 2020 and
today we have over 120,000 users using screen readers to
program in VS code.
In 2021 we made this code easier to acquire and
expand its footprint onto new platforms.
So now we're available in the new Windows Store.
We're included in the Raspberry Pi Linux distro and we
support Apple's new M1 hardware for better battery life and
performance.
But I think the most exciting platform to go live
in 2021 has to be GitHub code spaces,
which provide a fully managed,
cloud hosted development environment powered by bees code and accessible
to the desktop tools or through the browser now.
Code Spaces utilizes the same development container technology.
Found in our remote containers extension so you can have
a reproducible development environment on your desktop or in the
cloud.
Whatever works best for you.
When we started this code,
we said we wanted to ship like a service,
meaning we could push a button.
It seems to update the product so that everyone runs
in the latest release.
The latest features, the latest bug fixes,
and most importantly the latest security updates.
Now, last year we shipped 11 stable releases,
one for each month except during the holiday season.
Now on top of those we shipped to 22 additional
releases to address critical bugs and security issues,
but hopefully all this was completely transparent to you.
Now, if that wasn't enough,
we also shipped more than 250 insider releases last year.
And honestly, I'm just glad we don't name those like
we do.
The stable release where the January release comes out in
February,
and so on. I mean,
if we did this for insiders,
then Monday release would ship on Tuesday and Tuesday on
Wednesday,
and of course the Friday release we ship on a
Monday on the holiday and then we ship on Tuesday.
It's very confusing. But probably more importantly,
those releases couldn't have been possible without you.
In 2021, we consumed almost 2500 pull requests from the
Community,
so thank you for taking an active role in building
VS code.
So not only did we ship off and we easily
ship more than 100 new experiences in 2021,
some big, some small, but obviously too many to list
here.
That said, I want to call it a few of
my favorites.
You know, over the past few years,
we've seen development tools and services become prime targets for
security attacks.
Our goal is to make sure that developers are secure
by default.
While being empowered to customize their environments to work as
efficiently as possible,
so with trusted workspaces, you can safely view and edit
your source code from unknown sources and without the fear
of the tools executing malicious code without your knowledge.
And as you tell Vius code which workspaces you do
trust,
the tool evolves overtime. Divide you with all the richness
you've come to expect,
but in your terms, not at hours,
not on the Internets. In his data science machine learning,
become fundamental to the core development experience.
We've been building notebook support into the core VS code,
and in 2021 we're able to finalize the API's and
provide native Jupiter support right out of the box.
We worked especially close for the Community bringing testing support
into VS code where we now have an integrated test
Explorer and the ability to discover,
run and debug test directly from the editor,
and the same goes for bracket pair colorization.
We worked with the community to bring the functionality of
this wildly popular extension into the core BS code where
we could dramatically improve the overall performance by integrating directly
in the renderer or the UI portion of VS code,
instead of having to span the extension API boundary.
I'd really encourage you to check out the great blog
post by Henning on our site,
where you can learn a ton about how we implemented
this experience.
The last thing I want to highlight from 2021 was
the release of VS code for the web or as
we like to call it VS code Dev.
It's a version of this code that doesn't require any
installation and runs fully in the browser in just about
any platform including the Apple Watch.
As you can see here.
Not that I would recommend you doing development on your
watch.
But you can. And if you have a chromium based
browser like Edge or Chrome,
you can quickly edit local files and folders with Vscode
Dev.
You can remotely edit GitHub or Azure DevOps Repository's,
including making commits and reviewing polar requests without having to
bring any code locally to your machine.
You can share your favorite themes through convenient these code
dev URL so you can friends can preview them live
and there are hundreds of extensions in the marketplace that
today work fully in the browser like Luna Paint,
which gives you the power to edit raster images right
in VS code.
When we first started the VS code project,
our primary goal was to be able to write code
in the browser.
And in a way, abuse code Dev is the realization
of that original vision.
But it's also the start of a completely new one.
We're in femoral code editor,
available to anyone with a browser and an Internet connection
is the foundation for a future where you can truly
edit any code from anywhere in the world.
2020 was a great year and thank you for helping
make this code what it is today,
and I'm looking forward to what we're going to build
together in 2022 and beyond.
Stay tuned here more about VS code DEV and web
enabled extensions from Eric Amadio,
the author of the Git Lens extension.
When the top extensions of this code which he recently
enabled in the browser.
Thanks again bye.
Hey everyone, I'm Eric Amodio and I'm thrilled to be
here at Vscode day.
I couldn't be more excited about the mission to bring
VS code back to the web.
The potential and power of bringing VS code in its
rich extension ecosystem into the browser is limited only by
our imaginations.
The zero install accessible from anywhere.
Ability to jump into a code base is extremely powerful
and it opens the door to so much more.
Which is why today I'm so excited about our latest
Git Lens 12 release,
which brings the power and insights of git lens to
VS code on the web.
Guillain supercharges your git experience in VS code.
Now, anyone from anywhere could jump into your code to
understand how and why it evolved,
bringing Git lens 12 to the web was no small
sweet git lens required direct access to git,
the file system and relied on many node JS API's,
none of which would be possible on the web,
reducing the reliance on node was pretty straightforward,
as VS code itself provides many similar APIs,
and I set up a dual webpack build to swap
out functionality for each environment.
From there, the hard part was abstracting direct access to
Git.
Thankfully, I already had some decent layering in place,
so I refactored the internals of git lens into a
provider based model to allow for the best provider,
whether local or virtual, to handle each get request.
Once that was complete, it was time to build out
the GitHub provider to translate the Git git requests into
GitHub API calls.
While the GitHub API's are rich and powerful,
they don't offer the same level of access that Git
does,
so it was definitely a challenge to adapt what could
and couldn't be supported while the web support in Gotland
12 is in preview today,
it supports and supports a lot of rich functionality.
We will continue to expand upon it as we go
forward into any extension developers getting started today.
Please think about adding Web support off the start.
Take advantage of the VS code APIs.
And avoid using node directly.
I would also highly recommend using Uris everywhere.
Don't use file paths if you can avoid it.
That was and remains to be one of my biggest
challenges as Git lens.
Use file paths and not urjas and way too many
places.
Anyway, let's dive in and check out get lens 12
on the web.
OK, so here we are on VS code dot dev
on the web and now I'm going to navigate to
the VS code repo.
And to that end. Here we are on the VS
code repo.
I'm going to now get lens installed so open the
extensions view type in git lens.
And right now I'm going to be using the insiders
edition by the time you watch this,
the stable version of Git lens will be available,
so definitely use that and here now we've got Git
lens installed.
We'll switch back to our editor.
And now you can see that git lens is enabled
in providing the rich inline blame and hover support that
hopefully you know and love.
So each commit shown here we have the you know,
commit message. You know who authored it as well as
when it came in.
So here in the hover we can get even more
details.
You can see that there's an auto link to an
issue and then down below get lens will show you
that you know the actual PR when it was merged.
If it was still open or closed and then same
with the issue so we can actually jump out directly
by clicking on that and go find out more information
about this specific PR. You know.
Get lens also provides a rich file blame so we
can look at this across the whole file.
So if we you know want to know all the
different lines changed for this particular commit,
we can quickly just switch and highlight of the changes
that were brought in as part of that commit.
And we can also get.
The same rich, rich hover information as well.
Additionally, Gatlands provides, you know,
rich navigation through history so we can just quickly jump
to the previous commit or alt click on it to
actually pick some previous commit in time.
So if I wanted to find out what this change
actually brought into the file can jump in here and
then specifically see the changes that came in as part
of that commit and the inline blame the the line
blames.
And in the rest of the support also work in
these modes as well.
And then we also have the rich sidebar views.
So if you want to look at,
you know all the commits,
then the repository or just specifically for the individual file
all get lens rich views work in the web as
well,
and then in git lens 12 we have some great
new feature.
The column visual file history.
So this is a brand new visualization that gives you,
you know you can pick your time frame and it
will show you.
You know who made changes to the file on the
Y axis here as well as to see the that
the size of the change,
the size of the changes,
both the additions and deletions.
As these stack bars as well as just,
you know overall. So if I wanted to get more
information I can click on these individual commits and dive
through the changes on those as well.
And yeah, so this would be a powerful new visualization
that is available.
Git Lens 12 also supports berch trees on the desktop.
They're not enabled on the web,
but that's a powerful feature to allow you to.
Work simultaneously on multiple branches,
so it'll be a powerful feature there and then.
We also have a new git lens getting started experience,
so in here just open this to full screen so
walks through all the features of git lens as well.
So you know, for neuter or existing users,
if you're unfamiliar, you can walk through to to get
familiar with how you can customize,
get lens how you could get it to work,
and get the most out of it.
So yeah, hopefully you'll try out get lens 12 today
and thanks everyone.