Computerprogram (Danish Wikipedia)

Analysis of information sources in references of the Wikipedia article "Computerprogram" in Danish language version.

refsWebsite

Global rank Danish rank

15web.archive.org

1^st place

3theregister.com

3,700^th place

low place

2ordnet.dk

7,195^th place

19^th place

1copenhagensoftware.com

low place

1uu.nl

2,467^th place

2,557^th place

1books.google.com

3^rd place

25^th place

1doi.org

2^nd place

13^th place

1worldcat.org

5^th place

36^th place

1theguardian.com

12^th place

35^th place

1olemiss.edu

9,088^th place

low place

1computer.org

5,196^th place

low place

1version2.dk

low place

310^th place

1cisa.gov

low place

1microsoft.com

153^rd place

528^th place

1repec.org

4,270^th place

4,076^th place

1dankaminsky.com

low place

books.google.com

Evans 2018, s. 21. Evans, Claire L. (2018). Broad Band: The Untold Story of the Women Who Made the Internet. New York: Portfolio/Penguin. ISBN 9780735211759.

cisa.gov

June 26, 2024, cisa.gov: Exploring Memory Safety in Critical Open Source Projects, backup Citat: "...We encourage others to build on this analysis to further expand our collective understanding of memory-unsafety risk in OSS, evaluate approaches—such as targeted rewrites of critical components in memory-safe languages—to reducing this risk, and to continue efforts to drive risk-reducing action by software manufacturers. For those considering further investment in memory safe programming practices, we recommend two references: The Case for Memory Safe Roadmaps and the December 2023 report on memory safety by the Technical Advisory Council of CISA’s Cybersecurity Advisory Committee.37..."

computer.org

"Embedded Software—Technologies and Trends". IEEE Computer Society. maj-juni 2009. Arkiveret fra originalen 28. oktober 2013. Hentet 6. november 2013.{{cite web}}: CS1-vedligeholdelse: Dato-format (link)

copenhagensoftware.com

"Arkiveret kopi". Arkiveret fra originalen 16. marts 2021. Hentet 11. marts 2021.

dankaminsky.com

Kaminsky, Dan (1999). "Why Open Source Is The Optimum Economic Paradigm for Software". Arkiveret fra originalen 22. maj 2012. Hentet 24. maj 2019.

doi.org

Fuegi, J.; Francis, J. (2003). "Lovelace & Babbage and the creation of the 1843 'notes'". Annals of the History of Computing. 25 (4): 16-26. doi:10.1109/MAHC.2003.1253887. ISSN 1058-6180.

microsoft.com

msdn.microsoft.com

"MSDN Library". Arkiveret fra originalen 11. juni 2010. Hentet 14 juni 2010.

olemiss.edu

home.olemiss.edu

"System Software". The University of Mississippi. Arkiveret fra originalen 30. maj 2001. Hentet 24. maj 2019.

ordnet.dk

"ordnet.dk: software". Arkiveret fra originalen 16. februar 2021. Hentet 26. maj 2019.
"ordnet.dk: computerprogram". Arkiveret fra originalen 16. februar 2021. Hentet 26. maj 2019.

repec.org

ideas.repec.org

v. Engelhardt, Sebastian (2008). "The Economic Properties of Software". Jena Economic Research Papers. 2 (2008-045). Arkiveret fra originalen 5. januar 2016. Hentet 24. maj 2019.

theguardian.com

"Ada Lovelace honoured by Google doodle". The Guardian. 10. december 2012. Arkiveret fra originalen 25. juni 2013. Hentet 25. november 2018.

theregister.com

2024-09-20, theregister.com: CISA boss: Makers of insecure software are the real cyber villains. Write better code, urges Jen Easterly. And while you're at it, give crime gangs horrible names like 'Evil Ferret', backup
28 Jun 2024, theregister.com: CISA looked at C/C++ projects and found a lot of C/C++ code. Wanna redo any of it in Rust? So, so many lines of memory-unsafe routines in crucial open source, and unsafe dependencies, backup Citat: "...Memory-safe languages, like C#, Go, Java, Python, Rust, and Swift, handle memory management for the developer, reducing the opportunity to make memory errors...The 2015 stable release of Rust, a language with strong memory-safety guarantees, gave tech firms a non-aligned systems language they could use to avoid the problems with memory-unsafe code. The competitive implications of adopting languages with strong corporate associations, like C# (Microsoft), Go (Google), Swift (Apple), or Java (Oracle) may have helped make Rust more appealing. But it took a few years for Rust to mature and catch on..."
3 Aug 2024, theregister.com: DARPA suggests turning old C code automatically into Rust – using AI, of course. Who wants to make a TRACTOR pull request?, backup Citat: "...The term stands for TRanslating All C TO Rust. It's a DARPA project that aims to develop machine-learning tools that can automate the conversion of legacy C code into Rust. The reason to do so is memory safety. Memory safety bugs, such buffer overflows, account for the majority of major vulnerabilities in large codebases. And DARPA's hope is that AI models can help with the programming language translation, in order to make software more secure..."I think all languages are about trade-offs, but certainly at the kernel-level it makes sense to move part of the code to Rust," he said..."

uu.nl

cs.uu.nl

"Compiler construction". Arkiveret fra originalen 2. november 2013. Hentet 24. maj 2019.

version2.dk

2024-09-20, version2.dk: USA’s cyberchef: Dårlige software-udviklere er den største trussel mod sikkerheden. CISA-chefen Jen Easterly skoser teknologileverandører for at levere produkter med indbyggede sikkerhedsproblemer, der åbner dørene for cyberangreb, backup Citat: "...»Vi har ikke et cybersikkerhedsproblem – vi har et softwarekvalitetsproblem. Vi har ikke brug for flere sikkerhedsprodukter – vi har brug for mere sikre produkter,« sagde chefen for den amerikanske cybersikkerhedsmyndighed CISA (Cybersecurity and Infrastructure Security Agency) Jen Easterly på en konference onsdag ifølge The Register. »Sandheden er: Teknologileverandører er de personer, der bygger problemer« ind i deres produkter, som derefter »åbner dørene for skurke, så de kan angribe deres ofre.«..."

web.archive.org

"ordnet.dk: software". Arkiveret fra originalen 16. februar 2021. Hentet 26. maj 2019.
"Arkiveret kopi". Arkiveret fra originalen 16. marts 2021. Hentet 11. marts 2021.
"ordnet.dk: computerprogram". Arkiveret fra originalen 16. februar 2021. Hentet 26. maj 2019.
"Compiler construction". Arkiveret fra originalen 2. november 2013. Hentet 24. maj 2019.
"Ada Lovelace honoured by Google doodle". The Guardian. 10. december 2012. Arkiveret fra originalen 25. juni 2013. Hentet 25. november 2018.
"System Software". The University of Mississippi. Arkiveret fra originalen 30. maj 2001. Hentet 24. maj 2019.
"Embedded Software—Technologies and Trends". IEEE Computer Society. maj-juni 2009. Arkiveret fra originalen 28. oktober 2013. Hentet 6. november 2013.{{cite web}}: CS1-vedligeholdelse: Dato-format (link)
2024-09-20, version2.dk: USA’s cyberchef: Dårlige software-udviklere er den største trussel mod sikkerheden. CISA-chefen Jen Easterly skoser teknologileverandører for at levere produkter med indbyggede sikkerhedsproblemer, der åbner dørene for cyberangreb, backup Citat: "...»Vi har ikke et cybersikkerhedsproblem – vi har et softwarekvalitetsproblem. Vi har ikke brug for flere sikkerhedsprodukter – vi har brug for mere sikre produkter,« sagde chefen for den amerikanske cybersikkerhedsmyndighed CISA (Cybersecurity and Infrastructure Security Agency) Jen Easterly på en konference onsdag ifølge The Register. »Sandheden er: Teknologileverandører er de personer, der bygger problemer« ind i deres produkter, som derefter »åbner dørene for skurke, så de kan angribe deres ofre.«..."
2024-09-20, theregister.com: CISA boss: Makers of insecure software are the real cyber villains. Write better code, urges Jen Easterly. And while you're at it, give crime gangs horrible names like 'Evil Ferret', backup
28 Jun 2024, theregister.com: CISA looked at C/C++ projects and found a lot of C/C++ code. Wanna redo any of it in Rust? So, so many lines of memory-unsafe routines in crucial open source, and unsafe dependencies, backup Citat: "...Memory-safe languages, like C#, Go, Java, Python, Rust, and Swift, handle memory management for the developer, reducing the opportunity to make memory errors...The 2015 stable release of Rust, a language with strong memory-safety guarantees, gave tech firms a non-aligned systems language they could use to avoid the problems with memory-unsafe code. The competitive implications of adopting languages with strong corporate associations, like C# (Microsoft), Go (Google), Swift (Apple), or Java (Oracle) may have helped make Rust more appealing. But it took a few years for Rust to mature and catch on..."
June 26, 2024, cisa.gov: Exploring Memory Safety in Critical Open Source Projects, backup Citat: "...We encourage others to build on this analysis to further expand our collective understanding of memory-unsafety risk in OSS, evaluate approaches—such as targeted rewrites of critical components in memory-safe languages—to reducing this risk, and to continue efforts to drive risk-reducing action by software manufacturers. For those considering further investment in memory safe programming practices, we recommend two references: The Case for Memory Safe Roadmaps and the December 2023 report on memory safety by the Technical Advisory Council of CISA’s Cybersecurity Advisory Committee.37..."
3 Aug 2024, theregister.com: DARPA suggests turning old C code automatically into Rust – using AI, of course. Who wants to make a TRACTOR pull request?, backup Citat: "...The term stands for TRanslating All C TO Rust. It's a DARPA project that aims to develop machine-learning tools that can automate the conversion of legacy C code into Rust. The reason to do so is memory safety. Memory safety bugs, such buffer overflows, account for the majority of major vulnerabilities in large codebases. And DARPA's hope is that AI models can help with the programming language translation, in order to make software more secure..."I think all languages are about trade-offs, but certainly at the kernel-level it makes sense to move part of the code to Rust," he said..."
"MSDN Library". Arkiveret fra originalen 11. juni 2010. Hentet 14 juni 2010.
v. Engelhardt, Sebastian (2008). "The Economic Properties of Software". Jena Economic Research Papers. 2 (2008-045). Arkiveret fra originalen 5. januar 2016. Hentet 24. maj 2019.
Kaminsky, Dan (1999). "Why Open Source Is The Optimum Economic Paradigm for Software". Arkiveret fra originalen 22. maj 2012. Hentet 24. maj 2019.

worldcat.org

Fuegi, J.; Francis, J. (2003). "Lovelace & Babbage and the creation of the 1843 'notes'". Annals of the History of Computing. 25 (4): 16-26. doi:10.1109/MAHC.2003.1253887. ISSN 1058-6180.