Chris Krycho

Thanks everyone for continued contributions. After a few more rounds of discussion in Framework Core, we've decided to make two tweaks to the proposal here: 1. We will do 12...

@jenweber very much noted, but: as it stands this will not require any change in cadence to increase the number of blog posts. Only major version releases will happen more...

@robbytx thanks for that comment—getting serious feedback is why we do this process, so I’m really glad that (a) you felt heard and (b) you feel comfortable with the outcome....

The Framework team talked about this last Friday and everyone is on board, so it is now going into Final Comment Period to merge!

This RFC has been in FCP for over a week now and we all agreed that it's ready to go at the most recent Framework Core team meetings, so: merging...

Roughly: classic classes themselves will go away. We could remove this earlier than those, though, so please do include it in that list!

My own take is twofold: 1. "Intimate API" was a bad idea. I know why we did it, but sometimes it's possible to *over*-do trying to help people. When you...

We discussed this RFC at today’s Framework Core meeting and decided to move it into **Final Comment Period to *Close***. (FCP to close means that we will close this next...

@NullVoxPopuli your response here is part of why I had actually suggested breaking this into two separate RFCs: *dynamic/client-side template compilation* is indeed finicky, but it does not require the...

@NullVoxPopuli > I'm not 100% sure what's controversial, even after reading this -- but maybe I can try re-phrasing and we can see how close I am? (I like lists)...