As a web dev a lot of this is simply ongoing maintenance of a largely unknown quantity. Most web devs know React and use it extensively; Astro is something they'll have to learn on the job or hire for specifically.
It's akin to writing a backend in Haskell. Chances are you could write something performant that leverages FP in a way that serves as a magic bullet for your domain. But now everyone after you needs to learn Haskell and how to model all future problems in a way that conforms with it - or rewrite things again.
This was far more of an option in the 1980s and earlier; a CEO being compensated 20-30x a line employee was pretty standard around then; now it's closer to 250-300x. I think there's more optionality than we may assume, we've just left the structural incentives that drive that difference in place.
This does suppose there are good jobs in the area, which can be a bit hit or miss especially out in the sticks. Not to say one couldn't move, but moving isn't in the cards for everyone.
> Taking this argument to its extreme, does this mean that introducing new technology always decreases technology?
I assume you mean "decreases security" by context. And in that case - purely from a security standpoint - generally speaking the answer is yes. This is why security can often be a PITA when you're trying to adopt new things and innovate, meanwhile by default security wants things that have been demonstrated to work well. It's a known catch-22.
In all fairness, a LOT of this was copied over from the military. From ranks to "High Year Tenure" (aka "Up or Out") nothing here is particularly innovative.
SKG is basically "right-to-repair" but for games. I do contend that if your phone breaks and the company says "we won't fix it and you aren't allowed to" then the government isn't doing its job. On the same token, if a game that you purchased turns off their servers and says "we won't run it and you aren't allowed to" then the government isn't doing its job.
Now, how I would be able to run it is a very open question and I do agree there are some ways that are more reasonable asks than others. But the present-day status quo of "company says suck eggs and you just have to deal with it" is not an acceptable final state.
The text "prevented further rollout and ultimately got the cameras shut down" is verbatim in their post maybe a few sentences after talking about how the muni piloted them.
Depends on the token; JWTs usually have payloads that are only base64 encoded. As well, if there's a refresh token in there it can be used to generate more tokens until invalidated (assuming invalidation is built in).
I don't consider myself fully qualified to speak to this, so please take it with a grain of salt.
From what I gather it seems like you could potentially create scenarios where TOCTOU is indeed a problem, but in considering the situations where it could come up I do feel like all my ideas are somewhat contrived in nature. And even when noodling on it I very much get the feeling that I return to my previous statement: consider what you're building. I think that the potential for TOCTOU could potentially compromise a hypervisor's security (i.e. letting an arbitrary number of user on a system make arbitrary io_uring calls) and even if I couldn't demonstrate how that could be weaponized I would avoid it. However, if you're writing an application that's going to do a read(2) or something, I don't see TOCTOU being a uniquely io_uring problem.
I've only dabbled, so I'm happy to have people with more linux-side knowledge to call me out on any inaccuracies here, but...
io_uring is effectively as "secure" as any other syscall unto itself. The issue is that the mechanism by which io_uring makes its syscalls as part of its submission/completion queues means that those underlying syscalls can't be filtered by seccomp. The real question is your security posture.
If you're writing a hypervisor that's intended to partition resources between underlying users in a secure fashion, the ability for io_uring to bypass seccomp is largely a non-starter. But if you own the machine and you just want to run an application on it (i.e. an HTTP server that uses io_uring for file/network io) you should largely be in the clear.
Similar sentiments here. I can't find much common ground with Charlie Kirk but that doesn't merit an assassination. Unfortunate all around, and a situation not too dissimilar from the Mangione case (in the context of what happened, not necessarily why).
That said, while I don't condone it I can't say I'm surprised by it. It seems stoking divisions is a large part of the modern media landscape and all it takes is one person with the motive and the means.
Yes, arrow functions have a different (and more intuitive) lexical `this` than their more verbose counterpart. It is subtly more than just a syntax sugar.
Seriously though! One of my Aussie buddies recently switched over to a recently-opened Oceanic server and while I was lamenting the loss we joked about not needing to step on each other's toes with scheduling.
I would wake up after my dad was gone for work, grab a pop-tart or cereal, take a ~1/4 mile walk outside to the bus stop, no longer able to see my house from the suburban sprawl, and hang out with the rest of the kids at my stop for 5-15 minutes before the bus showed up. Then I eventually got a car.
Don't get me wrong, if I was offered a ride (my parents, friends parents, friends with cars) I'd often take it. But ensuring I got on the bus? When the alternative was that my parents would get a phone call about me being missing? Trust that the lessons I'd get at school were far preferable to the lectures I'd get at home if I skipped class.
The US observance of DST was done for energy consumption, largely coming out of our 2 world wars when energy was a key issue. That said, in watching a state that relatively recently adopted DST, it actually increased energy consumption[1].
Meanwhile, research has shown that the impact of losing an hour due to DST observation has an impact on the heart[2][3][4].
So this policy appears to be one that literally saves lives while at the same time having the additional benefit of potentially reducing energy consumption at a time when we're dealing with an energy crisis.
> Policy decisions based on dodgy, whataboutism-esque figures
You're arguing that people should increase their exposure to acute myocardial infarction (among other concerns) to account for dodgy whataboutism-esque energy consumption figures from the 1910s and 40s-50s that have been observed to actually increase energy consumption in modern times?
All I'm going to say is that - after experiencing about a decade of living in AZ and not worrying about toggling time - I'd still be in that camp that support permanently choosing a time.
I'm all for either implementation of this (standard or savings); I have no particular skin in the game when it comes down to where daylight hours are positioned. Having lived about a decade in Arizona it literally never negatively impacted my life once.
Since moving I've come to participate in what seems to be the standard dread of moving hours back and forth. I either lose sleep and need to adjust my Circadian rhythm or I gain a one-off hour to... I dunno, lay in bed longer because I've already gotten my sleep?
The worst is being a gaming raid leader (and I'd imagine anyone dealing with globalized scheduling), though, because every time we do this I have to reach out to my gamers in other states/countries who don't play collective clock madness and ask them to adjust to those of us that still do for what appear to be largely outmoded "reasons".
Alternatively, if all you're doing is supporting RSS, you could opt to just use the DOMParser API (native to most browsers) and navigate a DOMTree which is a type of JavaScript Object already...
It's akin to writing a backend in Haskell. Chances are you could write something performant that leverages FP in a way that serves as a magic bullet for your domain. But now everyone after you needs to learn Haskell and how to model all future problems in a way that conforms with it - or rewrite things again.