Maven? Fucking nightmare! All the dependencies, and installs, and builds, and XML files, and setting the projects, and downloading, and... pisses me off. Specially since I can work out things in a much more simpler way by just linking "User Libraries" with Eclipse. Seriously.

Maven is explicitly designed to download fresh incompatibilities.


All the systems have a dependency version 2.4.5. One package decides to update their stuff and adds a dependency to version 2.4.6.

Maven attempts to helpfully download the updated package behind your back. Then it refuses to build because of the version conflict.


Maven is flawed by design. The concept is that you always have compatible builds. In practice because it is pulling from public sources it establishes a bunch of requirements that are difficult if not impossible to keep correct, and then strictly enforces them by continuously breaking the build.

I think people install it because they don't want to do real work any more.

Do you know what's worse than configs? Working with other teams in your company, and trying to tell them why their high priority issues don't make sense.

One example:

Analytics: We need you to send us the total number of users who have successfully registered through the website.

Me: Get that from the DB. Applications don't keep track of those.

Project Manager: This is a high-priority issue, and is certainly a blocker (keyword for "I'll report this to the CEO if you are not doing what I say").

Me: It is not a blocker because it is only analytics, and does not prevent the application from functioning.

Analytics: But we need the total count.

Me: We don't keep track of the total users! You talk to the DBAs for that!

Project Manager: Could you come to our meeting tomorrow?

Horrible horrible horrible. People need to be educated about technology stacks before they are allowed to work in any tech industry.

Two hours. The printer on my wife's computer doesn't work. Windows can't find it. Never mind that the printer prints every single piece of network information, the printer must be just randomly generating fake network data. The print name? Fake. IP Address? Made up.

Edit:

3 hours later, I finally figured out the simple solution. Open the services, disable the print spooler, reboot, delete the printers, go to the C:\Windows\System32\spool\printers folder, delete everything in there, reboot, restart the print spool service, and reinstall the printer.

So simple even the most casual observer could do it.

Two hours. The printer on my wife's computer doesn't work. Windows can't find it. Never mind that the printer prints every single piece of network information, the printer must be just randomly generating fake network data. The print name? Fake. IP Address? Made up.

Edit:

3 hours later, I finally figured out the simple solution. Open the services, disable the print spooler, reboot, delete the printers, go to the C:\Windows\System32\spool\printers folder, delete everything in there, reboot, restart the print spool service, and reinstall the printer.

So simple even the most casual observer could do it.

Printers are the devil

Warning: If you're a Linux / Unix fan, skip this post !

Why the #### are Linux programmers "so out to lunch" ?!

Things that I run into all the ###ing time:

1: Creator abandons their program right after release, forcing their users to fix the bugs

2: No documentation

3: Documentation that is next to imposable to figure out

4: Incomplete / missing / inaccurate in program help menu

5: Misleading or missing comments in code

6: Programs and API that are not even close to the definition of intuitive

7: Changing entire file trees around during every minor version updates

8: Intentionally spaghetti codes everything ( ####ing hate this when debugging )
9: Has no clue what a program wizard is for

10: Has no clue what defaults are for

11: Program requires the support of several other third party API / libraries

12: Over use of Monty Python variables

Maven? Fucking nightmare! All the dependencies, and installs, and builds, and XML files, and setting the projects, and downloading, and... pisses me off. Specially since I can work out things in a much more simpler way by just linking "User Libraries" with Eclipse. Seriously.

Maven is explicitly designed to download fresh incompatibilities.

[...]

I think people install it because they don't want to do real work any more.

I once had a project. Then we decided they forced me to use maven and configuring the maven build became my project...

Doesn't python have pretty big issues with maintaining backwards compatibility with older code bases?

.

Yes

YES

F###ING YES

I may write a rant on Python now that you brought up one of my many "pet peeves" with that language -

Doesn't python have pretty big issues with maintaining backwards compatability with older code bases?

Python has no problem maintaining backwards compatibility with older code bases. It explicitly doesn't maintain backwards compatibility with older code bases, but that's a feature, not a bug.

How many of you are running a compiler that still conforms to the exact spec of ANSI C'89? And now, how many of you care that your compiler may/not conform to the exact spec of ANSI C'89?

Deprecation is a good thing™

Deprecation is a terrible thing. It forces me and everyone else to, for no actual benefit, fiddle with existing code that was long ago already tested by QA to actually do what it's supposed to. The only people who can live with (not benefit from, live with) deprecation are people who write throwaway stuff, or have toy programs a few 100 k lines in size.

Since this is a rant thread, I might as well rant a little. I'm going to rant about OpenGL. And about deprecation.

So, I recently thought I'd start making a game (nothing fancy, just a hobby project) and decided to see what happened in OpenGL since the last time I tried it (which may very well be 10 years ago).

So, I quickly find out that a lot of stuff has been deprecated, and the deprecation process seems to be ongoing. So much that it´s actually difficult to know whether what you're doing is deprecated or not.

I found out how to write shaders. A few days later I found out that shaders are supposed to be written in some other way now, because the "old way" is deprecated already. But I'm still not sure since which version the shader changes appeared, so I'm not exactly sure how things are done for my target version of OpenGL. I might be using a deprecated shader or shader features that haven't yet appeared in my target version. Who knows?

Trying to figure this out is really tedious.