You can start steam just fine without the packages. In fact, if you install without them, it'll ask you to install them every time, but you can skip that and it'll work, just 32bit games won't launch
Edit: Looks like I'm partially wrong, as pointed out by a commenter below, steam currently only launches the 32-bit version of the client, despite support for a 5l64-bit client
Eine Minute später kommt der Zug, der vor zwei Stunden kommen hätte sollen, neues Problem
It'sintended to be used when the cookies are actually required for the app to work. For example, to preserve your login, you need a cookie, no way around. Unfortunately, as mentioned by others, it's often abused
Does "Database > Merge from Database" not work for your case? I remember it helping when I had a similar situation
When everything closes, are you sure that's the lock screen and not the login screen? It sounds like cinnamon is crashing, which means you're automatically switched back to the display manager (login screen). This can sometimes show the boot logo while it's switching, happens on my laptop as well, noy sure why that is.
If it is crashing, you might find the cause in the logs, run journalctl -e and dmesg to check for errors
555 is still in beta, so I wouldn't be surprised if something doesn't work. That said, I haven't experienced what you have (on GTX 1070 TI), though using 555 causes lots of kernel errors for me. Checking dmeg might reveal something in your case as well.
Usually we don't distinguish between many2one and one2many, since it's the same just viewed from the other entity.
There is one more class though, which is one2one. That is, the entities have a direct relationship. Sometimes this also includes the case where you have zero or one, i.e. the relation is optional on one side. This can be accomplished with an FK plus unique constraint or by merging the tables.
Love the expressions in this
streaming small commits straight into the trunk
The image even calls it like that
Some things don't have good CI/tests, so it doesn't make sense to include the build step, especially on a small team where we trust each other. But yes, it's not good practice, and we don't do this on every project, but sometimes it's necessary to adjust the flow to the specific project
With git. Every time we start work, we pull. After every commit, we push (and pull/merge/rebase) if necessary.
We do, for two 2-3 person projects, where no code reviews are done. This is mostly because (a) it's "just" a rewrite and (b) most new functionality is small and well-defined. For bigger features a local branch is checked out and then merged back later. Commits are always up-to-date, which makes it much easier to test integration of new featues.
Not quite correct. For html, that is to signal standard compliance, you can leave it away and the browser will still handle it. For the bash one, all (most) shell scripts use .sh, so you need to give a shebang to tell the loader which executable (sh, bash, zsh, csh, ...) to use
Also on Linux xdg does take file extensions into account, just executables do not