5 ms·

All of that is basically standard library over HTTP

• asim 4y ago
  Why is the standard library not a HTTP call? Maybe all of this stuff ends up in WASM, I don't know, but I just get the feeling like if it was all over a network that's constantly evolving and becoming faster, that we end up with something that looks more like a networked and emergent language. Programming languages are stuck in the old world of compile and run locally, but what if they weren't, what if they were networked and evolutionary.
  • krapp 4y ago
    We already have "standard library as an HTTP call." It's called modern javascript. Having your software depend on an infinite fractal of networked code that can dynamically wreck your shit at any arbitrary moment in time is a bad idea.
    • thunky 4y ago
      > Having your software depend on an infinite fractal of networked code that can dynamically wreck your shit at any arbitrary moment in time is a bad idea. This is the most succint argument against kubernetes I've heard yet.
  • 0x445442 4y ago
    > Why is the standard library not an HTTP call? You mean like string concatenation? Come on man. As far as evolution goes, that’s what semantic versioning is for.
  • Cthulhu_ 4y ago
    What you describe sounds familiar, I believe it was Akka's actor model (https://doc.akka.io/docs/akka/current/typed/guide/actors-intro.html https://doc.akka.io/docs/akka/current/typed/guide/actors-int...) that allows actors to run on either the same machine or a different (cluster of) machines, but doing so completely transparently to the developer. Is that something that interests you? It means that the developer doesn't have to think about RPCs or consuming HTTP APIs in the first place.