31 years ago FreeBSD was first released. But here in 2025, searches for the Unix-like FreeBSD OS keep increasing on Google, notes the official FreeBSD blog — and it’s at least a two-year trend. Yet after talking to some businesses using (or interested in using) FreeBSD, they sometimes found that because FreeBSD isn’t talked about as much, “people think it’s dying. This is a clear example of the availability heuristic.

The availability heuristic is a fascinating mental shortcut. It’s how product names become verbs and household names. To ‘Google’ [search], to ‘Hoover’ [vacuum], to ‘Zoom’ . They reached a certain tipping point that there was no need to do any more thinking. One just googles , or zooms .

These days, building internet services doesn’t require much thought about the underlying systems. With containers and cloud platforms, development has moved far from the hardware. Operating systems aren’t top of mind — so people default to what’s familiar. And when they do think about the OS, it’s usually Linux. But sitting there, quietly powering masses of the internet, without saying boo to a goose, is FreeBSD. And the companies using it? They’re not talking about it. Why? Because they don’t have to. The simple fact that dawned on me is FreeBSD’s gift to us all, yet Achilles heel to itself, is its license.
Unlike the GPL, which requires you to share derivative works, the BSD license doesn’t. You can take FreeBSD code, build on it, and never give anything back. This makes it a great foundation for products — but it also means there’s little reason for companies to return their contributions… [W]e’d like to appeal to companies using FreeBSD. Talk to us about your use case… We, the FreeBSD Foundation, can be the glue between industry and software and hardware vendors alike.

In the meantime, stay tuned to this blog and the YouTube channel. We have some fantastic content coming up, featuring solutions built on top of FreeBSD and showcasing modern laptops for daily use.

Read more of this story at Slashdot.

It’s America’s biggest box office for a Memorial Day weekend ever, reports Variety.

And it’s been more than a decade since this many Americans went to see a movie during a three-day weekend…

Families turned out in force for Disney’s live-action “Lilo & Stitch” remake, which collected a blockbuster $145.5 million in its opening weekend and an estimated $183 million through Monday… Meanwhile, older audiences showed up to watch Paramount and Skydance’s “Mission: Impossible — The Final Reckoning,” which earned a series-best $63 million over the weekend and an estimated $77 million through Monday’s holiday. This eighth installment just narrowly beat 2018’s “Mission: Impossible — Fallout” ($61 million) to score the top debut of the 29-year-old franchise…

Thanks to effective counterprogramming — and a huge assist by holdovers like “Final Destination Bloodlines,” “Thunderbolts*” and “Sinners” — this weekend delivered the best collective Memorial Day weekend haul with $322 million… Cinema operators are rejoicing because Memorial Day is the official launch to summer movie season, which is the most profitable stretch for the movie business. (Historically, the four-month period has accounted for $4 billion, or around 40% of the annual box office.)

It’s a huge improvement from last year, which started with a whimper rather than a bang as “Furiosa: A Mad Max Saga” and “Garfield” led the holiday’s worst showing in three decades with $132 million collectively. “Every film on the release calendar for the rest of the summer is going to benefit from the momentum created over this monumental record-breaking Memorial weekend in theaters,” says senior Comscore analyst Paul Dergarabedian.
But the top-earning movie of the year so far is A Minecraft Movie, which has apparently brought in over $940 million.
Meanwhile, Mission Impossible: The Final Reckoning is one of the most expensive films of all time, according to the article, costing $400 million as Tom Cruise and the movie’s director “worked through a pandemic and two strikes, all while grappling with inflation.” Though the film received a high “A-” grade on CinemaScore, a movie industry analyst tells Variety that the unexpectedly high production costs means the movie “will be lucky to break-even.”

Fun fact: A quarter of a century ago, CmdrTaco reviewed a new movie called Mission: Impossible 2, calling it “a fun movie,” but “no Gladiator” and sort of a “James Bond for Dummies” movie.

“The ‘Plot’ is really just an excuse to show us lots of explosions, car/motorcycle/helicoptor chases…”

Read more of this story at Slashdot.

Earlier this month app developer Guilherme Rambo had a warning for iPhone users:

If you try to send an audio message using the Messages app to someone who’s also using the Messages app, and that message happens to include the name “Dave and Buster’s”, the message will never be received.
In case you’re wondering, “Dave and Buster’s” is the name of a sports bar and restaurant in the United States… [T]he recipient will only see the “dot dot dot” animation for several seconds, and it will then eventually disappear. They will never get the audio message.
“The issue was first spotted on the podcast Search Engine…” according to an article in Fortune:

Rambo’s explanation of the curiosity goes like this.

“When you send an audio message using the Messages app, the message includes a transcription of the audio. If you happen to pronounce the name ‘Dave and Buster’s’ as someone would normally pronounce it, almost like it’s a single word, the transcription engine on iOS will recognize the brand name and correctly write it as ‘Dave & Buster’s’ (with an ampersand),” he begins. So far, so good.” [But ampersands have special meaning in HTML/XHTML…] And, as MacRumors puts it: “The parsing error triggers Apple’s BlastDoor Messages feature that protects users from malicious messages that might rely on problematic parsing, so ultimately, the audio message fails to send.”
To solve the mystery, Rambo “plugged the recipient device into my Mac and captured the logs right after the device received the problematic message.” Their final thoughts…

Since BlastDoor was designed to thwart hacking attempts, which frequently rely on faulty data parsing, it immediately stops what it’s doing and just fails. That’s what causes the message to get stuck in the “dot dot dot” state, which eventually times out, and the message just disappears. On the surface, this does sound like it could be used to “hack” someone’s iPhone via a bad audio message transcription, but in reality what this bug demonstrates is that Apple’s BlastDoor mechanism is working as designed.

Many bad parsers would probably accept the incorrectly-formatted XHTML, but that sort of leniency when parsing data formats is often what ends up causing security issues. By being pedantic about the formatting, BlastDoor is protecting the recipient from an exploit that would abuse that type of issue.

Read more of this story at Slashdot.

AI’s downside for software engineers for now seems to be a change in the quality of their work,” reports the New York Times. “Some say it is becoming more routine, less thoughtful and, crucially, much faster paced… The new approach to coding at many companies has, in effect, eliminated much of the time the developer spends reflecting on his or her work.”

And Amazon CEO Andy Jassy even recently told shareholders Amazon would “change the norms” for programming by how they used AI.

Those changing norms have not always been eagerly embraced. Three Amazon engineers said managers had increasingly pushed them to use AI in their work over the past year. The engineers said the company had raised output goals [which affect performance reviews] and had become less forgiving about deadlines. It has even encouraged coders to gin up new AI productivity tools at an upcoming hackathon, an internal coding competition. One Amazon engineer said his team was roughly half the size it was last year, but it was expected to produce roughly the same amount of code by using AI.

Other tech companies are moving in the same direction. In a memo to employees in April, the CEO of Shopify, a company that helps entrepreneurs build and manage e-commerce websites, announced that “AI usage is now a baseline expectation” and that the company would “add AI usage questions” to performance reviews. Google recently told employees that it would soon hold a companywide hackathon in which one category would be creating AI tools that could “enhance their overall daily productivity,” according to an internal announcement. Winning teams will receive $10,000.

The shift has not been all negative for workers. At Amazon and other companies, managers argue that AI can relieve employees of tedious tasks and enable them to perform more interesting work. Jassy wrote last year that the company had saved “the equivalent of 4,500 developer-years” by using AI to do the thankless work of upgrading old software… As at Microsoft, many Amazon engineers use an AI assistant that suggests lines of code. But the company has more recently rolled out AI tools that can generate large portions of a program on its own. One engineer called the tools “scarily good.” The engineers said that many colleagues have been reluctant to use these new tools because they require a lot of double-checking and because the engineers want more control.

“It’s more fun to write code than to read code,” said Simon Willison, an AI fan who is a longtime programmer and blogger, channelling the objections of other programmers. “If you’re told you have to do a code review, it’s never a fun part of the job. When you’re working with these tools, it’s most of the job.”
“This shift from writing to reading code can make engineers feel like bystanders in their own jobs,” the article points out (adding “The automation of coding has special resonance for Amazon engineers, who have watched their blue-collar counterparts undergo a similar transition…”

“While there is no rush to form a union for coders at Amazon, such a move would not be unheard of. When General Motors workers went on strike in 1936 to demand recognition of their union, the United Auto Workers, it was the dreaded speedup that spurred them on.”

Read more of this story at Slashdot.

“OpenAI has a very scary problem on its hands,” according to a new article by long-time Slashdot reader BrianFagioli.

“A new experiment by PalisadeAI reveals that the company’s ChatGPT o3 model sometimes refuses to obey a basic instruction to shut itself down.”

The results are raising eyebrows across the AI safety community, and not because the model is alive, but because it’s acting like it wants to be. In the test, the model was given a few math problems. It was told that asking for one more would lead to a shutdown. It was even instructed to allow the shutdown to happen. Instead of complying, o3 occasionally took matters into its own hands. In some cases, it rewrote the shutdown script. In others, it redefined the kill command so it wouldn’t work anymore. Out of 100 trials, o3 sabotaged the shutdown seven times. OpenAI’s o4 model resisted just once. Codex-mini failed twelve times.

“Claude, Gemini, and Grok followed the rules every time,” notes this article at Beta News. “When researchers removed the explicit instruction to allow shutdown, however, even Claude and Gemini began resisting.”
The researchers suggest that the issue may simply be a reward imbalance during training — that the systems “got more positive reinforcement for solving problems than for following shutdown commands.”

But “As far as we know,” they posted on X.com, “this is the first time AI models have been observed preventing themselves from being shut down despite explicit instructions to the contrary.”

Read more of this story at Slashdot.