Ok, I understand what you meant, thanks.
Basically, after I’ve read all of that, it’s clear as day that security is not a priority on Testing. And while band-aid solutions do exist, it’s simply not designed to be secure.
Yeah, I wouldn’t run it in a production environment.
Sure, but even in those “few cases” Testing will get them soon.
I did read at some point that Testing may receive security updates later than stable, might be in those cases in which backports come straight from unstable.
I don’t recommend going for (Debian’s/Devuan’s) testing (branch) as it targets a peculiar niche that I fail to understand; e.g. it doesn’t receive the security backports like Stable does nor does it receive them as soon as Unstable/Sid does. Unstable/Sid could work, but I would definitely setup (GRUB-)Btrfs + Timeshift/Snapper to retain my sanity.
From https://backports.debian.org/ :
Backports are packages taken from the next Debian release (called “testing”), adjusted and recompiled for usage on Debian stable
So by definition, security backports in stable are present in Testing in the form of regular packages, right?
I remember having some issue like that, but I’m not sure if this was the fix.
Try unchecking “Show desktop notifications when the song changes” on Spotify’s settings (right now it’s under the Display section).
Makes sense, thanks.
New to Linux: in which case would you stick with an “old-old-stable” release?
Software incompatibility?
The band played 2 early albums + their latest one in sequence. Listening to whole albums in one go was great for many reasons.
Fellow PT-PT ISO user here. And although I use PT-PT in the OS, both my mechanical keyboards’ physical layout is DE ISO, which has most special symbols in the same place. (finding DE keyboards is easier)
I’ve considered switching to UK ISO before. Typing brackets “[] {}” and a semicolon “;” is harder in PT-PT.
Especially the curly brackets {}, which are really awkward to type with my small hands.
One that is written in C and also has a Python module: https://aubio.org/
I don’t agree with the problem they aim to solve with those goals.
But today it takes several years of mastering tools and frameworks to get to that stage. HTML First principles should allow people to unlock that feeling, and level of mastery, much earlier on in their coding journey.
The onboarding process can be made easier for devs new to the project (junior or senior) with decent documentation. Just enough install/build the project in their local machine and understand the gist of the technologies.
May be a coincidence, but it stopped launching for me too. Worked Monday and Tuesday, yesterday I didn’t try to play, today it didn’t work.
Tried:
I’m running a 6700XT and weirdly enough it pre-compiled in Linux but not in Windows.
It’s really stuttery for a while in Windows, with low GPU usage and erratic frequency, until it normalizes.
I’m getting none of that in Linux, smooth from the start in-game. Only getting some weird fps fluctuation in the start menu.
Makes sense, thank you for the clarification.
It is also a file browser.
And apparently also supports FTP/SFTP, quite nifty.
I’m new-ish to Linux and new to Debian, but I literally just did a (second) Debian 12 install, so I have one note about your Firefox’s documentation, specifically about “chromium’s suggestion” when uninstalling Firefox. https://makedebianfunagainandlearnhowtodoothercoolstufftoo.computer/doku.php?id=start:firefoxesr
Besides Firefox ESR, it came bundled with “Konqueror”. Don’t know if it depends on your installation’s configuration, though. I selected to install “non-free” software, if it helps. So for me it didn’t complain when I uninstalled Firefox ESR, it just set Konqueror as the default web browser
you can easily forget to catch it and handle it properly
Even if I coded the form by hand and that happened, it’s on me, not on the programming language.
But I don’t, I use a framework which handles all that boilerplate validation for me.
When you say user, you mean a user of a function? In that case PHP would throw a TypeError, and presumably only happens when developing/testing.
If you mean in production, like when submitting a form, an Exception may be thrown. In which case you catch it and return some error message to the user saying the date string is invalid.
My point is, you won’t ever try. You’d only use “weak” variables inside the function you’re working on.
It’s explicit when you absolutely need it to be, when the function is being called and you need to know what arguments to pass and what it’ll return
I like it in modern PHP, it’s balanced. As strict or as loose as you need in each context.
Typed function parameters, function returns and object properties.
But otherwise I can make a DateTime object become a string and vice-versa, for example.
I don’t know if we’re discussing semantics. A performance score is attributed, and before the fix their scores were all 166. It doesn’t work, as you said. So the consequence is the preferred core being “random”, isn’t it?
This one in South Korea is pretty recent (October 2022).