That's just silly. I've worked with many math majors holding interesting non-teaching jobs.

in your pi hole? =P

what libraries are you talking about? the kernel has kept binary compatibility with all programs virtually since it's inception. X11, GTK and KDE programs all run with very high levels of binary compatibility. on the rare instances they are changes, (say gtk2 to gtk3) it's a clear cutover and all ditros ship with both so all programs keep running.

what i believe you're referring to are the *internal* kernel ABIs. yes, this is a PITA for people writing drivers for video cards. but come on: that's not what you (nor i, nor 99.44% of the people here) do. more than a decade i've programmed on linux (GUIs, server-side, you name it). it all runs in userspace and code i wrote (and compiled) a decade ago still runs just fine on a modern kernel.

btw, if anyone needs convincing, type xbill into your "ubuntu software center" search bar. THAT program i fricking old. runs like a champ tho!

ohhhh.... you know, good point. i bet those thousands of independent scientists worldwide who've been studying global warming for decades forgot all about deforestation as a possible cause. it's a good thing concerned citizens with awesome gut instincts like yourself are around to show them the way! :)

pffft. someone who was way to eager to give up his email address to some random web site in 1998. =P

well, i do remember gnome 1. it was no panacea.
more like "barely usable" and "ugly as sin".

i agree that they {unity/gnome3} uselessly through away years of good UI engineering work. and i understand the need to move to clutter. but moving to a new framework is tough enough - don't try to re-invent the whole desktop paradigm while you're at it.

but what do i know? i'm sure a 4-digiter will swoop in here and save us from our delusions. =P

it's because i do trust the free market i want (good / common-sense) regulation. good regulations makes markets more free, not less. this is why we regulate "not throwing a brick through your competitor's storefront".

likewise, how robust do you think the air-conditioning equipment market would be if you're electric company was free to cap your Carrier-brand AC compressor's electricity usage but leave cap-free their own home-brand compressor? (like how netflix usage is included in your data cap but at&t's u-verse movie streaming is cap-free...)

i don't think you know what "isn't much more than" means.
clue: it includes "a little more", as in "packt is a little more than a vanity press (but not much)".

=P

one of their recruiters approached me last year to write a book on numpy. which was curious to me since while i've used it (and posted some very minor public code using it), i'm not a contributor, nor involved in the community in any way.

some googling led to some fairly consistent stories:
very little editing work
very low sales (rep told me 1000 copies would be considered successful for a sequel)
don't expect more than your initial front (~$3500, which isn't even a front; they pay it out over the different chapters you submit)
if they can they get multiple authors writing in the same category at the same time (which means you're basically competing against your own publisher)

needless to say: didn't want to sign my name to anything like that...

hell yea!

but you can motivate a person who wants to create today and doesn't expect to be a corpse tomorrow.

here's a pointer: don't use javascript. =P

i don't know those specific tools, but it sounds like your solution to poor commenting is to write the same code twice in two different languages. =P

have you ever met a software engineering person who writes actual code? we had a whole software engineering phd program where i went to grad school and most of them couldn't open a socket when needed. (literally - we shared classes with them) nor have i met them on the job. (over a decade of full-time work at this point)

i personally believe there is no right way to write software, anymore than there is a right way to write a novel. you just have a lot of wrong ways to use as obstacle avoidance, and some "worked for me" suggestions that you have to evaluate for your current project.