AFAIU, the people suing have no privity; they're just a neighbor and don't have any right to enforce the covenant. (If the covenant had granted them an interest, they could have.) Presumably the original property owner who granted the land, or their successors in interest, could sue to enforce the covenant, but they haven't.
> That reason seemed to boil down to: "If it was good for a Sun/3 in 1986, then it must also be good for a Linux box in 1996." It was a dumb reason.
ext2 disk corruption, especially on power failure or a crash, was a common threat in the 1990s. Not merely to the point of requiring fsck and a bunch of orphaned files (which was inevitable on an unclean shutdown), but just totally fubar'd, requiring a reformat. The only thing worse was then trying to reinstall Slackware from the floppy disks, at least one of which had a better than even chance of corruption from just sitting in the drawer since the last reinstall, requiring another long night nursing a download over the 2400 baud modem.
I use OpenBSD, and while FFS2 has been far more robust than 1990s Linux ext2, smart partitioning is still warranted, not just for minimizing blast radius, but also for managing backups, etc. I haven't had the chance to use ZFS, and it might be the only filesystem I might consider skipping partitioning for on a workhorse system, but even if you trust the design and code quality of ZFS, it's running unprotected alongside a bunch of horribly buggy kernel subsystems and drivers, so....
You raise an interesting point. Please allow me to enhance it.
It could get worse than reinstalling Slackware, again, from floppies. I didn't get to experience corrupted floppies; I instead had a habit of recycling my Slackware disksets for other purposes after the system was up and running. So any complete re-install started by booting up MS-DOS to run Telemate to start downloading them fresh from Sunsite...again.
But at least it was Telemate, so I could manage files to free up more floppy disks while this process slowly continued at [I guess I was fortunate] 9600 or 14.4kbps. ;)
I don't recall much difficulty with ext2 being fragile (though I can provide horror stories about OS/2's HPFS). If I had issues with it, they didn't leave any scars.
But I accept your correction. It may have been the case that splitting the filesystem into different partitions made sense because ext2 was fickle, and I was just very lucky in deliberately ignoring that advice after the first time I misjudged the partition sizes at install and ran out of space in some directory or other.
Hard drives seemed so small back then. Installing a real OS meant a serious tradeoff in the ratio between user data and system data.
---
Anyway, ZFS. The ZFS way is that it owns the whole disk -- for a long time, the preferred method didn't even use partitions at all. Nowadays OpenZFS does create one partition for itself by default, but it uses the whole disk just the same.
Blast radius is limited by having different datasets (think "filesystem-light"), and read-only snapshots, and easy, consistent backups (if you have a compatible device or service to send them to -- otherwise, it's ~the same backup dance as any other filesystem with snapshots).
It's a different way of doing things, like a subsystem in and of itself. It keeps its own caches and generally wants to be as close to the metal as it can be. Which sounds scary, but meh: Almost everything worth doing gets done with two commands, zfs and zpool, and the syntax has been consistent enough over the years that old documentation from Sun still has value.
I've been using it for most of a decade now and I find it to be ridiculously good. My only wish is that it could be a first-rate player on Linux, but license incompatibilities be that way sometimes.
The president has a large degree of control over the agencies and their output, so in practice agency delegation granted presidents immense power. This power went largely unexercised due to norms. But that has been slowly changing, and under Trump radically changing. And if SCOTUS adopts the Unitary Executive Theory, as they seem poised to do, then we'll have something very close to a king, difficult to distinguish from 18th century Great Britain.
I don't see how requiring Congressional ratification for rule changes would grant the president more power than he has now. Currently the primary checks are procedural limitations; but were Trump a better, more well organized leader these procedural checks wouldn't pose much of a hurdle at all.
If you want a more technocratic administrative state, the agencies would require more autonomy from the president than they have now, but things are moving in the opposite direction both as a practical matter and constitutionally.
> don't see how requiring Congressional ratification for rule changes would grant the president more power than he has now
A modern economy has a million small emergencies every day. Given the choice between dysfunction and autocracy, humans routinely choose the latter. So every time an emergency emerges that Congress takes too long to act on, and where the President steps in, the window shifts power to the executive.
Alpine is a very popular platform for both compiling and hosting Go applications--especially static, no n-CGO binaries--given it's minimal footprint.
A common issue people have with Alpine is musl libc's DNS resolver, which can behave differently (thus confusingly) than glibc's. But that wouldn't effect Go applications unless CGO is enabled and it uses the libc resolver. Go's native resolver behaves differently than glibc's, too, but I don't think that's any more of an issue. And the musl resolver has fewer quirks today than it used to, so fewer surprises than a few years ago.
WG14 adopted variably modified types, a kind of dependent type. From a security standpoint it offers all the same qualities. It also in principle was easier to integrate from a backwards compatibility standpoint, with the exception of struct member analogs (which we now have but aren't yet standardized).
Maybe we would have been better off with Ritchie's counter proposal. But neither proposal was chiefly concerned with security, thus no proposals for, e.g., automatic bounds checking.
Just to be clear, I often think we would have been better off with Ritchie's proposal, assuming it would have seen at least as much adoption in implementations and usage as variably modified types, which sadly remained poor for many years after C99, and arguably still poor. But being better off doesn't mean being in a drastically better situation than we are today from a security perspective. The proposed alternatives were prerequisites for substantively improving security, but far from sufficient. And the delay in adopting and refining variably-modified types has cost much more than whatever marginal benefit Ritchie's proposal offered. Ditto for other gaps, like better facilities for handling arithmetic, e.g. overflow and mixed type comparisons. The first step in addressing overflow only came with C23 (overflow checking routines), and the latter only in the forthcoming C2y (typesafe, mixed-signedness min/max, etc).
The support for variably modified types is excellent, if you discount MSVC which is lacking support for modern C anyway (it seems to catch up a bit though).
Real-world usage certainly remains poor. Using pointers to VM types remains annoying, and I wish the committee would settle on a solution to the ordering of VM parameters. But, yeah, the VM types are solid in GCC and clang and should be used more.
I think both AMD and Intel employ and/or fund GCC and LLVM developers to add support for each new architecture. Compiler and product release schedules are independent so the target and tuning support in the latest compiler release may be slightly behind or even ahead of the latest microarchitecture release. GCC 16.1 has support for Zen 6, which has even been released, yet. (https://gcc.gnu.org/gcc-16/changes.html#x86)
By the time the Europeans arrived Singapore had long since declined:
> However, by the time the Portuguese arrived in the early 16th century, Singapura had already become "great ruins" according to Alfonso de Albuquerque.
How far back and how much context is required for a simple narrative to not constitute lying? And for a narrative about national origin, is it not also misleading to insinuate that successive settlements and polities constitute a singular, shared history?
And Europeans were not the first colonial powers to land on and assert control over the peninsula. In fact, the incumbent Muslim powers the Europeans encountered had colonized the peninsula only a couple of centuries beforehand. Aboriginal peoples (pre-history "colonizers") still live in Malaysia, and they're still as isolated and impoverished by the state as they were before Europeans arrived. Malaysia even has its own Plymouth Rock-like monument (on the coast somewhere near Malacca, IIRC), and it's not where Europeans first stepped ashore. And it seems a little odd to presume Singaporeans would identify with the political and social history of their Malay and aboriginal predecessors when Singapore, a majority Chinese community, was kicked out of Malaysia precisely because of racist and xenophobic sentiments of many Malays.
The racial politics of Malaysia and Singapore are at least as complicated as in the US if not more so. I count South Africa and Malaysia as the two countries where racial politics are not only as complicated, but open and explicit as in the US, and like the US the relationship between European colonizers and the "native" groups constitutes only a portion of that complexity. Many other countries have similarly diverse groups, but usually one group is unchallenged in its power and there's very little open discourse about the subject. But contemporary anti-colonial rhetoric whitewashes (figuratively and literally) all of this.
Not sure about Singapore but Malaysia's racism is not complicated. It is discrimination into law. It makes things rather clear. About discourse of course there is not discussion to have.
The most amusing part of Malaysia's discrimination is in the term "bhumiputra," which is Sanskrit for "son of the soil," but today it's used for Malay muslim.
All these lands were Dharmic originally, all the way to Japan, before the various cults arrived.
What nonsense, colonizers do not live and settle there for thousand of years. Would you called majority Japanese now a colonizers since the originally come from Korea/China and before them they were people there?
>Singapura had already become "great ruins" according to Alfonso de Albuquerque.
Albuquerque was the first European colonial who conquered Malacca in the early 16th CE, later Dutch and then British. They all came because they wanted to bypass what they considered "trading bottleneck" created by Ottoman, the most powerful maritime empire in the Mediterranean and Europe for many centuries.
The local authorities most probably very well deployed a typical scorched-earth strategy to prevent the Albuquerque to fully utilize Singapore infrastructure. The British did exactly this to most part of Singapore including totally damaging the very important causeway when the were defeated by Japanese in the mid 20th CE. Fun facts, the world busiest causeway still not return to the its original sophisticated design with elegant pass-thru water design until today, thus pollution side effect are still happening and not being solved [2].
> Would you called majority Japanese now a colonizers since the originally come from Korea/China and before them they were people there?
Depending on context, yes, especially considering that (AFAIU) there still exist identifiable (socially, not just genetically) ethnic groups on the Japanese archipelago who predate that colonization event, and who still experience forms of ostracization typical of such colonization. There'd be no cognitive dissonance for me because I refuse to internalize a definition of colonialism that tacitly presumes European exceptionalism and supremacy through a sort of reverse White Man's Burden logic of moral accountability and historical criticism.
For the same reason, I recognize that groups we (i.e. westernized, globalist, cosmopolitan, what-have-you types) typically call aboriginal in a homogenizing, undifferentiating manner were often colonizers themselves thousands of years ago, displacing other aboriginal groups that may or may not still exist today. There are multiple such groups in Southeast Asia. And the first such modern human aboriginal group may have colonized an area occupied by pre-modern, archaic humans. (Or possibly vice versa!)
Buying into the logic of modern anti-colonialism critical theory is not required to appreciate and criticize the harms European colonization inflicted and continues to inflict. But rejecting that logic might be a prerequisite to recognizing and appreciating the exact same dynamics and harms that played out and still play out today among non-European ethnic groups.
Here is a piece of history trivia. Not trying to have an argument.
> they wanted to bypass what they considered "trading bottleneck" created by Ottoman
The Ottomans didn't exactly close the Silk Road, but they made it harder and more expensive to use it.
But the major reason for the maritime routes taking over the cargo traffic was that it's much more efficient to sail to Asia with your cargo than to walk it on camels.
So when the Portugese found the way around Africa and landed in Calcutta on May 20 1498, the trade patterns changed forever.
>So when the Portugese found the way around Africa and landed in Calcutta on May 20 1498, the trade patterns changed forever.
This new route discovery actually significantly increased the importance of Strait of Malacca and Singapore, not decreasing it.
Actually even before that important turning point event, the European already knew about about the importance of Strait of Malacca including both the metropolis Malacca and Singapore/Temasek. The is one famous quote by a 16th CE Portuguese explorer Tomé Pires, who declared: "Whoever is lord of Malacca has his hand on the throat of Venice".
To say that Singapore was an obscure fishing village is disengenious by the colonial powers and those believing this wicked narrative are in denial.
My once top comment about this "elephant in the room" has been downvoted to oblivion, but hey c'est la vie. There's a very popular saying, "you can fool some people all of the time, and all people some of the time, but you simply cannot fool all of the people all of the time".
There's also a narrative that if the tea via land it's called chai and if if the via sea it's called tea [1].
The Ottoman controlled both the land and sea route to Europe creating the trading bottleneck from the European perspective for many centuries to the far East, they never close it. Thats's why both Dutch and British created their very own East India Companies about the same time around 1600 CE as the vehicles to trade in Asia once they found the new trading route around Africa to Asia. Due to their highly profitable business endeavour, their governments willingly become the side-kick colonizers for their new companies and becoming complicit to wrestle and overcome any countries that refused to their own unfair business arrangements, terms and conditions including trading monopolies.
[1] Tea if by sea, cha if by land: Why the world only has two words for tea (317 comments):
reply