2 ms·
I don't think there's anything about tcl that is inherently insecure, but it indicates that the code might be quite old and from a time where many vulnerabiliti
by SoftTalker 2y ago
I don't think there's anything about tcl that is inherently insecure, but it indicates that the code might be quite old and from a time where many vulnerabilities and ways to avoid them were not well understood.
Tcl and Rivet to me says the code is from the 1990s or 2000s. Does FlightAware go back that far? Otherwise I am surprised at those choices for anything newer.
- bigmoat 2y ago2005. There was still code and pages dating back to then running and being used. But over the years, more and more was built on top of it rather than a different stack. Frontend code would vary with whatever flavor a developer liked at the time, but the backend was still always going through Rivet/TCL. ICs would complain about it but the founders cashed out to the tune of 9 figures in the end, so it worked out for them. I’ll agree that TCL isn’t inherently insecure, but you aren’t getting any libraries or frameworks with it either to make your life easier or safer.