Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "line endings"
Biggest challenge: Remember to put ';' (semicolons) in line endings after coding python for 5 years.1
Why the f*** was the computer industry not able to contract to common line endings? The trouble started many years ago when I was coding scripts on my Windows machine and they were not every time able to run on a Linux machine. Well I then somehow learned on the hard tour that this is due to wrong line endings. Thought that might be the last time I've seen such problems in my career...
And 10 years later I was going to migrate from CVS and SVN to git, and BAM: the f****** line endings appears to be causing much more problems than in all the ten years before. Why? I ask why is this still necessary in 2017 that a dev has to think about the line endings anymore?? This is so 1991!!!7
How to piss off a developer?
1) Make your SDK bundled with an IDE and provide no way to update only the SDK, forcing them to loose all of their IDE settings and customizations.
2) Make GNU tools bundled in the SDK that are compiled 10 years ago and haven't been updated.
3) Provide a Linux version of the SDK, but only save all files in Windows-style line endings.
4) Provide SDKs that introduce bugs and break builds.
Had to work in Windows today.
Ugh! how can anyone be productive in that mess???
Having to use the mouse to do anything is not productive.
It took me twice as long to do my work on Windows platform than on Linux.
I am working with a colleague this week and need to use specifically Visual Studio for its TFS, usually I am good with Jetbrains Rider on Linux.
Working in Windows is simply.....slow....In Linux I do everything I need in terminal, in Windows I have to click around find the setting or feature I need click click click....mice need to be deprecated.
And don't get me started on the directory separator, or how user permissions work, or uncommon distorted names for cli functions, or line endings!13
F*cking windows and thair stupid alternative line endings. Spend way to much time on trying to make my bash file work. Aparently i copied some command from a website that used windows endings. Wich f*cked everything up6
My worst code review involves line endings. In one of our products we use the facade pattern, and one of the facades is about 5000 loc.
Well, a dude in our team messed up with line endings, so our diff tool showed that 5000 lines have changed. A newb I was at that time, I didn't know any other diff tool, so I went through all the lines manually only to see that 2 lines effectively have changed.. and the newb I was, didn't thought about rejecting the change immediately! We then had somehow to revert that commit, but messed up our central repo (was still with CVS). In the end we had to restore the daily backup for the repo because we couldn't manage it to do it right.
Never ever had such a disastrous code review again.
Fuck you windows and your bizarre line endings.
^M (CR) all over the place now, fuck this, going to make an automated tool now that converts all line endings to LF5
Spend hours debugging a python script because tests fail. Turns out ftp (the unix binary) adds CR bytes to every byte in a .gz file that looks like a LF on upload (in test setup). Client and server are both linux. 😭
Yes i know switch to binary mode (that fixed it - why not default??). But still WHY CR? Didn't ask for it. No windows in sight.1
God damnit windows and your stupid dos line endings now I gotta dos2unix the entire gcc and binutils source. Just cuz I ran git clone from the wrong “side” of the machine.2
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 :(2