00:00
00:00
MSGhero
Free time is nice time.

Nick @MSGhero

Age 30, Male

Somewhere in the North

Joined on 12/15/10

Level:
17
Exp Points:
2,848 / 3,210
Exp Rank:
19,885
Vote Power:
5.85 votes
Rank:
Police Sergeant
Global Rank:
6,517
Blams:
456
Saves:
937
B/P Bonus:
12%
Whistle:
Normal
Trophies:
6
Medals:
661
Supporter:
11y 5m
Gear:
3

Comments

Every time it looks like something's good enough, there's always that one thing that you end up finding that borks it either a little (if you're lucky) or entirely (if you're not), and is just nagging enough that you can't shove it under the rug and pretend it doesn't exist.

With regards to your previous post, it's frustrating to say the least when you have to face breaking changes in upstream. I haven't faced that issue directly, but I've had ones where a library that looked promising (albeit poorly documented) just turned out to have a ton of logic errors after all the finagling I had to do to fix the syntax errors, leaving me to find an alternative which meant my time before that was pretty much a total wash.

Offtopic, but if there's anything I hate about academia, it's that people end up having horrendous code and zero documentation at all to go with it. I totally understand the reasons why this happens but damn if it isn't frustrating as all hell. (Don't even get me started on Python 2 vs. 3, everything seems to be written haphazardly and in a throwaway manner - little to no attempts at futureproofing at all)

Yeah, I’m starting to find the more involved libs don’t work with the level of control I’m after.

Jamming in

@MSGhero or you find the library that meets everything you need, and it was last updated 5 years ago ^^;;

(although yes i do realize that old libraries aren't necessarily something to shy away from, but the number of actually stable/frozen libraries there are by individuals on github tends to be few and far between.)

I should revisit my older github repos and update them with the changes I've made since the last commit...