News for hackers. Stuff that matters.
Re:It's time to let go, Apache Software Foundation by zoogeny on Monday September 25, 2023 @12:28PM (#37646491)
There is a quote: "When you stop growing you start dying" (William S. Burroughs). I am not sure I believe that the kind of governance that Apache is providing is helping to grow the projects under its supervision.

Your comparison to Terraform is also interesting. Apache Kafka, for example, has been absorbed by Amazon (MSK). Apache Spark is Amazon EMR. Just looking through Amazon's paid service offering I find several Apache projects rebranded and for sale. A cynical take could be that Apache is an org that helps companies like Amazon profit off of the work of open source developers.

Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @12:38PM (#37646649)
But with software, sometimes there comes a time when it really should stop growing. When any further "enhancements" make the software worse.

It's something I've seen countless times in my life. A piece of software achieves something pretty close to perfection for its task, but the self-imposed "need" to continue development on it ruins it.

Re:It's time to let go, Apache Software Foundation by rzzzt on Monday September 25, 2023 @01:05PM (#37647147)
Does it read mail and/or contain a subset of Common Lisp?
Re:It's time to let go, Apache Software Foundation by worthless-trash on Tuesday September 26, 2023 @12:26AM (#37654356)
All software will eventually grow to send email. And lets be honest, if its not written in lisp, are you really trying ?
Re:It's time to let go, Apache Software Foundation by systems_glitch on Monday September 25, 2023 @01:12PM (#37647271)
Absolutely. Some things go into bugfix-only mode because their code has reached perfection for the 99% use case.
Re:It's time to let go, Apache Software Foundation by broeng on Monday September 25, 2023 @02:01PM (#37648011)
And then we fear it's a dead project, and move on in search for something else with active contributors.
Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @02:03PM (#37648034)
Certainly not everyone. Personally, I pay little attention to that sort of thing at all. I don't care if it's a "dead" project or not -- as long as the software is meeting my needs, that's the only thing that matters. If/when it stops doing that, then I'll look for alternatives.
Re:It's time to let go, Apache Software Foundation by systems_glitch on Tuesday September 26, 2023 @01:34PM (#37662854)
Same here. I run Slackware on all of my engineering and development workstations. It does what I want, nothing gets hosed when running updates, and I don't feel like my main job is sysadmin.

But I keep getting told I need a "Slackware intervention" :P

Re:It's time to let go, Apache Software Foundation by AlbertCory on Monday September 25, 2023 @02:37PM (#37648538)
Hot take: Python 3.

Totally unnecessary.

Re:It's time to let go, Apache Software Foundation by Master_Odin on Monday September 25, 2023 @03:32PM (#37649321)
The move to python 3 helped shake loose a number of text processing bugs with library I work on, that was never caught in python 2 with its loose goosy text type handling.
Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @04:38PM (#37650297)
But as an end user, it's made using applications based on (or even tangentially using, as I learned first-hand a couple of months ago) Python highly problematic due to extreme version incompatibility.

I now try my best to avoid anything that involves Python.

Re:It's time to let go, Apache Software Foundation by janoc on Monday September 25, 2023 @05:19PM (#37650806)
Sorry but that's nonsense. Python 3 has been released in 2008 - 15 years ago. And the last Python 2 version has been EOLed 1.1.2020, three years ago, after a decade of deprecation!

With your argument about compatibility no programming language would ever be able to evolve or deprecate/remove some features. Look at how many things changed e.g. between recent C++, Rust or C# major releases. Python had only one major revision in 15 years in comparison!

If you are using software that still requires Python 2 that's very much a problem of that application and not Python. Complain to the vendor responsible, not about Python. They had ample time to update their code.

End users had no business touching Python 2 for at least a decade now. And upward compatibility between the point releases of Python is (and has been) generally pretty good.

Re:It's time to let go, Apache Software Foundation by AlbertCory on Monday September 25, 2023 @05:46PM (#37651154)
all arguably true, but it has no bearing on whether 3 was necessary in the first place.

> With your argument about compatibility no programming language would ever be able to evolve

"evolve" and "change" are not ends in themselves. If it was usable as it was, then there was no need to evolve or change in an incompatible way.

15 years ago: also irrelevant. World War One was unnecessary, and that was 109 years ago. Whatever issues existed are sorted out by now, but that doesn't mean it had to happen.

Re:It's time to let go, Apache Software Foundation by janoc on Monday September 25, 2023 @06:02PM (#37651340)
There have been some very good reasons why Python 3 made those changes.

That you find them unnecessary because the original code was "usable as is" for you is irrelevant.

The reasons why these changes have been done (for a developer they have been fairly minor) has been hashed and rehashed for the past 15 years, Guido van Rossum wrote on it extensively too.

Most has been performance-related (Python 3 is significantly faster than 2) and probably the biggest user-visible change is the clean up of string handling with everything being Unicode now.

Frankly, anyone complaining about this stuff today is just beating the old dead horse for the sake of having something to complain about. The same like some people constantly bringing up the Linux systemd discussions after more than a decade, even though they are completely irrelevant today.

Re:It's time to let go, Apache Software Foundation by AlbertCory on Monday September 25, 2023 @08:19PM (#37652635)
the age of an unnecessary change is irrelevant. Here's your sequence:

1. It's not true

2. It's true, but it's not important

3. It's true, and it's important, but we're tired of talking about it.

Re:It's time to let go, Apache Software Foundation by JohnFen on Monday September 25, 2023 @05:49PM (#37651195)
> Sorry but that's nonsense.

I'm not lying. This problem cost me a full weekend earlier this year. I may have misremembered the exact version numbers, though. Perhaps it wasn't between 2 and 3. Is there a Python 4?

The problem is that you can't have one Python interpreter that covers all versions of Python, and Python is very unforgiving about using the wrong interpreter version.

In any case, it was a serious problem that cost me a lot of time and really soured me on Python as an end user. I've not encountered a similar issue with any other language before, so this appears to be uniquely a Python thing.

But I don't know. I'm happy enough to just avoid Python-based anything whenever possible now.

Re:It's time to let go, Apache Software Foundation by janoc on Monday September 25, 2023 @06:11PM (#37651421)
There is no Python 4 - and may not ever be.

If you have downloaded Python 2, you must have done it intentionally, it isn't even available from the Python.org website download anymore - and had not been for a long time.

>The problem is that you can't have one Python interpreter that covers all versions of Python, and Python is very unforgiving about using the wrong interpreter version.

Because it doesn't make sense. The language evolves. Nobody is going to stop working on it only because it could break some old code somewhere. The changes from 2 to 3 happened *15 years ago*.

There is no reason to try to compile/run old Python 2 code today - and if you still do need it for some reason, then you need to download the Python 2 version (which are still available, if you need them but one has to look for them). But then you better know what you are doing.

If some old code requires Python 2, any somewhat experienced Python developer will spot that right away (e.g. the use of print statement in Python 2 vs. print() function in Python 3 is a dead giveaway).

>In any case, it was a serious problem that cost me a lot of time and really soured me on Python as an end user. I've not encountered a similar issue with any other language before, so this appears to be uniquely a Python thing.

I don't doubt it has costed you a lot of time but this was a problem entirely of your own doing by not doing your homework.

You would have exactly the same problems if you tried to compile old K&R C code or C++ code from 20 years ago using modern compilers. Or tried to feed modern C# code to a compiler from 10 years ago. Or, God forbid, tried to run some modern Javascript code using old browser - or that old HTML with Flash and what not in a modern browser ...

Python is actually much more lenient in this regard because a major language change has happened only once, 15 years ago, with Python 2 being deprecated for well over a decade. The point releases are all upward compatible with no issues.

Re:It's time to let go, Apache Software Foundation by jen20 on Monday September 25, 2023 @10:13PM (#37653468)
I’m with you on Python 2 to 3 being a fine idea and an improvement but…

> You would have exactly the same problems if you tried to compile old K&R C code or C++ code from 20 years ago using modern compilers. Or tried to feed modern C# code to a compiler from 10 years ago.

If you feed 10 year old C# to a modern compiler it will compile it fine. I’d imagine most C and C++ of even 20-year vintage will still compile. The issue is of forward compatibility, not backwards.

Re:It's time to let go, Apache Software Foundation by pjmlp on Tuesday September 26, 2023 @05:13AM (#37656514)
No it won't, as it might be using the breaking for change introduced in C# 5, or .NET Framework features not made available on .NET Core.

Likewise C and C++ have had enough breaking changes since 2010.

Re:It's time to let go, Apache Software Foundation by neonsunset on Tuesday September 26, 2023 @09:43AM (#37659200)
It depends. Some projects can be retargeted to netstandard2.0/net6(8).0 without any changes at all, some require minor update of dependencies and some other - do face breaking changes in library code because APIs did get deprecated.

With that said, neither IL nor C# itself had any changes breaking forward compatibility (aside from a very early change to foreach recently discussed here).

Re:It's time to let go, Apache Software Foundation by pjmlp on Tuesday September 26, 2023 @11:13AM (#37660559)
C# isn't used in isolation without standard library.

Also, "it depends" isn't the same as "If you feed 10 year old C# to a modern compiler it will compile it fine."

Re:It's time to let go, Apache Software Foundation by augustk on Monday September 25, 2023 @12:59PM (#37647033)
Why do you think software needs to grow?
Re:It's time to let go, Apache Software Foundation by kuchenbecker on Monday September 25, 2023 @01:12PM (#37647274)
It needs at least a stable set of users, but maintaining a set of users is essentially managing the set of people onboarding and the set of people migrating off.

If you're shrinking then a competitor is providing better options, or your problem space has shifted.

Re:It's time to let go, Apache Software Foundation by dale_glass on Monday September 25, 2023 @06:15PM (#37651458)
Software as big as Open Office may not need to technically grow, but still needs a lot of work to stay current.

Various dependencies, like XML parsers, JPEG decoders, HTTP libraries, etc, change over time, drop deprecated APIs and need the main application to adapt. It'll also bump into the tech changing around it -- UTF8, year 2038, 64 bit CPUs, etc.

For a project this size it takes work just to stand still and keep it comfortably buildable on a modern Linux distro.

Re:It's time to let go, Apache Software Foundation by znpy on Monday September 25, 2023 @01:31PM (#37647561)
> "When you stop growing you start dying"

death is part of life though, and the only thing that grows without and end is cancer (quite literally).

I don't see why project can't just be considered "done": yeah you update dependencies and make it work with new/current formats, but essentially it's done. The use case is now clearly defined, implemented and tested.

Re:It's time to let go, Apache Software Foundation by rbowen on Monday September 25, 2023 @01:40PM (#37647699)
I'm fascinated at your characterization of both Kafka and Spark as being absorbed by Amazon.

AWS offers hosted versions of each. They are not, as you say "rebranded and for sale", but rather are hosted services, running whatever upstream releases.

But to say that the project as been absorbed by AWS (in either case) is simply false. Spark is developed by a community of numerous companies, of which Databricks is usually most prominent. Kafka is likewise a community of several organizations, of which Confluent tends to be the most influential.

Yes, Apache is (and always has been) business-friendly. The license enables companies to profit on those projects. But, for the most part, companies that benefit from those project also contribute back to them, as a way to ensure sustainability. That's how it is supposed to work.

Re:It's time to let go, Apache Software Foundation by toast0 on Monday September 25, 2023 @01:46PM (#37647788)
> A cynical take could be that Apache is an org that helps companies like Amazon profit off of the work of open source developers.

Apache httpd certainly helped tons of companies profit, so helping companies profit doesn't seem off-brand.