Views : 530,663
Genre: Education
Date of upload: Aug 5, 2021 ^^
Rating : 4.935 (235/14,145 LTDR)
RYD date created : 2022-04-09T12:26:06.934743Z
See in json
Top Comments of this video!! :3
Thanks for that great explanation! I speak English and Spanish and this is by far the best video in both languages that Iāve found on the web explaining the difference between all of the confusing concepts of .Net, I was so frustrated that I couldnāt found a video or document that explains all of that but you have done it in a easy and excellent way, thanks a lot!!!!!!!
22 |
I would have loved some graphics to accompany this discussion, but even without graphics the representation was easy to follow. Nice job.
I've worked with Microsoft software/systems since the 80's and one thing I can say is you really need to understand the historical progression of its systems to really appropriately understand where thing are. This simple discussion of the progression and reasoning behind going from Framework to Core is an example of how drawing that historical background is truly helpful.
11 |
Wondering why you havenāt mentioned the support libraries as well. I think this is what you meant when you used the term āabstraction layerā. Any language on a given platform requires all kinds of helpers to do things like open files, communicate via the network, print, and common tools like lists, stacks, numerical processing, etc. Framework required pre-installed libraries. These libraries tended to be monolithic (large and not very modular). Core modularized and packaged parts of the framework libraries allowing developers to pick and choose the parts of the ālibrariesā they needed for an application. This was necessary for a couple of reasons. One, cloud servers needed to be fast to spin up. Requiring that the entire set of framework libraries be present increased storage consumption and install time. Two, the framework had a bigger footprint because it was all one big thing and it would load and initialize things that the app may never use. So modularizing it and enabling the dev to specify only what was needed made application installation smaller and faster and it also made application startup smaller and faster. Framework = monolithic install. Core = modular packaging.
172 |
@droam129
2 years ago
Iāve probably googled this question a dozen times over the past couple years, and this is the first time Iāve understood it. Thank you, Tim.
845 |