✳flâneur — a map of the web's best reading

Why Python Won't Be the Language of LLMs | LinkedIn

linkedin.com · 624 words · saved by 1 readers

Python has long had a monopoly on data workflows — everything from data analysis to data science to machine learning. Anything that can't be done in SQL is done in Python. But Python won't be the language for LLMs. Why did Python become the language for data workflows? Cross-platform. Data analysts are much more likely to work on Windows. Python was one of the first languages to have a simple cross-platform toolchain. Dynamic Typing. Data science is often exploratory. As a result, code churns at a much higher rate. Why go through the trouble to type every numpy array with different shapes when the code will never go to production and might be replaced soon? REPL / Scripting. Why do we rarely see different languages used in Jupyter notebooks? Built-in data structures. First-class support for sets, dictionaries, and lists. Python's import/namespace design vs. Ruby's global namespace. There's more to unpack here, but the main discussion on this point is why Python over Ruby? Brevity over

Python has long had a monopoly on data workflows — everything from data analysis to data science to machine learning. Anything that can't be done in SQL is done in Python. But Python won't be the language for LLMs. Why did Python become the language for data workflows? Cross-platform. Data analysts are much more likely to work on Windows. Python was one of the first languages to have a simple cross-platform toolchain. Dynamic Typing. Data science is often exploratory. As a result, code churns at a much higher rate. Why go through the trouble to type every numpy array with different shapes when

Explore this link on the map →

related reading