is rust and go the new ruby and php? what makes programming languages sticky and why they die...

will rust and go share a similar fate to ruby, php and perl?
why did ruby die?
will google carbon (which doesn't really exist yet) survive rust and go?
what makes a programming language sticky and why do they die?

in this video chris explores the 4 major reasons why a programming language survives and why it dies. he looks at popular languages of today and of the past and explores which languages are likely to flourish or survive and which ones are likely to die or are dying. he looks at the reasons why and what those languages can do to survive.

if you're interesting in programming languages and their history and where you should invest your time, this should be an interesting watch. if not controversial

00:00 - introduction
00:45 - octoverse top programming languages
02:00 - popular languages reasons to exist
02:06 - python
02:55 - typescript
03:30 - c#
04:06 - php
04:52 - c++ and C
05:54 - rust
06:20 - go
06:38 - perl
07:00 - ruby
08:05 - reasons to exist must solve a problem
09:30 - reason to exists may no longer be relevant
09:50 - are the reasons to exist for top languages still relevant
15:13 - sticky platforms
15:48 - javascript
16:00 - python
18:38 - java
21:42 - c# and .net
22:13 - php
23:17 - C++ and C
25:00 - ruby on rails
25:45 - objective c and swift
27:45 - dart and flutter
29:25 - blockchain languages like solidity
30:31 - reason to exist is not enough
30:49 - dead languages of the past
31:10 - pascal, turbo pascal and delphi and windows
32:25 - c# and .net kills pascal
33:23 - fortran, COBOL and the mainframe
34:20 - ruby, perl and PHP no longer have sticky platforms
35:18 - algol-68
36:37 - simula, smalltalk and erlang
37:10 - does rust and go have a platform?
38:42 - ecosystems
43:19 - next generation languages and compatibility
43:30 - typescript
45:05 - swift
45:20 - kotlin
45:30 - zig
46:50 - google carbon
47:58 - conclusion