@Shakes's banner p

Shakes


				

				

				
0 followers   follows 0 users  
joined 2025 November 07 15:29:13 UTC

				

User ID: 4029

Shakes


				
				
				

				
0 followers   follows 0 users   joined 2025 November 07 15:29:13 UTC

					

No bio...


					

User ID: 4029

That’s why you would invent a superset, to add type-checks and other context checks. You throw all your existing python that your non-technical professors and data scientists and math majors worked out. Then as you generate new “scrython” code you are reasonably confident it isn’t creating more problems to solve later. That code will be rigorously defined and checked by a linter which will constrain the universe of possible AI errors.

I don’t think this is the only way to add guardrails around AI but eventually someone will have to do something like this. The sheer volume of python written and being written means AI will be asked to write python for a long time to come.

Rust is an interesting programming language, because it perfected the nanny-state compiler. Rust is infamously difficult to get to compile if you don’t know what you’re doing. You can spam .unwrap() and unsafe and write unsafe code, but it requires you to at least actively choose to accept these flaws as opposed to passively letting them by accidentally.

If AI is going to write code, I think Rust is actually going to point the way toward the future. AI can make writing code very easy but introduces all sorts of potential zero-day bugs and faults. Rust actually solves much of this because many bugs the AI could write in other languages are not even valid Rust. The future of programming languages belongs to whoever develops an even more restrictive and advanced compiler that eliminates whole categories of AI errors from running. (A superset of python or typescript would be very appealing here.)