dathinab

50 ms·

601.
by dathinab 1y ago
yes cancer is only one of the more deadly and more reliably attributable to cigarettes things there are quite many things made much more likely with smoking which would end very deadly but modern medicine has learned to to move into the non
602.
by dathinab 1y ago
honesty depending where you are such allegations might be very baseless & meaningless for many reasons like - high base humidity of the place (e.g. the city where I live has a yearly avg. humidity of 70%, but specific to my apartment an
603.
by dathinab 1y ago
> so it's relatively meaningless to share individual cost-benefit analyses. yes 1. it's very affordable to fix 2. long term exposure always adds a non negligible risk so just fix it I'm confused why people get hung up on a
604.
by dathinab 1y ago
> and you can reduce it to basically 0% for little money. which is why I'm confused by people second questioning how bad it actually is in context of _fixing_ it (not in context of a national health scope) if there is something whic
605.
by dathinab 1y ago
them disabling it is only about Android/Chrome not about their servers I wouldn't be surprised if they do have servers with it enabled when very useful. and Android Linux kennels lack behind in their version
606.
by dathinab 1y ago
yes but what this isn't telling you is that android has a long history of running hopelessly outdated kennels and it being very common that Linux kernel related android cves related to newish features have already been fixed upstream b
607.
by dathinab 1y ago
no, only if you have a quasi monopoly on Office Application in pretty much every single (western) government through all departments and sectors.
608.
by dathinab 1y ago
you can have both having a lot of intend to keep it complicated and cause vendor locking and comply in bad faith and this being very easy to archive just by not trying to improve on a status quo and creating a standard where you are the onl
609.
by dathinab 1y ago
they probably do, parsing the XML syntax was never the complexity issue with OOXML, or XML formats in general everything on top of the XML AST is the issue
610.
by dathinab 1y ago
> The business model is just screaming that GPL'd LibreOffice is toast. or MS might find itself accidentally toasting themself a lot of places (including very important MS Office customers) insist in a open document format for vario
611.
by dathinab 1y ago
yes HTML and CSS have went unhinge without question big reason for that is that they where not designed for modern requirements like being used as a general purpose application UI toolkit especially CSS was designed printable documents, not
612.
by dathinab 1y ago
> The OOXML format is likely a not very deeply thought out XML serialization of the in memory structure or of the old binary format it somewhat looks like that, but that old binary format changed with every nth yearly major new version a
613.
by dathinab 1y ago
> is absolutely easier to parse/interop with than a legacy binary format depends you can have well, clean and fully documented binary formats which are relatively easy to parse (e.g. msgpack, cbor, bson) you might still not know wha
614.
by dathinab 1y ago
> They didn't have the luxury to first come up with a clean file format and then write the tools around it. This is just not right. They where not required (AFIK) and in some edge cases also didn't provide a perfect conversion
615.
by dathinab 1y ago
> Looking at Latex, I don't think hand tuning some parameters until you get right look in every single case is much better user experience... In my experience you do that more in Word then in Latex (the I added some paragraphs here
616.
by dathinab 1y ago
even many of the very widely used LaTex "editors" do have some semi live "preview" feature which often allow some WYSIWYG like features in the preview similar if someone random non technical person just needs to write id
617.
by dathinab 1y ago
honestly OOXML looks a loot like someone took a non XML format and gave it a XML encoding like XML is a mark up language so it _should_ interleave quite "naturally" and well for text formatting tasks (i.e. see OpenDocument example
618.
by dathinab 1y ago
as far as I understand just parsing OOXML is by far not enough to get anywhere close to having a reasonable correct understanding of the layout of the document due to how it's "supper flexible" in ways going "beyond the
619.
by dathinab 1y ago
I wonder how much of this is related accidental grown complexity (in their original closed format) and their WYSIWYG just doing dump stuff devs aren't sure how or why it ended that way but also don't want to touch least it breaks.
620.
by dathinab 1y ago
The is why I said read the WAL doc page in a different answer ;) They do point out the risks here: https://sqlite.org/wal.html#avoiding_excessively_large_wal_f... sqlites design makes a lot of SQL concurrency synchronizatio
621.
by dathinab 1y ago
yes, per "open connection", hence why not closing+reopening connections all the time helps the cache ;)
622.
by dathinab 1y ago
if you enable WAL mode with sqlite then readers are not blocked by writer so only writers queue up without needing any special case handling to archive it (in general you _really_ should use WAL mode if using sqlite concurrently, you also s
623.
by dathinab 1y ago
There are multiple aspects to it: - sqlite is a bit like a RWLocked database either any number or readers xor exactly one writer and no readers - but with WAL mode enabled readers and writers (mostly) don't block each other, i.e. you c
624.
by dathinab 1y ago
that can be the reason, but it's a very bad example it's quite unlikely that it would be _that_ much smaller if it had been written in C or C++ with the _exact_ same goals, features etc. in mind. like grep and ripgrep seem on the
625.
by dathinab 1y ago
fun fact there is work in progress to have a cranelift based backend, which isn't exactly an interpreter but more like a AOT compiler build for WASM but it anyway does compile things much faster at the cost of less optimizations (doesn
626.
by dathinab 1y ago
> is unfixably slow it's not at all unfixable, I mean sure there is a limit to speed improvements but many of the things you mention aren't really as fundamental as they seem one one hand you don't have to go crazy with ge
627.
by dathinab 1y ago
yesn't they require you to compile a binary (or multiple ones when nested) before being able to compile your binary and depending on a lot of factors that can add quite a bunch of overhead especially for non-incremental non-release bui
628.
by dathinab 1y ago
> They're not; it's complicated, and simple the simple answer is rust compiler times are not dominated by the borrow checker at all, so "it's fast" and you can say it's not overly related to their being borr
629.
by dathinab 1y ago
I won't say it's not hording, but there are also some other reasons you can't well untangle from hording: - buying games you played pirated before (now that you can afford them), but you already played them so no need to play
630.
by dathinab 1y ago
I think, It's because the locking is part of the transaction commit locking, but yes it should be mentioned. But it's oversimplified a case of "high queue load f* up the availability/timings for other DB operations"

More ›