Deno and Node.js both intend to be general-purpose platforms for running JavaScript code. Things like instantiating TCP servers are performed in user-land code. You could, for example, build a daemon with Deno or Node.js which subscribes to changes in stock prices and runs a raw SQL query when they change.
Osgood intends to be a server-only platform with extremely granular whitelist-only permissions for outbound I/O. It does not aim to be general purpose. For example, Osgood applications won't be able to instantiate TCP connections in user-land. However, they can call abstractions representing more complex operations performed in Rust, like user-land code being able to run some sort of read operation against a database.
In this regard I personally think of Osgood as being more like PHP, where instead of generating a TCP packet I would use built-in modules and configure a database connection and run a query.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Deno and Node.js both intend to be general-purpose platforms for running JavaScript code. Things like instantiating TCP servers are performed in user-land code. You could, for example, build a daemon with Deno or Node.js which subscribes to changes in stock prices and runs a raw SQL query when they change.
Osgood intends to be a server-only platform with extremely granular whitelist-only permissions for outbound I/O. It does not aim to be general purpose. For example, Osgood applications won't be able to instantiate TCP connections in user-land. However, they can call abstractions representing more complex operations performed in Rust, like user-land code being able to run some sort of read operation against a database.
In this regard I personally think of Osgood as being more like PHP, where instead of generating a TCP packet I would use built-in modules and configure a database connection and run a query.