

Your talking about their discretionary powers and that’s not going to be relevant on a protest enforcement action where their senior officer in command will have laid out exactly what the criteria to arrest is.
FLOSS virtualization hacker, occasional brewer
Your talking about their discretionary powers and that’s not going to be relevant on a protest enforcement action where their senior officer in command will have laid out exactly what the criteria to arrest is.
Yeah I don’t think this is an ncdu issue but something is broken with the OPs system.
I’m not surprised. My mum would tell me stories about dodging creepy old men on the train when going to school in the 50s. She seemed to accept it as just one of those things and I’m sitting there with my GenX sensibilities thinking yikes!
I don’t know why we couldn’t have what we already have on mobile. My kids phones have isp enforced restrictions that prevent them stumbling onto most adult sites. At home I’ve got their devices fairly locked down but I’m fairly technical so know how it works. I don’t know why households couldn’t just have a setting with their ISP that allows them to opt in/out of blocking non-OSA compliment sites rather than doing a blanket censorship.
I get the reasoning behind the OSA - a lot of parents don’t know how to protect their kids online and defer to the government to sort it out. However the implementation has been a giant flustercuck.
Looks like 🙂
On the actual topic I know a number of people getting injection privately and swearing by the results. There is a pretty aggressive referral campaign as well which considering the monthly cost is going up you can see why people will sing it’s praises.
Not exactly complaining about grannies being arrested are they?
For context watching South park?
There is a difference between reviewing code and the feedback when you have the job and during an interview when trying to get a job. I’m not saying you should never expect to be pulled up on mistakes just that an interview experience is very different to the work experience.
Maybe there are ways to ameliorate the stress during the interview to get a better view of how a candidate will perform once hired but I think it’s a tricky balance to strike.
I think there is a difference in setting. Pair coding is a useful exercise but demands a degree of trust that the two of you are working together on a solution rather than one of the pair judging the other.
If you’re expecting to be stressed all the time at work then that is a red flag. Some professions may involve a degree of stress, which should be mitigated, from time to time but software engineering shouldn’t.
In my first interview they put me in a room with a PC with Borland C and a copy of K&R and a sheet with a simple problem to solve and some extra enhancements if I had time. They said they would be back in half an hour and left me to it. That I passed fine.
Some twenty-ish years later I was asked to write a C function to reverse a string on a white board and I failed because I’d misformatted the for loop. I don’t think it was because I’ve become a worse C coder in the intervening years.
When I’m actually coding I’m sat with my editor configured Just So with completion, compilation and unit tests at my finger tips. My favourite coding music blasting my speakers and a handy browser window for looking up anything in unsure of. This is my most productive setting and expecting the same performance in a stressful interview setting is foolish in my opinion.
Working through problems on a white board can work well but you are looking for the problem solving approach, not an encyclopedic knowledge of regex syntax. Those same problems get immeasurably harder when explained over a phone call.
My personal preference when evaluating candidates ability to code is reading their actual production code, the break down of commits, the commit messages and the sort of unit tests they add with a feature. The interview is more focused on their soft skills, what about the work excites them and what they are looking to get out of the role.
You could if you want fork from when it was GPLv3: https://github.com/stenzek/duckstation/commit/7f4e5d55dbdef5a50e0aa4994f667fb03d854928
From the linked comment it sounds like there was a license change in the projects history. I’m surprised the various distro packagers didn’t just collaborate on a renamed fork, unless there are more actively developed emulators still under a FLOSS licence?
Edit yep it was GPLv3 about 11 months ago: https://github.com/stenzek/duckstation/commit/7f4e5d55dbdef5a50e0aa4994f667fb03d854928
I’ve got an Ampere workstation (AVA) which from a firmware point works fine. They may even fix the PCIe bus on later versions.
Asahi is a powerful example of what a small well motivated team can achieve. However they are still face the sisyphean task of reverse engineering entirely undocumented hardware and getting that upstream.
If you love Apples hardware then great. Personally when I have Apple hardware I just tweak the keys to make it a little more like a Linux system and use brew for the tools I’m used to. If I need to I can always spin up a much more hackable VM.
Arm has been slowly pushing standardisation for the firmware which solves a lot of the problems. On the server side we are pretty much there. For workstations I’m still waiting for someone to ship hardware with non-broken PCIe. On laptops the remaining challenge is power usage parity with Windows and the insistance of some manufacturers to try and lock off EL2 which makes virtualization a pain.
My octopus rate gives me 15p per kwH I export. The overnight rate is 7p per kwH so it makes sense to export as much as I can and charge the car on cheap rate.
The gap between sunset and cheap rate is about 4-8 kwH so rather than getting a battery my next step is a bi-directional charger so my car can cover the gap.
No - the inverter needs the 50hz signal from the grid AC to work.
There are large areas of open source that don’t rely on volunteer labour because companies with a vested interest pay people to work on them. They tend to be the obvious large projects that are continuously developed and gain new features. The trouble with something like xz is it was mostly “done” (as in it did the thing it was intended to do) but still needed maintenance to address the minor niggles, bug reports and updates to tooling and dependencies.
The foundations could do a better job here of supporting the maintainers. After Heartbleed the Linux Foundation started the Core Infrastructure Initiative to help fund those under recognised projects. I would hope the people running that could be more proactive identifying those critical understaffed components.
Edit I think it’s now called the Open Source Security Foundation: https://openssf.org/