Editing Talk:1988: Containers
![]() |
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 7: | Line 7: | ||
:Agree. --[[User:Joshupetersen|Joshupetersen]] ([[User talk:Joshupetersen|talk]]) 15:55, 3 May 2018 (UTC) | :Agree. --[[User:Joshupetersen|Joshupetersen]] ([[User talk:Joshupetersen|talk]]) 15:55, 3 May 2018 (UTC) | ||
:Agree! [[Special:Contributions/108.162.237.184|108.162.237.184]] 17:08, 3 May 2018 (UTC) | :Agree! [[Special:Contributions/108.162.237.184|108.162.237.184]] 17:08, 3 May 2018 (UTC) | ||
− | |||
I don't know if its just docker, almost any time I've gone to build mobile anything the API needs new libraries, their "secure" connecting functions must be used, or some other blackbox MUST be /glued/ to my work. If I don't stay on top of every platform, this in and of itself is a head ache I can't imagine what it'd be like if I had to learn and comply with the content of these libraries. {{unsigned ip|172.69.90.40}} | I don't know if its just docker, almost any time I've gone to build mobile anything the API needs new libraries, their "secure" connecting functions must be used, or some other blackbox MUST be /glued/ to my work. If I don't stay on top of every platform, this in and of itself is a head ache I can't imagine what it'd be like if I had to learn and comply with the content of these libraries. {{unsigned ip|172.69.90.40}} | ||
Line 15: | Line 14: | ||
For some reason, this really, really, REALLY feels like it's a continuation of 1987. Agree? Disagree? Also, the 'wasting a lot of computing resources to do small tasks inside entire emulated systems' does not feel like valid criticism, since they are just walled-in processes sharing the same kernel (and everything below). Firing up full-blown separate VMs for things that could just as well run in containers is the real wasteful choice IMHO. [[Special:Contributions/162.158.238.70|162.158.238.70]] 07:29, 3 May 2018 (UTC) | For some reason, this really, really, REALLY feels like it's a continuation of 1987. Agree? Disagree? Also, the 'wasting a lot of computing resources to do small tasks inside entire emulated systems' does not feel like valid criticism, since they are just walled-in processes sharing the same kernel (and everything below). Firing up full-blown separate VMs for things that could just as well run in containers is the real wasteful choice IMHO. [[Special:Contributions/162.158.238.70|162.158.238.70]] 07:29, 3 May 2018 (UTC) | ||
− | : | + | :The (en)light(ening)est (co)processes are started with fork() and exec(). [[Special:Contributions/172.68.34.52|172.68.34.52]] 22:20, 3 May 2018 (UTC) |
− | |||
− | The (en)light(ening)est (co)processes are started with fork() and exec(). [[Special:Contributions/172.68.34.52|172.68.34.52]] 22:20, 3 | ||
− | |||
− | |||
− | |||
− | |||
Is it worth adding that "achieved enlightenment" is probably a reference to http://www.thecodelesscode.com/? | Is it worth adding that "achieved enlightenment" is probably a reference to http://www.thecodelesscode.com/? | ||
The idea behind docker is that you do ''not'' glue together small code snippets. Whether from StackOverflow or elsewhere. What you are gluing together is in effect entire machines with software already installed. You normally don't know or care about any details finer than that. Not even which operating system the code was written for, which computer language it was written in, or whether the software has some odd and specific requirements about what else is installed on that machine. It is true that many programmers that copy snippets from StackOverflow don't really understand what those snippets are doing. But if you view this comic as an explanation of what Docker is all about, a reference to "copying small code snippets" seems to miss the point. [[User:Epsilon|Epsilon]] ([[User talk:Epsilon|talk]]) 04:54, 4 May 2018 (UTC) | The idea behind docker is that you do ''not'' glue together small code snippets. Whether from StackOverflow or elsewhere. What you are gluing together is in effect entire machines with software already installed. You normally don't know or care about any details finer than that. Not even which operating system the code was written for, which computer language it was written in, or whether the software has some odd and specific requirements about what else is installed on that machine. It is true that many programmers that copy snippets from StackOverflow don't really understand what those snippets are doing. But if you view this comic as an explanation of what Docker is all about, a reference to "copying small code snippets" seems to miss the point. [[User:Epsilon|Epsilon]] ([[User talk:Epsilon|talk]]) 04:54, 4 May 2018 (UTC) | ||
− | |||
− |