Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
en:modul:m291:learningunits:lu04:theorie:01 [2025/01/22 13:36] – [Frameworks vs. Library] vdemiren:modul:m291:learningunits:lu04:theorie:01 [2025/03/07 07:57] (aktuell) vdemir
Zeile 1: Zeile 1:
-====== LU04a - Framework vs. Library =====+====== LU04a - Framework VS Library =====
  
 ===== Learning objectives ===== ===== Learning objectives =====
-  - Definition what a software library is +  - Explaining what a software library is 
-  - Definition what a framework is +  - Definingwhat a framework is 
-  - Names the differences of both+  - Naming the differences of both 
 +  - Explaining the Who-Calls-Who Principle
  
 ===== Introduction ===== ===== Introduction =====
Zeile 13: Zeile 14:
 ===== Library ===== ===== Library =====
 A software library is a collection of pre-written, reusable code that provides specific functionality for developers. Libraries simplify programming tasks by offering modules or functions for common operations, such as handling data, managing files, or creating user interfaces. Unlike frameworks, libraries are less prescriptive, allowing developers to call and integrate them as needed without imposing strict design patterns. A software library is a collection of pre-written, reusable code that provides specific functionality for developers. Libraries simplify programming tasks by offering modules or functions for common operations, such as handling data, managing files, or creating user interfaces. Unlike frameworks, libraries are less prescriptive, allowing developers to call and integrate them as needed without imposing strict design patterns.
 +
  
 ===== Framework ===== ===== Framework =====
 A framework is a structured platform or foundation for developing applications, offering pre-written code, tools, and guidelines to streamline the process. It provides a standardized way to build and deploy software, saving time and ensuring consistency. Frameworks support specific languages or domains, such as web development (Django, Angular) or data analysis (TensorFlow), enabling efficient and organized coding practices. A framework is a structured platform or foundation for developing applications, offering pre-written code, tools, and guidelines to streamline the process. It provides a standardized way to build and deploy software, saving time and ensuring consistency. Frameworks support specific languages or domains, such as web development (Django, Angular) or data analysis (TensorFlow), enabling efficient and organized coding practices.
  
 +{{ :en:modul:m291:learningunits:lu04:theorie:was_ist_ein_framework_in_der_programmierung.mp4 | Was ist ein Framework in der Programmierung? }}
 ===== Summary ===== ===== Summary =====
  
 {{:en:modul:m291:learningunits:lu04:theorie:who_calls_who.jpg?800| Who-calls-who diagram }} {{:en:modul:m291:learningunits:lu04:theorie:who_calls_who.jpg?800| Who-calls-who diagram }}
 +{{:en:modul:m291:learningunits:lu04:theorie:framework_vs._library.png?800|  Quelle: https://medium.com/@vinciabhinav7/library-vs-frameworks-c7fae502bbcb}}
  
 Libraries and frameworks are tools that simplify software development by providing pre-written code. Libraries offer reusable functions for specific tasks, giving developers control over when and how to use them. Frameworks, on the other hand, define a structured architecture, requiring developers to work within their rules. The "who-calls-who" distinction highlights that in libraries, the developer calls the library, while in frameworks, the framework calls the developer’s code. Libraries and frameworks are tools that simplify software development by providing pre-written code. Libraries offer reusable functions for specific tasks, giving developers control over when and how to use them. Frameworks, on the other hand, define a structured architecture, requiring developers to work within their rules. The "who-calls-who" distinction highlights that in libraries, the developer calls the library, while in frameworks, the framework calls the developer’s code.
  
 ===== Who-Calls-Who Principle ===== ===== Who-Calls-Who Principle =====
-There is also another aspect, which claims to explain the difference between frameworks and libraries: The Who-Calls-Who approach+There is also another aspect, which claims to explain the difference between frameworks and libraries: The Who-Calls-Who-principle
  
 {{ :en:modul:m291:learningunits:lu04:theorie:what_is_the_difference_between_a_framework_and_a_library.mp4 | Who-Calls-Who-Approach}} {{ :en:modul:m291:learningunits:lu04:theorie:what_is_the_difference_between_a_framework_and_a_library.mp4 | Who-Calls-Who-Approach}}
Zeile 47: Zeile 51:
 You will find a list with JavaScript-Libraries und Frameworks including an explaination and a rathing as follows: [[https://www.ionos.de/digitalguide/websites/web-entwicklung/beliebte-javascript-frameworks-und-bibliotheken/ | here ]]. You will find a list with JavaScript-Libraries und Frameworks including an explaination and a rathing as follows: [[https://www.ionos.de/digitalguide/websites/web-entwicklung/beliebte-javascript-frameworks-und-bibliotheken/ | here ]].
  
 +----
 +[[https://creativecommons.org/licenses/by-nc-sa/4.0/|{{https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png}}]] Volkan Demir
  
  • en/modul/m291/learningunits/lu04/theorie/01.1737549408.txt.gz
  • Zuletzt geändert: 2025/01/22 13:36
  • von vdemir