thargor90

While you are right about the PS4 (and xbox), the Nintendo consoles are nothing like desktop platforms.

WiiU is the same architecture as the Wii and the Switch is the same platform as Nvidia Shield.

The claim is not there is no data races in Java programs. The claim is that Java programs are memory safe, because the underlying virtual machine memory model is free of data races.

Go does not have that.

(Of course also Java may suffer from memory safety issues on system boundaries to unsafe code and due to JVM bugs.)

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.

The biggest problem is heating in winter, which requires way more energy than cooling in summer. So for colder areas doubling Panels will not be enough.

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.

To get std you need some kind of libc replacement. You don't need that if you just want to use alloc.

You cannot approximate NP-complete functions. If you could approximate them with a practically useful limited error and at most P effort you would have solved P=NP. (disclaimer my computer science classes have been a long time ago)

They won't be able to write it off though, because they still could Release it.

To be pedantic: writes may also make use of indices, if you have constraints (like foreign keys) the db needs to check for every write.

I was under the impression this is how things always work in graphics pipelines. You don't want to give up on all the precision between 0 and 1

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.

I have been able to fix these random lags by doing multiple full disk reads. The first one will take very long, because it will trigger these lags. Subsequent ones will be much better.

The leading theory I have read is that maintenance/refreshing on the ssd is not done preventative/correctly by the firmware and you need to trigger it by accessing the data.

As a non-native speaker: how is it pronounced differently?

Maybe I'm biased, but in my opinion crime risk is higher in the US, where you have "no-go-zones" than ok most parts of Western Europe, where this concept does not really exist.

But where to migrate to?

Too have fun with laws/rule systems take a look at nomic

You are right. The /8 is 10.0.0.0/8.

I guess it's not a typo, but a weird way to write 10.0.0.0/8 excluding 10.1.0.0/16 .

Yes, this explains the how, but not the why.

Why is there no optimization in place for this? Converting a=x or a=y or a=z to a in(x,y,z) should be trivial and the db should have heuristics to calculate the expected query cost to decide when to apply this transformation.

That's weird. I thought this would be optimized based on database statistics and not depend on the query syntax. At least for those simple queries.

Can anyone elaborate why this is the case?

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.

Is the Wii stillconsidered to be in the market?

Don't know how far the 5g rollout is, but in Vienna, Austria we have full 4g in all subway lines and stations since 2018. No need for wifi.

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.

Because they never realize capital gains. Instead they take a loan and use the stock as collateral to get liquidity . They never pay back that loan, but just pay interest, which again lowers their taxable income.

That's what I did as well.

The problem often is fighting the urge to correct things. For me the only thing that helped was sleep deprivation, but probably alcohol has a similar effect.

Do you know any IDE or editor that implements this? I would love to try it.

What I hate about python/yaml/etc is that copy/paste + reformat does not work.

Yes it forces clean indentation, but it gives the writer the burden to take care of it. That sucks. Let the computer do the work.

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.