@ChrisWere I like letting the user design. Not creating such a restrictive design that they can't freely resize. Letting them resize the window so it's comfortable. Like HTML is supposed to be - flexible.
(Your site does all this).
@ChrisWere @uoou It's actually poor web design. Too wide (or too narrow) text regarding anything will make it harder for the reader to focus on the text and too wide text makes it harder to jump to the next line and keep the flow when reading.
A correct width has also been proven to help with the level of engagement for the reader.
There's a lot of information regarding this on the web if you're interested. It's actually a quite interesting topic. :)
@hund @ChrisWere I know, that's what I was referring to. But the idea that text in a web browser can be "too wide" is nonsense - resize your window until it's not. The best thing you can do is give your user the ability to *choose* how they'd like to view your site and fixed text widths impede that.
@uoou @ChrisWere With that logic we don't need web standards at all, or any kind of standard for anything. Maybe not even laws? Because after all, people are expected to know how things works without any knowledge or help regarding the subject. Subjects whom others spent years researching and thinking about.
Warning: Might contain sarcasm.
@hund @uoou @ChrisWere no but I do know how to adjust my car seat, mirrors and change the occasional light. And on my monitor I know tow to adjust the stand, brightness and contrast. Expecting end users to know how to adjust things to tastes is not the same as expecting them to write their own Web page.
People have different sized monitors, some people like to maximise, others not. People have different font size preferences. And, while there are sensible guidelines (with which I agree), people prefer different line widths.
There's no prescriptive method that works for everyone - the web doesn't have a fixed 'page size'.
@ChrisWere I would do that with no second thought
You should put your website under version control. Pages like this would benefit greatly.
@ChrisWere I believe that you can omit the -acodec with ffmpeg if the file ending is already an MP3.
For that matter, you could probably describe the whole syntax of basic ffmpeg commands like so:
ffmpeg -i input.mp4 [-r <target framerate>] [-c:a <audio codec>] [-c:v <video codec>] output.mkv
@benrob0329 Nice! Thanks for that tip.
I haven't mentioned it, but I do intend on giving the simplest version of the commands possible, so that's a really useful bit of info there.
Linux Geeks doing what Linux Geeks do..