Stayed up extra late fixing a bug. Fucking bug is buried in a thousand lines of MOTHERFUCKING SML.
FUCKING ASSHOLE SHIT-WAGGLING COCKSMEAR AND THAT SHITTY, GODDAMNED BACKWARDS FUCKING LANGUAGE!
Fucking wasted an entire night chasing down a fucking bug in SML with no positive effect.
I wound up commenting out 7/8 of the entire fucking codebase to try to find the fucking bug. No positive effect.
Finally had to go to sleep because my son was about two hours from waking up.
Getting back to work, and within twenty minutes I found the fucking bug and fixed it.
Fucking wasted nearly an entire night's sleep, and I ended up fixing the fucking bug before finishing my morning coffee.
I seriously fucking hate motherfucking SML.

Good. Rant all you want. Thats why we dev bros are here to help in ranting : that motherfucking bugs of yours.........

Reseting (sleeping) usually saves me more time then if I tried to fix a bug for that long. 😋

@wolt SML is very useful if you want to do one or two simple tasks recursively. (like changing all the ' ' chars to '_' chars) Very useful as a child process to a more flexible language, but as a standalone program it is like trying to ride a bike that only makes left turns, the steering components are made out of reinforced concrete with no bearings or lubrication, you have to backpedal if you want to move forward, and if you slip up and pedal forward (as is the natural inclination) then it will find the nearest wall and crash into it.
Also, it is very VERY anal about allowing you to use printouts.
It also does not allow bitwise computation naturally
Plus the documentation has huge gaps and is largely outdated.
You read that right: You can't just type "print("Hello World")", you need a very particular instatiation in order to print to screen without closing out the entire fucking compilation unit.