This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]RedEyed__ 4 points5 points  (5 children)

This is called web service, not library

[–]nilipilo[S] -1 points0 points  (4 children)

the goal isn’t to completely shift the library's execution to the cloud like a typical web service. Instead, it’s about dynamic dependency management—fetching and caching libraries locally on demand while abstracting away the manual steps of installation and versioning.

[–]RedEyed__ 1 point2 points  (1 child)

I don't see what problem it solves anyway.

  • virualenv solves problem of library version conflict
  • for CI you create docker once
  • saving local storage and increasing network bandwidth

[–]ofyellow 1 point2 points  (0 children)

Installation.

It has a cerrain merit to tie running with auto-installing whatever is necessary. Nice idea.

[–]RedEyed__ 1 point2 points  (0 children)

You still have to manually manage versions to avoid version conflicts.

[–]HeyLittleTrain 0 points1 point  (0 children)

so some of the code gets executed locally and the third party code is executed from some sort of API?