This. But flares are still waiting to come back in this case. To get my foot in the door writing windows GUI programs I often have to obfuscate the fact I am using Delphi (don't ask, don't tell) or work with clients without big IT departments.
Disclaimer - No clients were ever injured during this experiment.
Seriously, can we just settle on that? It's objectively the best and the fact that there are so many of competing alternatives is the reason why we're still stuck with that 8bit artifact ridden ancient JPEG.
From what i've seen JPEG XL always wins against AVIF in every category. What makes you say AVIF would be "objectively the best" while JPEG XL boasts better compression, more funtionality(32bit support e.g.) and faster encoding?
AVIF does better at low-bitrate scenarios ( low bits per pixel, quality is going to be poor anyway, avif can make it less poor) while JpegXL does great at higher bpp and lossless scenarios
hello, at work, I am not admin. I have developed a small flask site using sqlite. Always using commandline was painful. I have considered phpliteadmin, but this requires many tasks for installation. My boss would not understand that I spend half a day on this.
I have discovered SQLite-web today. It took me less than a minute to use it.
This is exactly what I was looking for.
I'd suggest spending a little time with Docker and compose.. even in small, single server applications it helps a lot to smooth out application deployments.
didn't they do that to test the effects of being in space for a long time on general health, dna status? See how much bones degrade, if blood chemistry stays the same, etc.
I think his point was mostly about "writing software". As in you won't need specific software anymore and the computer/network would do what you tell it without specific "apps".
Would it be a problem since the wal you delete, its inode, will still be open and processed at the DB closing normally? Just guessing, never tried that.
There are cases where the wal file is not merged on shutdown of the application. I think a corrupted database can also prevent merging the wal file automatically. A corrupted database can often be repaired, but it needs to be done manually.
I've been bitten badly by that issue once. I just mounted the .db file into a docker container and didn't realize that sqlite creates wal files. On an non-graceful shutdown of the application the wal file was not merged into the db and the container deleted. And around a day of changes were lost.
Conclusion: Sqlite databases should be placed into their own folder, so it's obvious that it's not always just one file.
This is configurable, and for small things you might disable WAL completely.
When using WAL, if you’re copying or backing up the database it’s possible to force a checkpoint, then you can copy the .db file alone knowing exactly up to when it contains data.
However, it's not specified to completely disable speculation, only "to the extent that such speculation can be observed through side-channels as a result of control flow speculation or data value speculation". So e.g. an implementation could decide to disable speculative memory access while still allowing arithmetic operations.
Preventing Spectre vulnerabilities is pretty much the only reason you'd want to disable branch prediction though (except for curiosity of course). Without prediction, performance would be as bad as if every branch was mispredicted, since the pipeline has to stop and wait at every single branch. The idea of branch prediction is that the "wasted" cycles waiting for the branch to resolve can instead be used to do some computation that may or may not be useful; if it turned out to be useful you saved some time, if not you didn't lose anything (besides maybe some electricity). So even a branch predictor that randomly guesses with 50% accuracy is a huge performance win over not speculating at all.
