{"action":"created","issue":{"url":"https://api.github.com/repos/apple/swift-nio/issues/492","repository_url":"https://api.github.com/repos/apple/swift-nio","labels_url":"https://api.github.com/repos/apple/swift-nio/issues/492/labels{/name}","comments_url":"https://api.github.com/repos/apple/swift-nio/issues/492/comments","events_url":"https://api.github.com/repos/apple/swift-nio/issues/492/events","html_url":"https://github.com/apple/swift-nio/issues/492","id":335516135,"node_id":"MDU6SXNzdWUzMzU1MTYxMzU=","number":492,"title":"Project is doomed because Swift has no memory model or guarantees","user":{"login":"virl","id":2991028,"node_id":"MDQ6VXNlcjI5OTEwMjg=","avatar_url":"https://avatars3.githubusercontent.com/u/2991028?v=4","gravatar_id":"","url":"https://api.github.com/users/virl","html_url":"https://github.com/virl","followers_url":"https://api.github.com/users/virl/followers","following_url":"https://api.github.com/users/virl/following{/other_user}","gists_url":"https://api.github.com/users/virl/gists{/gist_id}","starred_url":"https://api.github.com/users/virl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/virl/subscriptions","organizations_url":"https://api.github.com/users/virl/orgs","repos_url":"https://api.github.com/users/virl/repos","events_url":"https://api.github.com/users/virl/events{/privacy}","received_events_url":"https://api.github.com/users/virl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-06-25T18:22:58Z","updated_at":"2018-06-25T18:54:37Z","closed_at":null,"author_association":"NONE","body":"Swift, compared to Java and Netty, have no well-defined memory model and memory guarantees (like Java JMM).\r\n\r\nFor example: https://bugs.swift.org/browse/SR-8101\r\n\r\nThat means that multithreading networking servers such as this project can never reach Java+Netty levels of resilience and reliability."},"comment":{"url":"https://api.github.com/repos/apple/swift-nio/issues/comments/400057965","html_url":"https://github.com/apple/swift-nio/issues/492#issuecomment-400057965","issue_url":"https://api.github.com/repos/apple/swift-nio/issues/492","id":400057965,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMDA1Nzk2NQ==","user":{"login":"virl","id":2991028,"node_id":"MDQ6VXNlcjI5OTEwMjg=","avatar_url":"https://avatars3.githubusercontent.com/u/2991028?v=4","gravatar_id":"","url":"https://api.github.com/users/virl","html_url":"https://github.com/virl","followers_url":"https://api.github.com/users/virl/followers","following_url":"https://api.github.com/users/virl/following{/other_user}","gists_url":"https://api.github.com/users/virl/gists{/gist_id}","starred_url":"https://api.github.com/users/virl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/virl/subscriptions","organizations_url":"https://api.github.com/users/virl/orgs","repos_url":"https://api.github.com/users/virl/repos","events_url":"https://api.github.com/users/virl/events{/privacy}","received_events_url":"https://api.github.com/users/virl/received_events","type":"User","site_admin":false},"created_at":"2018-06-25T18:54:37Z","updated_at":"2018-06-25T18:54:37Z","author_association":"NONE","body":"@helje5 Erm, so you want this project to have the same reliability/security as projects written in C? I guess it's too bad for the project then, especially if it positions itself as Netty alternative.\r\n\r\n> And given that it uses no GC, you'll have less OOM crashes and servicing hiccups.\r\n\r\nGC can't lead to OOM, excessive memory usage is. Because OutOfMemoryException in Java is always thrown after GC is free all possible memory."}}
{"actor":{"display_login":"virl"}}