Hacker Newsnew | past | comments | ask | show | jobs | submit | QuantumNoodle's commentslogin

Valid points, with which I agree and share the concern. I can't compete with colleagues, whom do things fast, if I want to learn. On the other hand, I no longer have to toil to work through things that I never truly learned, like tasks that require to be done a few times a year. Mastery is never acievable bc I forget, side quests become much less derailing. However, I am deprived of going through the motions and researching.

What's the realistic outcome here? The gov cannot label them as a supply-chain risk but still free to cancel contracts with Anthropic? Or do gov agencies has autonomy to use whoever they want?

The government is free to cancel its own contracts. The judge is saying that the government cannot prohibit other entities (like private contractors) from doing business with Anthropic.

Internally, we've created such good debugging tools that can aggregate a lot from a lot of sources. We've yet to address the quality of vibecoded critical applications so they aren't merged, but one off tools for incall,alert debugging and internal workflows has skyrocketed.

Either the number of big airline incidents around the world grew in the last 24 months or reporting on it became more popular. I wonder how much people get hurt relative to number that fly now.

“around the world” citation needed

It looks like jet safety got better just about everywhere except the US, and 2025 was a bad year for turboprops:

https://www.iata.org/en/pressroom/2026-releases/2026-03-09-0...

On average, it was slightly worse globally, especially if you count fatalities (which were much worse).


Excellent source! Thank you.

Looks like more flights in 2025 than previous years and less accidents. 2025 does have more fatalities, which are more memorable than emergency landings where everything was alright. So that is likely what skewed my view.


This is purely anecdotal. Some search queries about incidents I remember

- Jan 2025 mid air collision with helicopter near Reagan National, Washington, D.C.

- April 2025 China Eastern Airlines Flight runway overrun at Chongqing Jiangbei

- June 2025 Air India crashed after departure from Ahmedabad

- August 2025 incident at London Stansted where a DHL A330 landed long and struck the runway end

- September 2025 Tokyo Haneda: Inflight engine fire

There was one where the plane ended up on side or back. But I don't remember enough details to find the event


I'm just lurking in the comments with popcorn, but if what you said is true and the maintainers of X decided it was a lost cause and unfixable, well that is the most informed opinion of them all. Nobody knows better then the maintainers. Sure, the replacement might have feature gaps initially but that is a transient issue.

> Sure, the replacement might have feature gaps initially but that is a transient issue.

It has been 17 years.


X11 was started in 1984 in MIT. That means, when Wayland was first conceived in 2008, there had been 24 years of X development.

I guess Kristian grossly underestimated the effort required to write a full features Display manager.

FWIW, innmy career the times I've had to perform very impactful changes in software, I always start from the current codebase and remove/simplify stuff.

As an example, once I was in a company that had built a huge Ruby monolith which was not scaling at all. It had APIs for everything, including "high frequency trading" in the same codebase server, under a METAL aws instance (that's how they scaled).

What we did initially was simply copy the repo N times (sign up, compliance, risk, trading, etc), spin up an copies of the same server and use a balancer to route APIs to the different boxes.

Then we started removing unused stuff from each of the repository to specialize them. Fiinally we simplified complexity on each separate codebase.

I would have approached X11 codebase similarly.


I studied signal processing in university and my career evolved to not use what I studied. Decades ago, giving an algorithm a sound file and isolating tracks was difficult.

How does your implementation accomplish this? Were you involved or did you use something off the shelf?

Edit: ah, using neural nets, demucs. I wonder if there is pure math approach that can compete?


Input: poop

Output: Optimizing internal output to drive personal growth and streamline biological efficiency. #WellnessJourney #Efficiency #BioHacking


Still no idea how a polymarket is legal with all the insider trading opportunities.


Insider trading is not about fairness, it's about theft. If you insider trade on the stock market then, in a crude simplification, you steal profits from the company you have a fiduciary duty to, or some extension of that. It has nothing to do with a level playing ground, every trading company out there is trying to find information others can't and then trade on it.


What? How do you figure that? If I happen to know that my company is about to report very bad quarterly numbers, so I sell all my stock, then it tanks, I’ve just screwed whoever bought the stock, that in the most cases, will be some random people. The company does not benefit or hurt from stock prices unless they are buying back or issuing more stock.


Because that's what the law says? And the company most definitely does benefit and hurt from a fluctuating stock price, it's one of the key drivers behind financing conditions. What you describe is a simpleton view of the financial market.


That’s how the criminal penalties are framed.


I ran a TrueNAS server that was based on BSD, loved jails. Then TrueNAS started using debian so more application can run on it. Selfishly I like getting more utility from my server so this was a welcomed change. What industry is BSD used in now a days?


firewalls are a common example (many Linux houses have a BSD-based firewall at the edge) but any "single application" setup may run on BSD - Netflix, for example.


The output the agent creates falls into one of these categories:

1. Correct, maintainable changes 2. Correct, not maintable changes 3. Correct diff, maintains expected system interaction 4. Correct diff, breaks system interaction.

In no way are they consistent or deterministic but _always_ convincing they are correct.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: