Most Adobe tools don’t have any good free alternatives even for home use.
inkscape is on a level with illustrator (maybe even better)
for drawing: try krita
if you want to pay money (much much less than for adobe): Affinity is on a level with fotoshop
it’s safe to assume there are similar issues in closed source. A big part of the snowden leaks was about how NSA could access lots of data at will. It wouldn’t surprise me if they also could execute code.
Also there is stuxnet. But I am not sure, if there were intentional backdoors, or only some “natural occuring” RCE.
is stateless possible without kubernetes? (and without vendor lock in?)
GP said:
RE: Containers, even if you DO go that route, do you really need Kubernetes, which will come at an additional monetary and also maintenance cost? The likely answer at least initially is a big fat “no”.
I agree, that good cloud engineers can save costs in the cloud. But I also think good non-cloud engineers, can save much much more.
When you are rewriting your entire stack to leverage cloud performance, you could probably spend a similar effort for a rewrite that increases regular performance by a similar factor.
RE: Containers, even if you DO go that route…
I was under the impression, that stateless stuff without containers requires a strong vendor login (aws lambda, google functions, azure function). Are you saying, I could do stateless without vendor-lockin and without containers and without kubernetes? This is news to me. Please point me to some resources
what does “get surprised on their own call” mean?
I’m no security expert and the sensible thing to do is using a library instead of taking a class.
Counterpoint: “not knowing your libraries” + “blind trust in the maintainer” will give you stuff like this: https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in
(the thread itself is worth a read. But also very impressive is the list of big players who fell for exactly this mentality)
drastically increases overall build times
oh wow. from 0ms all the way up to 0ms. That’s almost 1000 times faster wow.
We need a SeniorProgrammerHumor community
to get an invide you must have at least 5 years of verifyable lemmy-experience
trend to hate on PHP
2 years ago I tried to give a drupal project the ci/cd makeover (i.e. containers, test-deployments, reproducable builds, etc)… that’s when my hate was freshly renewed.
At this point I think it’s ok to let a dead language die and move on to something else (anything else, really)
Latex: Problem --> \def\please@#1#2#3#4{\e@kill#2#3{\me#1}#4@now} --> 
I don’t see how “scammers creating scam repos” [2] is newsworthy at all. At least the headline seems like a big nothing-burger to me.
farther down in the article are 2 interesting informations, namely this diagram [1] and the fact that scammers seem to have moved from pip to github, and then started to use forks to make their scam-clones appear more believable.
[1] https://apiiro.com/wp-content/uploads/2024/02/Malicious-Package-Timeline.png
[2] 1000 guys make 1000 clones of 1000 legit libraries, and than create 1000 forks of their clones, to make them seem more legit than the original lib. 999 of each 1000 clones get autofiltered by github
–> 100010001000*1000/1000 = 1.000.000.000 infected repos(inkluding forks) and 1.000.000 (wihout forks).
so the number of 100.000 infected repos doesn’t seem to be interesting or unexpected in any way.
how does it compare to yt-dlp?