We could invade other countries and take their actors. We could reinstate the actor's draft or do mandatory 1-2 years actor's service like some other countries do
The domain name reminds me of the venerable DOS "debug.com" command, which managed to combine an interactive and scriptable debugger, assembler, and disassembler into a program weighing a few kilobytes. I spent many long hours in my youth using it to reverse engineering copy protection on games. I really wish we had a similar tool for the modern era.
Sure I remember, but since I purchased Spinrite doing lowlevel was needed just once while changing ST-506 controller to a different type or for a new disk, former was quite much rarer needed.
Then even after std lowlevel it was worth using Spinrite to check if interleave value was proper. And if it wasn't it was worth letting it first before anything else. Same when changing a faster CPU as it could speed up IO so much that no interleave would not needed any more and get faster IO.
Spinrite was such a great tool and time saver fixing or making preventive periodic maintenance to customers disks, even though it chugged hours even 30M disks. And just because not to take absolutely any risk it was necessary to make full backup first, which that took quote long also. LapLink was a great tool for that, before LAN became more common.
But it's when you consider taking first full drive backup times. It still takes 'forever' when you'd rather like to get on with fixing single disk issues. Or like when you wait RAID rebuilds too.
We did plan our maintenance tasks so, that there was something else useful we could do while obligatory backup and Spinrite was running. Upgraded another devices EPROM's, PC BIOS or dot matrix printer EPROM, cleaned printer heads, chaff and dust from chassis, changed colour ribbon to it. Ran updates to software we had sold etc. And went lunch with the customer:)
It turned into 5 days. After realising I'd forgotten to change the block size to 4096 and it was horribly slow, I yanked the drive out, tried with my utility to set it to 4096 bytes and failed, found another utility that did the job, put the drive back in, wait 3 days for it to rebuild the array without the new disk, and then another two days to add the disk back in. Sigh.
Still, with 4k block sizes, it goes like shit off a shovel.
WinDbg is just a debugger: it does not assemble or disassemble. It can't patch running programs in memory. Moreover, I don't consider Windows to be part of the modern era, as I haven't used a Windows machine for 20 years.
A more apt analogy: I don't consider North Sentinel Island to be part of the modern world, since there is no relevant innovation going on there, it has no influence on the rest of the world, and there is nothing to be learned there.
You miss debug.com, wish there was an equivalent for the modern era, find out that windbg does almost all these things today, and say there's nothing of value there.
I say this as something who does all the things you described debug.com as doing, in this modern era.
Maybe so, but that's not what you claimed. You claimed that WinDbg "does not assemble or disassemble", when of course it does. Try to be more accurate with your claims if you want serious people to take you seriously.
Actually, I didn't even get to this part of your message, windbg absolutely can patch currently running programs. It does all the things you think it can't do.
Okay, but is it not what you wished for, "a similar tool for the modern era"?
edit: I see I simul-posted with u/modeless, but I can't remove it now that there's a (duplicate) reply. Maybe mods can remove or at least collapse mine (their ID is one lower so they were first)
WinDbg is just a debugger: it does not assemble or disassemble. It can't patch running programs in memory. Moreover, I don't consider Windows to be part of the modern era, as I haven't used a Windows machine for 20 years.
If OP wanted to know whether WinDbg and debug.com can be considered feature-similar, they could have read my first comment [1], where I specifically said that debug.com is a "debugger, *assembler*, and *disassembler*". Of those three features, WinDbg provides one.
> Sounds like you aren't familiar with Nvidia's dedication to low-power ARM SOCs. Ever heard of the Nintendo Switch before? The Tegra inside that is a 15w TDP gaming SOC. And it supports CUDA (somehow).
I think that GP comment is not intending to throw shade at ARM SOCs (many of which are quite nice, including those from Apple an Qualcomm), but specifically the Microsoft products built on them.
I'm mostly surprised by the insinuation of bad performance or battery life. That's what will be ostensibly solved by putting an Nvidia SOC where a Ryzen or Intel one used to be.
Has this chip actually been used in any real product yet? Nvidia has, er, a bit of a historical problem with overpromising and underdelivering with their mobile chips (in particular see the Tegra 2 and Denver); I would be cautious until there are real benchmarks. It's hard to describe any previous Nvidia general-purpose mobile chip as anything other than a failure.
I agree that that's the point he's making, but I don't see how that would work practically. His attitude is that malloc(1<<63) should immediately crash the system, every time? How is that better?
No, if a process allocates an infeasible amount, malloc fails and the process needs to deal with the failure (which is what already happens, "malloc doesn't fail on Linux" is only really true for smaller-than-page-size allocations). The point being made is that the system should account conservatively for all memory that can be used, not just the optimistic underestimate that overcommit enables (i.e. the plane should always carry enough fuel for contingencies, and landing with extra fuel is a good outcome).
You never need to crash the system if you remove overcommit. You just crash the one process. Practically speaking, you don't even need to crash here; you just return null (which malloc is always free to do) and let the consequences speak for themselves.
Always baffling to me that people accuse researchers and doctors, people who have devoted their life to helping others, of brazen greed and deception. With no evidence, of course. Maybe the accusation says more about you than about them?
The researchers and doctors probably have better motives but the pharmaceutical industry wants nothing more than getting you on a lifetime of prescriptions. They are just like street dealers but they dress better and blend in with normal society.
If you're a Catholic, then the choice of interpretation is clear: you must accept the Pope's interpretation. That's what it means to be Catholic. The Pope is God's representative on Earth. To defy him is to defy God.
The alternative would be to declare him a False Pope and to select an alternative divine representative. Of course, that would make you a heretic. If you ditch the pope as soon as he says something you don't like, you're not much of a Catholic. The Church is not a democracy.
> If you're a Catholic, then the choice of interpretation is clear: you must accept the Pope's interpretation…
cf. Hyperpapalism
Thankfully, Hyperpapalism is a misunderstanding of the role of the teaching-governing authority of the Bishop of Rome, and Catholics can be and remain good Catholics while disagreeing with the Pope on a variety of matters.
Pope John XXII publicly taught erroneously re: death and the Beatific Vision. Jean Gerson threatened to burn him at the stake and in general there was much public resistance, from royalty to common folk.
"Erroneous" is an opinion. Papal doctrine is the word of God until a subsequent pope says otherwise. Jean Gerson is entitled to his opinion, even if speaking that opinion made him a heretic.
> Papal doctrine is the word of God until a subsequent pope says otherwise
No, that’s Hyperpapalism, which is an error.
The Pope does not have the authority-power to transform error into truth, nor can he make “new truths” (of the Faith), whatever that might mean. He does have the solemn duty to faithfully hand on and explain the Apostolic Tradition. In an extra-ordinary act of his office, the Pope can, without error, define the proper understanding of Catholic teaching on a matter of faith or morals.
In the case of John XXII he proposed something false as pertains to Catholic doctrine, repeatedly, in public sermons. He was rebuked for it and recanted before he died. What he taught was not somehow “intermittently true”, it was an error through and through, and it was completely right that his subjects called him out on the matter.
> The Pope does not have the authority-power to transform error into truth,
The problem with your argument is that it is "left as an exercise for the reader" to determine what is actually true. If that were the case, then the Pope, as the representative of God on Earth, serves no purpose: everyone can individually determine what is true and what is an error. That does not agree historically with the role of the papacy.
If everyone has a right to their own interpretation of doctrine, what does the Pope do, and why should anyone listen to him?
Your position that absolute faith in the word of the pope
is a fallacy is itself a self-supporting fallacy, which you hold only because you don't believe in the correctness of the pope.
> he taught was not somehow “intermittently true”
Yes, it was. God would not allow a Pope who spoke in error.
a few comments back, you stated a Catholic must accept the pope's interpretation; I think this is generally true?
The problem here is, we're saying the person who claims to be pope has contradicted past teachings that popes infallibly taught already. So the only way out then would be to consider they were never popes in the first place or else you have the contradiction of a pope taught error or that the pope is not infallible.
For example in Dignitatis Humanae (Declaration on Religious Liberty) in the Vatican 2 documents it states: "This Vatican synod declares that the human person has a right to religious freedom. Such freedom consists in this, that all should have such immunity from coercion by individuals, or by groups, or by any human power, that no one should be forced to act against his conscience in religious matters, nor prevented from acting according to his conscience, whether in private or in public, within due limits."
This is obviously contrary to the Catholic understanding of conscience and coercion - the "due limits" and "religious freedom" are never defined, when they were already somewhat clearly defined.
Hence being ambiguous, we would understand these in themselves to not be Catholic teachings. Consider if someone asked a person if they are a Catholic and they answered "I am a Christian". In itself, their answer does not explain if they are Catholic or not: some Catholics might argue that "only Catholics are Christians" and that the statement could mean "I am a Catholic"; some protestants might argue that "only non-Catholics can be Christians" so that the statement means "I am not a Catholic". Hence, in itself the statement is "objectively ambiguous" - the Vatican 2 statements are of this character, and if you had to categorize them as either "Catholic or not", it seems they would resolve to being considered as "clearly not Catholic". In any event, it seems we would be forced to reject the language as it stands and new documents that are clearer would have to be drawn up and agreed to.
For example, a person does not have the right to declare they have the "religious freedom" to be a "Pirate" and that they are free to steal from other people "conscientiously"; they are allowed to be "coerced" to not steal, if they try to steal.
Regarding John XXII from the other comment, I believe St. Robert Bellarmine in De Romano Pontifice examined all cases of alleged papal heresy and explained why no popes had been heretics. John XXII simply speculated as a private theologian about an issue that had not been defined by the Church yet, hence did not enter in to error in doing so.
Huh? Have you forgotten Clippy, the first AI agent?
/s
reply