adhocmobility

Why insist on calling this a queue when it doesn't really have queue semantics? Queues do the job of load balancing between different workers. When workers acknowledge tasks, they get deleted, and there are visibility timeouts.

This is a log.

It's not really solving the problems you claim it solves. It's not, for instance, a replacement for SKIP LOCKED based queues.

I think its pretty clear that in the coming decade intelligence and cognitive labor is going to become very cheap. So your kid should develop some skills outside of that to stay competitive in the job market.

Apple has invested a lot in making sure that they STAY in "an order of magnitude better position". They know that the ultimate winner in personalized AIs will be whoever has the best edge hardware. That is why they have been investing so heavily in special purpose on-device chips for running neural networks.

The answer to what they're building is written on Karpathy's twitter - "A kind of Jarvis"

Hi everyone, author of the article here. I'm sorry if the article sounds overly pessimistic. I'm not making any claims with this article. I'm not proposing anything either. I do think technological progress is a good thing, even in this case. But I wrote this blog because I did have an emotional response to this technology, and wanted to pen down my thoughts.

Its one thing to look at a report about the economic impact of new technology, but another to experience it first-hand. This is just a story about someone who will be impacted. Calling it a "sob" story is very harsh. This story is very real and the feeling of losing your job to automation is anything but pleasant.

You are being given a chance to dispute it. Give an example of a problem that any human would be easily able to solve but GPT4 wouldn't.

> "good model of a model of reality"

That is just a model of reality. Also, a "model of reality" is what you'd typically call a world model. Its an intuition for how the world works, how people behave, that apples fall from trees and that orange is more similar to red than it is to grey.

Your last line shows that you still have a superficial understanding of what its learning. Yes it is statistics, but even our understanding of the world is statistical. The equations we have in our head of how the world works are not exact, they're probabilistic. Humans know that "Apples fall from the _____" should be filled with 'tree' with a high probability because that's where apples grow. Yes, we have seen them grow there, whereas the AI model has only read about the growing on trees. But that distinction is moot because both the AI model and humans express their understanding in the same way. The assertion we're making is that to be able to predict the next word well, you need an internal world model. And GPT4 has learnt that world model well, despite not having sensory inputs.

We resolve this in two ways

1. All git-lfs files are kept in the same folder

2. No one can directly push commits to one of the main branches, they need to raise a PR. This means that commits go through review and its easy to tell if they've accidentally commit a binary, and we can just delete their branch form the remote bringing the size back down.

If you just want a git for large data files, and your files don't get updated too often (e.g. an ML model deployed in production which gets updated every month) then git-lfs is a nice solution. Bitbucket and Github both have support for it.

I can't imagine it, which is why I asked. You certainly seem skeptical. Your arguments aren't very convincing though.

> Too many different start batteries

Okay... that's because there's no standard. But isn't that why standards are developed? Could you explain why developing a standard and a limited number of battery sizes is not feasible?

> Risk of storing and handling them improperly

Could you explain why batteries are riskier than petrol?

And while we're discussing this China's decided to try it out [0].

[0] https://www.reuters.com/business/autos-transportation/inside...

Waiting anywhere while your car is charging seems like an awful user experience. I've always imagined that a quick battery swap service would become the standard. Don't know how feasible it is though, maybe someone can shed more light on that.

The second case is preferable if numbers is an Optional[List], which is usually the case when passing lists around as arguments.

  def custom_sum(numbers: Optional[List[int]] = None) -> int:
    if not numbers:
      ## something

    return sum(numbers)

I'm a very passive hackernews reader, and don't engage much with posts. I want to break that passivity to say that Visidata is the tool that has given me the greatest joy out of any other piece of software I've ever used.