i do too. you may have heard of Oberon perhaps? this was one effort towards this based on a language that was also an operating system.

Go is based on a lot of the design principles in Oberon, which is descended from Modula and then to Pascal. the principle is that source code becomes the primary form of distribution of applications and libraries and in theory you could wrap such a runtime engine inside linux, darwin, bsd mach, and windows kernel, and then you would have a universal design. throw in the extension of the "everything is a file" principle of unix to "everything is a server" of plan 9 and who needs browsers anymore. your whole GUI is a browser from top to bottom, running fast binary code compiled from the source code fetched from the internet.

i mean, in theory most of it could be interpreted, to have a shorter time for first deployment but Go's insanely fast build system proves you can do the same with binary.

IMO, the biggest mistake with the browser-as-app-runtime is the way it messes up the boundaries between presentation and application logic. it is not that difficult to abstract a clean interface between the two things and eliminate the single-language requirement. but most of the dev world is obsessed with objects, even though they are just primarily a mechanism for breaking domain boundaries. applications are called processes in most operating systems for a reason. not OBJECTS. objects are some kind of frankenstein between application and data. once you blend these two things together, it becomes impossible to do certain things efficiently at higher levels of abstraction, and it creates a bottleneck in development that sees endless major version upgrades, with codebases that are entirely chopped and changed, again and again for no reason, destroying the whole point of software development's most important principle: clean interfaces, and separation of concerns.