That's the purpose of reproducible build initiatives like TFA. The idea is to ensure that identical source produces bit-for-bit identical builds on multiple machines when the packages are built.
Sure, if the source itself gets got, then it does nothing. But it at least puts up one more barrier against tampering with the artifacts.
Best example of this is NIMBYs in the Bay Area abusing hearings to block affordable housing, or making it as expensive as possible to replace single family homes with denser construction.
And all of the passthrough towns between LA and SF who have gummed up the high speed rail in court because the state kneecapped its own eminent domain rights through well-meaning self-regulation.
Regulations or the lack thereof aren't good or bad in themselves, but its easy to see why people on all sides of every issue want to make it so; saves them from having to actually argue the merits and demerits.
And nothing is ever simple - the second and third order effects of both regulations and deregulation are hard to know, let alone argue about.
Totally agree - it’s not at all the same. White boarding and the camaraderie you build in person are the things I miss. Thankfully my team still gets together for a week once a quarter. I think that’s an pretty ok balance.
Interesting, I've been using it with zero issues (including performance) for several years now. Compiled stuff, ran scientific calculations, trained neural nets with GPU passthrough, even switched over a workload from an old Red hat box to WSL Alma.
Only weirdness has been systemd can sometimes be quirky, and GUI stuff can be glitchy (which doesn't affect me much, because 99% of what I do is in the terminal)
So, anecdotally it is perfectly adequate for workloads beyond a Hello World. What issues are you running into?
/mnt/c etc from within WSL, and access to Linux FS paths are effectively a plan-9 file share service... Beyond this, if you use Docker Desktop (or similar) with volumes on the host OS (Windows or Mac) it's a weird FS sync between the host and container environment)... if you do volumes in WSL2 inside a Linux/WSL environjment it works fine (normally).
Permissions between Windows and Unix are always (generally) a mismatch, as is the nature of OS differences.
This sounds like pseudolegal folklore (in the US at least). Do you have any actual examples where this affected a case?
In the US, you get copyright on your work automatically, with or without a label.
The only thing a label does in the US is defend against "innocent infringement" defenses. But even that defense doesn't absolve the other party from liability; you just can't recover as much.
There is no reason you can't have `(C) 200X-$currentYear Acme Inc` or whatever.
Yet your earlier comment said "200x-$currentYear" not "200x-$modifiedYear" in reply to someone automatically inserting the year. That shows a misunderstanding of copyright AND an intent to mislead when you believe others view it as last updated.
You're better off omitting it entirely in generated web pages. No one cares unless they don't understand copyright, the year shown isn't the current year, and they're already looking to find fault. In other words, for those that treat it as last updated, they must already be struggling to find value when they scroll to your copyright notice, and at that point, after feeling the page looks stale, is seeing the current year going to change their mind?
I'm not sure what the point being made here even is, beyond arguing just to argue?
It does not matter in the US whether you use the current year or last modified date. At worst, omitting a date entirely makes it easier for the other guy to claim "innocent infringement", which only reduces your damages. Show me one US court case from this century where the tail of a date range had a material affect on the outcome.
Moreover, it is an objective fact that people use the current year and the modified year in web pages being written today. And based on the comment that kicked this whole chain off, clearly people are using it as a signal of when the page was changed.
Glad I'm not the only one! I love these kinds of games; played the heck out of Turing Complete and Zachtronics' Engineer of the People... But I'd never heard of 3 state logic until today.
Really threw me for a loop! I'm still trying to wrap my head around making level 3's NOT gate.
This is such a cool idea, definitely the first 3-state circuit puzzler I've seen! Throw a cute story over it and I bet this would get some takers on Steam.
It's just HP and HPE split up. HPE took all the nice enterprise stuff, plus the supercomputing business (they own Cray). HP took the consumer stuff, and proceeded to milk as much as they could.
No, wrong decade and wrong split - the test & measurement equipment and scientific equipment was long gone from HP at the time of the HP -> HP inc + HPE split. It ended up in Agilent (1999) and from there Keysight.
HP semiconductors went HP -> Agilent -> Avago, now broadcom.
I've got two garages full of 80's and 90's HP lab equipment, and most of it even works. In that era, HP had the best hardware design/production capability in the world.
Unfortunately, in the same era, their software was almost always complete crap. I think the same rigid processes and controls that allowed them to make great hardware were the reason their software was awful. Their rigid processes made changing the software difficult, so it was harder for the devs to improve (and they usually didn't bother).
Sure, if the source itself gets got, then it does nothing. But it at least puts up one more barrier against tampering with the artifacts.
They have a tracker for what percent of the distro is reproducible: https://reproducible.archlinux.org/
reply