Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "bloodshed"
-
Started a new game dev job. Fortunately, they already have a Rubber Ducky chilling at the desk. Only thing, it's less of a duck and more of an evil imperial guard with a lust for bloodshed. I hope he likes C++.1
-
My dream project -
An App that will reduce human impressions from this country without bloodshed.
Seriously ... People are everywhere, here. It is surety that you will get to see some or many people, no matter where you are. Park, Jungle, Mountain, River bed, Abandoned Land, Osama's bunker, House with annabelle ghost, Cloud, Space, Other planet .... damn
That way I am only helping mankind and nature. And then I will get nominated for Nobel Prize too.3 -
Hate grows inside my soul when you are talking about a new feature and it's implications in the code base. Then you suggest a first approach, everyone agrees but one, someone whos rotten soul is craving for bloodshed, someone who says something like "Hell now, that's too much work" and then after hours of arguing he/she/it proposes the exact same approach... saying it's a better way.
-
Have you ever used Dev-C++ back in the days? For me it was a bloodshed, just like the name of their company.3
-
Using Bloodshed Dev-C++ and not wanting to change that for Visual Studio.
Transistion for VS wasn't simple, as I learned from the beginning od Dev-C++ and amount of 'hacks' that worked in DevC++ and didn't in VS were frustrating me. After a while I understood that DevC++ was a bad first choice IDE and things it did shouldn't have place, but habits die hard I guess.
Still like the lightweigh it had, tho. Wish VS was so simple in use at the beginning. :)1