zvrba

10 ms·

61.
by zvrba 4y ago
I think your diagnosis is wrong. When the program exits, in whatever way, all resources/locks/etc are cleaned up. (Hey, the OS is also nice enough to tell waiters about abandonend mutexes.) There's no built-in GUI, but there&
62.
by zvrba 4y ago
Eh. What about updated libc.so or libssl.so? If daemons using them do not get restarted, they keep using the old version. If they do get restarted, well, then, it's just as if you rebooted the machine. Somewhat quicker, but in effect i
63.
by zvrba 4y ago
> How would the multiple copies find the global memory segment? They would all use the same reserved "name". It's possible to atomically create or open a SHM segment with a given "name". Then have a header at th
64.
by zvrba 4y ago
??? All the time? I reboot ca once a month, for windows update.
65.
by zvrba 4y ago
> I don't know how you could avoid this, and it has me wondering if you understand the issue. I understand the issue. Someone else has already mentioned how you could avoid this: allocate fds randomly instead of sequentially. This
66.
by zvrba 4y ago
The windows feature is not buggy, the process that created the file potentially is as the creating process chooses the sharing mode. Except for executable images (EXE/DLL): they're always locked on the filesystem as long as any ru
67.
by zvrba 4y ago
Like Windows file share mode. Mandatory, "hard" lock on a file. The OS doesn't let you delete it if another process holds it open. (You can forbid any of 3: reading, writing, deleting by another process. It is completely orth
68.
by zvrba 4y ago
> Why everything which doesn't work as someone expected is called "damned"? Because POSIX doesn't provide features that are necessary for reliability. Workarounds, if they exist, are highly platform-specific. That I&#
69.
by zvrba 4y ago
I read this as a damnation of POSIX filesystem semantics. File descriptors getting reused, insane locking semantics on close, allowing you to delete an open file and providing no means to prevent it, fork causing problems, unspecified behav
70.
by zvrba 5y ago
> If a malicious userspace program writes predictable data to /dev/random immediately on boot, Hmmm, how did the program get there? A case for secure boot, no? At least initialization of RNG state should be included in the tru
71.
by zvrba 5y ago
A naive question from a hobbyist with over-average interest in particle physics: quantum theory is based on complex numbers. Has anyone considered that mass/gravity may also have an imaginary component that manifests itself as "da
72.
NATO expansion – what Gorbachev heard(nsarchive.gwu.edu)
6 points by zvrba 5y ago|0 comments
73.
by zvrba 5y ago
WTF/wow. As a native speaker of Croatian I can understand 80% directly and additional 10-15% by "interpolating into the context". Good work. EDIT: I don't like Slovio either, especially because of using x/cx/et
74.
by zvrba 5y ago
A bit funny, one never reads about such bizarre problems with commercial databases. DB2, SQLServer, Oracle...
75.
by zvrba 5y ago
> You don't have to do things like [...] carve out their own way to represent lists, mappings, and numbers I work with XML extensively and out of hundreds of classes and fields, I've needed an arbitrary dictionary maybe a handf
76.
by zvrba 5y ago
> and if not in Haskell/Scala then what languages Java and C#.
77.
by zvrba 5y ago
> the schema is acting as a basic version tag Except that it's syntactically separate so no other version tag can masquerade as yours. PLs have namespaces as a separate syntactic construct as well, and for a good reason. > Embedd
78.
by zvrba 5y ago
> So you'd mix and match elements from different versions of the schema in the same document? No, the use-case is having an archive of documents conforming to different schemas. Or another use-case: schema evolves during the system&
79.
by zvrba 5y ago
https://bishopfox.com/blog/json-interoperability-vulnerabili...
80.
by zvrba 5y ago
The serializer exports the schema and you map the schema to whatever code is needed, using whatever XML library, to extract the data based on the schema. XML rules are strict and how to extract data from the document, given schema, is unamb
81.
by zvrba 5y ago
1) If _you_ are designing a new API, then my answer still holds. Choose a serializer and let it decide the wire format for you. 2) If someone else has already published the API, well, then it's already decided. In both cases, your obje
82.
by zvrba 5y ago
> How do namespaces help with versioning? That seems like a complete non-sequitur. They tell you how to interpret data and to which schema definition the data conforms to. Elements `<a:MyElt>` and `<b:MyElt>` tell you explici
83.
by zvrba 5y ago
> I've never known any of XML's features to help with actually solving a business problem. Namespaces let you version data and unambiguously mix elements with the same (simple) name in the same document. Esp. the first point is
84.
by zvrba 5y ago
> When do you put something in an attribute and when do you give it its own tag? [...] Oh, the same old red herrings around irrelevant details. The simplest answer is: it doesn't matter. Let your serializer of choice handle it. More
85.
by zvrba 5y ago
Yes, MSVC STL implementation is dog-slow in Debug. I solved the problem by creating a new build configuration called "RelNoOpt" that builds with "Release" runtime-libraries and STL, but turns off all optimizations. I get
86.
by zvrba 5y ago
So someone "reinvented" mastermind with letters instead of colors.
87.
by zvrba 5y ago
When someone writes "More extensible than XML", you know they've never truly seriously studied and used XML.
88.
by zvrba 5y ago
Ah, quoting in cmd is its own kind of hell. Not so fun fact and actually the only part of Windows APIs that I truly hate (and I've worked with many of them): command-line arguments are passed to the program as a single flat string. Spl
89.
by zvrba 5y ago
> drop \ for / API calls accept / as path separator (and interpret it correctly). Shell is a different beast though.
90.
by zvrba 5y ago
> The problem with this dream is that to achieve it, (1) everything would need to be rewritten in a single language Not true. Look at COM. It has a reputation for being "ugly" and "legacy", but having worked with it,

More ›