Cybersecurity Experts NOW Recommending These Languages

U.S. Cybersecurity experts are moving away from programming languages that require manual memory management like C and C++.

Citing a major reason for exploits, they are now recommending that organizations put together a plan to move towards languages that are "memory-safe."

In this video, we'll discuss the issue with C and C++, why big players like Microsoft are in agreement, and exactly what programming languages these experts are recommending.

Timestamps
00:00 Intro
00:13 The official statement
01:24 What is memory safety?
02:52 Issues with C and C++
03:29 Language 1
03:33 Microsoft all in
04:58 Language 2
05:32 Language 3
05:49 Language 4
06:11 Language 5
06:27 Language 6
06:54 More languages
07:23 Outro

** Career Path Coding Tracks **

** My Coding Blueprints **

** I write regularly **

** FREE EBOOKS **

LET'S CONNECT!

/ travisdotmedia

#cybersecurity #programminglanguage #rustprogramming #security

** Some of the links in this description may be affiliate links that I may get a little cut of. Thank you.

[nahiandev]

Kinda misleading! No matter how far Rust reaches, C/C++ is here to stay.

[ByThisShallAllMenKnow]

Started with Assembly then C++, haven't done either in decades, and re-started in the last 8 months with Python and C.

[king_rai]

I'm not dropping either C or C++. Bite me

[rinzler]

I am yet to meet an actual "Cybersecurity expert" who is actually an expert.

[synen]

I absolutely love Go, my favorite language right now.

[paulsander]

I'm surprised LISP isn't on the list. It's about as memory safe as you can get. And it was built around the functional programming paradigm, which is all the rage right now.

[testtest-qmcj]

If your C++ code in 2024 looks like 1:44, I full-heartedly recommend you to stop write anything in C++ for the sake of the WHOLE WORLD. That piece of code is only acceptable if you are an employee tasked to maintain a 20+ years old legacy code written in C++98/03. Large portion of the industry have already migrated to C++14 or 17 for their new codes, and one of the first things they prohibit is exactly what is written in 1:44. As can be often witnessed in various benchmarks, presenting 1:44 as a representative C++ code is simply disingenuous and disappointing.

[DataPastor]

We will soon have cpp2 with a permissive licence, and it solves most common memory safety problems of C++. The Rust bubble has already popped, and the hype is fading away. The large scale future is somewhere around Carbon, Circle or cpp2. Rust might be able to get some niches, but its hype is already in the disillusionment phase.

[haliszekeriyaozkok]

I'm currently using rust in my projects and i'm pretty much happy with it. I'dont need any other language except android or ios.

[sergeiromanoff]

$10M doesn't really make it 'all in' for microsoft

[shubh.]

Interesting content, but the issue is, the use of C and CPP is so vast particularly in Embedded Systems and device drivers that it will take a lot of effort before the full transition can actually happen. It will be interesting to C how much adoption these languages get. Another thing is that today in most of the university curriculum C is the primarily used language and even in most interviews too candidates are asked C. So if things really have to change those need to be done right from the grass root level, i.e., the universities and schools so that the GenZ can really appreciate why it is needed.

[jebotipasmater]

My dude has the best logo for Swift! 🤣

[christ.]

I think compiling to Web Assembly will be the future. Write once run everywhere.

[aipujols]

Primarily code in Python, but Go has really caught my attention. ( market need is strong)

[rajendranramachandran]

Cybersecurity experts recommend prioritizing memory safe languages for software development.
Click to expand
00:01
✦
CISA recommends moving away from C and C++ due to memory safety vulnerabilities.
00:59
✦
Memory safety languages automatically manage memory to prevent security vulnerabilities.
01:59
✦
US cybersecurity experts recommend transitioning from C and C++ to memory safe languages like Rust.
02:57
✦
Cybersecurity experts recommend using Rust for its memory safety and reliability.
03:55
✦
Recommended programming languages for cybersecurity
04:52
✦
Python is a popular and versatile language.
05:50
✦
Switching to memory-safe languages for security reasons

[Serene-efkx]

Folks who were using C/C++ were doing so because they needed the performance. That pretty much instantly eliminates GC languages. All you are left with is Rust, maybe Zig, and possibly Mojo from modular. The only other option is Carbon (presuming google adds some memory safety features. For now, I can only recommend Rust.

[VectorAlphaSec]

I started learning programming with C++ as my first introductory language. But as of now i havent programmed in C++ for 3 years. I moved primarily to Python, Zig, and Flutter with plans to learn Mojo soon next month.

[traezeeofor]

Rust
GoLang
C Sharp
Python
Java
Swift

[GoWithAndy-cptz]

I know C and I like it, but since I know how to program in GO it's so hard to push myself to do anything in C. I like C++ but I don't know ++11, 14, 17, 20, 23, Just C++98. I hate templates and auto pointers and all that new stuff because I don't use it very frequent and didn't memorize it yet. Modern C++ seems to me so strange. But Rust looks even worse to me than modern C++:) Cheers!
How about Zig?

[romania-nq]

just wait until you find the vulnerabilities in Rust just use a fast easy to understand memory safe language like c#