rm - rf /

I'm new to DevRant

Made an account just to say how much I hate lf-crlf errors. Fucking waste of time. Everytime. Feeling creative? How about spending hours on SO?

The first time you go to DevRant :
- " Mmh not bad "

When you realise you can win a stress-ball :
- " OMG need to find something funny to say !! "

It's almost 2019 and CRLF is still a fucking thing

Fuck CRLF.

CR? LF?
Who cares, this is Windows, we accept all line separators!
#CRLF

U: we had LF, which is enough for our needs
W: you know whats cool? lets have CRLF, because why not

/me joining a new front-end project with enforced prettier rules to complete the build pipeline.

No double-quotes ! Single-quotes all the way !

- weird flex, but OK. I'll comply

No CRLF ! LF only !

- Ok, now you're starting to annoy me. With git autocrlf I can have my precious CR locally bu check in only LF and YOU CAN GIVE THE FUCK ABOUT WHAT LINE ENDINGS I USE LOCALLY WHEN EVERYTHING WILL BE CORRECT WHEN PUSHING COMMITS!

No semi-colons !

- Now I hate you

Convert all LF to CRLF

or

Convert all CRLF to LF?

UGH.

CRLF line endings.

Opened a minified css file. Went online and unminified it. Came out to be 12k lines. Coollllll.

New war idea: CRLF vs LF?

Why did my bash script stop working?

I accidentally pushed back to git from my windows machine, and it sharted on all my line endings. What a waste of an hour :(

First time I've had a problem with LF & CRLF.... Stupid university assignment wants us to store data in an EFFING TEXT FILE, so my Windows group mates were like "why are the data in the file all in one line?"

So your API sends uncompressed JSON AND with CRLF instead of LF?