News for hackers. Stuff that matters.
Re:Selecting All Columns Except One in PostgreSQL by slap_shot on Saturday May 19, 2018 @12:24PM (#17108522)
Except that's not how real software is built. Real software has to add new features to remain competitive. Just look at a few of the features for Postgres 9.4 to 10:

JSONB data type, ALTER SYSTEM statement for changing config values, ability to refresh materialized views without blocking reads, dynamic registration/start/stop of background worker processes, Logical Decoding API, GiN index improvements, Linux huge page support, database cache reloading via pg_prewarm UPSERT, row level security, TABLESAMPLE, CUBE/ROLLUP, GROUPING SETS, and new BRIN index[113] Parallel query support, PostgreSQL foreign data wrapper (FDW) improvements with sort/join pushdown, multiple synchronous standbys, faster vacuuming of large table Logical replication, declarative table partitioning, improved query parallelism

We'd all love for software to be bug-free and stable, but features have to be added.

Re:Selecting All Columns Except One in PostgreSQL by city41 on Saturday May 19, 2018 @01:06PM (#17108705)
For sure, that is the reality we live in. Doesn’t mean it’s a good thing though. There’s even been some push back to this trend, such as Apple reconsidering how they do release cycles due to iOS becoming so buggy.

It also depends on what kind of software we are talking about. A trendy mobile app is very different from a critical database.

I personally prefer software that’s more conservative in its approach to new features. It’s becoming harder to find software that has this philosophy but not yet impossible.

Re:Selecting All Columns Except One in PostgreSQL by RussianCow on Saturday May 19, 2018 @01:03PM (#17108685)
Nobody is arguing that products shouldn't have features. But there is a real cost to each feature that you add, and so you have to weigh the tradeoffs before blindly building everything anyone asks for. Selecting all columns but one seems like it would bring much less value than JSONB.
Re:Selecting All Columns Except One in PostgreSQL by slap_shot on Saturday May 19, 2018 @02:15PM (#17109015)
The parent comment said he preferred software with less features, and favored bug fixing and stability over feature X. Feature X could be swapped with any request in Postgres's backlog.

I agree with you: all features have to have a cost and value. The market decides what features are valuable, and they get built and supported. SELECT EXCEPT is not one that the market values yet. And that's fine.

Re:Selecting All Columns Except One in PostgreSQL by mmt on Saturday May 19, 2018 @10:19PM (#17110817)
> The market decides what features are valuable, and they get built and supported.

I'm curious as to what you envision as "the market" in the context of free software, or Postgres in particular, since I don't expect it's the cliche of people literally deciding which product to pay for among competing ones.

A couple possibilities came to mind, but, having no intimate familiarity with any major project like this, I didn't want to parade mere assumptions as multiple choice.