►
Description
Community links for this week: https://www.one-tab.com/page/mMnTUMCLTp-HVnQ7OBK5yw
B
C
C
C
B
B
C
I
did
a
tweet
where
I
had
a
page
on
the
github,
a
stay-at-home
wiki,
so
people
could
get
the
the
bits
like
a
week.
Early
yeah
I
mean
you
know
if
they're
willing
to
he
says
some
caveats,
and
so
we
had
a
few
people
download
that
I,
don't
think
of
him
and
says,
but
anyway,
yeah
like
we
launched
for
real
last
week,
right
I,
wisely.
C
Good
well
now
it
is
live
now.
We
had
really
good
like
really
solid
sort
of
feedback
in
terms
of
positive
feedback
like
it
was.
We
were
very
happy
that
for
a
for
a
minor
release,
you
don't
want
things
to
break
and
stuff.
That
was
good,
a
lot
of
people
being
up
to
update
successfully
with
very
little
problem.
C
We've
had
some
good
feedback
around
continued
confusion
around
some
of
our
versions
to
start
so
some
folks
hadn't
seen
our
versioning
dark
update
around
how
we
were
going
to
be
doing
versioning
of
the
SDK
and
the
runtime
moving
forward.
So
if
people
recall,
we
had
a
2-1
SDK
like
last
year,
which
threw
everyone
off,
obviously,
because
that
was
a
terrible
idea
in
retrospect,
and
so
we
have
a
new
versioning
scheme
where
the
major
and
the
minor
will
always
align
from
now
on.
C
Camera,
oh,
oh!
Oh!
It's
because
I'm
like
fiddling
with
something
here,
there's
a
good
time,
and
so
we
from
now
on,
like
when
two
two
comes
out.
The
SDK
version
will
be
two
to
one
hundred
there's
a
new
scheme
for
doing
SDK
version
II,
where
the
third
number
will
always
represent
new
stuff
in
the
SDK,
whether
it's
like
a
patch.
So
the
first
patch
release
for
the
SDK
will
be
dot
301
because
it'll
be
two
dot
one
dot
301.
C
And
if
we
added
a
feature
to
the
SDK
like
a
new
version
of
C,
sharp,
like
7.3
or
whatever,
the
next
one
is,
or
a
new
version
of
new
get,
which
is
an
individual
component
but
is
pulled
in
by
the
SDK,
then
it
would
go
to
two
dot,
one
dot
400.
So
if
that
makes
sense,
so
we
can't
use
semver
for
the
SDK,
because
it
represents
a
group
of
products
that
version
independently.
C
And
so
we
can
come
up
with
the
scheme
that
we
think
is
the
most
confusing
of
all
the
options,
which
is
the
major
and
the
minor
always
match
the
branded
version
for
dotnet,
which
the
branded
version
for
dotnet
core
is
aligned
to
the
runtime
version,
which
is
why
I
start
they
call
2.1
so
now
the
sdk,
who
is
also
2.1,
but
then
there's
this
third
number.
That
tells
you
more
detail
about
that.
Add
sdk!
It's
like
oh
well!
C
B
C
Good
yeah,
that's
all
I
need
to
say
that
I
think.
As
always,
when
we
attempted
to
do
some,
what
we
thought
was
very
clear
messaging
about
what
dot
bet
standard
was
intended
to
solve
you
specifically
around
replacing
PC
ELLs
and
having
a
sort
of
monotonically
ever-growing
standard
that
would
only
get
core
API.
Is
that
it
over
time?
C
We
had
actually
I
mean
I,
remember
being
on
stage
and
having
Scott
be
on
stage
and
literally
say
the
opposite,
which
is
done.
The
core
is
where
we
would
add
new
API,
because
we
have
the
freedom
to
do
that,
much
quicker
in
a
side-by-side
non-breaking
fashion.
Your
lower
risk
fashion,
I,
should
say,
etc,
etc,
and
then
we
could
work
things
into
the
standard
based
on
when
they
appear
in
other
platforms,
but
for
whatever
reason
that
messaging
was
lost
on
at
least
a
portion
of
the
audience.
C
So
we
are
gonna,
do
some
work
to
try
and
clarify
that
messaging
and
then
a
coming
week
or
two
and
I
think
there's
a
PR
out
right
now
to
the
standard
repo.
The
mo
is
working
on
that
tries
to
clarify
like
how
does
tenant
governance
will
work
moving
forward
and
like
what
is
the
process
for
getting
new
api's
and
they're
not
understand
it.
Like
I
said
some
people
seem
to
have
the
impression
that
we
will
just
add.
C
B
I
did
see
some
I
mean
I
can
understand
from
a
library
author
point
of
view
where
it's
nice
to
always
target
standard,
and
then
things
just
light
up
when
a
new
platform
supports
a
standard
right,
but
obviously
that
you
need
to
like
know
what
to
put
in
the
standard
based
on
you
know,
like
some
implementations
is
there,
do
we
have
guidance
or
like
let's
say,
I
do
want
to
use
new
stuff?
That's
in
dotnet,
core
I.
Basically,
I
need
to
target
and
net
core
to
get
those
features
right.
Yeah.
B
C
Use
it,
and
so
in
a
world
like
net,
where
there
are
multiple
platforms
that
have
different
release
schedules
and
they're
constrained
by
different
things
like,
for
whatever
reason,
whether
it
be
schedules
or
the
thing
they
ship
in
or
compatibility
requirements,
then
you
I
think
you
have
to
expect
that
for
a
certain
set
of
api's
you're
always
going
to
have
to
cross
target
at
some
point
like
saying,
depending
on
what
your
library
does
like
for
the
most
basic
library,
that
only
has
very
basic
needs.
You
can
just
target
one
version
under
standard.
C
That's
low
and
you'll
get
you'll
get
the
broad
reach
anytime.
You
want
to
take
advantages
of
new
api's,
no
matter
what
they
are.
Like
you
know,
any
new
API
by
definition
requires
a
new
standard
which
then,
by
definition,
you
have
to
wait
for
all
the
platforms
you
care
about
to
get
that
new
standard
or
implement
that
new
standard
I
should
stay.
In
order
for
you
to
better
use
that
API
that
there's
always
going
to
be
a
lag.
It's
if
you
just
kind
of
what
that's
the
way
the
standard
works.
B
C
You're
gonna
have
to
cross,
compile
your
soon
it'll
be
early
new
new
new
API.
You
have
to
multi
target.
You
have
to
at
least
target
more
than
one
version
of
dante's
standard,
if
not,
or
even
a
dotnet
standard,
plus
a
specific
platform
or
two
or
three
in
order
to
be
able
to
use
the
API
that
are
only
available
in
a
certain
platform.
C
That's
just
sort
of
the
nature
of
the
beast.
Now,
what
is
fair
to
say
is
that
we
haven't
prior
for
the
library
authors
in
the
audience.
We
haven't
prioritized
multi
targeting
as
a
first-class
experience
in
Visual
Studio,
and
the
command
line
is
pretty
good,
but
in
Visual
Studio
and
the
other
ideas
multi
targeting
is
probably
fair
to
say
nowhere
near
where
it
needs
to
be.
For
that
to
feel
really
natural.
C
C
Like
them,
delete
the
target
framework
property
and
at
a
different
property,
which
you
just
have
to
know
right
like
missus,
so
it
is
not
first
class
now
once
you
do
that
certain
features
do
light
up.
It
shows
up
in
solution
explorer,
but
you
can't
straight
right.
Mouse
click
add
target,
which
is
what
it
should
be
if
it
was
really
a
first
class
feature.
C
So
I
am
like
we
were
talking
about
this
today,
like
we
do
intend
to
prioritize
those
things
higher
now,
I
think
it's
fair
to
say
that
our
focus
had
been
on
fixing
some
of
the
other
issues
that
we
had
worked
through.
We've
gotten
a
call
from
one
to
one
one
to
two:
oh
two
to
one
and
the
subsequent
dotnet
sneer
moved
from
PCL
stood
under
standard
done,
the
standard
one
did
understand
or
two
etc.
C
B
B
C
C
Those
were
the
folks
that
we
expected
would
be
would
be
into
it
and
then,
once
it
went,
live
I
think
the
number
of
people
like
x,
10,
who
suddenly
showed
amazing
how
to
use
everywhere-
and
we
were
like.
Oh
that
happened
quicker
than
we
kind
of
know.
Yeah
yeah
I,
think
you
kind
of
back
that
caught
us
by
surprise
a
little
bit.
Sorry
that
that's
a
good
problem
to
have
to
your
point.
I
guess
that
people
are
more
excited
than
perhaps
we
anticipated.
So
all.
B
A
B
Need
an
extension
that
hides
the
okay
yeah,
so
here's
the
here's,
the
official
post,
you
know
on
the
release,
so
you
know
I
got
a
I
got
a
say
like
as
far
as
a
release,
you
folks,
really
I
I,
think
there's
a
great
role
out
that
you
did
on
the
blogs
like
where
you've
got
you've
been
updating.
The
feature
serves:
there's
a
nice
drill
down
posts
on
all
of
these.
So.
C
By
the
time
we
launched
our
team
so
that
our
blog
post
could
be
as
straightforward
as
just
go
and
read
all
the
docs.
Here's
the
could
the
deep
links
into
all
the
new
great
stuff
really
really
really
good
job.
Now
we
also
did
get
some
feedback
from
some
folks
that
this
blog
post
format,
however,
isn't
particularly
good
for
folks
reading
on
like
a
mobile
phone
who
just
want
to
like
scan
one
big
document
to
see
all
the
new
stuff
and
so
we're
thinking
about
what
we
can
do
in
the
future
say
in
a
tutu.
C
Could
we
still
have
the
same
basic
infrastructure?
We
have
a
whole
bunch
of
Docs
that
were
added,
but
somehow
we
could
like
snapshot
or
roll
up
the
salient
content
into
like
one
post
that
people
could
just
like
scroll
through
we've
got
nothing
about
quite
quickly
and
that's
fair,
so
we'll
we'll
keep
working
on
it
as.
B
B
A
B
C
So
we
we
worked
with
app
service
team
closely
to
try
and
minimize
that
lag
between
when
the
bits
were
available
and
when
they
were
available
on
Asia
now,
there's
obviously
other
places
where
people
on
the
VST
s
I
think
are
still
I
think
was
today
even
late.
The
fifth
right
I
think
today
was
the
target
for
when
the
VST
s
build
agents
would
get
to
point
one
and
obviously
it's
not
in
Visual
Studio.
C
C
It
wasn't
everywhere
in
Azure
on
day
one
it
was
in
like
one
region
and
then
the
rollout
takes
right
up
to
five
days,
and
so
for
a
couple
days
we
did
have
a
few
folks
saying
I'm
trying
to
use
it
I'm
getting
an
error,
and
then
we
were
like
just
try
again.
It
just
went,
live
and
that's
just
a
difficult
problem,
because
there's
just
like
physics,
it's
just
it
takes
prime.
C
B
A
B
Is
cool
and
a
lot
of
people
talking
also
about
their
build
time?
So,
of
course,
there's
both
the
runtime
and
the
and
the
build
and
the
sorry
like
the
dev
and
build
time
yeah.
You
know
the
inner
loop
cycle
stuff
so
that
build
times
I
saw
people
tweeting
about,
like
oh
my
gosh,
my
build.
You
know
it's
down.
You
know
we
used
to
take
a
minute.
Now,
it's
20
seconds
or
whatever
it
is
so
that
is.
C
C
B
C
So,
like
I
think
my
assumption
I
think
the
laughs
your
run
is
probably
gonna,
be
the
one
that
makes
round
16,
and
then
this
run
that's
running
right
now.
If
it
isn't
there
already
the
one
that's
already
finished,
they
will
both
make
that
the
round
16.
So
these
numbers
are
pretty
much.
What
round
16
will
be
yeah.
B
A
B
C
B
C
You
can
see
seven
there
and
then
we're
again
at
number
eleven
and
then
I'm
gonna
number
17,
depending
on
what
framework
you're
using
and
what
their
access
technology
you're
using.
And
then
this
is
plaintexts
and
we're
at
number
11,
for
whatever
reason,
I
think
there's
a
yeah
so
for
whatever
reason
in
this
round,
because
basically
everything
in
the
top.
What
11
here
is
network
bound
run
to
run
like
it
can.
C
C
B
A
C
Is
there
we
go?
Oh
wow
that
is
laggy
yeah,
alright,
so
they
so
you
can
see
like
it's
starting
to
spread
out
already
and
so
like
1
to
7
yeah.
So
like
way
down
to
number
12
now
and
that's
moist
lucky
because
we're
CPU
bound
in
that
environment,
whereas
the
super
fast
you
can
see
the
top
are
all
native
languages
yeah,
it's
C++,
C,
rust
and
Java
when
the
sneaky
in
there.
But
we
know
we
still
have
always
to
go
to
beat
some
of
the
raw
performance
of
the
Java
networking
stack.
So
yeah.
C
Wouldn't
be
surprised
if
you
see
like
the
you
libs
and
the
lib
reactors
and
the
the
the
rust
frameworks
doubling
their
performance,
because
there
they
are
network
band
right
now,
like
yeah,
we
will
likely
we
will
go
faster
than
7million,
obviously,
because
we'll
get
more
network,
but
we're
not
going
to
go
to
14
like
we're.
Not
gonna
double
is
my
guess.
B
C
C
So
any
latency
in
how
you
schedule,
reading
off
the
socket
and
then
like
in
your
thread,
pool
and
memory,
pools,
knots
up,
stuff
and
then
process
a
request
and
then
have
send
that
back
any
latency
in
there
will
show
up
as
a
drop-in
app
yes,
so
we
have
some
work
to
do
in
dotnet
land
to
to
to
work
on
that
and
we're
still
working
on
it
like
it's
an
it
your
job
or
is
particularly
good
here.
You
can
see
like
act,
and
this
is
again
the
cloud
one.
So
the
numbers
a
lot
lower.
C
If
you
go
look
at
the
physical
one,
where
it's
a
lot
less
bounded,
you
can
see
them
really
stretch
their
legs
but
yeah.
If
the
cloud
workloads
there's
a
lot
of
people
are
using
and
they're
using
an
extra
large
VM,
which
is
what
this
is
bailing.
This
is
a
four
core
VM
or
maybe
it's
a
night,
coffee,
Marc
I
remember.
This
is
pretty
typical
of
the
type
of
hardware
and
all
other
people
running
on
so
cool.
B
Alright,
one
last
performance
related
one,
and
this
is
for
peach
pie.
What's
cool
with
this?
Is
they
they've
been
it's
been
pretty
fast
for
a
while,
however,
been
started
just
looking
at
the
the
benchmarks
and
noticed
some
things
to
do
as
far
as
configuration,
so
one
thing
was
like
making
sure
that
the
target
was
set
correctly
so
that
server
GC
was
turned
on.
So
some
things
like
that,
so
in
doing
that,
the
performance
went
up
significantly
so
you're
seeing
peach
pie
is
the
top
top
result.
Now
for
a
PHP
which
yeah.
B
C
The
other
thing
we
didn't
call
out
explicitly-
which
we
showed
is
that
the
one
of
the
biggest
performance
improvements
in
this
around
that
we're
proud
of
four
to
one
is
actually
the
database
performance
improvements
which
is
like
the
fortunes
in
the
single
data.
The
single
query,
multi,
query
and
update.
C
We
worked
with
the
community
to
to
improve
the
Postgres
driver
and
the
my
sequel
driver
for
a
do
net,
and
you
can
see
they're
like
we're
number
11
in
the
cloud
one,
and
if
you
were
to
go
back
to
the
physical
one,
I
think
we're
actually
in
the
top
ten
yeah,
and
most
of
that
is
is,
is
to
factor
one.
We
submitted
a
platform
level
test,
but
most
of
it
actually
came
from
the
it
was
share.
C
C
Pipelining
of
the
queries
over
over
shared
database
connections
and
there's
been
a
long-running
debate
about
whether
that's
valid
or
not,
and
the
benchmark
folks
have
said
it
is,
and
so
now
we're
you're
trying
to
figure
out
what
the
right
approach
is
to
try
and
achieve
a
similar
thing
in
net
and
whether
it's
correct
or
not,
and
so
anyway,
so
like
drastically
improved.
It's
like
ten
times
better
than
we
used
to
be
so
yeah.
C
Says
the
is
Bradley.
Granger
is
the
name
of
the
my
sequel
community
dev,
who
has
done
the
work
there?
So
if
you
scroll
down
you'll,
see
that
there's
a
my
sequel
version
of
these
tests,
a
spinet
core
and
middleware
ad?
Oh
my!
So
that's
39,
yep
158,000,
like
our
previous
runs.
We
were
getting
like
40,000
like
even
on
Postgres.
So
again,
the
massive
machine
equipment.
Number
33
is
my
sequel
as
well.
Yeah.
B
So
yeah
it
was
fun
in
my
talk
saying,
like
look
upgrading
from
you
know,
previous
version
to
this
version
is
like
a
few
lines.
You
like
it's,
it's
usually
pretty
straightforward
and
like
huge
performance
improvements,
so
it's
pretty
cool
to
show
that
it's
like
here's,
here's
how
I'm
gonna
lure
you
into
running
the
latest
version,
yep.
C
And
just
to
remind
folks
so
far,
this
is
all
on
Linux.
The
tech
and
power
infrastructure.
Today
is
Linux
only
we're
looking
at
helping
out
with
that
as
well
and
trying
to
figure
out
how
we
can
get
it
running
on
Windows
and
they
are
I
believe
looking
at
standing
up
sequel
on
Linux
right
now,
so
that
the
next
round
could
have
results
for
sequel
server
running
in
Linux
and
I'm.
Assuming
we'll
go
through
a
similar
process
of
finding
bottlenecks,
and
you
know
making
the
sequel
client
better
as
well
so
cool.
B
Alright,
moving
off
to
performance
stuff,
so
the
this
is
another
update
from
Phi
as
an
update
on
the
graph
QL.
So
we've
been
he's
been
doing
a
series
on
these.
Previously
there
were,
it
was
a
pretty
simple
model,
and
now
it's
set
up
with
many
to
many
relationships
or
one-to-many
relationships.
Excuse
me,
so
you
know
some
of
this
is
kind
of
standard,
although
it's
it's
good
to
kind
of
review
the
the
one-to-many
relationships
and
how
those
are
set
up
with
EF.
B
So
he
chose
say:
yeah
kind
of
you
know,
migrations
and
set
up,
and
the
main
kind
of
configuration
stuff
is
in
the
kind
of
the
graph
type
configuration
here.
So
so
there's
kind
of
the
configuration
of
one-to-many
graph
configuration
and
then
the
the
kind
of
payoff
towards
the
end
here
is
being
able
to
you
know
to
query
and
get
a
like
a
one-to-many
result.
So
so
that's
that's
sort
of
the
general
idea
there
and
again
the
the
repository
is
is
out
here,
so
you
can
follow
along
that
pretty
cool,
Oh,
Amy
and
Bowden.
B
So
this
is
an
interesting
idea.
This
the
idea
I'll
scroll
to
the
end
and
then
we'll
come
back
up
and
look
at
implementation,
but
the
idea
here
is
changing
changing
CSS
kind
of
wrapping
up
in
packaging
CSS
display,
and
you
did
this
using
a
view
component.
So
it's
a
view
component
and
then
adding
in
some
tag
helper
to
to
simplify
implementation.
So
there's
this
dynamic
display
model-
and
this
has
you
know
some
CSS
properties
here
so,
like
you
know,
pixel
and
and
other
things
like
that,
mom
so
and
then
this
is.
B
This
is
packaged
up
in
a
view
component.
So
there's
there's,
you
know,
as
view
component
is
set
up
here
as
far
as
how
we're
setting
which
different
ones-
and
then
down
in
here
he's
got
this
tag
helper,
ASP
for
and
calling
in,
and
then
that
dynamic
display
is
saying
based
on
what's
passed
into
it,
what
the
user
selected
changing
the
CSS
properties.
B
C
Kind
of
cool,
so
I
mean
it
seems
like
if
this
is
actually
being
used
to
Bill,
is
actually
building
UI,
where
they
need
to
be
able
to
allow
the
customers
to
change
these
things
like
a
CMS
or
like
some
visualizer
or
where
you
need
to
say,
I
want
something
in
the
three
columns
wide
and
two
rows,
and,
and
so
they
just
come.
They've
come
up
with
a
way
of
supporting
flowing
user
input
into
layout
effectively
exactly.
B
Yeah,
so,
based
on
on
that
input,
then
it's
kind
of
bubbling
up
through
this.
This
view
component
and
it's
being
used
to
kind
of
change
the
CSS
properties
on
the
fly
yeah,
it's
kind
of
kind
of
an
interesting.
You
know
bring
parts
together
to
solve
a
front-end
problem,
cool
all
right.
So
this,
oh
gosh,
I
forget
his
name
again.
B
I
did
that
last
time
too,
I
forget
Ilia
status
is
his
user
name
and
that's
what
I
remember
him
as
gosh
apologies,
but
so
this
is
cash
cow,
and
this
is
an
update
on
the
series
and
he's
talking
about
so
this
he
had
previously
cash
cow.
There
was
a
one
over
j'en
for
previous
version
of
you
know
for
previous
nbc5.
B
This
is
an
update
and
what
he
had
found
is
kind
of
updating
this.
Previously
his
caching
implementation,
you
you
did
everything
through
the
API,
you
added
and
invalidated
things
through
the
API
and
now
he's
actually
he's
got
this
set
up
so
that
it
uses
kind
of
a
provider
system
and
can
work
with
etag
based
and
validation.
So
it's
it's
kind
of
a
you
know
an
in-depth
thing.
This
is,
if
you
really
want
to
kind
of
control
things
he
does
talk
about.
You
know
comparing
with
SP
nut
cores.
You
know
built
in
HTTP,
caching
and
stuff.
B
Okay,
so
yeah
so
so
interesting
shows
here,
he's
got
this
time
to
eat
egg
extractor
and
and
talks
about
different
ways
of
doing
it,
and
then
kind
of
the
implementation
is
actually
pretty
simple
here.
It's
just
you
know
sending
cash
factory
and
giving
a
time
out
yeah
all
right.
This
is
neat.
This
is
this
is
from
deke,
showing
dotnet
notify
react.
So
the
idea
here
is
this
is
a
mvvm
and
reactive
based
kind
of
back-end
and
its
communicating
to
the
front
end
using
signal
are
so
kind
of
putting
those
parts
together.
B
React
and
react
native
go
so
yeah,
that's
pretty!
That's
a
it's!
A
cool
update
to
see
I,
recall,
yeah,
okay,
I've
been
pointing
out.
You
know
useful
kind
of
global
tools,
and
this
this
is
our
global
tool
of
the
week
here.
This
is
so
Jerry
Peltzer.
It
has
this
dotnet
outdated
and
the
idea
here.
This
is
kind
of
a
useful
thing
where
you
can
look
for
outdated
packages,
so
you
can
say
I'm
gonna,
scan
through
my
project
and
find
outdated
packages
from
the
command
line.
That's.
C
B
C
There
isn't
anything
concrete
today
to
help
with
that
now
there's
been
some
ideas,
but
there's
nothing
that
I'm
aware
of
Kathleen
might
have
some
more
data
on
some
more
idea.
If
there's
any
concrete
plans
on
actually
do
something,
there
had
been
ideas
like
being
able
to
search
for
global
tools
in
the
'quran
line
or
being
able
to
filter
for
them
and
new,
get
that
or
got
something
like
that,
but
yeah.
B
Really
cool
stuff,
okay,
so
here's
Dave
clicks
discovered
net.
So
this
is.
This
is
a
really
cool
thing
he's
put
together
that
kind
of
pulls
a
lot
of
different
things
together,
all
in
one
place.
So
this
is,
for
the
most
part,
I
try
and
focus
really
just
on
asp
net
course
or
asp
net
stuff.
But
this
one
is
kind
of
dotting
it
all
up,
but
it's
you
gotta
follow
this,
so
this
is
this
includes
events,
projects
Help
Wanted,
you
know
tasks
for
different
projects.
B
So
this
this
is
really
kind
of
a
you
know.
Recent
discoveries,
so
there's
just
a
ton
information
here.
What's
also
cool
and
I
kind
of
worked
with
him
early
on
and-
and
you
know,
made
some
feature
requests
as
he
was
going
as
far
as
things
like
feeds,
so
you
can
actually
subscribe
to
specific
feeds
on
here.
You
can
say:
I
would
like
a
feed
of
events
or
I
would,
like
you
know,
projects
or
issues
or
stuff,
but
definitely
I
think
this
is
really
cool.
B
B
C
C
What's
that
Wayne?
When
will
that
on
their
framework,
installers
come
when
will
the
framework
installers
come
with
patches?
I
have
infrastructure
running
behind
a
satellite
that
will
join
the
two
nlts,
but
a
100
Meg
download
after
every
update
is
real
fun.
So
I
think
the
question
is:
will
there
ever
be
a
way
to
get
a
delta,
install
I?
Think
and
the
answer
is
there
won't
be
don't
need
core
is
side
by
side
by
nature.
So
every
install,
we
don't
do
in-place
patches,
but
that's
it
that's
the
answer.
C
There
are
no
in
place
patches
and
on
their
call.
When
you
get
a
new
version
of
the
framework
say
when
to
one
one
comes
out:
hopefully
in
a
week
and
a
half
from
now,
then
you
will
install
2.1
to
one
which
will
be
2.1
dots
301
as
the
sdk
version
that
will
install
side
by
side.
Ok
and
then
your
apps
will
roll
forward
onto
that
automatically
because
of
our
patch
roll
forward
policy
by
default
in
the
host
and
in
2.1
and
beyond.
That
also
includes
the
a
spear
core
stuff.
C
C
Let's
have
a
look.
The
next
question
was
from
Luke
Luke
Latham
is
the
Derek
host
you
to
replace
web
host
four
to
two?
Is
it
more
of
a
300
move?
That's
more
of
a
three-way
move.
We
can't
replace
the
web
host
without
it
breaking
into
two
I
mean
in
theory.
We
could
just
change
the
templates.
We
could
come
up
with
a
new
composition
model
for
running
web
apps
on
top
of
the
general
host.
C
That
is
how
could
I
take
the
general
host
as
a
base
and
then
extend
it
to
support
the
web
stuff
we
could
do.
We
could
decide
to
change
that
in
the
template
into
two
and
build
that,
but
we
don't
have
any
plans
to
do
that.
If
we're
going
to
unify
those
two
things
we
would,
we
would
do
that
in
the
300
timeline,
a
question
from
Raphael
there's
some
ideas
on
the
roadmap
for
github
and
net
core
slash
net
standard
like
make
new
get
CVA
detection
happen
on
repositories.
C
As
for
j/s,
there
are
discussions
about
this
buried
or
ins.
Who
is
our
security
and
identity?
Pm
is
looking
at
that
area
right
now.
You
know
what
would
it
mean
for
new
get
to
support
the
idea
of
a
package
being
marked
as
vulnerable
by
its
owners
and
then
having
that
data
flow
into
places
like
github
or
actual
security
center
or
vs
al
the
command
line?
So
you
could
type
net
packages.
Audit,
for
example
like
NPM
has
now,
and
it
would
tell
you
hey.
You
have
this
package
version
in
your
graph.
That
is
vulnerable.
C
B
You
know
that
that
one's
funny
cuz
just
timing
wise
the
last
Friday
I,
was
after
a
talk.
I
gave
them.
Somebody
came
up
to
me
and
said:
hey
IVA
I
have
a
you
know
relatively
popular
package,
and
it
does
something.
Security
related
and
I
need
to
be
able
to
surface
vulnerability.
Issues
and
I
said
you
know,
he's
a
wicked
idea
and
I
said
you
know
why?
Don't
you
log
an
issue
and
then
he
did
he
went
to
do
that.
He's
like
oh.
There
is
one
right
now
going
on
so
okay.
C
Let's
go
I
just
replied
to
a
text.
For
my
wife,
let's
have
a
look.
Question.
Question
question:
yes,
Yanni
the
community
stand
up
is
very
baited
right
now:
yes,
okay
from
buck
s,
ma
bu
ke.
What's
the
correct
place
to
bug
to
lug
bugs
with
the
scaffolding
of
the
identity,
UI
I
think
that's
in
the
scaffolding
repo.
You
could
lock
them
in
either
the
scaffolding
repo
or
the
identity,
repo
they'll
get
moved
to
the
right
place.
Don't
worry
about
it!
C
C
Okay,
let's
have
a
look.
Wayne
says
g'day
from
Darwin
get
a
Wayne
a
oh
three.
Eight
nine
one
says
are
non
global
tools:
deprecated
now
they're
useful
in
some
classes
like
CI,
where
some
project
uses
a
specific
version
of
at
also
deprecated
is
a
very
strong
word.
I
will
say
that
the
seat,
the
project
tools,
we
call
them
project
tools;
they
we
don't
the
ones
that
we
had
shipped.
C
We
will
not
ship
new
versions
of,
though
we
have
deprecated
our
project
tools
so
the
ear
you
know,
dotnet
EF
and
dotnet
watch
and
they've
all
migrated
to
global
tools.
The
globe,
the
the
project
tool
feature
itself.
It's
still
in
dotnet,
core
SDK,
but
I
believe
the
the
recommendation
is
that
folks
look
to
global
tools.
I
do
believe
they
actually
have
plans
to
support
global
tools
that
are
project
specific,
which
has
a
little
weird.
But
NPM
has
this
support
today,
so
you
can
basically
I
think
they
call
it
local
execution
or
global
tools.
C
So
you
can
sort
of
have
a
way
of
bringing
a
global
tool
down
into
a
local
context
or
just
at
all.
In
that
case,
you'll
note
that
the
command
line
for
installing
a
global
call
isn't
dotnet
tool,
install
its
dotnet
tool
installed
dash
G,
because
they
in
envisage
that
there
will
be
a
dotnet
tool,
install
that
isn't
global
in
the
future.
C
So
that's
a
long
way
of
saying
that
yeah
pretty
much
CLI
tools
are
deprecated,
that
you
should
look
to
global
tools,
knowing
that
at
the
moment,
there's
a
gap
there
and
they're
looking
to
address
that
I'm,
not
sure.
If
they're
going
to
address
that
in
to
to
or
not
I
did
say
the
plan
I
can't
remember,
but
they
do
want
to
address
those
that
scenario,
but
I
can't
pronounce
his
name
but
reading
God
redeemed
bad
routine.
Thank
you.
C
C
B
C
C
Swag
is
like
a
desktop
tool
that
you
can
run
and
appointed
a
doc
or
at
an
API,
endpoint
it'll
generate
you,
some
C
sharp
code,
for
example,
so
yeah
with
that.
That
scenario,
though,
of
how
do
I,
have
a
descriptive,
endpoint
or
like
a
DB
context
and
then
generate
everything
down
to
the
client
that
wants
to
call
that
we
are
definitely
interested
in
that.
C
Question
will
you
be
taking
a
feature
request
for
github
I?
Think
Nick
crater
wants
a
wide
view
and
dark
view.
Can
you
sort
that
out?
No,
so
I
use
it
a
Chrome
extension
to
get
a
wide
view
of
github,
which
I
know
everyone
else.
Does
they
we
don't
own
github?
Yet
we
just
announced
our
intention
to
buy
github
and
it
alone
it'll
run
as
a
whole.
You
end
of
solidity
from
the
depressed
release
that
I
read.
I
know
as
much
as
everyone
else
does
in
the
public.
C
C
C
B
C
One
question
jeremy
just
asked:
is
there
a
way
to
find
the
effective
scheme
used
in
authentication?
So
I
think
they
guess
I
get.
I
guess
they
mean
in
the
context
of
a
request
so
that
if
you're
like
in
a
piece
of
code,
that's
in
a
request-
and
you
want
to
know
what
scheme
was
used
to
off
this
code-
I
decided
this
request.
Probably
I
don't
know
what
it
is.
I
thought
my
head
ask
a
question
on
the
security
repo,
a
speii
net,
slash
security
on
github
I'd.
C
Be
amazed
if
there
wasn't
I'm
pretty
sure
it's
persisted
somewhere
during
the
life
of
the
request.
Geeky
Sacramento
asked
me:
did
you
buy
your
glowforge?
Yet
glowforge
is
a
laser
cutter?
Does
I
at
home
laser
foot
I
believe
he
owns
one
no
I
took
the
the
week
person's
way
out
and
I
simply
just
bought
two
Racetrack
cutouts
from
Amazon
no
dude
tantum
own
in
the
last
show
was
3d
printing
me
like
small
Formula,
One
race
tracks,
and
then
someone
pointed
out.
C
That's
really
the
wrong
technology
to
use
for
this,
like
you
should
be
using
a
laser
cutter
and
then
he
blaze
it
cut
one
in
12
seconds
to
prove
it
and
then
on
Amazon
there
you
can
just
buy
like
you
can
buy
ones
that
are
like
this
big
or
this
big
and
they're
like
multi-layer,
birch
and
finished
in
vinyl
on
the
top.
They
look
beautiful
and
I
just
ran
a
stuff.
It
I
just
bought
two
of
the
$99
eh
I
bought
like
monza
and
I
bought
Monaco
and
then
I'm
gonna.
C
C
But
speaking
of
this
as
a
complete
tangent
and
nothing
relevant
to
what
we're
talking
about
I'm,
just
kicking
out
now,
Geoff's
and
Crist,
who
runs
the
developer,
advocates
group
right
and,
like
I,
think
he's
actually
high
up
and
that
he
might
probably
runs
more
stuff,
probably
under
selling
it.
He
was
tweeting
about
his
new
driving
rig
that
his
building
and
I
was
getting
major
Envy
looking
at
his
stuff.
So
he
has
new
fender
tech
gear,
which
is
what
I've
been
eyeing
off.
C
Is
my
next
upgrade,
which
is
like
the
top
of
the
line,
those
steering
wheels
and
hubs
and
pedals
and
shifters
and
stuff
it's
like
and
now
$1500
I
think
to
get
a
six
like
my
logitech
was
like
280
bucks
and
this
right
just
and
then
he
has
this
kit
that
he
bought,
which
is
you
let
you
build
this
incredible
aluminum
chassis
that
you
put
your
seat
in
and
all
your
wheel
gear
and
stuff
and
mount
three
I.
Think
30h
38
inch
ultra
wide
curved
gaming
monitors
in
a
so.
C
B
C
Get
me
wrong:
I
got
my
seat
and
I
got
my
got
my
55
inch,
TCL
4k,
HDR,
TV
and,
like
you
know,
it's
all
Perman
I
could
just
go
down
there
hit
the
button.
I
mean
fours
are
in
like
a
minute:
it's
fantastic,
but
three
screens
like
a
wraparound
and
like
oh,
my
goodness,
it
looks
incredible
and
because
the
step
up
from
that
is
a
motion
rig
right.
C
This
thing
go
all
the
way
to
like
$6,
okay,
yeah,
oh
yeah,
and
then
that
then
you
can
do
if
you're
a
PC
game
and
then
you
can
also
do
the,
but
that's
just
a
cost
of
adding
a
rift.
At
that
point,
we
just
as
much
at
all
right
because
once
you've
got
all
dupe
the
PC
powerful
enough
to
drive
you
4k
display
in
everything
anyway,
the
the
V
arts.
B
C
Trajectory
to
myself
but
yeah,
otherwise,
it's
it's
seriously.
Cool
someone's
asking
for
pigs,
so
I
do
have
some
pictures
of
my
my
current
rig
somewhere
in
my
Twitter
feed
they're,
not
particularly
good
pictures
because
they
just
like
took
my
I
need
to
do
some
baddest
H
pictures
I
was
actually
gonna.
Do
it
I
actually
need
to
have
to
learn
how
to
do
like
a
not
twitch
the
Xbox
one
like
mixer
right,
because
you
can
plug
like
cameras
into
your
Xbox
now
and
it'll
just
light
up
as
a
webcam
for
you
you're
streaming.
C
C
B
C
Going
way
off
track,
but
yeah
simracing
is
fun
and
expensive.
That
was
that's.
What
fixer
said.
Okay
we've
got
one
more
question
and
then
we
will
have
to
finish
up
two
more
questions.
When
the
decision
for
supporting
or
not
Blazer
will
be
sounded
like
Yoda
didn't
it,
it
will
soon
I
hope,
I
mean
we're
continuing
the
experiment.
The
experiment
is
going
well.
C
B
B
C
But
that's
part
of
determining
what
a
minimal
Viable
Product
is
from
one
Oh
is
like
well,
obviously
has
to
be
fast
enough
in
order
to
build
the
reasonable
type
of
apps
that
people
want
to
so
yeah
we're
not
going
to
ship
it
if
you
can't
build
apps
on
it,
but
yeah
I'm,
not
promising
anything.
I'm,
hoping
and
I
probably
believe
it'll
happen
at
some
point,
but
we
don't
have
a
timeline.
C
Yet
Brian
asks
have
their
the
server
with
net
core
to
one
on
a
bun
to
1404
and
ran
into
100%
CPU
utilization
memory
leak
in
the
app
after
migration
is
there
anything
I
should
look
for
into
one
when
debugging,
this
not
sure
I'd
like
a
bug,
and
then
we
can
hopefully
get
some
folks
to
help
you
out.
There
is
a
wiki
page
on
the
dotnet
core
repo
that
has
a
whole
bunch
of
instructions
on
how
to
do
memory,
memory,
analysis
and
profiling
on
Linux,
which
is
what
you'll
probably
need
to
end
up
doing.
C
If
you
actually
just
want
to
look
at
a
like,
do
some
actual
analysis
like
there's
some
instructions,
you
can
follow
to
capture
a
perfu
profile,
which
you
can
then
open
in
perfu
on
windows
or
to
capture
like
an
elf
dump,
which
you
can
then
analyze
using
some
Linux
style
tools
beyond
that,
it's
kind
of
hard
to
give
you
any
specific
data
in
this
type
of
menu.
So
alright
awesome,
oh,
and
he
says
it
was
a
dotnet
core
one,
one,
two,
two
on
migration:
okay,
yeah!
C
That
is
a
lot
more
significant
I'm
going
through
that
myself
with
the
live,
a
speed
net
website,
it's
still
running
on
doc.
They
call
one
one.
Even
though
I
did
those
videos
like
a
year
and
a
half
ago
where
I
moved
it
to
I,
never
deployed
it,
and
so
I
have
to
I'm
still
I'm,
actually
redoing
it
going
from
one
month
or
two
and
the
identity
stuff.
The
old
stuff
was
quite
breaking
between
1
1,
&,
2,
oh
and
so
getting
over.
C
That
hump
took
a
couple
hours
and
then
I
have
to
go
through
and
do
the
razor
pages
conversion
again
as
well,
which
now
is
easier
because
I've
done
it
a
couple
times
now,
but
yeah
it's
a
little
bit
of
work
going
from
1
1
to
2,
2
or
2
1
going
from
202
to
1
is
fairly
trivial.
It's
just
update
a
couple
things
in
your
files
and
off
you
go
so
alright
time.