Developers love automating solutions to their problems, and with the rise of generative AI, this concept is likely to be applied to both the creation, maintenance, and the improvement of code at an entirely new level.
OBITUARY
COMPUTER AND INFORMATION TECHNOLOGY
Computer pioneer Niklaus Wirth died on 1 January 2024, just weeks before his 90th birthday. The long-serving ETH Professor of Computer Science achieved world fame by developing the Pascal programming language in the 1970s. In 1984, he became the only German-speaking computer scientist yet to have received the Turing Award, which is regarded as the Nobel Prize for computer science.
Top 5 Open Source Visio Alternatives in 2024
The drawbacks of Microsoft Visio will make the app unsuitable for many people. That is why an open-source alternative for Visio can be the ideal solution for some. Learn the 5 best options to install today and start practicing your drawing skills! https://edrawmax.wondershare.com/visio-alternative/open-source-visio-alternative.html
- mentions Dia
Microsoft Visio is one of the most popular diagramming platforms backed by a reliable company name. While Microsoft Visio is undeniably an innovative diagramming tool with robust features, it faces criticism for being less user-friendly and having high pricing plans.
“Big design up front is dumb. Doing no design up front is even dumber.” This quote epitomises what I’ve seen during our journey from “big design up front” in the 20th century, to “emergent design” and “evolutionary architecture” in the 21st. In their desire to become “agile”, many teams seem to have abandoned architectural thinking, upfront design, documentation, diagramming, and modelling. In many cases, this is a knee-jerk reaction to the heavy bloated processes of times past, and in others, it’s a misinterpretation and misapplication of the agile manifesto. As a result, many of the software design activities I witness these days are very high-level and superficial in nature. The resulting output, typically an ad hoc sketch on a whiteboard, is usually ambiguous and open to interpretation, leading to a situation where the underlying solution can’t be communicated, assessed, or reviewed. If you’re willing to consider that upfront design is about creating a sufficient starting point, rather than creating a perfect end-state, you soon realise that a large amount of the costly rework and “refactoring” seen on many software development teams can be avoided. Join me for a discussion about the lost art of software design, and how we can reintroduce it to help teams scale and move faster.
In Simon Brown’s talk at AOTB 2019 he explores the visual communication of software architecture based upon a decade of Simon’s experiences working with software development teams large and small across the globe.
He looks at what is commonplace today, the importance of creating a shared vocabulary, diagram notation, and the value of creating a lightweight model to describe your software system using the “C4 model”, which he created as a way to help software development teams describe and communicate software architecture, both during up-front design sessions and when retrospectively documenting an existing codebase.
It’s very likely that the majority of the software architecture diagrams you’ve seen are a confused mess of boxes and lines. Following the publication of the Manifesto for Agile Software Development in 2001, teams have abandoned UML, discarded the concept of modelling and instead place a heavy reliance on conversations centered around incoherent whiteboard diagrams or shallow “Marketecture” diagrams created with Visio. Moving fast and being Agile requires good communication, yet software development teams struggle with this fundamental skill. A good set of software architecture diagrams are priceless for aligning a team around a shared vision and for getting new-joiners productive fast.
Based on Python and PyQT5, serial-plotter is a new beginning, with an emphasis on correct data acquisition and real-time data visualization with a little processing thrown in. Think, acquire data, show the raw values as well as the mean value, and RMS noise all on the same windows side-by-side, all of which is easily tweakable with a bit of programming using Numpy and Matplotlib.
One of the established and most popular programming languages is the C programming language. It is relatively easy to learn, and highly practical.
Maybe surprisingly, the C programming language keeps evolving, slowly and carefully. If you have GCC 13 or LLVM (Clang) 16, you already have a compiler with some of the features from the latest standard (C23).
A blend of proprietary and open source licensing is becoming more popular and is posing a threat to open source software.
In a notable shift within the software industry, Delayed Open Source Publication (DOSP) has emerged as a nuanced strategy blending proprietary and open source licensing. This approach involves initially releasing software under a proprietary license, followed by a planned transition to an open source license.
Often these programs are released first as open source software and then re-released with a promise of eventually reappearing as an open source program. The Open Source Initiative (OSI) has released a study delving into DOSP’s history, patterns, and evolving trends.
Build applications faster than everCreate beautiful UI, generate clean code, and deploy to the app stores or web in one click. Fully extensible with custom code. https://flutterflow.io/
In 1995, Niklaus Wirth made a plea for lean software, decrying software that was “megabytes in size.” 30 years later, Bert Hubert makes the same plea, in a software development culture where garage door openers have millions of lines of code.
ChatGPT on nyt reilun vuoden ajan vallannut monenlaisia sovelluksia, mutta koodaajat olivat ehkäpä ensimmäinen ryhmä, joka ryhtyi täysipainoisesti hyödyntämään generatiivista tekoälyä. Mutta mihin koodarit käyttävät tekoälyä?
12 prosenttia käyttää tekoälyä koodinpätkien selittämiseen. Toieksi yleisintä on tekoälyn käyttäminen koodin optimointiin tai dokumenttin generointiin (9% haastatelluisa). Koodiesimerkkejä tekoälyät pyytää 8 prosenttia kehittäjistä. Lähes yhtä suosittua (7% haastatelluista) on koodin yksinkertaistaminen.
Haastatteluista selviää myös, että joka viides koodari käyttää tekoälyä työssään säännöllisesti. Joka kolmas käyttää tekoälyä ajoittain, mutta joka viides ei ole vielä kokeillut uusia AI-työkaluja. Vain joka neljäs tekoälyä apurinaan kokeillut ei pitänyt sen käyttämisestä.
FOSDEM 2024 There are vital lessons to be learned from the history of Unix, but they’re being forgotten. This is leading to truly vast amounts of wasted effort.
Apple just launched a new open-source programming language
News
By Luke Hughes published February 05, 2024
Apple wants to make configuration easy and scalable with Pkl
Have you ever been in a situation where you are looking at your Jira backlog and think that you have no idea what the title of the ticket means or what is supposed to be implemented in the scope of the ticket? Read on to learn about key requirements engineering tools: user stories and use cases.
Requirements engineering is a tricky business. Software requirements should be written in a concise manner but overly detailed requirements can also be a hindrance and an undue burden for the development process if applied every time. User stories and use cases are essential tools that, when applied correctly, can produce the most favorable outcome.
hterm is a JS library that provides a terminal emulator. It is reasonably fast, reasonably correct, and reasonably portable across browsers. https://github.com/chromium/hterm
One of the items that needed to be resolved was removal of part of the project that was written in Ruby as it is a dynamic language.
What is the background/reason for not allowing a dynamic language to be used in a secure setting? Is this the government being slow to adopt new technologies? Or do dynamic languages pose an additional security risk compared to static languages (ala C++ or Java)?
Only way to know for sure is if your acquaintances ask their employers for the reason. But I can risk a guess: static type checking is another layer that helps the correctness of mission-critical software. It won’t get rid of bugs, of course, but it’s a step in the right direction: the computer is doing some of the work for you. (Yes, I’m aware this is holy wars territory).
SEARCH
Programming language source code example on monitor
What Is Memory Safety, and What Does It Mean for Federal Agencies?
The Cybersecurity and Infrastructure Security Agency recently issued guidance on how to transition to memory-safe programming languages to reduce software vulnerabilities.
The C and C++ languages are unsafe. Instead, the U.S. National Security Agency would like devs to use memory-safe languages—because most security vulnerabilities are caused by bugs in memory usage.
Neal Ziring (pictured), the NSA Cybersecurity Directorate director, says all you programmers are making “simple mistakes” that are “still entirely too common.” He’s talking about problems such as buffer overflows and use-after-free bugs.
In the Holy Programming Language Wars, the lingua franca of system programming – also known as C – is often lambasted for being unsecure, error-prone, and plagued with more types of behavior that are undefined than ones that are defined by the C standards. Many programming languages were said to be ‘C killers’, yet C is still alive today. That didn’t stop the US White House’s Office of the National Cyber Director (ONCD) from putting out a report in which both C and C++ got lambasted for being ‘unsafe’ when it came to memory management.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
We are a professional review site that has advertisement and can receive compensation from the companies whose products we review. We use affiliate links in the post so if you use them to buy products through those links we can get compensation at no additional cost to you.OkDecline
766 Comments
Tomi Engdahl says:
https://ask.libreoffice.org/t/python-library-or-package-for-read-write-data-in-libre-office-calc/67713
https://pypi.org/project/pyoo/
Tomi Engdahl says:
https://imzye.com/Shell/bash/concurrency-in-bash/
Tomi Engdahl says:
Self-healing code is the future of software development
https://stackoverflow.blog/2023/12/28/self-healing-code-is-the-future-of-software-development/
Developers love automating solutions to their problems, and with the rise of generative AI, this concept is likely to be applied to both the creation, maintenance, and the improvement of code at an entirely new level.
Tomi Engdahl says:
https://developer.mozilla.org/en-US/docs/Web/API/SerialPort
https://www.npmjs.com/package/modbus-serial
Tomi Engdahl says:
Do better coders swear more, or does C just do that to good programmers?
For open source C code, curses mean quality, a recent bachelor’s thesis suggests.
https://arstechnica.com/science/2023/03/is-code-that-contains-swears-higher-quality-than-code-that-does-not/
Tomi Engdahl says:
https://nitor.com/fi/artikkelit/state-of-the-javascript-ecosystem-in-2023?fbclid=IwAR2Ml12L_uvoqndcPLu7KeHzG8UVKO5PZnC8c4mh_H6caO3Lw2v7khkx6oo_aem_AeiD0CXmFrTOWf0tHZP7R6J2EPzu9UZ706mI0h0w1v8So6VRY5lJcG7aQYdjB9Zhsz9d2ICvvpY33V5UWTqXbtGb
Tomi Engdahl says:
Computer pioneer Niklaus Wirth has died
https://ethz.ch/en/news-and-events/eth-news/news/2024/01/computer-pioneer-niklaus-wirth-has-died.html
OBITUARY
COMPUTER AND INFORMATION TECHNOLOGY
Computer pioneer Niklaus Wirth died on 1 January 2024, just weeks before his 90th birthday. The long-serving ETH Professor of Computer Science achieved world fame by developing the Pascal programming language in the 1970s. In 1984, he became the only German-speaking computer scientist yet to have received the Turing Award, which is regarded as the Nobel Prize for computer science.
Tomi Engdahl says:
The World Depends on 60-Year-Old Code No One Knows Anymore
https://www.pcmag.com/articles/ibms-plan-to-update-cobol-with-watson
Tomi says:
Python on suosituin, mutta C# oli viime vuoden ohjelmointikieli
https://etn.fi/index.php/13-news/15763-python-on-suosituin-mutta-c-oli-viime-vuoden-ohjelmointikieli
Tomi says:
Top 5 Open Source Visio Alternatives in 2024
The drawbacks of Microsoft Visio will make the app unsuitable for many people. That is why an open-source alternative for Visio can be the ideal solution for some. Learn the 5 best options to install today and start practicing your drawing skills!
https://edrawmax.wondershare.com/visio-alternative/open-source-visio-alternative.html
- mentions Dia
7 Best Online Visio Alternatives for Making Diagrams (Free & Paid)
https://edrawmax.wondershare.com/visio-alternative/open-source-visio-alternative.html
Microsoft Visio is one of the most popular diagramming platforms backed by a reliable company name. While Microsoft Visio is undeniably an innovative diagramming tool with robust features, it faces criticism for being less user-friendly and having high pricing plans.
Tomi says:
https://c4model.com/
Tomi says:
Simon Brown — The lost art of software design
https://www.youtube.com/watch?v=UzFpFQgeEyc
“Big design up front is dumb. Doing no design up front is even dumber.” This quote epitomises what I’ve seen during our journey from “big design up front” in the 20th century, to “emergent design” and “evolutionary architecture” in the 21st. In their desire to become “agile”, many teams seem to have abandoned architectural thinking, upfront design, documentation, diagramming, and modelling. In many cases, this is a knee-jerk reaction to the heavy bloated processes of times past, and in others, it’s a misinterpretation and misapplication of the agile manifesto. As a result, many of the software design activities I witness these days are very high-level and superficial in nature. The resulting output, typically an ad hoc sketch on a whiteboard, is usually ambiguous and open to interpretation, leading to a situation where the underlying solution can’t be communicated, assessed, or reviewed. If you’re willing to consider that upfront design is about creating a sufficient starting point, rather than creating a perfect end-state, you soon realise that a large amount of the costly rework and “refactoring” seen on many software development teams can be avoided. Join me for a discussion about the lost art of software design, and how we can reintroduce it to help teams scale and move faster.
Visualising software architecture with the C4 model – Simon Brown, Agile on the Beach 2019
https://www.youtube.com/watch?v=x2-rSnhpw0g
In Simon Brown’s talk at AOTB 2019 he explores the visual communication of software architecture based upon a decade of Simon’s experiences working with software development teams large and small across the globe.
He looks at what is commonplace today, the importance of creating a shared vocabulary, diagram notation, and the value of creating a lightweight model to describe your software system using the “C4 model”, which he created as a way to help software development teams describe and communicate software architecture, both during up-front design sessions and when retrospectively documenting an existing codebase.
It’s very likely that the majority of the software architecture diagrams you’ve seen are a confused mess of boxes and lines. Following the publication of the Manifesto for Agile Software Development in 2001, teams have abandoned UML, discarded the concept of modelling and instead place a heavy reliance on conversations centered around incoherent whiteboard diagrams or shallow “Marketecture” diagrams created with Visio. Moving fast and being Agile requires good communication, yet software development teams struggle with this fundamental skill. A good set of software architecture diagrams are priceless for aligning a team around a shared vision and for getting new-joiners productive fast.
Tomi says:
https://www.w3schools.com/react/
https://www.w3schools.com/react/showreact.asp?filename=demo2_react_test
Tomi Engdahl says:
https://hackaday.com/2024/01/29/need-a-serial-data-plotter-better-write-your-own/
Based on Python and PyQT5, serial-plotter is a new beginning, with an emphasis on correct data acquisition and real-time data visualization with a little processing thrown in. Think, acquire data, show the raw values as well as the mean value, and RMS noise all on the same windows side-by-side, all of which is easily tweakable with a bit of programming using Numpy and Matplotlib.
Tomi Engdahl says:
Microsoft seeks Rust developers to rewrite core C# code
Embrace, extend, and … port?
https://www.theregister.com/2024/01/31/microsoft_seeks_rust_developers/
Tomi Engdahl says:
https://www.tivi.fi/uutiset/these-are-the-10-worst-ways-to-demotivate-coders/6859beda-318a-48e4-be63-0c83907aab31?utm_source=Facebook&utm_medium=Paid_social&utm_campaign=Tivi_in_English_FB&utm_content=Tivi_in_English_FB&fbclid=IwAR0soHpTyLqSsYYthelaLUF0rlIgwWq_z3_2Y47U6oo8qDli_06LWjdDrsY_aem_AaGbRlVvghgOcCZDEtQhxDqpz8G-lEip-Fwblnchru-HmfquK2NRUToQhRGyCYjFbKd3qnt62T0DkZk7fYmH6rn4
Tomi Engdahl says:
C23: a slightly better C
https://lemire.me/blog/2024/01/21/c23-a-slightly-better-c/
One of the established and most popular programming languages is the C programming language. It is relatively easy to learn, and highly practical.
Maybe surprisingly, the C programming language keeps evolving, slowly and carefully. If you have GCC 13 or LLVM (Clang) 16, you already have a compiler with some of the features from the latest standard (C23).
Tomi Engdahl says:
https://www.fraktio.fi/blogi/rajapintakehitys-kokemuksiamme-sudenkuopista-ja-toimivista-periaatteista
Tomi Engdahl says:
https://www.qt.io/product/qt6/qml-book/ch13-networking-rest-api
https://stackoverflow.com/questions/21529266/http-post-request-from-a-pyqt-gui
https://github.com/pudymody/rest-client-qt
https://www.pythonguis.com/installation/install-qt-designer-standalone/
Tomi Engdahl says:
https://www.kiskolabs.com/investointilaskuri
Tomi Engdahl says:
https://thenewstack.io/where-does-the-time-go-rusts-problem-with-slow-compiles/
Tomi Engdahl says:
Delayed Open Source Publication Emerges as Open Source Rival
DOSP involves initially releasing software under a proprietary license, followed by a planned transition to an open source license.
https://thenewstack.io/delayed-open-source-publication-emerges-as-open-source-rival/
A blend of proprietary and open source licensing is becoming more popular and is posing a threat to open source software.
In a notable shift within the software industry, Delayed Open Source Publication (DOSP) has emerged as a nuanced strategy blending proprietary and open source licensing. This approach involves initially releasing software under a proprietary license, followed by a planned transition to an open source license.
Often these programs are released first as open source software and then re-released with a promise of eventually reappearing as an open source program. The Open Source Initiative (OSI) has released a study delving into DOSP’s history, patterns, and evolving trends.
Tomi Engdahl says:
Build applications faster than everCreate beautiful UI, generate clean code, and deploy to the app stores or web in one click. Fully extensible with custom code.
https://flutterflow.io/
FlutterFlow – sovelluskehitystä ilman koodausta
https://identio.fi/blogi/flutterflow-sovelluskehitysta-ilman-koodausta/
Miltä kuulostaisi, jos kertoisin, että on olemassa työkalu, jonka avulla kehitysaikaa voidaan lyhentää ja kustannuksia leikata? Liian hyvältä ollakseen totta?
Tomi Engdahl says:
https://github.com/klaasnicolaas/home-assistant-glow
Tomi says:
Understanding Inter-process Communication in Linux: Fork, Pipes, Shared Memory, and Message Queues
https://towardsdev.com/understanding-inter-process-communication-in-linux-fork-pipes-shared-memory-and-message-queues-2503a9e334ad
https://opensource.com/article/19/4/interprocess-communication-linux-networking
https://opensource.com/article/19/4/interprocess-communication-linux-channels
Tomi says:
https://towardsdev.com/understanding-inter-process-communication-in-linux-fork-pipes-shared-memory-and-message-queues-2503a9e334ad
https://www.apriorit.com/dev-blog/web-python-ipc-methods
Tomi says:
Python web servers
https://www.geeksforgeeks.org/flask-creating-first-simple-application/
https://bottlepy.org/docs/dev/
Tomi says:
Top Python Frameworks for Web Development in 2023
https://www.browserstack.com/guide/top-python-web-development-frameworks#:~:text=Top%20Python%20Frameworks%20for%20Web%20Development%20in%202023,Flask%20…%208%208.%20Bottle%20…%20More%20items
Top Python Frameworks for Web Development in 2023
1. Django
2. CherryPy
3. Pyramid
4. Grok
5. TurboGears
6. Web2Py
7. Flask
8. Bottle
9. Tornado
10. BlueBream
Tomi says:
List of 7 Best Python Frameworks to Consider For Your Web Project
https://www.monocubed.com/blog/top-python-frameworks/
Tomi Engdahl says:
In 1995, Niklaus Wirth made a plea for lean software, decrying software that was “megabytes in size.” 30 years later, Bert Hubert makes the same plea, in a software development culture where garage door openers have millions of lines of code.
Why Bloat Is Still Software’s Biggest Vulnerability A 2024 plea for lean software
https://spectrum.ieee.org/lean-software-development?share_id=8090172&socialux=facebook&utm_campaign=RebelMouse&utm_content=IEEE+Spectrum&utm_medium=social&utm_source=facebook&fbclid=IwAR3bCphRwSqYYsCNSZs3rrH3UENXJLCAU-gdXZ5Soer22-rZgJBI9uUoS54
This post is dedicated to the memory of Niklaus Wirth, a computing pioneer who passed away 1 January 2024.
Tomi says:
Näin koodaajat käyttävät tekoälyä
https://etn.fi/index.php/13-news/15846-naein-koodaajat-kaeyttaevaet-tekoaelyae
ChatGPT on nyt reilun vuoden ajan vallannut monenlaisia sovelluksia, mutta koodaajat olivat ehkäpä ensimmäinen ryhmä, joka ryhtyi täysipainoisesti hyödyntämään generatiivista tekoälyä. Mutta mihin koodarit käyttävät tekoälyä?
12 prosenttia käyttää tekoälyä koodinpätkien selittämiseen. Toieksi yleisintä on tekoälyn käyttäminen koodin optimointiin tai dokumenttin generointiin (9% haastatelluisa). Koodiesimerkkejä tekoälyät pyytää 8 prosenttia kehittäjistä. Lähes yhtä suosittua (7% haastatelluista) on koodin yksinkertaistaminen.
Haastatteluista selviää myös, että joka viides koodari käyttää tekoälyä työssään säännöllisesti. Joka kolmas käyttää tekoälyä ajoittain, mutta joka viides ei ole vielä kokeillut uusia AI-työkaluja. Vain joka neljäs tekoälyä apurinaan kokeillut ei pitänyt sen käyttämisestä.
Tomi Engdahl says:
https://hackaday.com/2024/02/15/linux-fu-curling-c/
Tomi Engdahl says:
Forgetting the history of Unix is coding us into a corner
The lessons of yesteryear’s OS are getting lost in translation
https://www.theregister.com/2024/02/16/what_is_unix/
FOSDEM 2024 There are vital lessons to be learned from the history of Unix, but they’re being forgotten. This is leading to truly vast amounts of wasted effort.
Tomi Engdahl says:
Google Spends $1 Million to Make Rust, C++ ‘Interoperable’
Eager to eliminate memory errors in C++-based Android apps, Google wants to make it easy for devs to write functionality in Rust instead.
https://thenewstack.io/google-spends-1-million-to-make-rust-c-interoperable/
Tomi Engdahl says:
List of open-source alternatives to everyday SaaS products.
https://github.com/btw-so/open-source-alternatives
Tomi Engdahl says:
https://www.techradar.com/pro/apple-just-launched-a-new-open-source-programming-language
Apple just launched a new open-source programming language
News
By Luke Hughes published February 05, 2024
Apple wants to make configuration easy and scalable with Pkl
Tomi Engdahl says:
https://www.karhuhelsinki.fi/blogi/tietotyyppien-sekamelskaa-wordpressissa/
Tomi Engdahl says:
Requirements Engineering: User Stories vs. Use Cases
https://www.valagroup.com/blog/requirements-engineering-user-stories-vs-use-cases/
Have you ever been in a situation where you are looking at your Jira backlog and think that you have no idea what the title of the ticket means or what is supposed to be implemented in the scope of the ticket? Read on to learn about key requirements engineering tools: user stories and use cases.
Requirements engineering is a tricky business. Software requirements should be written in a concise manner but overly detailed requirements can also be a hindrance and an undue burden for the development process if applied every time. User stories and use cases are essential tools that, when applied correctly, can produce the most favorable outcome.
Tomi Engdahl says:
https://www.infoq.com/news/2024/02/loco-new-framework-rust-rails/
Tomi Engdahl says:
https://hackaday.com/2024/02/19/linux-fu-forward-to-the-past/
Tomi Engdahl says:
terminal emulator for web
https://hterm.org/
Tomi Engdahl says:
hterm is a JS library that provides a terminal emulator. It is reasonably fast, reasonably correct, and reasonably portable across browsers.
https://github.com/chromium/hterm
Tomi Engdahl says:
Why does the US government disallow dynamic languages for secure projects?
https://softwareengineering.stackexchange.com/questions/206558/why-does-the-us-government-disallow-dynamic-languages-for-secure-projects
One of the items that needed to be resolved was removal of part of the project that was written in Ruby as it is a dynamic language.
What is the background/reason for not allowing a dynamic language to be used in a secure setting? Is this the government being slow to adopt new technologies? Or do dynamic languages pose an additional security risk compared to static languages (ala C++ or Java)?
Only way to know for sure is if your acquaintances ask their employers for the reason. But I can risk a guess: static type checking is another layer that helps the correctness of mission-critical software. It won’t get rid of bugs, of course, but it’s a step in the right direction: the computer is doing some of the work for you. (Yes, I’m aware this is holy wars territory).
Tomi Engdahl says:
https://fedtechmagazine.com/article/2024/02/memory-safety-perfcon#amp_tf=L%C3%A4hde%3A%20%251%24s&aoh=17090649790159&referrer=https%3A%2F%2Fwww.google.com&share=https%3A%2F%2Ffedtechmagazine.com%2Farticle%2F2024%2F02%2Fmemory-safety-perfcon
SEARCH
Programming language source code example on monitor
What Is Memory Safety, and What Does It Mean for Federal Agencies?
The Cybersecurity and Infrastructure Security Agency recently issued guidance on how to transition to memory-safe programming languages to reduce software vulnerabilities.
Tomi Engdahl says:
Programming languages: It’s time to stop using C and C++ for new projects, says Microsoft Azure CTO
The industry should treat C and C++ languages as “deprecated,” says Azure CTO Mark Russinovich.
https://www.zdnet.com/article/programming-languages-its-time-to-stop-using-c-and-c-for-new-projects-says-microsoft-azure-cto/#amp_tf=L%C3%A4hde%3A%20%251%24s&aoh=17090648996700&referrer=https%3A%2F%2Fwww.google.com&share=https%3A%2F%2Fwww.zdnet.com%2Farticle%2Fprogramming-languages-its-time-to-stop-using-c-and-c-for-new-projects-says-microsoft-azure-cto%2F
Tomi Engdahl says:
NSA’s Plea: Stop Using C and C++ (Because You’re Idiots)
https://securityboulevard.com/2022/11/nsa-memory-safe-richixbw/#amp_tf=L%C3%A4hde%3A%20%251%24s&aoh=17090648996700&referrer=https%3A%2F%2Fwww.google.com&share=https%3A%2F%2Fsecurityboulevard.com%2F2022%2F11%2Fnsa-memory-safe-richixbw%2F
The C and C++ languages are unsafe. Instead, the U.S. National Security Agency would like devs to use memory-safe languages—because most security vulnerabilities are caused by bugs in memory usage.
Neal Ziring (pictured), the NSA Cybersecurity Directorate director, says all you programmers are making “simple mistakes” that are “still entirely too common.” He’s talking about problems such as buffer overflows and use-after-free bugs.
Tomi Engdahl says:
The White House Memory Safety Appeal Is A Security Red Herring
https://hackaday.com/2024/02/29/the-white-house-memory-safety-appeal-is-a-security-red-herring/
In the Holy Programming Language Wars, the lingua franca of system programming – also known as C – is often lambasted for being unsecure, error-prone, and plagued with more types of behavior that are undefined than ones that are defined by the C standards. Many programming languages were said to be ‘C killers’, yet C is still alive today. That didn’t stop the US White House’s Office of the National Cyber Director (ONCD) from putting out a report in which both C and C++ got lambasted for being ‘unsafe’ when it came to memory management.
https://www.whitehouse.gov/oncd/briefing-room/2024/02/26/press-release-technical-report/
Tomi Engdahl says:
White House urges developers to dump C and C++
Biden administration calls for developers to embrace memory-safe programing languages and move away from those that cause buffer overflows and other memory access vulnerabilities.
https://www.infoworld.com/article/3713203/white-house-urges-developers-to-dump-c-and-c.html
Tomi Engdahl says:
Blazingly fast memory vulnerabilities, written in 100% safe Rust.
https://github.com/Speykious/cve-rs
Tomi Engdahl says:
Starting over: Rebooting the OS stack for fun and profit
Making full effective use of new persistent memory means tearing up the rulebook
https://www.theregister.com/2024/02/26/starting_over_rebooting_the_os/