Re:We need visual programming. No, not like that
by az09mugen on Monday July 15, 2024 @06:58AM
(#40966734)
While I totally agree with you, I'm looking for a counter example. The only one which comes to my mind, is non trivial and quite fast for js/ts is this : https://github.com/tsoding/raycasting
An implementation of raycast in a 2D canvas
The dev tried to implement hot reloading, and you can see all the process there https://www.youtube.com/playlist?list=PLpM-Dvs8t0VZ08cYW6yqN...
Even though I didn't measured the loading time, an effort has been made to accelerate everything that could be accelerated.
Re:We need visual programming. No, not like that
by jbverschoor on Monday July 15, 2024 @07:36AM
(#40966912)
Even the simplest type inference can cause typescript to stall for minutes. The problem is in the inference. That problem goes away when you're actually specifying types. Tooling should add typing automatically (not implicitly)
Re:We need visual programming. No, not like that
by zarathustreal on Monday July 15, 2024 @08:12AM
(#40967128)
Minutes? There’s no way you’ve seen a minutes-long stall caused by TypeScript inference..I need to see some evidence on this one
Re:We need visual programming. No, not like that
by jbverschoor on Monday July 15, 2024 @05:37PM
(#40971683)
I'll look into it.. But yeah, had that multiple times (older versions though). Specifying the type solves is, and I was not the only one after some googling
Or show me a non trivial open source ts project that’s instant; doesn’t exist and I have literally no clue why people keep defending this stuff; you didn’t make it right? I would be embarrassed but definitely not defending it.
https://www.kirandev.com/open-source-nextjs-projects-open-fo...