Comments by "miraculixx" (@miraculixxs) on "ByteByteGo" channel.

There are some glarying issues with your summary graphic. All programming languages need source code, not just Python. Python is compiled to Bytecode first, and only then executed by the Python VM (the interpeter). Very much the same as Java.
15
The dependency management doesn't go away with a mono repo, it is just more complex and requires meticulous tagging. With micro repos there is technically no need for tagging since the dependencies are managed with release artifacts, not source code.
6
@frogzie the python compilation is also done once, not every time you run the code.
6
Unfortunately this is a very common misconception. In fact "to compile" just means translating from source code format to execution format. It does not, however, mean to translate into (native) CPU instructions. There are many languages that compile source code into so called bytecode, which then gets executed by an interpreter, also known as a "virtual machine" (VM). For example Java, Python, JavaScript, Ruby all use this approach.
5
@vijayvijay4123 t Good idea, yet that's not how it works. Bytecode always gets executed by a VM. Some VMs do "hot native compilation" which turns some parts of the bytecode into CPU machine code, making it faster. That's called just in time compilation, JIT for short.
3
Yes, unfortunately it is misleading in regards to Python. See comments
2
@potatoandpippen Your comment makes me so happy 😁
2
@josealvaradotorre6870 that is incorrect. Python code is not compiled "on the fly". Rather before programm execution starts all code is compiled. Just as with Java. Further, circular imports happen when A imports B imports A. It is independent of where you start: import B or import A, same result. The typical problem that many people have with Python's import semantics is to understand its module search path. That's a level 8 problem: Its not really an issue with Python but a failure to learn about how it works. In a nutshell, always start your program at the root of your source tree, not just about anywhere. Problem solved.
2
@gurupartapkhalsa6565 I'll ignore the ad hominems. My stand by my argument. I'm not sure what is your point.
1
@gurupartapkhalsa6565 Mozilla: Compiling is the process of transforming a computer program written in a given language into a set of instructions in another format or language. A compiler is a computer program to execute that task. Wikipedia: In computing, a compiler is a computer program that translates computer code written in one programming language (the source language) into another language (the target language). Enc. Britannica: Compiler, computer software that translates (compiles) source code written in a high-level language (e.g., C++) into a set of machine-language instructions that can be understood by a digital computer’s CPU Techopedia: Compile refers to the act of converting programs written in high level programming language, which is understandable and written by humans, into a low level binary language understood only by the computer. Seems to be a pretty universal definition. Still not sure what you're on about. Again, I'll ignore your adhominems but rest assured they don't reflect well on you.
1
@superdingo9741 actually Python works the very same way as Java. Some implementations even have a JIT compiler (eg pypy). Python code is compiled before execution, not line by line.
1
@superdingo9741 that's a minor detail.
1
I appreciate the presentation. However I don't agree that mono repos are better for code quality or dependency management. No matter what kind of repo strategy, management of code quality and dependencies are necessary. Mono repos just make it humongously complex unless there is a dedicated team that builds all the tools that you get for free with micro repos. I dare say mono repos are an unresolved (and by now unresolvable) technical debt owed to a drive for "simplicity" at the start of those companies when having multiple repos seemed too much of an effort. That made sense back in the early ~2000 years when setting up a new repo essentially meant to buy a new server and spend a couple of weeks configuring it. Luckily those days are gone, setting up a new repo is literally two or three clicks & commands, and above all it is virtually free.😅 My advise is to use micro repos and not lose another thought to this question. Save your energy for more important decisions.
1
@potatoandpippen you are so nice to people, a real role model. Thank you 🙏
1
Compiled languages also use C bindings (or some other convention) to call library code. No difference there.
1