It’s really nice seeing the project continue to move forward after Mozilla took out support.
It’s really nice seeing the project continue to move forward after Mozilla took out support.
If you own an instance it’s better to check with a lawyer. They might give you a warning first or they might go after you immediately. How effective that is depends on what country you live in and which country the server is in.
On the flip side I sold my house in December of 2019. Then decided to rent for a year to figure out where to buy next. Didn’t pay close enough attention to the market before it was too late. I still stay up at night sometimes thinking of how bad that went.
You didn’t get any instructions before hand? Is this in higher education or earlier?
You having regrets depends on your expectations. If you want a very stable system with little maintenance then you’ll be happy. Packages will be older but that’s what makes it easy to keep stable.
I’m not personally a fan of vanilla Debian because the stable versions are a bit too outdated for the things I like to work with. I do use Debian derivatives though the LTS versions.
Because the seals on the mask itself weren’t rated and they didn’t go through FDA authorization. You HAVE to go through FDA clearance if you want to claim your product meets medical standards.
I protest voted one year because I hated the candidates. That was the year Trump got elected. I’m never doing that again. Lina’s well worth supporting in the next few elections, but the real options this year are already set. Everything else is equivalent to not voting at all.
I highly doubt someone who’s struggling with a phone is going to do well with a screen projected on your hand that has very sensitive hand interaction requirements.
I knew someone who did this but swapped out the physical hard drive each time. I wouldn’t dual boot because then it’s much more obvious to IT what you’ve done.
This is only realistically feasible though if the hard drive is easily accessible. If it’s something like a Mac or soldered in dual booting is your only choice. As others have said, this could get you in a lot of trouble with your company. Check the docs you’ve signed
You should also check out git commit --fixup ...
paired with git rebase -i --autosquash ...
. you specify a commit target to the fixup to say you want to fix that commit with the code you’re currently committing. It will create a fixup commit at HEAD. The auto squash will reorder your fixup commit and mark it as a squash so you have way less work to do.
It shouldn’t break if you just install packages from the main app installer. It’s more of a concern if you’re trying to install anything from source.
Also make sure to try a live cd or live USB to make sure the OS is compatible with your hardware. VM is not sufficient for this last one. This is usually only an issue if you have very new hardware.
I would get comfortable with the idea of breaking things. Make regular backups of your data. The best that I’m aware of for making it easy to work backwards from breaking things is NixOS, but I wouldn’t consider it beginner friendly.
You learn a lot from trying to bring a system back online. But it depends if you’re trying Linux to learn it more or just to take advance of privacy.
Yes, though this is true of a lot of the easier distros.
Not a lawyer, but worked closely with them in the past. It REALLY depends on your employment contract. Changing variable names and language still makes it a derivative work, so it would depend on the original license. I’m assuming it doesn’t have a license which would mean either you or the company owns the copyright: depends on your employment contract. Whether you’re a contractor or full time also affects ownership.
Without ownership or a license, you do not have the legal right to copy the work or make a derivative of it.
I’m not clear on whether you actually wrote any code though. If that’s the case (that no code was written) then I’m not really sure how that works out. If you do post it and they find out, AND they’re mad about it, you could definitely get fired. I’m not sure if there could also be legal trouble or not.
If you need it for a resume item, you can just list it on your resume and talk about it. You could also implement it on your own time (but not share it until you’re sure you’re safe from legal action), that way you could talk about tradeoffs you’ve made, etc. in the real implementation.
In general, if you’re not sure and you’re worried about getting sued, you should ask a lawyer.
I was newish to Linux and had just run rm -rf ./.*
to remove all the hidden files/dirs in a directory. I then wanted to run rm -rf ./*
to clear the rest, but I accidentally ran rm -rf . /*
. By the time I noticed it was taking too long and hit Ctrl+C, it was too late.
What IT guys did you go to?
How complex are the API calls you need to make? Debugging interop mismatch can end up being more work than writing the tests if you need to deal with complex types.
The .NET languages support c interop. The documentation could use some love though.
Had a team of 10 working nights and weekends for a month because someone in sales sold a contract for an integration with a 3rd party that didn’t exist yet. In the years I was there after that project shipped, only 1 person even looked at the feature, one time. It never actually got used
Can we get those settings for adults too?