Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
temac
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
61 ms
·
571.
▲
by
temac
7y ago
Binaries are probably not mapped with MAP_SHARED, but I checked the mmap manual for MAP_PRIVATE and read: "It is unspecified whether changes made to the file after the mmap() call are visible in the mapped region." I learn somethi
572.
▲
by
temac
7y ago
And even then mmap does not guarantee performance. So for example just don't use mmap for small files, and for larger ones benchmark to see if you really get some perf. As for the code, if you just can let it crash, prefer that to atte
573.
▲
by
temac
7y ago
Or if your FS is slightly corrupted and figures out quite late it does not know where part of the file is. Or if you suddenly loose access to the hard drive. If you write your program carefully, you can handle it, but it is way more difficu
574.
▲
by
temac
7y ago
Except that we continue to slowly automate away human intervention (must be done reasonably; it must still be possible , it is just less current in practice). Just look at the state of the art in field X at date T, then 10 or 20 years afte
575.
▲
by
temac
7y ago
ISDN is an edge point to point protocol (although used to get on a network). I don't really see how it has to do specifically with anything related to AD vs Azure (a data link is a data link, you could has well have used an analog mo
576.
▲
by
temac
7y ago
> Software is also moving into critical spaces like aerospace, medicine, banking, etc. The thrust of the article is that we're trusting more-and-more critical infrastructure to a discipline that anyone who's worked in knows is
577.
▲
by
temac
7y ago
A 486/66 ran Doom well and Duke Nukem 3D mostly ok. (Even a 386 run Doom, although quite poorly.) It's quite reasonable to be able to draw a few polygons on it at low res, although it can depend on tricks and skill of the programm
578.
▲
by
temac
7y ago
You had a bad ram socket that silently corrupted data while you used ecc?
579.
▲
by
temac
7y ago
Probably that plays a role. However, not everything is a startup. Accumulating technical debt during even just a few years like there is no tomorrow is also a non negligible risk. You can also go from billion to zero in a few years...
580.
▲
by
temac
7y ago
The funny thing is that most people never even attempt to do that, and then still manage to complain about it being impossible. Yes in some projects that can be harder, but I'm not buying the ambiant: "in most projects".
581.
▲
by
temac
7y ago
Just to nitpick, there are counter examples of finished but not abandoned software. As usual, Tex comes to mind. Or they just could. E.g. we could probably take the current Python 3 and freeze it and debug it for 20 years, at which point it
582.
▲
by
temac
7y ago
If your textual copy past includes some requirements of conforming to a contract, or simply actual copy past of "knowledge" (which can very well also be a under the form of a big textual pattern), the mere form of "primitiv
583.
▲
by
temac
7y ago
If things needs to evolve to separate direction, you can duplicate them. Unreasonable X is unreasonable, that's true no matter X but that's not very insightful. Unreasonable factorizing is unreasonable. So are unreasonable copy pa
584.
▲
by
temac
7y ago
Of course you were going to buy a $50k computer to a luxury brand but can't find bodyguards. Which maybe it is even the case; and in that case you probably should think hard about if you are not slowly drifting away from the realit
585.
▲
by
temac
7y ago
> That said, pipe() is not "portable" either, so whether to use platform-dependent code for pipes or semaphores... no big difference. pipe() is in POSIX base since forever. If it is not portable, I don't know what is. Oh w
586.
▲
by
temac
7y ago
I would not call avoiding a classic thundering herd problem a bad choice, especially when the top maintainer of Linux does it himself in Linux: which is arguably more probable than him rewriting GNU Make (well we all know he could do it,
587.
▲
by
temac
7y ago
On the contrary one of the reason of COM is to not depend on the C++ ABI, which is not stable at all under Windows (it has been de-facto stable for the three last version of MSVC, but was broken each time before, and the recent stable strid
588.
▲
by
temac
7y ago
Is it really not UB to attempt to modify RO things? Typically (on major implementations, e.g. GNU/Linux or MSVC/Windows) it will crash, and I don't think it is allowed to crash on non-UB things?
589.
▲
by
temac
7y ago
If the string was in a variable, yes, but in this case most implementations will put it in a RO section.
590.
▲
by
temac
7y ago
It is known since... forever?, that one should not speculate across security boundaries. This was not enough to avoid Spectre, but this was largely enough to avoid TONS of security vulns Intel is also susceptible to. Somebody messed-up big
591.
▲
by
temac
7y ago
For C: both platform have been EXTREMELY compatible over the years. They probably both treat breakage as bug. This is a must given the fundamental APIs are defined in term of C headers, and must remain compatible. Even for C++: gcc has been
592.
▲
by
temac
7y ago
While that's true, expecting bad maintainership to not have any effect and third parties not discussing about the quality of the software is also delusion. (And in practice, maintainers maintain, and I'm glad they do, because othe
593.
▲
by
temac
7y ago
> he didn't have to do any of that Of course he didn't, in the legal sense of the term. And then people didn't have to stop criticizing him, in the legal sense of the term. And obviously for the ethical / moral point
594.
▲
by
temac
7y ago
Half (more probably 99% actually) of our critical infrastructure software use that wording (or an equivalent one), regardless of it is free software or proprietary software. Yet most are maintained responsibly, if they are used for serious
595.
▲
by
temac
7y ago
While I 100% agree with you, project having chronically technical issues are bound to get a bad reputation. So what is "missing" is a common way to discuss about that kind of issues, as a community, while staying civil and not in
596.
▲
by
temac
7y ago
> First of all, a larger change to code a teammate wrote has a ring of saying: it was badly written. Not necessarily. In actively maintained projects code change all the time in some area, and if you are doing proper commits very often a
597.
▲
by
temac
7y ago
> seeing your code being rewritten after a week is no fun, and it's a huge blow to your confidence as well. The people doing the rewrite benefit from your work though. They might would have done the initial writing "worse"
598.
▲
by
temac
7y ago
Comparing single threaded speeds is also very valid for tons of contexts. Of course if one algo can't be multithreaded, maybe it will be better to use one that can instead, if that's interesting for a particular application, but i
599.
▲
by
temac
7y ago
> Languages with null still have value types that cannot be null. Not all languages. > C++ doesn't define this, but the OS does (and even has help from the CPU). That's not how it works anymore, because C / C++ front-en
600.
▲
by
temac
7y ago
> A healthy engineering team is constantly building trust. Rewriting your teammate’s code without a discussion is a huge blow to your ability to effectively collaborate on a codebase together. I'm against the idea that people shoul
More ›