Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
temac
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
79 ms
·
781.
▲
by
temac
8y ago
A lot of affordable machines a few years old even had 4M. I remember my dad upgraded from 4 to 8 and from Win3.11 to Win95. The computer had maybe 1 or 2 years, hardly more. It was around 1500€ (well, it was 10000 FRF at the time) when boug
782.
▲
by
temac
8y ago
Cutler certainly did not write the whole first kernel alone, although the initial size of the NT team was quite small, at least at the very beginning. The story of the development (until the at least the first release, IIRC) is in the book
783.
▲
by
temac
8y ago
> It was definitely a weird time - the transition from "home computers" (8-bit mostly) to "personal computers" (32 bit mostly) - and 16 bit machines were mostly skipped over Well, IBM PC & clone started their live
784.
▲
by
temac
8y ago
I just checked and both of my benchs were done with Defender. When I disable it, it is down to ~0.5s I would not build a Linux kernel here instead of in a VM, but for tons of things, this is very usable.
785.
▲
by
temac
8y ago
Well in the end we are using any X rather than Y tech because of manpower, regardless of pretty much any other characteristics. So let's put manpower kind of aside for the bulk of the dev (where thousands of man-years are needed for an
786.
▲
by
temac
8y ago
About shared libraries, I know that there is this line of thought considering them "evil" (well at least sufficiently to want to get rid of them); but I'm quite unsure about what a modern system would look like without them (
787.
▲
by
temac
8y ago
You want to ditch shared libraries and mmap to map your big processes using GB pages to make fork fast again (despite it not being the main and only drawback)??? OS research might be relevant, and it's good that some people have wild i
788.
▲
by
temac
8y ago
On 1803 and 1903 it's 3 to 4 times faster than MsysGit (WSL is ~1s on my laptops). It is possibly slightly faster on 1903 as my laptop running it is faster than the other for this bench, despite having an older processor. Now in a Linu
789.
▲
by
temac
8y ago
That's always a possibility and there are others. Many people found that whole class of possibilities not especially interesting, because they are falling on the irrefutable slope; if there is a "god" that absolutely can not
790.
▲
by
temac
8y ago
I don't see why JO would be any different from other Jcc, especially since JL is SF ≠ OF. Maybe you were thinking of the problem with INC/DEC and CF, but even then that's a problem of INC/DEC, not of Jcc.
791.
▲
by
temac
8y ago
> The second area is memory consistency guarantees. x64 has relatively strong guarantees, allowing simpler assembly code but at the cost of more complex memory subsystem between cores. A64 has much weaker ordering guarantees, which saves
792.
▲
by
temac
8y ago
IIRC Notepad source code is in a Windows SDK. Probably an old one, but it only started to be actively maintained quite recently (and even then: only very lightly), so the source code you can get will likely cover most of its lifespan for no
793.
▲
by
temac
8y ago
And it would actually change the historical and current behavior of exec returning ENOEXEC for 0 bytes executables (see also https://news.ycombinator.com/item?id=19081124 ) . So I am changing my mind: a binary true is bette
794.
▲
by
temac
8y ago
Oh it is not nearly as good as I thought then. I actually tested it and zero byte exec still make exec() returns ENOEXEC on Linux. So a small binary is definitively more versatile...
795.
▲
by
temac
8y ago
It would be a valid approach but it is less elegant and harder to maintain. Probably the kernel could special case 0 bytes executables, if you really want to optimize the scripted truth.
796.
▲
by
temac
8y ago
true once was, and IMO should be again, implemented as a 0 bytes executable. Since then, it has infinitely bloated on most systems. It actually began at AT&T, where they apparently decided to copyright the trueness. From there it went d
797.
▲
by
temac
8y ago
You don't know what you are talking about and accuse others of your very sins just because of internet points... FYI mitm attacks have been employed against high profile targets, and VLC is deployed pretty much everywhere. This is a ve
798.
▲
by
temac
8y ago
I saw no controversy in at least the second (reddit) link, appart from an anonymous coward insulting him and making random gratuitous hypothesises - moreover likely unrelated to anything...
799.
▲
by
temac
8y ago
Tons of people have already interpreted that it is ready, and some of them have died. Maybe they are to blame. But for practical reason, I don't care much. I interpret Tesla's communication as highly misleading, for the very simpl
800.
▲
by
temac
8y ago
As far as I know Win NT threads are 1:1. Not even sure how it would work or even make any sense to have N:M handled by the kernel. N:M is usually a mainly a userspace thing. And Windows is even less likely to use that kind of convolution, b
801.
▲
by
temac
8y ago
hm is NT a purer Unix than Unix then? After all, it has all its object in a filesystem-like tree...
802.
▲
by
temac
8y ago
> No, because in reality those are handled by different computational units. Integers are handled by the ALU, and pointers are handled by the loader. They are distinct things to the CPU. I strongly disagree. Yes some execution units are
803.
▲
by
temac
8y ago
But is the fallback path for production even correctly tested, then? And if it is, then what becomes the point of the assertion?
804.
▲
by
temac
8y ago
If you have a fancy "USB" port which allows connexion of graphics cards (so basically a PCIe port, although it also accepts USB), chances are that you can do whatever you want with unrestricted DMA through this port. It seems that
805.
▲
by
temac
8y ago
If the effects are merely limited to a widget behaving weirdly, this is a sound strategy. And this seems to be the case for front-end code in well designed systems.
806.
▲
by
temac
8y ago
So assertAndContinue makes no sense, right? On my side I don't really see its point anyway. If the code is actually ready to handle such failures, this is merely an error trace, so it should just be called that.
807.
▲
by
temac
8y ago
I'm not sure even sure they will ever change it. It was designed for Vista using a security model that now corresponds to the "always ask" setting, and hastily changed to propose the two other settings for Windows 7 because u
808.
▲
by
temac
8y ago
It isn't has bad as the Apple one though. But of course, Dell should also fix their shit.
809.
▲
by
temac
8y ago
Engineering, especially at this level, is not supposed to work like that. You certainly not do dev proto, then switch to prod both in one step and without even rechecking the tests you did on the proto. So their official explanation might
810.
▲
by
temac
8y ago
Today a graphic chip is also good to compute ultrasound images. I suspect that you can even do it on a CPU. I'm not sure if it is that practical to process in a FPGA if you want to compute non-potato image quality: you would need to
More ›