4 ms·

I can't help but feel this will be either a useless toy or an absolutely horrific malicious software injector.

agiacalone 4y ago
Downvote, eh? Okay then. > Cosmopolitan Libc does come with some tradeoffs as well > (static compilation, C codebases, no multithreading > (Update 2022-07-27:, no multithreading yet, > the pthreads API takes a while to fill Toy. > Regarding python packages with C extensions, the build > process for adding them to the APE is rather unwieldy > (2022-07-27 adding C extensions to the APE is much more > elegant now because of the Cosmopolitan monorepo Horrific malware. Unchecked C (even libsafe) is bad. Edit: Nevermind that each app using this software will need to be individually updated every time a new security patch for Python comes out.
- baq 4y ago
  while you aren't wrong, this is exactly the same as any statically built software (e.g. all of go) and people still build software this way.
- krageon 4y ago
  The downvotes are because you're not really adding anything (I think). This just reads as empty complaining. You have an edited-in point that isn't widely seen as an issue (it is the case, but why do you think it's bad?). That makes it tedious to read, not very stimulating.
- jart 4y ago
  If you're concerned about security, then you can use pledge.com to sandbox python.com https://justine.lol/pledge/ https://justine.lol/pledge/
ahgamut 4y ago
I wanted Python to work across at least Windows/Linux because I have a bunch of these tiny scripts that I keep running everywhere. (For example, I always use `python.com -m http.server` when I want to share files in the local network without SSH). Cosmopolitan Libc made it easy for me to run my scripts across Linux/Windows and more, and the running scripts can be accessed via a browser GUI, which makes it very convenient if someone not use to CLI has to monitor what is going on. Plus I can update my scripts any time by just adding them to the executable via a `zip` command. Toys are still fun to play with :)

Downvote, eh? Okay then. > Cosmopolitan Libc does come with some tradeoffs as well > (static compilation, C codebases, no multithreading > (Update 2022-07-27:, no multithreading yet, > the pthreads API takes a while to fill Toy. > Regarding python packages with C extensions, the build > process for adding them to the APE is rather unwieldy > (2022-07-27 adding C extensions to the APE is much more > elegant now because of the Cosmopolitan monorepo Horrific malware. Unchecked C (even libsafe) is bad. Edit: Nevermind that each app using this software will need to be individually updated every time a new security patch for Python comes out.

baq 4y ago
while you aren't wrong, this is exactly the same as any statically built software (e.g. all of go) and people still build software this way.
krageon 4y ago
The downvotes are because you're not really adding anything (I think). This just reads as empty complaining. You have an edited-in point that isn't widely seen as an issue (it is the case, but why do you think it's bad?). That makes it tedious to read, not very stimulating.
jart 4y ago
If you're concerned about security, then you can use pledge.com to sandbox python.com https://justine.lol/pledge/ https://justine.lol/pledge/

ahgamut 4y ago

I wanted Python to work across at least Windows/Linux because I have a bunch of these tiny scripts that I keep running everywhere. (For example, I always use `python.com -m http.server` when I want to share files in the local network without SSH). Cosmopolitan Libc made it easy for me to run my scripts across Linux/Windows and more, and the running scripts can be accessed via a browser GUI, which makes it very convenient if someone not use to CLI has to monitor what is going on. Plus I can update my scripts any time by just adding them to the executable via a `zip` command. Toys are still fun to play with :)