BC DOTNETHOTRELOAD
Saved by @m4rc0v0nh4g3n

So, there have been some things going on with .NET Hot Reload you may have heard of this week. It's an important issue. Others had it covered so I thought I'd hang back, but I've seen calls for more voices, so here's mine. 🧡 1/

 Some background: Microsoft merged a PR that removed Hot Reload from the .NET 6 despite it working, an unusual move, and said it was due to prioritization for Visual Studio. There has been lots of backlash, snark, and attempts to reinstate it as a result. 2/
First up: Lots of amazing people work at MS who care about OSS and the community. Folks I continue to look up to. MS contains multitudes, and I think we'd all do well to keep that in mind. I'm rooting for them. 3/
On to the opinion section-- This decision is troubling for a bunch of reasons: 1) The surprise factor 2) The transparent business interest driving it while pretending otherwise 3) the communication around it 4) The implication of those business moves for the larger community. 4/
1) Surprises: this code was working, in an RC release, and people were starting to use it. It had been touted as a great feature of .NET 6. Then it was just gone, "de-prioritized". But de-prioritized doesn't mean it has to be removed. Patterns exist for flagging it, etc. 5/
My initial reaction was "well, MS has to support it, so it's only fair that they get to prioritize or not what they take on". I sympathized with MS. But then I realized it was essentially feature complete and usable, and things seemed fishier from there. 6/
2) Business interest: then the Verge piece came out saying that an MS CVP is essentially clawing this stuff back from OSS and wants to make it a proprietary feature of Visual Studio for business reasons. Oof. That's really not OK. 7/
MS should be all about making profit. But I wanted to believe they'd learned a lesson about making profit at the expense of community and "bigger tent" strategy. This flies in the face that. Terrible business decision. Squanders goodwill. /8
3) Communication: Initially I thought this was poor communication about readiness. I was going to suggest longer explanations in PRs, a call for the community to help, an open discussion on the roadmap sooner. But since the Verge article, I'm realizing it wasn't about that. 9/
This truly does seem to be the "old" Microsoft rearing its head again, and trying to sneak it in under the radar with vague corporate speak around priorities. That's very disheartening. And it does make me mad. 10/
4) Implications: The reason it makes me mad is that I truly feel that, warts and all, we're working toward a better place in .NET OSS. And the MS turnaround has been such a big part of that. For a CVP to endanger that is just bananas reckless. 11/
With one move, this decision gravely undermines the idea that .NET works in the open, that it builds for community first, that it wants to be a player in an overall ecosystem vs "just get yours" mentality for its product teams. It is actually a big deal. 12/
So, how can MS fix this? 1) Revert that PR if it's being held back for any reason other than quality and/or completeness. 2) Re-affirm that this was a mistake, both of leadership vision and of communication. 3) Work toward a unified approach to OSS and ensure CVPs respect it. 13/
Since MS hasn't fixed it yet, it sounds like the community is going to. Forks are beginning to take place of these tools. This is probably the appropriate thing to happen. If the community wants the tooling and MS won't look out for it in this case, 14/
Then "we'll do it ourselves" is the correct response. Looking forward to seeing how I might jump in there.

MS: This is not a good look. Do better. Listen to your OSS veterans. They have your best interests at heart. 15/
OSS is more than just tech. It is also a social contract and a community you agree to participate in alongside your most ardent fans and adopters. Don't take that for granted. There are many inside who know that already. Elevate them. (fin) 16/16.
17/16: I stink at tweet threads and forgot links because of course I did.

* Original PR with vague wording and blog post link: https://t.co/5fpHvtiLan

* The Verge article: https://t.co/wHkGETk2PI

* Great blog by @dustinmoris on the topic: https://t.co/gZBknsbRnX
18/16: Lastly, I'll say that I think folks are trying to work on this internally. I see you and I love you for it. Corporate culture change is so difficult. You have my utmost respect.

You May Also Like

JayneshKasliwal
JayneshKasliwal
@JayneshKasliwal
ULTIMATE GUIDE TO 21 and 200 Moving Average
SUNDAY THREAD πŸ”–
A trend Following System That will Help You Improve Trading immensely.

RETWEET AND SHARE πŸ”„
@kuttrapali26 @AmitabhJha3
#stocks #StockMarket
1/n

Moving averages
EMA and SMA
1. Exponential MovingΒ Average (EMA) is similar to Simple Moving Average (SMA), measuring trend direction over a period of time.
2. However, whereas SMA simply calculates an average of price data, EMA applies more weight to data that is more current
2/


21 EMA : SHORT TERM TREND
1. Calculates the Average Price of past 21 days
2. A stock above 21 ema is in strong momentum , which will give pullbacks to 21 ema again and again.
3. Stock above 21 ema should never be shorted so as to stay with the trend
3/n

3. A stock which moves 10-15% above 21 ema will be too extended and hence will generally pullback
Stocks take dynamic support on 21 ema
4. You can Short only if its too extended like 15 to 20% from 21 ema ( Not advised )
#ADANIPOWER:
#pnbhousing
4/n


1. Whenever 21 ema is sloping upwards its called uptrend
2. Whenever 21 ema is sloping downwards its called dowtrend
3. Whenever 21 ema is sideways its called consolidation
⏫Buy in uptrend
⏬Sell in downtrend
Examples:
5/n
MOVINGAVERAGES , MOVING AVERAGE 20021 , ALL
Billy Bostickson \U0001f3f4\U0001f441&\U0001f441 \U0001f193
Billy Bostickson πŸ΄πŸ‘&πŸ‘ ...
@BillyBostickson
Tip from the Monkey
Pangolins, September 2019 and PLA are the key to this mystery
Stay Tuned!


1. Yang


2. A jacobin capuchin dangling a flagellin pangolin on a javelin while playing a mandolin and strangling a mannequin on a paladin's palanquin, said Saladin
More to come tomorrow!


3. Yigang Tong
https://t.co/CYtqYorhzH
Archived: https://t.co/ncz5ruwE2W


4. YT Interview
Some bats & pangolins carry viruses related with SARS-CoV-2, found in SE Asia and in Yunnan, & the pangolins carrying SARS-CoV-2 related viruses were smuggled from SE Asia, so there is a possibility that SARS-CoV-2 were coming from
ALL
Advertisement
KrishnaLeela
KrishnaLeela
@Talesofkrishna
πŸŒΏπ‘»π’‰π’† π’”π’•π’π’“π’š 𝒐𝒇 𝒂 𝑺𝒕𝒂𝒓 : 𝑫𝒉𝒓𝒖𝒗𝒂 & π‘½π’Šπ’”π’‰π’π’–

Once upon a time there was a Raja named Uttānapāda born of Svayambhuva Manu,1st man on earth.He had 2 beautiful wives - Suniti & Suruchi & two sons were born of them Dhruva & Uttama respectively.
#talesofkrishna https://t.co/E85MTPkF9W


Now Suniti was the daughter of a tribal chief while Suruchi was the daughter of a rich king. Hence Suruchi was always favored the most by Raja while Suniti was ignored. But while Suniti was gentle & kind hearted by nature Suruchi was venomous inside.
#KrishnaLeela


The story is of a time when ideally the eldest son of the king becomes the heir to the throne. Hence the sinhasan of the Raja belonged to Dhruva.This is why Suruchi who was the 2nd wife nourished poison in her heart for Dhruva as she knew her son will never get the throne.


One day when Dhruva was just 5 years old he went on to sit on his father's lap. Suruchi, the jealous queen, got enraged and shoved him away from Raja as she never wanted Raja to shower Dhruva with his fatherly affection.


Dhruva protested questioning his step mother "why can't i sit on my own father's lap?" A furious Suruchi berated him saying "only God can allow him that privilege. Go ask him"
RELIGION
Brian Cates
Brian Cates
@drawandstrike
Trump is gonna let the Mueller investigation end all on it's own. It's obvious. All the hysteria of the past 2 weeks about his supposed impending firing of Mueller was a distraction. He was never going to fire Mueller and he's not going to


Mueller's officially end his investigation all on his own and he's gonna say he found no evidence of Trump campaign/Russian collusion during the 2016 election.

Democrats & DNC Media are going to LITERALLY have nothing coherent to say in response to that.

Mueller's team was 100% partisan.

That's why it's brilliant. NOBODY will be able to claim this team of partisan Democrats didn't go the EXTRA 20 MILES looking for ANY evidence they could find of Trump campaign/Russian collusion during the 2016 election

They looked high.

They looked low.

They looked underneath every rock, behind every tree, into every bush.

And they found...NOTHING.

Those saying Mueller will file obstruction charges against Trump: laughable.

What documents did Trump tell the Mueller team it couldn't have? What witnesses were withheld and never interviewed?

THERE WEREN'T ANY.

Mueller got full 100% cooperation as the record will show.
POLITICS
Roger Grosse
Roger Grosse
@RogerGrosse
Important paper from Google on large batch optimization. They do impressively careful experiments measuring # iterations needed to achieve target validation error at various batch sizes. The main "surprise" is the lack of surprises. [thread]

https://t.co/7QIx5CFdfJ


The paper is a good example of lots of elements of good experimental design. They validate their metric by showing lots of variants give consistent results. They tune hyperparamters separately for each condition, check that optimum isn't at the endpoints, and measure sensitivity.

They have separate experiments where the hold fixed # iterations and # epochs, which (as they explain) measure very different things. They avoid confounds, such as batch norm's artificial dependence between batch size and regularization strength.

When the experiments are done carefully enough, the results are remarkably consistent between different datasets and architectures. Qualitatively, MNIST behaves just like ImageNet.

Importantly, they don't find any evidence for a "sharp/flat optima" effect whereby better optimization leads to worse final results. They have a good discussion of experimental artifacts/confounds in past papers where such effects were reported.
MACHINE LEARNING