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

This isn't really porn adopting ChatGPT, it's OpenAI allowing porn. There was nothing stopping Pornhub from releasing their own LLM. If porn became a feature gated behind YouTube Premium I would probably say "wow they really need customers huh".

> There was nothing stopping Pornhub from releasing their own LLM

There's probably a lot stopping them considering there's about 3 companies making models that aren't shit.


I mean, there's very specific reasons either color gets support from their voters. I wouldn't say all of those reasons warrant the same amount of fervor, passion, and loyalty that they do. But "blind support" is a bit reductive when for some people it literally means their rights being stripped away.

What appears to be "blind support" is people desperately clinging onto what tiny bit of representation they have. It's sad for both sides. It's Stockholm syndrome mixed with political pragmatism. It sucks, but the current political landscape in the US has entrenched itself so deeply in a local minima that people feel like they have to work backwards to make progress. Just see how any discussion of a third party is seen as a psyop to get that side to have a spoiler effect.


As someone who typically supports a lot of third parties at the ballot box, I have to say that our problem is actually not people seeing us as a psy-op.

It's people seeing us as, at best, irrelevant; and at worst, a joke.

I've been voting since the late eighties, and have come to realize it is our lack of organization and, at times, our policies. Which in all honesty can be at once, foolish and bizarre.

It's difficult to bring the platforms of any new party in hand precisely because they are attracting people whose ideas are maybe not very popular in the mainstream parties. The mainstream parties have bizarre and foolish policies as well, but they've had 40 years to brainwash their voters. It's hard to have the same effect in, say, 2 or 4 years.

So you have to have a pristine platform and stick to it.

This is where as independents and third party supporters, we've repeatedly failed.


Voting third party in a first-past-the-post electoral system is a coordination problem. If I, as an individual, have some grab-bag of political stances, with varying weights of importance to me, it is likely that some issues will become a matter of "I am willing to cast my vote in any direction that minimizes the chances that someone with the opposing view does not take power". For example, for people who strongly oppose a backslide into Facism in the US, the only real choice in the last presidential election was voting Democrat, because while there might have been third party candidates that would have been better, the Dems were the most likely opposition to that to win. Absent extremely effective widespread coordination, a vote for a third party increases the probability of an unacceptable outcome.


I think most people aren't leaving their house each day with the same worries people in the 20th century had. It is certainly much nicer to be alive now than then, especially in places like Europe.

What personally has me worried is the derivative and 2nd derivative. How much is my current comfort sustained purely because of the momentum of systems made possible less than a lifetime ago (post WW2 reconstruction). So ironically your comment induces more stress in me. The idea that just as recently as the 20th century, times that my grandparents were conscious for, that many people lived through that much suffering. To me it seems incredibly easy to end up right back there.


I don't know, in the 80s we had a really nice welfare system in the Netherlands that alleviated worry because there was always a safety net. Rent prices were government-set. Healthcare was good and very cheap.

In this century everything was cut and privatised due to globalization, neoliberalism and the financial crises. Wages are not keeping up with inflation, social security is less, national healthcare keeps being cut. I don't care about getting rich but I do want to live my life without worry.


It has never been possible to live life with complete security but the amount that you worry about it is completely up to you.


No but life was a lot better back then. We had less money (we couldn't even afford a car though one is not really necessary here) but that's not so important.


Honestly this is one of the undersold advantages of public transit. It can be fun to optimize your path and switch things up both on a macro and micro timescale. In a car since I'm constantly aware of what I'm doing, taking a less efficient path feels like I'm wasting a part of my life. Taking a less efficient path on public transit feels like I'm taking more time to stop and appreciate my surroundings. Especially because sometimes that alternate path gives me a better view.

A coworker once told me his view of his commute drastically changed when he realized he could take the ferry to work. He got fresh air, it was less cramped, and it only took an extra 5-10 minutes.


The restrictions are initially limited to those countries.


When I started, I was told that one of the easier ways to get promo at L5 was to become a manager. I don't know how true that was at the time, but I think this could be a consequence of that sort of local optimizing. I think now they don't even allow you to be a manager at L5 unless you're grandfathered in?


Search and ads, at least, had the L6 requirement for manager going back as long as I’m aware. I was under the impression that the requirement was relaxed at some point in some of the less revenue critical orgs, but that the L6 restriction actually goes back a long way.


FWIW I was L5 manager (on the SWE ladder) in two PAs. The L6 requirement did exist but in my experience was quite soft. All that my management had to do was justify to the VP that I was capable of doing the job and would soon be ready for promo to L6 (though the first org got nuked and the promo took a long time).


Interesting. Where I was I never saw an exception to the L6 rule.


This is a JAX article, a parallel computation library that's meant to abstract away vendor specific details. Obviously if you want the most performance you need to know specifics of your hardware, but learning the high level of how a GPU vs TPU works seems like useful knowledge regardless.


> abstract away vendor specific details

Sounds good on paper but unfortunately I've had numerous issues with these "abstractors". For example, PyTorch had serious problems on Apple Silicon even though technically it should "just work" by hiding the implementation details.

In reality, what ends up happening is that some features in JAX, PyTorch, etc. are designed with CUDA in mind, and Apple Silicon is an afterthought.


Same here. Part of me wonders if primary school trains your brain to learn via writing things down on paper.


Thinking more cynically: political corruption and connections I'm guessing? Just a couple months ago Musk was treating the US government like his personal playground.


I don't understand this? The comment is next to the code it's mentioning. If the comment doesn't have enough context then the comment isn't long enough. Worst case you should be able to find necessary context in the blame.

I agree that for particularly complex issues you need to file a ticket, explain all the context, maybe give reasons on why it wasn't solved in the original commit. But for forced issues you can easily have the _opposite_ problem to what you're describing. That is: you're left with a bunch of skeleton issues filed only for the sake of shoving it into a TODO comment. Those tickets end up getting auto closed after X time anyways.

Obviously have guidelines, maybe even have a linter warning. But don't implement strict rules. It's a comment.


> That is: you're left with a bunch of skeleton issues filed only for the sake of shoving it into a TODO comment

Nobody says it needs to be one ticket per TODO. For example, I usually maintain a CSS punch list ticket to avoid too much yakshaving when developing functionality. Not only will it be more likely to get scoped and done, but another dev will know exactly where the fixes are needed by grepping for the ticket number.

But the other upside is that if it's really not worth filing a ticket for, why not just do it? I'm curious what scope of work you think is worth tracking in TODOs but not tickets. If it would be a point of work it probably deserves a ticket. If it's less than a point of work, shouldn't you just do it?

> Those tickets end up getting auto closed after X time anyways.

That feels like it reinforces my argument to me. If you can't make time for it when it's a ticket, how would you make time when it's just a comment? At least if the team decides in grooming that the work doesn't really need to be done, it's a group decision and not just me passing the buck.


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: