Live data from Hacker News

Python Is Eating the World

zdnet.com

361–370 of 993 posts

Re: Python Is Eating the World

#361
Interesting article, I would love to read one regarding Java and Kotlin, or if even someone here would share some knowledge with me, I would be grateful.

Is Java dying, what is its future? Where is Kotlin heading, currently it is the hottest language for Android development, can it also compete with Python in some branches?

Re: Python Is Eating the World

#362
post #110
post #69

Earlier quoted context omitted.

Gosh yes. These slow languages offload thinking to burning fossil fuels. INEFFICIENT.

Tell that to accounting that is paying for AWS instance usage. Facebook has an interesting talk about how much electricity 1% performance improvement saves.

> Tell that to accounting

Are you suggesting that accounting only cares about the AWS bill but not at all about the salary of developers?

Re: Python Is Eating the World

#363

Earlier quoted context omitted.

> I really enjoy working with python over any other language. I assume you mean, "over any other language I have tried" ? As someone with a mathematical background myself, I am always surprised at how many data scientists and quants are ignoring more mathematically principled languages like F#, OCaml and Haskell.

I dont know about F# and ocaml, but haskell's numerical libraries really pale compared to numpy.

It's language vs libraries. If you have a library that has a function

    get_the_shit_done_quick ()
than you don't care much about the language.

When you don't have such function, you need an expressive language to write it (and a bulk of python libs are not written in python, tho mostly for the performance reasons).

So it's all about finding a sweet spot between fancy libraries which do the shit for you, and fancy language, which let you to express things, absent in libraries.

This sweet spot differs from domain to domain, from user to user. Even in numerical stuff someone could have a requirement for a better language, although this domain is indeed to well defined to have enough fancy libraries.

Re: Python Is Eating the World

#364

Earlier quoted context omitted.

Thanks for posting. I've wondered if it's just me or does anyone else want to leave software engineering because of Python's dominance. There's no arguing against it either because as this thread shows, "I like it for my use case, look at these libraries that let you get X and Y done SOOOO easy, so it must be great for everything."

I've contemplated leaving SE behind because of JavaScript, not because of Python. Do you tolerate JS?

I hated Javascript back when all it had were callbacks, but once native promises stabilized, I loved the simplicity + ubiquity of the promise abstraction, and then later async/await. Now it's actually my favorite dynamically-typed language.

I've noticed a lot of Javascript hate also comes from people just disliking client development (which isn't easy on any platform).

Re: Python Is Eating the World

#365

Earlier quoted context omitted.

Stop using flake8. The original PEP 8 document doesn't even recommend 80 characters anymore. Pylint and mypy and black are way more useful.

Flake8 is customisable. I use it with 120 chr override. Maybe there are good alternatives but Flake8 starts from PEP8 until you tell it otherwise.

black -l 120

Re: Python Is Eating the World

#366

Earlier quoted context omitted.

That doesn’t even work in all situations. What if the system requires development packages? What if it’s a different OS or architecture? Packaging is a nightmare.

What if you are on Linux and your binary requires a slightly newer version of glibc for some reason etc. Static, portable binaries on Linux are hard.

That's why Docker is a good idea for packaging things up. You basically get exactly the combination of binaries, libraries, etc. you intend to run. Probably not a bad idea to use it for development as well. Or at least something like pyenv or whatever it is called these days.

Re: Python Is Eating the World

#367
post #294

Earlier quoted context omitted.

Over-sensitive individuals are hard to please and often unhappy. That's more of a personality flaw than a flaw with the current state of software engineering. If there's one thing wrong with our profession is a lack of ethics and accreditation - we're essentially letting random people build critical infrastructure and utilities. We don't have a tooling problem, in fact we have too many tools. I see so many people (es…

Is that supposed to help someone? I fail to see how telling someone "just ignore the stuff that irks you that you have to spend 40+ hours a week dealing with. You are overly sensitive and your concerns are irrelevant" helps anyone . Even if it was true, it was delivered in such a ham-fisted manner that I can't imagine anyone taking it to heart.

I sometimes have a tendency to focus only on the negative aspects of some things, while ignoring that all in all, those things are fine. I don't think I'm alone in that, certainly not in our line of work.

A call to "snap out of it" seems that it can help in such situations. Python is not a programming language that should make people burn out or angry. Very few languages should be capable of that, so I think this issue goes deeper than just flawed tools.

I find that the only way not to go nuts in this profession is to ignore most of it and most of it is really not relevant to building good software. There are just too many tools and always searching for the perfect tool is a recipe for being unhappy.

Re: Python Is Eating the World

#368
I have used all code from c+, java, php, javascript, ruby and more and found python is the easiest and simplest to use (you do not have to setup 5 classes to declare 1 variable) the only thing i hate about python is there is no built in parser to handle formatting.

Which is a simple but big design flaw for me.

Re: Python Is Eating the World

#369
post #356
post #294

Earlier quoted context omitted.

Over-sensitive individuals are hard to please and often unhappy. That's more of a personality flaw than a flaw with the current state of software engineering. If there's one thing wrong with our profession is a lack of ethics and accreditation - we're essentially letting random people build critical infrastructure and utilities. We don't have a tooling problem, in fact we have too many tools. I see so many people (es…

>If there's one thing wrong with our profession is a lack of ethics and accreditation - we're essentially letting random people build critical infrastructure and utilities. https://ncees.org/ncees-discontinuing-pe-software-engineerin... There was a license for a professional software engineer; they're discontinuing it, apparently due to lack of demand. If folks wanted to get a "software people taking the FE" study gr…

It's a vicious circle.

Our industry's working in a survival of the fittest mode, where fitness is almost exclusively measured through profit.

Re: Python Is Eating the World

#370

Earlier quoted context omitted.

Having such a basic part of a programming language be awful is inexcusable. It's not just that it takes a lot of time; even if it took no extra time, you're still wasting extra space on your computer, risking breakage on external updates, and compromising security because you can't even tell what code you're running.

"Inexcusable". You know this started in 1989 and its major competition was Perl and TCL, right? The same issues exist in C, C++, Java and nobody seems to be complaining about those at the same volume.

this issue outlined above doesn't exist in java, as long as you use maven.
Post reply on HN