nah, webservices/webapis would have necessitated it without python, but without containerisation I think that python would have died off as the catch all scripting/orchestration lang awhile ago.
it's nice for small stuff, but for anything that needs to scale and has complex cicd it's a fricking nightmare and should be killed off.
rust is unironically better to deploy and it's a fricking ten tonne behemoth compiled language
I'm trying to install pyopenjtalk right now and the devs just basically said I need to download visual studio so I won't get a pip subprocess error i think. I'm not sure but thats what im doing rn. That after using conda with a virtual environmenta and installing pytorch nighly. C/C++ is a contender but python is up there. oof.
>. venv/bin/activate
That's a fricking bash source.
A programming language has no business fricking with your shell. At least makefiles and configure keep environment variable shit to the build and compile step.
I'd just like to interject for a moment. What you're referring to as Python, is in fact, Python/Linux, or as I've recently taken to calling it, Python plus Linux.
Python does not have applications unto themselves, but those that represent components and libraries already installed on a full Linux OS as defined by POSIX.
Many computer "programmers" run python-modified versions of Linux systems every day without realizing it. Through a peculiar turn of events, application deployed today are often considered as "written in python", and many of their users are not aware that they are basically just using a Linux system, developed by others.
There really is a Python, and these people are using it, but it is just a part of the Linux system. Python is the glue-code: the hacked together mess that the "programmer" uses to facilitate access to the system and its libraries developed by others with more talent. Python is an essential part of the bikeshed, but is useless by itself; it can only function in the context of the already-existing Linux system. Python is normally used in combination with the Linux operating system: the whole application is essentially Linux with python painted on top, or Python/Linux. All the so-called Python applications are really just components of Linux hacked together!
If my deployment process is more difficult than "git push" i give up
no i mean if somebody else wrote python code and you want to run it
oh. Well they should just publish instructions because there's a bunch of ways to pull in dependencies with Python.
requirements.txt
literally the easiest dep in the world
you've clearly never worked on a bigger python project
actually, you haven't even fricking touched python in the past 2 years
according to this you are a caveman
I'll continue using requirements.txt and there's nothing you can do about it
found the updooter
We must return to monke at once!
works on my machine
dumb dolan dumper
I unironically believe that Python is the main reason Docker exists.
nah, webservices/webapis would have necessitated it without python, but without containerisation I think that python would have died off as the catch all scripting/orchestration lang awhile ago.
it's nice for small stuff, but for anything that needs to scale and has complex cicd it's a fricking nightmare and should be killed off.
rust is unironically better to deploy and it's a fricking ten tonne behemoth compiled language
Completely wrong.
Docker exists because of the fundamental design philosophy of Linux: shared system-level libraries.
>deploy
>python filename.py
wow that was hard
python3 -m venv venv
. venv/bin/activate
python3 -m pip install -r requirements.txt
python3 niglet.py
not that hard
I'm trying to install pyopenjtalk right now and the devs just basically said I need to download visual studio so I won't get a pip subprocess error i think. I'm not sure but thats what im doing rn. That after using conda with a virtual environmenta and installing pytorch nighly. C/C++ is a contender but python is up there. oof.
>. venv/bin/activate
That's a fricking bash source.
A programming language has no business fricking with your shell. At least makefiles and configure keep environment variable shit to the build and compile step.
I'd just like to interject for a moment. What you're referring to as Python, is in fact, Python/Linux, or as I've recently taken to calling it, Python plus Linux.
Python does not have applications unto themselves, but those that represent components and libraries already installed on a full Linux OS as defined by POSIX.
Many computer "programmers" run python-modified versions of Linux systems every day without realizing it. Through a peculiar turn of events, application deployed today are often considered as "written in python", and many of their users are not aware that they are basically just using a Linux system, developed by others.
There really is a Python, and these people are using it, but it is just a part of the Linux system. Python is the glue-code: the hacked together mess that the "programmer" uses to facilitate access to the system and its libraries developed by others with more talent. Python is an essential part of the bikeshed, but is useless by itself; it can only function in the context of the already-existing Linux system. Python is normally used in combination with the Linux operating system: the whole application is essentially Linux with python painted on top, or Python/Linux. All the so-called Python applications are really just components of Linux hacked together!
>every lang has to be JUST LIKE my preferred lang
>It just has to, because..REASONS!
If I can figure it out you have no excuse
Are you too stupid to figure out docker?