6,563 karma · joined October 10, 2013
Whether Europe or North America have a problem with too much immigration and not enough integration is debatable, maybe - and I suspect that's where your perspective comes from - but Japan decidedly does not (maybe too much tourism, and I feel at least some of the antagonism towards foreigners comes from that, but no matter). Immigrants still make up a very small percentage of the population, mostly in Tokyo; given the existing challenges with immigration, they tend to be extremely diligent, respectful, appreciative of Japanese culture, and hard-working.
This is just a populist conservative government pandering to the some of the worst aspects in society to distract from their failures.
Not discounting the importance of supply/demand, or the damage that restrictive zoning regimes have done, but I'm not sure if this should be so strongly stated, depending on how you want to define "small differences in rental law". For example, per Wikipedia:
> In 1971, the Swedish economist Assar Lindbeck, a housing expert, said that "rent control appears to be the most efficient technique presently known to destroy a city – except for bombing". In 1989, Nguyễn Cơ Thạch, then Foreign Minister of Vietnam, observed, "The Americans couldn't destroy Hanoi, but we have destroyed our city by very low rents. We realized it was stupid and that we must change policy."
Obviously banning junk rental fees is not the same as rent control, but in either case we're talking about rental law that as an unintended second-order effect is going to (to some degree or another) discourage supplying rentals by making it harder to make money renting.
So, in the interest of being charitable to the OP, I think they're including zoning laws, building regulations, and so on in what they're saying: these cities claim to view housing as a human right, yet simultaneously seemingly do everything in their power to make it incredibly hard, expensive, and risky to supply it.
I don't agree that this attitude is exclusive to big progressive cities: the right theoretically claims to love free enterprise and deregulation, but in practice they're often just as happy with overbearing government control as long as it's their guy doing it. And if anything these days the right more than the left fetishizes certain images of American life that motivate stricter regulations on development; NIMBYism cuts across the political spectrum. But it's an attitude that maybe makes better bedfellows with the left and its intrinsic distrust of markets, and maybe afflicts those left-leaning coastal cities more because they're otherwise much better places to live and thus have higher demand.
Everything's subjective, but I think most people would say that the art style was great then and is still great, and the theme is pretty unique and compelling. That's why people like it so much.
The puzzles and interface really are awful though, and I say that as someone with a reasonable tolerance for adventure game logic. It's far-and-away the worst-playing classic LucasArts adventure, and even though I'm sure there's plenty of adventure games with worse puzzle design, I'm struggling to think of one with a wider gap in quality between the game design and everything else. Everything's frequently so disjointed and it's such a slog to get around, it's not even one of those "use a walkthrough when you get stuck" games; it's a "just follow a walkthrough constantly" game, or maybe even a "just watch a longplay" game.
Made using the leaked debug build and its symbols, which shows how meaningful the work the game preservation community that acquires and distributes these things is.
OTOH this is pretty off-putting:
> Where the compiler needed a particular source shape to reproduce a register choice or a schedule and no natural spelling was found, the construct is marked with a // COMPILER-DIFF: comment (644 of them: dead tests, empty asm("") launders and anchors, register T x asm("rN") pins, padding statements).
To me the value of a decomp isn't reproducing the original bytes per se (we already have the original bytes after all) - it's about reconstructing the understanding of the original game as represented by human-readable source code; getting byte-for-byte is just an indication that you've gotten it right. Needing to add a bunch of slop to force the compiler to match the original output is actually just an indication that you've gotten it wrong - and it's a demonstration of the danger of Goodhart's law, especially as it applies to AI.
They haven't had a stable 1.0 release yet, but they've had many pre-1.0 releases. It's not some personal experiment that's been sitting in the dev's Github that people are piling onto; the author has gone out of their way to promote it, beg for donations, and lash out at any criticisms.
The issue has never been the quality of the language per se, the issue has been 1) wildly misrepresenting the quality of the language in the present tense; 2) not even having any kind of a realistic roadmap towards achieving the kind of outsized and implausible claims about the quality of the language; and 3) using these outsized, implausible misrepresentations as a way of soliciting hype and funding for the author.
I was reading your comments on Java, nodding my head, upvoting, without checking your profile and realizing that you're a member of the Java team. Knowing that doesn't mean I now suddenly disagree with you or anything. But while in an ideal world it doesn't matter who's saying something when evaluating it, there's some human factors at play - I'd like to turn up my internal sense of skepticism when dealing with someone, effectively, selling something their salary depends on; even if you're being entirely earnest, it's ultimately a sales pitch, and I feel bamboozled for not recognizing it - that'd make me appreciate transparency.
(FWIW, even though I prefer being coy about my place-of-work, I have no professional relation to this conversation. I've never used Java in my 9-5 and I haven't even really used it in earnest since, like, version 5 back in high school. I think it's always been underrated by the hacker crowd, though!)
If you insist on finding a way to criticize leftists on the climate file, a much better tack would be pointing out how some environmentalists have opposed nuclear power or densification.
I don’t know enough about high performance microarchitecture design to evaluate that argument confidently, but it seems to make sense to me.
It's not academic but the closest similar case that's coming to mind off the top of my head was when James Frey (who FWIW is white) got found out for A Million Little Pieces, which definitely was major news.
As Flannery O'Connor wrote, "The result of the proper study of a novel should be contemplation of the mystery embodied in it, but this is a contemplation of the mystery in the whole work and not or some proposition or paraphrase. It is not the tracking down of an expressible moral or a statement about life." We don't read literature with the hopes of a book laying out a precise thesis and incontrovertibly demonstrating it.
If you come into GEB expecting a scientific explanation of consciousness (like I did, when I first read it) you walk away confused and maybe disappointed. Hofstadter observed something transcendentally beautiful about self-reference and had a spiritual or religious revelation that, for him, related it to consciousness, and he attempted to convey that beauty and spiritual revelation in - appropriately self-referentially - a book that embodied it. You're meant to appreciate it in your heart and soul, not (just) in your mind. It's literature, not science.
Never mind how compact, beginner-friendly, and just plain fun they were to use. It's been said countless times but I'll say it again - we've lost something over the years.
Is the UI updating itself automatic or manual? Because if it’s manual, that’s precisely the error-prone part that you’re saying this approach somehow solves - you’ve done the “How to Draw an Owl” meme. If it’s automatic, that doesn’t seem especially different from the React/Redux/Elm/SwiftUI approach (as a sibling points out).
I don't know about forcing, but there's certainly a long history of emacs users trying to convince vim users that they're wrong. Without loss of generality - the same is true in the other direction of course.
Software devs are more than used to having a multitude of tools at our disposal (text editors, programming languages, Linux distros...), having strong preferences, and engaging in the delicate balancing act of advocating for our favourites while living-and-letting-live as the cosmic ballet goes on. It's part of our culture; I don't think that culture necessarily exists outside. For instance, a common layman question to ask is, "Why are there so many programming languages? Why doesn't everyone just use the same one?" And I don't think mathematicians are immune to this blind spot.
The nearest equivalent to "tooling" in math, traditionally, would be notation I suppose, and mathematicians are accustomed to eventually coalescing around a single standard notation.
* the SB-SIMD contrib now supports ARM64. (Thanks to Sylvia Harrington)
* AVX512 instructions are now supported on X86-64. (Thanks to Robert Smith and Arthur Miller)
* additional support for SIMD instructions on ARM64 and X86-64. (Thanks to Arthur Miller)
These seem like pretty awesome additions. Does anyone know how SIMD works in SBCL? Is this at the codegen layer? i.e. can it auto-vectorize or anything like that? Or are these intrinsics you have to explicitly ask for?And meanwhile, Java the language improved and Kotlin came along as (arguably) the better better Java, so there became less of a need for it.
“It is Kant who made really bad writing philosophically acceptable. We can no longer point to some atrocious sentence by someone else, and say ‘How can it be worth reading anyone who writes like that?’ The answer could always be ‘What about Kant?'”
(Kind of relevant to this thread actually! Hah!)
In the preface to the second edition of the Critique, Kant himself acknowledges that "a talent for lucid exposition" he "cannot regard [himself] as possessing".
FWIW I suppose I am in Kant's audience, as a (long-since graduated) philosophy student.