Recent submissions

Comment · 8 years ago
Down in the Netherlands as well. So "notjustme"...
Comment · 8 years ago
Thanks for reporting the broken links, they have been fixed. And, as we're trying to port more standard libraries, help is very welcome.
Comment · 8 years ago
I'm afraid the current webpage is a DYI project. Having been a freelance technical / scientific application programmer for most of my life, web design is just something I do if really needed. In the long run probably the site should be made by "real" web designer.

Meanwhile can you indicate what's most disturbing about it? I guess the mobile experience is the most problematic? Or just the layout? Fonts? Accessability? We should probably have a professionally designed logo as well. But currently we're focused on making the compiler better. 3.6 -> 3.7 was really a big step, due to the modules.

There will also be a special website to play with Transcrypt. The URL was already reserved: tsfiddle.org. But it will be a while until somebody finds the time to turn it into a playground / educational site. Everyone working on Transcrypt has a daytime job as well, that's how it is with open source, although the past months I think most of my time was spent on Transcrypt.

The project was born from practical needs for a medical imaging project. In my experience the switch to Python is a great improvement in productivity and clearness. And it's more fun, above all...

Comment · 8 years ago
Comment · 8 years ago
Starting with Transcrypt v3.6.101 it is now possible to create native JavaScript component frameworks using the Transcrypt Python to JavaScript compiler. This makes it possible to write compact, fast JavaScript components for the browser in Python.

The project can be found at:

https://github.com/qquick/Transcrypt

Components can be freely mixed on a page without requiring recompilation. A developer doesn't need Transcrypt or any knowledge of it to use such a framework.

Each page has one unit that contains the Transcrypt runtime and, if needed, any central facilities. It is compiled with the -u .run switch. In addition each page can hold as many separate components as needed. Compile these with the -u .com switch.

A loader is generated, accepting a list of components. By varying this list, each page can have its own subset of components, without the need to recompile. The generated JavaScript code for components can be very small, typically a few hundred bytes. The runtime and central facilities are included in the page only once.

Comment · 9 years ago
Comment · 9 years ago
It has been fixed. Sorry, it's the demo devil, I guess...
Comment · 9 years ago
That's very bad! I'll repair it!

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton