HN user

thargor90

126 karma
Posts0
Comments48
View on HN
No posts found.

LPs can prove optimality of a result but sometimes this is to expensive and you stop as soon as you reach near optimality based on known bounds.

For several problems you can prove lower and/or upper bounds for the optimal results. For example you can prove that a route between two points may not be shorter than their distance.

If you use LP in production you often don't care about optimality and can work with suboptimal results very well. Worst case you stop after a timeout and just pick the best result.

Edit: I forgot to mention that during solving of a LP you usually get dynamically computed bounds. The branch and bounds algorithm works by computing bounds on relaxed problems that give upper bounds for the original problem.

You are right in that there is a class of algorithms for which it is possible to do that. It is just not possible to decide if any algorithm is in that specific class of algorithms or not. There is an even smaller class of algorithms that can be constructed bottom up from halting sub algorithms. But these are not as powerful.

Nobody is arguing that the usecases are the same. In the end you can't even chat with gzip (although you could with it's predictor).

The thing is, that building the predictor is almost the same thing for compression and LLM. Of course the goals and taken tradeoffs are different. The paper shows this analogy.

ChatGPT et al use structured prediction to simulate intelligence. Building the predictor is fancy lossy compression.

Questions arise if lossy compression of things without copyright is legal or not. If I mp3 a lossless recording we currently think it is not legal. With LLMs this is not entirely clear yet.

We use micro because we could develop a custom plugin without too much effort and it is very easy to deploy (copy) to systems that have no good terminal editor available.

Prefer vim usually, but it's too much effort to deploy a sane configuration to our target systems.

I'm not sure how it works in the US , but there are plenty other jurisdictions were the estate is not required to settle debt but may just transfer it to the heir.

There is also jurisdictions were there is no inheritance tax, which would otherwise require to sell at least some of the estate.

LineageOS 20 4 years ago

Be careful with Titanium backup. It cannot handle several modern Android things properly. (E.g. proper SE Linux file properties)

I learned the hard way after the fact...

Reviewing merge commits is harder because they will sometime have huge diffs to both branches.

Rebasing is the process of redeveloping your feature based on the current master. This is smaller, easier steps to review later.

It is a pitty that we can't have tooling to create "hidden" merge commits to allow to connect rebased branches, this would retain the history better and allow pulling more easily.

You are allowed to trust the Hungarian hosting provider because they are legally bound to comply to GDPR.

You are not allowed to trust the US provider, since there are US laws that are not GDPR compliant. It is not possible to provide a compliant hosting service under US jurisdiction.