Rendered at 07:22:51 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
CJefferson 2 hours ago [-]
Wow, that might be the worst name for a project I’ve ever seen. I think every programmer who sees this is going to assume it’s a Python thing.
With regards the library itself —- I think it’s generally known the c++ standard library is a poorly designed mess in places but if you make an entirely new one you lose all the software already written, at which point why use C++ nowadays?
smokel 1 hours ago [-]
It is a Python thing, in the sense that it is Python-inspired:
> design-wise copy the Python standard library's APIs whenever possible [1]
This is giving the same vibe as Windows Subsystem for Linux[0] - it kinda makes sense once somebody explains it, but is confusing as hell when you first see it
Just like Windows storing 64-bit binaries in System32 dir and 32-bit binaries in SysWOW64 dir kind of makes sense (if you are insane)
integricho 2 hours ago [-]
Agreed, I thought this is a wrapper for STL under Python, what does the py prefix stand for here actually?
As for the why c++ at all, as long as one falls into the "don't care" category, it works fine.. lately I found myself I rather build my apps in C with NODEFAULTLIB (under Windows at least), and creating my own size-optimized standard library which on Windows wraps the Win32 API wherever possible. The size savings are incredible, my executable is in the ~500KB range, ultra small and ultra fast. This is unattainable with normal modern C++.
pjmlp 9 minutes ago [-]
I instead, use VC++ latest with C++23 import std.
As for the size requirements, and having Windows experience all the way back to Windows 3.0, you can do exactly the same tricks with C++.
dsab 1 hours ago [-]
Out of curiosity what are your projects written in C for Windows? GUI apps?
integricho 1 hours ago [-]
Yes, I am building GUI apps. This "standard library" of mine is built from the ground up in a cross platform manner, such that it compiles on Windows wrapping Win32, with Windows 95 being the CI machine, making sure it works on the whole Windows family upwards, and it wraps POSIX under Linux/MacOS/any POSIX system. The goal being to reuse the available shared library dependencies that are always present on these platforms anyway, giving me these ultra small binaries.
nok22kon 5 minutes ago [-]
why support Win9x? actual users? as a fun thing to do?
pjmlp 8 minutes ago [-]
> C++ is actually very fast to compile, the slowdowns come mostly from the way the standard library is implemented.
Only if using classical headers, std as module is already a reality on VC++.
nok22kon 4 minutes ago [-]
wasn't there a lot of talk that modules are still not really working, in practice I mean?
squirrellous 4 minutes ago [-]
Love to see someone implementing pathlib in c++. It is what stdfs could have been.
With regards the library itself —- I think it’s generally known the c++ standard library is a poorly designed mess in places but if you make an entirely new one you lose all the software already written, at which point why use C++ nowadays?
> design-wise copy the Python standard library's APIs whenever possible [1]
[1] https://github.com/jpakkane/pystd
0. https://www.reddit.com/r/bashonubuntuonwindows/comments/t952...
As for the why c++ at all, as long as one falls into the "don't care" category, it works fine.. lately I found myself I rather build my apps in C with NODEFAULTLIB (under Windows at least), and creating my own size-optimized standard library which on Windows wraps the Win32 API wherever possible. The size savings are incredible, my executable is in the ~500KB range, ultra small and ultra fast. This is unattainable with normal modern C++.
As for the size requirements, and having Windows experience all the way back to Windows 3.0, you can do exactly the same tricks with C++.
Only if using classical headers, std as module is already a reality on VC++.