It's not a mirror. It's the primary repository. And yes unfortunately they aren't accepting PRs or using it for issue tracking, but it's a start.
Ha no. SQLite can easily handle tens of GB of data. It's not even going to notice a few thousand text files.
The initial import process can be sped up using transactions but as it's a one-time thing and you have such a small dataset it probably doesn't matter.
I don't think there were any standards for this sort of thing when Flatpak and Snaps first came out, and they arrived at the same time and have pretty big differences. So this doesn't apply.
Not sure about freelance, but for a salary in my experience, answer some recruiter spam on LinkedIn. I always thought they'd be crap since they are spammy... But after using some I've totally changed my mind. At least in my industry (silicon verification):
- Companies use them.
- You get a foot in the door & can bypass all the HR crap.
- They know all of the relevant companies. I learnt about my current company from the recruiter.
- They give you some hints about the interview process.
- They do all of the chasing up for you.
Also, they get a big payoff if you get a job, so their interests are more or less aligned with yours. The only slight difference is that they just want you to get any job, so they might push you to a job you don't really want. But it's minor.
Basically you get a lot of benefits for using them and you aren't paying the cost - the company is. They won't pay that cost to you if you don't use a recruiter and save them cash, so there's no real reason not to use a recruiter.
It may be very different for less niche sectors; I don't know.
You can transform any recursive algorithm into iterative pretty easily though; just create a manual stack.
The rule definitely makes sense in the context of C code running in space. Unbounded recursion always risks stack overflow, and they probably don't have any tooling to prove stack depth bounds (you totally can do that, but presumably these standards were written in the 1500s).
pointing and saying “this is shit. Look at this shit”
Yeah you only get to do that if you're Linus 😄
Go to bed, you're drunk.
This, of course, only works on little-endian machines. On big-endian machines, c has to be bytereversed.
Interesting advantage of little endian!
uv is fantastic. I would highly recommend it. I've used it in a quite complex environment, with no issues (quite an achievement!) and it's about 10x faster than pip.
I mean... I guess it's not surprising given uv is written in Rust and pip is written in Python, but even so given pip is surely IO bound I was expecting something like 4x improvement. 10x is impressive.
They chose “version” because they are just that, versions. Improvements over the original design that benefit from new insights and technological improvements. We’re lucky they had the foresight to include a version number in the spec.
No they aren't. A higher version of UUID isn't "newer and better", like the word "version" implies. It's just different. It's like they called a car "vehicle version 1" and a motorbike "vehicle version 2". The common use of "version" in the software world would mean that a motorbike is a newer and hopefully improved version of a car, which is not the case.
The talking pumpkin is 100% right that they should have used "type" or "mode" or "scheme" or something instead.
Saving this for when people try to claim that naming things isn't important!
Also that is clearly a security issue. Anyone who tries to claim otherwise is forgetting that humans exist. Though I suspect they were just trying to avoid admitting fault and doing work. Disappointing either way.
FizzyOrange
joined 2 years ago
I think this strategy makes perfect sense and is really working.
Most of the open source community uses Linux or Mac for development. Windows is pretty much an afterthought. You even sometimes see "cross platform" projects that don't work on Windows.
But now that you can use WSL for all that development there's much less reason to use Linux in the first place. At my company we have a couple of hundred people using Linux, and we're considering all moving to Windows with WSL because the hardware support on Linux is just too unreliable - random crashes, laptops not going to sleep when you close them, poor thermals, bad memory management, etc.