Netch

6 ms·

31.
by Netch 2y ago
If you want more than 1-second precision, 64 bits are not enough. (Hmm does all C++ std::chrono implementation utilize 128-bit integers for nanosecond precision?)
32.
by Netch 2y ago
> if you do what the various specs on the internet suggest you do if you have an integer > 2^53: you encode it as decimal value as a string. Hexadecimal is better - more compact, much less encoding/decoding effort. Alternatively,
33.
by Netch 2y ago
> The tooling? There's open source tooling that generates code like any XDR tooling and like PB tooling and like MSFT RPC tooling. There is no open source tooling that combines really used scheme understanding - in 5G this includes
34.
by Netch 2y ago
It seems you posit taglessness to be a universal crucial merit of any encoding scheme. This is good in an ideal world, heh. I have had a misfortune to work for 5G which is full of PER-encoded protocols. Dealing with discrepancies in them -
35.
by Netch 2y ago
> I genuinely dislike CBOR. Formats which require me to calculate the length of the message before sending it CBOR is not. No full message length. Only primitive type values. Compound type values require length _in items_ (not bytes) but
36.
by Netch 2y ago
If you mention tab-completing, if starting with the detailest component it wonʼt work at all because of context search problems. If you press something like "alice<Tab>", in deepest-first order it will have to search the who
37.
by Netch 2y ago
> Are these required or useful in this context? At least 64-bit numbers are crucial in any system context.
38.
by Netch 2y ago
If you show your code to unlimited public, there is plenty of sites for this like GitHub or Bitbucket, but itʼs your problem to attract enough reviewers (both in quantity and quality) to attend your project. You donʼt directly need an open
39.
by Netch 2y ago
A similar idea was tested in an experimental BSD clone in Berkeley in mid-1980s. (Great sorry I havenʼt kept link to the description, so rephrase with my own words. Maybe this was in the McKusickʼs book?) No suid or sgid was allowed. A daem
40.
by Netch 3y ago
> Which, ten years down the line, should free up a bit more opcode space when they decide to no longer support CS/DS/ES/SS segment prefixes. The space could be used for instructions that are the same in 32-bit and 64-bit m
41.
by Netch 3y ago
1. Reading the current spec I'm most wondering with mandatory paging enable. This requires prefilled paging catalogs in RAM. Does it mean CPU can't start until ME (or another external agent) generates these catalogs? It also looks
42.
by Netch 3y ago
The design of current x86s is that multiple regions under 4GB boundary are occupied by I/O regions, some of them tied to processor (as APIC, HPET, etc.) and some to extension cards which reject working in 64-bit mode. 3.2GB is an examp
43.
by Netch 3y ago
While the _engineers_ of Intel are definitely not idiots - otherwise they couldn't have been getting enough success - the quasi-engineer layer over it, which makes the real technical decisions, showed a truly summit of folly, multiple
44.
by Netch 3y ago
> Those modes and microcode need to be validated, tested and add bloat to the boot software stack. Just allowing booting directly in 64-bit mode and making 64-bit SMM mode would be enough to avoid boot software stack problems. Riddance o
45.
by Netch 3y ago
Every time I see a yet next inventor designs its own configuration language and foolhardily crosses a rake field of syntax conflicts, design errors, and subtle logic bugs, I recall LISP with its S-expressions. The two last cases were CMake
46.
by Netch 5y ago
As any unlimitedly editable documents this one has been vandalized :( there is no more point to visit it.
47.
by Netch 6y ago
> The code already has that problem. Only in untyped or dynamically-typed languages. But even in JavaScript one may write +obj.version instead of obj.version to make it numeric. Evading this is a straight way to hell. In a statically typ
48.
by Netch 6y ago
> You don't end up in a situation like this contrived example: Modern languages repair this with mandatory block braces: {C style} (Rust, Go, Swift...) or Modula/Ada style (if x then foo else bar end). C style is easier for edi
49.
by Netch 6y ago
> We had that a decade ago. It was called XML and XML Schema. It would be true if XML was not full of all this SGML debris like "entities" (really, uncontroller macros), if real schema formats was flexible enough (I needed <
50.
by Netch 9y ago
I am from Kiev, Ukraine, initially studied English at classic Soviet school with explicit orientation to British style. Nevertheless, it suggests 93% American. Initially I guessed this is due to r-coloring, but words like "plastic bags
51.
by Netch 10y ago
There isn't Chrome for FreeBSD. When I access google.com/chrome from Firefox under it, it says I needn't download it because my Chromebook does it by own means :) Shall I retry later on?