Whitespace.
Oook.
Quad.
But seriously, have you got an end result in mind? Learning Java will get you an easily portable (and web-based) audience for such works as you eventually release. C++ is probably where you want to head off to if you want to make fully compiled executables (not as automatically portable, but you should be able to make them 'port'able, and recompile them for different platforms) that can be fast and much more powerful, but I'd probably suggest starting with C[1] to get the basic non-OO principles off pat.
Python promises to have an approach that's... if not
best of both worlds, certainly without some of their obvious failings. Not sure how commercial it is, compared to the other two (not seen many "Python Developer required, for immediate start" adverts, as opposed to equivalents for the other two), but you'd be in good company. I've got a Python book at home that I'm
about to start reading, properly, whose first section's few introductory quotes basically equate to explaining the difficulties with the C-family/Java family, and then round it off with a Monty Python quote. You have to be there, but the first few paragraphs proper suggest in the (obviously biased opinion of the author) that Python is the way to go. I've yet to establish that for myself. I find Python easy to read, but I've done precious little of my own writing in it, yet.
I have a soft-spot for Perl, especially for my near-eternal prototyping prior to going into whichever one of the other languages I can work in, I but I don't think it's going to be much use for you. But it
is good for working ideas out, if you don't mind then realising that the final target language is more strictly typed, or some other botheration, and you need to implement a lot
more work to get a given simple Perl sub or block working in this other dialect.
I can also offer advice on COBOL, Forth, LISP, Pascal/Delphi, various BASIC subsets, etc, etc, and that general advice would be that they either don't do the kinds of things that you want them to do or the way of getting them to do them is not worth the bother or just plain not in the modern paradigm, even the likes of the BASICs that are specifically games-orientated. Still, they're each fun, in their own ways.
Not that you'll be getting anywhere near it, and it's of a similar irrelevancy level to COBOL, but avoid Ada like the plague! Most horrible language that I've ever used. And I'm including COBOL and some of my own intentionally awkward/obtuse esolang implementations in that comparison...
[1] Albeit that you might be having to learn Object Orientated approaches after you've already gor a function-orientated mindset, but hopefully you'll still be malleable, in that regard. There are intermediary Object-C dialects, but I rather jumped straight from K&R to ++. And as yet have yet to be convinced to try C#.