Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Comment Re:How much do we care? (Score 1) 39

True, but to be fair, the scientists, engineers, and scholars are largely fleeing the country, the tech industry is in a massive slump (agriculture is the only sector growing jobs according to the last reliable official figures), and there's a political need to create the impression that the country isn't in a bad way.

Programming

Stack Overflow Went From 200,000 Monthly Questions To Nearly Zero (stackexchange.com) 92

Stack Overflow's monthly question volume has collapsed to about 300 -- levels not seen since the site launched in 2009, according to data from the Stack Overflow Data Explorer that tracks the platform's activity over its sixteen-year history.

Questions peaked around 2014 at roughly 200,000 per month, then began a gradual decline that accelerated dramatically after ChatGPT's November 2022 launch. By May 2025, monthly questions had fallen to early-2009 levels, and the latest data through early 2026 shows the collapse has only continued -- the line now sits near the bottom of the chart, barely registering.

The decline predates LLMs. Questions began dropping around 2014 when Stack Overflow improved moderator efficiency and closed questions more aggressively. In mid-2021, Prosus acquired Stack Overflow for $1.8 billion. The founders, Jeff Atwood and Joel Spolsky, exited before the terminal decline became apparent. ChatGPT accelerated what was already underway. The chatbot answers programming questions faster, draws on Stack Overflow's own corpus for training data, and doesn't close questions for being duplicates.

Comment Re:Space dust (Score 1) 39

I'm a native speaker of English. If you say something stopped, that sentence gives no information about how or why.

In English, you don't make huge complicated sentences such that the entire article with all its details is written in a single sentence that you can conveniently also use as the headline. The headline is not the article. "There is information in the article that isn't in the headline!" is not a valid criticism.

Comment Re:4 day work week, two month pto, ubi, blah blah (Score 1) 87

Automation didn't shorten the work week. Automation didn't shorten the work week.

Yes it did. It shortened the work week from six days to five, and shortened the work day to eight hours.

Hard to believe in these our enlightened times, but yes, in 1830, people used to work 69.1 hour work weeks.

Comment Re:Space dust (Score 1) 39

I would say that the fact that is stopped leaking is reasonable evidence that the fix worked.

The headline implies that it stopped itself.

The headline said stopped. If you are adding "by itself" to the headline, that is your addition, not what was written.

It was stopped, it didn't just stop miraculously without explanation.

The explanation is right there in the summary. And if you wanted more, you could even try reading the article, although that could be a bit too much to expect.

Comment Re:Why is their collection not digitized? (Score 3, Informative) 37

This is horrifying, terrifying, and sadly well-known even to those who superficially monitor such things.

Popular media: More than one US film/tv studio has "lost" or "suffered a mysterious fire" in un-digitised archives, destroying the lot, during battles to preserve. The BBC sued Bob Monkhhouse for preserving material it destroyed. In Britain, it has been no better. Fans of the British TV series "The Avengers" can only see old episodes because armies of previous fans descended on rubbish tips and, at great risk to themselves, collected as much film as possible.

General history: Places like the John Ryland's Library and the British Library have suffered with rescuing archives at risk of becoming submerged or destroyed by mould. The Archimedes Palimpsest was partially destroyed by one collector filling in the pictures with coloured pens and by another collector allowing the book to be severely damaged by mould.

The National Archives have mysteriously "lost" a great many files over the years and are only digitising those they've retained at an incredibly slow rate. I know because I've personally forked out several hundred to get just two scanned, all because politicians far prefer frippery to archiving. We've absolutely no idea how many of the manuscripts held in other archives are still in usable condition because nobody bothers to check.

It's not just limited to archives, of course. The US has, over the last couple of decades, demolished numerous buildings within the US that are over 300 years old because malls produce profit and ancient structures don't. (They also then complain they have no history...) The Space Shuttle is to be taken to Texas for a PR stunt, which will require it being dismantled and those things aren't designed for that. There is no guarantee any of it will survive the journey. All because PR matters and preservation does not. Other countries? The Louvre... well... probably best not to talk about that utter disgrace. In Egypt, 3000 year old gold artefacts are routinely melted down so the conservators can pocket some extra cash.

It's at times like this that Kenny Everett's general comes to mind.

Comment Re:Standby on Linux (Score 1) 59

ah, I will check out memory hole on some of my systems.

At least on 6.1 you have to be below 50% RAM usage too.

I found this in a RHEL doc that pointed to a kernel README that looked old af but said the same thing.

I have a few systems that run an app on solar during the day at 80% RAM and I had to stop the service before suspend to get it to work.

Yet it worked for a couple months in disk hibernate but then stopped and only memory sleep would work. On a Debian Bookworm stable kernel, so who the heck knows what broke (wasn't me!).

Battery usage overnight is different enough with many machines that I wish hibernate to disk worked reliably.

Anyway if I have 16GB RAM and a 36GB swap it seems bonkers to me that it is by design only working if less than 8GB of RAM is committed.

The subsystem is quite brittle and everybody seems to know.

Comment Blind Package Management (Score 1) 49

Most package management systems require us to figure out which card we have, figure out which package supports it, and install that.

Really we wanted "install the package that supports my card".

Apparently this current problem highlights this disconnect when a package no longer does what it used to but the package system blindly updates it anyway.

Being 2025, surely somebody in the past 30 years has floated a meta package management system to handle this mapping? Or an apt plugin? Anybody here know that history?

I mean, we even have nvidia-detect for their cards to do the actual probing work.

Granted arch is rolling and rolling gonna roll, but we can have software that makes this work correctly.

Comment Re:What could possibly go wrong? (Score 1) 271

Well, the obvious ones:

No built-in instruction-level or block-level parallelism
Array/vector operations are highly inefficient
Multiprocessing is pretty feeble
No CSP, you have to use OS primitives which are often unsafe
No formal contract system, best you can do is show statements don't do anything bad, you can't show functions do what you intend
Heavy software verification is difficult to impossible

Slashdot Top Deals

What the large print giveth, the small print taketh away.

Working...