The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I never can get used to the number of shell aficionados who insist that for automatic operations, such as cron tasks, you must have a command line interface and a script or configuration file. How could you otherwise tell what, say, the backup system should do nightly?
If you try to argue that you could select what to do in a GUI (e.g. select which directories to back up in a directory tree presentation), activate options by check boxes, radio buttons etc. with proper labeling, help functions and menu selections of previously defined plans, and have the backup application preserve that in its internal format, these shell guys gasp: But then I have no control!
Even though they (may) admit that in theory it would be possible to manage a system the way it is usually done in a Windows environment, it would not give them the necessary control. Control is that which is exercized in 7-bit ASCII input by use of command line actions.
In my archives of computer humour, there is a printout of a long discussion on NetNews (The discussion forum in the pre-web-days) from the late 1990s: This one guy who stubbornly insisted that high level languages were useless and would soon fade away. His major argument: He wanted the VAX C compiler to compile one of his functions to exactly that one machine instruction, and there was no way he could make the compiler do that! Others pointed out that it would be silly to use that instruction in that context, but he insisted: If the compiler wouldn't do what he wanted, it was useless and should be thrown away. Assembly code is the only way to get what you want! ... This was in the 1990s, not the 1960s...
When I talk with shell guys that insists that GUIs are useless for serious work, I think that they must be close relatives to this assembler code guy.
I think shell and console apps are useful for automation, but for serious work a GUI is intuitive, shows you what's possible and enables you to work without reading a lot of documentation.
Anyone who says GUIs are useless haven't worked with good UIs or are just pretentious jerks
And maybe some people still live in the past where GUIs weren't invented yet.
Can it be harder than LaTeX (did I get the stylization right?)? I remember fighting with this thing for the sole reason of everybody else doing it and brackets, which permeate scientific writing like mold are a friggin' nightmare. The escaping rules for them are less consistent than escaping in C for no good reason.
My wife wrote a big document with latex back then... I lost count how many times I had to jump in (without having learned latex) to get the format as she wanted and / or to fix things
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Actually, I don't mind that kind of key sequences as an input method, sort of like an extension of control characters and function keys. In an HTML editor, I wouldn't mind if two blanks followed by return would replace it with <p>[newline]<p>.
But actually, I hate HTML / XML as an input format; it is like writing a user application in x64 assembler code (with no debugger available). If you need markup/markdown, you are writing a text document. Then you should use a document editor, not documentation assembly code - whether you call it markup, markdown, Postscript, HTML, TeX or LaTeX - they are all like different document CPU instruction sets. Not document development languages.
but it's disorder surely dissert wouldn't be last?
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
Depends on the type of question. If it's a "this doesn't work / what's wrong" then it's QA for sure. If it's a narrative or liable to be a long discussion, then the forums are a better bet as conversations is what they are all about.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
The discussion boards are for discussions. Possibly rambling, possibly focused, but free-form without necessarily requiring a reply to be an answer. Great for exploring or discussing a topic.
Quick Answers is for direct, specific questions and direct answers. It's not a place to have long discussions. Questions need to be posed in a way that means they are understandable and have a chance at being answered, and answers should be focused and to the point.
Discussions for discussing. Quick Answers for answering quickly.