News for hackers. Stuff that matters.
Re:Practical Go: Real-world advice for writing maintainable ... by ilovecaching on Thursday February 21, 2019 @08:47PM (#19222417)
So I don't know how to fly a commercial airliner, but I could probably figure my way around a small single prop airplane. That's basically the difference between Go and a language like Rust or C++ or any language that requires a lot of up front investment, but then let's you work at power level 9000.

So yeah, Go will get you there. It will take you a lot longer to get there when you aren't going 600MPH, and you can carry a lot less people, but at least you aren't driving a car like the people using Python. Sure it's probably not going to be as rigorously inspected as the Boeing borrow checker, but Go is at least getting an inspection, whereas your Python code is just going to break down on the side of the road when the problems surface itself because you didn't check the oil light.

To me, Go is a better Python. It's easier to learn, faster, more scalable, and safer, and just as easy and quick to write. It's just not a language for big projects.

Re:Practical Go: Real-world advice for writing maintainable ... by bschwindHN on Thursday February 21, 2019 @09:41PM (#19222672)
I'm sorry but most analogies for programming languages just don't make any sense. This is why no one takes software "engineers" seriously.

What the hell does "power level 9000" even mean for a programming language?

Big, successful projects have all been written in Go, Rust, C++, Python, and many more languages. The key is that they've been chosen in cases when it makes sense to choose them. And it has nothing to do with childish "Rust is fast jet. Python is slow car." analogies.

Re:Practical Go: Real-world advice for writing maintainable ... by wishinghand on Friday February 22, 2019 @02:45AM (#19223784)
> What the hell does "power level 9000" even mean for a programming language?

Power level 9000 is a reference to Dragon Ball Z. I haven't watched it but I gather it's up there on the power scale.

I think the analogy makes sense. Sometimes it is better to take a car than a Cessna or a jet, so it doesn't necessarily fail as you think it does.

Re:Practical Go: Real-world advice for writing maintainable ... by bschwindHN on Friday February 22, 2019 @03:48AM (#19223954)
The analogy might "make sense" but it's not useful. All it does is drive discussion towards arguments framed in the context of the analogy. Except we're not talking about public transportation! We're talking about programs! Points about "roads are everywhere" and "Are you driving across the Pacific?" are just snark.

As an example, let's take this quote:

> So yeah, Go will get you there. It will take you a lot longer to get there when you aren't going 600MPH, and you can carry a lot less people, but at least you aren't driving a car like the people using Python.

If Go was the name of a Cessna, C++ the name of a commercial airliner, and Python the name of a car, then that statement might make _some_ sense. But no, they're programming languages and you can't just throw this analogy out there and then try to have a serious discussion based on it.

Sometimes a Go program performs faster than a C++ or Rust program, and is written in less time. For certain domains, you might get something working (and performing faster) in less time in Python than writing it in Go. Python (and others) can call out to C libraries. Oh, I don't recall your car being able to summon a commercial airliner to pick it up in the middle of highway traffic. But that's how you'd have to explain FFI in this make-believe world of programming language cars.

Re:Practical Go: Real-world advice for writing maintainable ... by wishinghand on Wednesday February 27, 2019 @03:07AM (#19261740)
All metaphors and analogies break down. No need to get pedantic about it.
Re:Practical Go: Real-world advice for writing maintainable ... by ybrs on Thursday February 21, 2019 @08:59PM (#19222468)
i'm riding that car for nearly a decade and never needed to pull to side. you can't ride a plane without airports, but you can travel to everywhere with a car - because roads are everywhere.
Re:Practical Go: Real-world advice for writing maintainable ... by ryl00 on Thursday February 21, 2019 @09:36PM (#19222649)
Driving across the Pacific anytime soon? :)
Re:Practical Go: Real-world advice for writing maintainable ... by platz on Thursday February 21, 2019 @08:58PM (#19222464)
But Go will never be a data science language like python, because Go is too limited to express that domain.

Python may leave you in the lurch when it comes to maintainability, but for some domains python is infinitely better than Go.

Re:Practical Go: Real-world advice for writing maintainable ... by fastbmk on Friday February 22, 2019 @06:40AM (#19224548)
Go fanboys won't get it. They are too busy proving their language doesn't need Generics.
Re:Practical Go: Real-world advice for writing maintainable ... by chewxy on Saturday February 23, 2019 @12:08AM (#19231770)
Hmm. Weird. Almost my entire data science pipeline is in Go.
Re:Practical Go: Real-world advice for writing maintainable ... by platz on Saturday February 23, 2019 @12:16AM (#19231802)
Data engineering is not data science
Re:Practical Go: Real-world advice for writing maintainable ... by ilovecaching on Friday February 22, 2019 @10:14AM (#19225979)
I agree with you, but data science is a separate field, so I don't normally factor it into my discussions of tools for software engineering.
Re:Practical Go: Real-world advice for writing maintainable ... by platz on Friday February 22, 2019 @10:22AM (#19226055)
tell that to the NumPy folks!
Re:Practical Go: Real-world advice for writing maintainable ... by mirceal on Thursday February 21, 2019 @09:59PM (#19222750)
if you want to fly anything other than a small plain you’re doing it wrong. think about it! we could get a new pilot and have them fly this in no time. it’s simple and can do this 2 tricks really well. everything is fluff and not for professional pilots. and google flies a couple of them so how could it be wrong?
Re:Practical Go: Real-world advice for writing maintainable ... by fastbmk on Friday February 22, 2019 @06:36AM (#19224537)
No wonder most Go developers come from Python, not C++. Go is a faster Python with concurrency. Go is not suitable for serious projects, but is ok for mediocre devops stuff.