Naturally, common MBA stuff.

Yes, compilation speeds of the 90's are slowly making a return, thankfully.

I thank Go for this. Go's compilation times seemed to inspire other language devs

I doubt Go has any sizable effect on the community of programming language developers. Probably Pascal has more impact on this.

Pascal has a lot of influence on this, but Go as well! My PL friends often talk about Go's benefits and flaws when thinking about advancing other their own projects or improving the mainstream languages they work on.

Go changed something, not sure if 20 or 21, where it will download the Go compiler of all your third-party which don’t match yours. It slows things down.

Yeah, not a fan of the idea that now the standard library is distributed as source code and packages are compiled on demand.

Note D as another example, and it predates Go.

Basically what the world has lost by ignoring Modula-2 and Object Pascal, and going down the C path.

The spirit of Pascal lives on in Nim.

It's arguably the closest modern language (with a sizeable community) to the Wirthian languages.

There’s a spirit of Pascal in Odin, although not a sizeable community.

http://odin-lang.org/

I would add that Delphi still follows along, enough for an yearly conference in Germany, and that C# since getting Native AOT and the low level programming improvements, is close enough to Modula-3 design.

There is Swift as well, although quite far from Wirthian compile times.

Plenty of games used Turbo Pascal as well, and it was for a long time the favourite language on PC demoscene.

Additionally most hit games back then were full of inline Assembly, regardless of the high level language, or even written 100% in Assembly.

Turbo Pascal 7 had a DOS extender.

There was Turbo Pascal for Windows 3.1, and with Delphi it started to be even more C++ influence with Pascal syntax, and safety first.

Even C has one, regardless of how tiny it happens to be, or the possibility of freestanding deployment.

In compiler speak, a runtime provides all infrastructure required by the language for program startup, shutdown, infrastructure for the standard library execution.

RUntime is an overused term here. The point is "no JS runtime, JIT-type"

Of course there is a (native) runtime, as there is for all languages (like you said) :)

Not at all, I can assert that the Spring code on my current project is classical programming.

In many places AI tools aren't even allowed to touch customer repos.

It already exists for years, it is part of Microsoft's MakeCode efforts for kids.

https://makecode.com/language

https://www.microsoft.com/en-us/research/publication/static-...

Much saner than a vibe coded compiler.

> It's pretty standard for "no runtime" to mean nothing on the device you install the compiled target app.

Only by layman that don't understand compilers.

Right, runtime is so broad that it's hard to say something has "no runtime". libgcc + your choice of crt0 is a C runtime, and the JVM is a Java runtime. That's a huge spectrum.

It's worth being charitable in your interpretation though and recognising "no runtime" probably refers to JVM-shaped or Node-shaped things, not libgcc+crt0-shaped things.

Alternatively, "runtime" is a derogatory term used by programmers who want to show superiority over others who use languages with more (built-in) features than theirs.

There's practically no difference for the overwhelming majority of software these days. Most people aren't working on embedded systems or operating systems.

This brings back memories, I thought it was long gone in the magpie attention world of frontend frameworks.