Interesting, that doesn’t even meet the statutory requirements in Canada, which is 1 week severence+ 1 week in lieu of notice per year of employment. One top of that civil case law will generally add another 2 weeks per year of employment for employees who have been with a company for more than 5 years. There are other factors involved in this however. The whole thing generally tops out at about 20 months, too.
Beaker. Even has a smiley. *8-0
That’s what I use. You can pick which weather service you use, too. I’m in Canada, but find that Norway meteorology service is good. When the wife and I are comparing forecasts she’ll ask, “What do the Norwegians say”.
Or later, “Your Norwegians never predicted this!”.
Wow. SNOBOL was one of the coolest, Stange languages.
The question implies that the OP wants to create one giant filesystem with all of their data on it. This has its own issues, especially if it is in /home. For one, as someone else pointed out, it’s fairly difficult to run your system without /home mounted, and that makes it difficult to resize. Sure, you can set up an admin account with it’s home in the /root filesystem and then log into that - but that seems to be a lot of work in itself.
If it was me, I’d set up mount points for file systems that make sense. Maybe /data/Photos, or /data/Music, or data/AppData, or whatever. As much as possible, I’d just point whatever software I was using to those new directories to find the data. If that isn’t feasible, for whatever reason, then a symbolic link from /home/Photos to /data/Photos will work seamlessly in most cases.
As far as I’m concerned, after administering enterprise systems using Unix going as far back as the early 90’s, symbolic links are a key tool in managing disk space that you shouldn’t just dismiss because it’s “an unnecessary layer of complexity”. Having smaller, purpose designed, file systems allows you to manage them better. Sticking everything into /home is probably not the right answer for anyone.
Resizing partitons is often not necessary. Use a symbolic link to relocate a subdirectory to another file system. For 99% of use cases this is indistinguishable from expanding the partition.
I guess they figure that Linux users already know what they are doing when it comes to security.
I call BS.
I’m Canadian and my parents immigrated here from England before I was born. I have a UK passport as well as a Canadian passport.
I’m not English-Canadian, I’m just Canadian. No one hyphenates in Canada, and you cannot say that Canada has any more unifying cultural heritage than the USA.
The US has been there before with the Nullification Crisis of 1832. https://en.wikipedia.org/wiki/Nullification_crisis?wprov=sfla1
He’ll, if the requirements were gender neutral, then every astronaut would be a woman based on weight alone.
Buy Canadian is best, but anything will do if it isn’t American.
In the very first real programmer job that had, back in 1986, the IT department estimated that they had a 51 man-year backlog of development work. That would have translated to two or three calendar years of work. Probably more, considering how crappy estimates always are, and the always under-estimate.
It turns out that this is pretty much the industry standard. Virtually ever place I worked for the next 35 years had a similar size of backlog. And that backlog isn’t standing still, either. All you can hope is that 3 more years worth of new requests don’t come in during the two years it takes to complete what you already have.
Some of those new things are going to have a higher priority than stuff that’s already in the backlog. The reality is that some item that’s down at the low end of the list is going to get bumped down, again and again, and never get done. Or it’s going to someday become an urgent priority that can’t wait any more.
So the pressure is always intense for the developers to go faster, faster, faster. And the business doesn’t understand or care about good engineering practices, even though the shit hits the fan when a critical bug gets released to production. And God help you if that backlog of 51 man-years has grown to 70 after a year because of the technical debt you introduced trying to go faster.
The fight to rein in scope is constant. At that first job, the head of the department told us, “to build Volkswagens, not Cadillacs”. It was laughable, because they were struggling to keep up while building Skodas.
You can’t just add more programmers because the productive backbone of the development team is a group of programmers that have all been there for at least 5 years and they are domain experts. It’s going take at least 5 years to bring new hires up to that level of knowledge.
And that’s all three sides of the project triangle: scope/quality, resources and time. You can’t meaningfully add resources, scope’s already stripped down to bare bones and the time is too long.
And the truth is that every one of those projects in that 51 man-years backlog is important, even critical, to some aspect of the business. But the development process is unfathomable to muggles, so can’t you just go faster? Can’t you wring a bit more productivity out of those domain experts?
Came here to say this!
That’s a little confused. From what I remember, it’s the server that matters, not the domain when being blocked. If you self-host this is a problem, but not if you use your own domain on a commercial service.
The “MX records and such” are all a function of domain management. You’ll have to do this whether or not you self-host.
Maybe…but two things:
If the number of obese people is lower, then what are the people who aren’t mildly overweight? They are healthy weight. So even if the percentage of mildly overweight people stay the same, the day to day comparison is with a bigger group of healthy weight people, so they probably were more recognizably overweight.
Secondly, with less really obese people you wouldn’t get desensitized to seeing fat all the time, which makes mildly overweight people seem more normal. Somebody with a BMI of 26 and about 15lbs overweight would have been more likely to be described as “plump” or “husky” back then. But when crowds are full of people that are 50+ lbs overweight, that 26 BMI seems downright healthy.
This is all speculation. I can’t remember how I perceived overweight vs obese people back in the 80’s.
That’s the thing 40 years ago you would realize that they were overweight.
This is true, but…
Moore’s Law can be thought of as an observation about the exponential growth of technology power per $ over time. So yeah, not Moore’s Law, but something like it that ordinary people can see evolving right in front of their eyes.
So a $40 Raspberry Pi today runs benchmarks 4.76 times faster than a multimillion dollar Cray supercomputer from 1978. Is that Moore’s Law? No, but the bang/$ curve probably looks similar to it over those 30 years.
You can see a similar curve when you look at data transmission speed and volume per $ over the same time span.
And then for storage. Going from 5 1/4" floppy disks, or effing cassette drives, back on the earliest home computers. Or the round tapes we used to cart around when I started working in the 80’s which had a capacity of around 64KB. To micro SD cards with multi-terabyte capacity today.
Same curve.
Does anybody care whether the storage is a tape, or a platter, or 8 platters, or circuitry? Not for this purpose.
The implication of, “That’s not Moore’s Law”, is that the observation isn’t valid. Which is BS. Everyone understands that that the true wonderment is how your Bang/$ goes up exponentially over time.
Even if you’re technical you have to understand that this factor drives the applications.
Why aren’t we all still walking around with Sony Walkmans? Because small, cheap hard drives enabled the iPod. Why aren’t we all still walking around with iPods? Because cheap data volume and speed enabled streaming services.
While none of this involves counting transistors per inch on a chip, it’s actually more important/interesting than Moore’s Law. Because it speaks to how to the power of the technology available for everyday uses is exploding over time.
I used KDE Connect on Ubuntu with Gnome. No issues.
They explained it more clearly later in the article. 4 weeks for the first year, then 1 week for each additional year of tenure. So a three year employee would get 4+2, which is the same as in Canada. But a 4 year employee would get 4+3 which is less than the statutory (1+1)*4 in Canada.
In Canada, once you get to about 6 years of employment, you can start to expect (1+1+2) * (# years). With a cap of about 80 weeks. You’d bust past the woeful 26 week cap with just 7 years of service.
And, BTW: You would need 23 years of tenure to hit that 26 week cap.