Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
axelriet
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
61.
▲
by
axelriet
7mo ago
Thanks for the free psychology assessment, I appreciate it, but I believe I’m fine. The series omits lots of details.
62.
▲
by
axelriet
7mo ago
Interesting point. Time will tell.
63.
▲
by
axelriet
7mo ago
The comment comes from the input field on the post form. Not clear it would show up as a comment. The old thread you refer to had little to do with Microsoft per se. Let me known if I can help with the inconsistencies you mention?
64.
▲
by
axelriet
7mo ago
I didn’t know that “subtitle” would appear as first comment.
65.
▲
by
axelriet
7mo ago
Could not have said it better myself. Thanks.
66.
▲
Decisions that eroded trust in Azure – by a former Azure Core engineer
(isolveproblems.substack.com)
1297 points
by
axelriet
7mo ago
|
648 comments
67.
▲
by
axelriet
7mo ago
A former Azure Core engineer’s 6-part account of the technical and leadership decisions that eroded trust in Azure.
68.
▲
by
axelriet
7y ago
It appears you did not read what I wrote. The similarities are out there for anyone to see, there is plenty of leaked Windows code floating around including on GitHub, and I did not need anything else to form my opinion.
69.
▲
by
axelriet
7y ago
My opinion about ReactOS has nothing to do with my job or my employer, you are trying to make this into something it is not.
70.
▲
by
axelriet
7y ago
I’m not speaking in the name of the company: I expressed my personal opinion about ReactOS and wrote back in 2017 that I think it’s a ripoff, after looking at their code. I’m not out there to destroy ReactOS, but if you ask me today what I
71.
▲
by
axelriet
7y ago
It’s not documentation no. Some smart people spent a lot of time observing and disassembling and explained a number of things but major aspects are entirely missing, and not all of what is written is accurate. In any case this definitely is
72.
▲
by
axelriet
7y ago
Someone pointed to that earlier. Great talk about how he gathers information to write his books.
73.
▲
by
axelriet
7y ago
That sounds reasonable (symbols inadvertently leaked). This would be a plausible explanation for at least some of the naming similarities.
74.
▲
by
axelriet
7y ago
Thanks for the personal attack lol. I watched and did not learn much, except that he’s a quite decent orator. I think what he describes is the process he uses to write his books.
75.
▲
by
axelriet
7y ago
I’d love that you point to an instance where the private symbols of the kernel actually shipped? It is very possible that some private symbols were part of some leak, but stolen data does not qualify as “shipping” :) Again, I stand behind m
76.
▲
by
axelriet
7y ago
It’s my personal opinion and it’s based on my lecture of ReactOS code at the time I downloaded it (circa when I wrote my reply on Quora). I think anyone who can read C code can reach similar conclusions just by eyeballing the code in ReactO
77.
▲
by
axelriet
7y ago
I cannot edit my comment for some reason, sorry for the typos. About my colleague’s hack don’t get too excited, this is ancient history but it was at the center of a public debate at the time. Some 3rd parties had an ask, the company said i
78.
▲
by
axelriet
7y ago
I expressed my personal opinion, here and on Quora. I think I’ll be fine.
79.
▲
by
axelriet
7y ago
Microsoft does not release the kernel’s private symbols, trust me on that. But yes there was some leaks in the past, small portions of NT4 and W2K were leaked, I think I link to a Google query pointing to articles discussing the leaks in th
80.
▲
by
axelriet
7y ago
Thanks for the link, o for a bunch of new followers on Quora today and was wondering why :) There are lots of good answers in this thread. In particular, someone took the time to look at the code, and that person wrote it only took them min