The project I get paid to work on takes > ten minutes to install, build, and test from a fresh repo. That's not hyperbole. It's just two #websites built with #typescript #nextJS #yarn #nixOS and #jest. There aren't even any #e2e functional #tests!

Ten fucking minutes everytime I switch branches!!

#struggleStack #webDev #transpiling

@tomw I think you could (???) write modern, modularized #es6 and ship it to the browser now, using #importmaps to direct the browser to where your module files live. I haven't tried it yet, and the support may be limited, but... maybe that's The Future™.

That may eliminate #transpiling, but we still have to deal with concatenation. With updated protocols like #HTTP3, maybe multiple simultaneous connections will be less of a problem?

And then #minification? I dunno man, maybe gzipping on the wire is good enough.

But I feel your pain. I'm hopeful for the future.

#javascript #programming #webdevelopment

Also, I want native #css loops. I think that's the last thing we need #preprocessors for.

I haven't worked with built-in web components, but that could be the answer to the "always a new framework" problem. But if it was, it prolly would have more uptake by now.

I honestly spend to much time thinking about this.

@levynoise it's not C++, but Nuitka does translation to C: https://nuitka.net/

#nuitka #transpiling #python

@levynoise The CoPilot interface in VSCode isn't really set up for translating thousands of lines of code, I don't think.

What's the reason for porting to C/C++, vs a safer language (Rust, Go, nim)?

There's a basic Python to Rust transpiler here: https://pypi.org/project/python-rs/

You can also incrementally change to Rust with PyO3.

Something like Nuitka can do automatic translation to C, while maintaining the original source.

#Python #SourceToSourceTranslation #CoPilot #nuitka #transpiling #C