dchest

47 ms·

571.
by dchest 8y ago
I'm so sorry that a little bit of HTML and JavaScript reminds you and other commenters under my post of web developer's Old Browser nightmares and brave endeavors of satisfying 100% of Web users at any the cost, but we're tal
572.
by dchest 8y ago
<dialog> <p>Hello world</p> <button>OK</button> </dialog> <script> let dialog = document.querySelector('dialog'); dialog.quer
573.
by dchest 8y ago
No, it's a attempt to intentionally slow down user. I don't remember nag screens that open websites: it either tells you that you press the wrong button and re-randomizes the button order or quits the program. There are also versi
574.
by dchest 8y ago
I wouldn't call it a dark pattern: there's no trickery or deception; nothing bad happens if you pressed the wrong button. It's called a "nag screen", and in many cases it's the only difference between a trial v
575.
by dchest 8y ago
Arbitrary precision integers is a JavaScript implementation detail; JSON standard doesn't specify number precision.
576.
by dchest 8y ago
On the other hand, gzip can reclaim most of those 33% with Huffman encoding.
577.
by dchest 8y ago
Since WASM can't create or access JavaScript objects directly, I bet it's still slower. MessagePack (or my preference, CBOR) is still useful and faster than JSON if you need to exchange raw bytes from typed arrays (for JSON you&#x
578.
by dchest 8y ago
This is mentioned in the article.
579.
by dchest 8y ago
Google: https://ai.google/research/pubs/pub43231
580.
by dchest 8y ago
They probably should have disclosed the relation (they disclosed that Intel, Cavium, and Qualcomm sent engineering samples to them), but accusing Vlad Krasnov of writing a PR piece for Qualcomm in the form of blog posts describing his work
581.
by dchest 8y ago
Gold can't be created, but it had real usefulness in manufacturing. Are you saying that the intrinsic value of gold is the price manufacturers of "useful" products from gold are willing to pay for it?
582.
by dchest 8y ago
Go: func Eul: fn Come on, it should be "fun".
583.
by dchest 9y ago
Better (smaller and/or faster) compression.
584.
by dchest 9y ago
Also https://www.lattepanda.com , around the same price.
585.
by dchest 9y ago
Some more cheap SBCs from my bookmarks: - BananaPi (Allwinner, MediaTek): http://www.banana-pi.org/ - Le Potato (Amlogic) and Renegate (Rockchip): https://libre.computer/ - NanoPi (Samsung, Allwinner) : ht
586.
by dchest 9y ago
Probably Egypt, based on beer brand.
587.
by dchest 9y ago
I agree that this library doesn't looks good — a proper implementation would use a better precision (e.g. 1/10000 of a currency unit) rather than "cents" (1/100), and of course, check ranges and the absence of fract
588.
by dchest 9y ago
Another interesting project is this open hardware ARM-based laptop made in Bulgaria, shipped as a kit to assemble https://www.olimex.com/Products/DIY-Laptop/ It costs €240, though.
589.
by dchest 9y ago
These are not integers! Integers are exactly represented from -2^53-1 to 2^53-1.
590.
by dchest 9y ago
Yes, the size is after optimization (although I suspect iconutil recompresses it) :-) It's just that there are 10 images inside, from 1024x1024 to 16x16.
591.
by dchest 9y ago
But there's no way to do so in JavaScript unless you implement a numeric type by hand This is not true: with 64-bit floating-point numbers, calculations on numbers in a range from Number.MIN_SAFE_INTEGER (2^53-1) to Number.MAX_SAFE_I
592.
by dchest 9y ago
JavaScript numbers can hold integers without losing precision up to Number.MAX_SAFE_INTEGER (9007199254740991, or 2⁵³-1), can be checked with Number.isSafeInteger(). Bitwise arithmetics, though, works on 32-bit numbers, so "casting&quo
593.
by dchest 9y ago
Fun fact: the icon for my Objective-C Mac app is larger than the executable binary (517 vs 394 KB).
594.
by dchest 9y ago
It's not the same, there's no commit indicating that Bob branched off Alice's branch. It appears as if the whole history before merging belongs to Bob's branch. There is such commit in Fossil. > If you really want tha
595.
by dchest 9y ago
It records which commits the commit came from, not which branch. merge /\ commit-hash1 commit-hash2 When branching, Fossil creates a branch commit with the branch name (similar to git tag object), and
596.
by dchest 9y ago
Here's a simple example: - Eve has a repository, Alice and Bob have access to it. Eve goes on vacation and nobody commits to "master"/"trunk". - Alice makes a branch "alice-fixes" and creates commits
597.
by dchest 9y ago
You can't see its name, try it.
598.
by dchest 9y ago
You are talking about history of commits, not branches. Here I commented about tracking branches, hopefully it's more clear: https://news.ycombinator.com/item?id=16806954
599.
by dchest 9y ago
Again, that's not the same. Each commit in Fossil belongs to some branch, because its name and the fact of adding or removing a name is recorded directly in the commit artifact. In Git, branches are local references to commit (local in
600.
by dchest 9y ago
:-) That's not a proper data structure, and you can't point to a random commit after merging and deleting a branch, and ask git to tell you which branch it came from.

More ›