- wk_endSo…if the Python team finds tail calls useful, when are we going to see them in Python?
- If you want to make your writing appear non-AI generated, the easiest way is to write it yourself. No typos necessary.
I’m sure with enough cajoling you can make the LLM spit out a technical blog post that isn’t discernibly slop - wanton emoji usage, clichés, self-aggrandizement, relentlessly chipper tone, short “punchy” paragraphs, an absence of depth, “it’s not just X—it’s a completely new Y” - but it must be at least a little tricky what with how often people don’t bother.
[ChatGPT, insert a complaint about how people need to ram LLMs into every discussion no matter how irrelevant here.]
- You could maybe make that claim about the original broadcast, but an article in The Verge about internet censorship - and the internet routing around censorship! - seems highly relevant to tech.
- No, I'm not. Really frustrating to have to explain this repeatedly.
While ethnic cleansing undoubtedly occurred, it wasn't the original intent "at the core" of the Zionist project. Rather, the intent at the core of the project was - precisely as always stated - desire for Jewish self-determination, and (once again) they initially set out to attain that through peaceful and legal means and were happy to accept an internationally supported solution that did not involve ethnic cleansing.
I'm really not sure how to make this clearer: there was an entirely workable plan that would have gotten the Zionists what they wanted without ethnic cleansing, they accepted it, no further violence needed to occur. The proof is in the pudding: if ethnic cleansing was core to the project, such a plan could not have existed and/or the Zionists would not have accepted it.
Instead, the Arabs refused this, had zero interest in trying to negotiate any kind of peaceful solution, began to ethnically cleanse Jews throughout the Arab world [0], and launched an international war effort to subjugate or oust the Jews from the region.
The Israeli defense and retaliation ultimately included ethnic cleansing of its own. That's undeniable. But even here it wasn't core to the project; it wasn't a war goal at the beginning. Per Wikipedia [1]:
It's tragic that they arrived at that "third and further aim"; I'm looking back on this with 80 years of both distance and hindsight, but I can at least conceive of a world in which they didn't.Initially, the aim was "simple and modest": to survive the assaults of the Palestinian Arabs and the Arab states. "The Zionist leaders deeply, genuinely, feared a Middle Eastern reenactment of the Holocaust, which had just ended; the Arabs' public rhetoric reinforced these fears". As the war progressed, the aim of expanding the Jewish state beyond the UN partition borders appeared: first to incorporate clusters of isolated Jewish settlements and later to add more territories to the state and give it defensible borders. A third and further aim that emerged among the political and military leaders after four or five months was to "reduce the size of Israel's prospective large and hostile Arab minority, seen as a potential powerful fifth column, by belligerency and expulsion".I don't mean to whitewash what the Israelis did in the war - any more than Palestinian supporters want to whitewash what the Arabs did and intended to do, I suppose. But I was replying to someone asserting that the State of Israel simply could not exist without ethnic cleansing, that to be a Zionist fundamentally means to support ethnic cleansing. This is what I'm disputing.
[0] https://en.wikipedia.org/wiki/Jewish_exodus_from_the_Muslim_...
[1] https://en.wikipedia.org/wiki/1948_Arab%E2%80%93Israeli_War#...
- I don't believe I referred to the Nakba or anything else as "peaceful" - of course the Zionists engaged in (non-peaceful) violence, before and during and after the war. But the point is that, contra the claims that ethnic cleansing is "at the core" of Zionism, violence wasn't the Zionist starting point and unlike the Palestinians they were content with a peaceful solution; neither of those things would've been the case if violence was fundamental to their project.
- From a different perspective, it's not that wild at all - if you go back far enough, there's a decent chance that we all speak languages in the same "language family".
After all, being part of the same language family doesn't imply that strong a connection - English resembles, say, Farsi very very little. It just means that "the people who spoke language A at one point split off from the same people who split off to speak language B". From that angle, that the same language family is spoken in New Zealand and Madagascar is roughly as wild as the fact that homo sapiens lives in both places.
What's really wild is that modern linguistics has managed to demonstrate that the Austronesian languages are related across those vast distances and time spans.
- Man, that DSP made the Falcon an insane piece of hardware for its time. Shame that it never found any real success.
- Browser performance tips from 2014 mean very little twelve years on. Not only have machines gotten faster and networks gotten faster, rendering engines gotten faster. And I'm doubtful it nested flexboxes would've been all that much of a problem in most cases even then.
The most important thing is to use the right tool for the job. If grid lets you express what you want in the most straightforward way, use it; if flexbox does - even if it needs nesting - then use it instead. Don't shoehorn one into a situation where the other makes more sense. And sometimes either will work for a particular situation and that's fine too; use whatever you find most ergonomic. They're both very good in their own way.
- A little more than just a multiplication instruction (the 68000, used in, say, the Sega Mega Drive, had one of those too). Have a look at https://www.copetti.org/writings/consoles/playstation/, and in particular, read about the GTE - it offered quite a bit of hardware support for 3D math.
Also, even though it didn't handle truly 3D transformations, the rasterizer was built for pumping out texture mapped, Gouraud shaded triangles at an impressive clip for the time. That's not nothing for 3D, compared to an unaccelerated frame buffer or the sprite/tile approach of consoles past.
- (Too late to edit but did not mean “isomorphic”, meant “orthogonal”. Wrong smart person word trying to look smart, how embarrassing, sigh.)
- You’re misremembering. SM64 was fully textured, outside of specific models.
Also flat shading (vs. say gouraud shading) is isomorphic to the question of texture mapping, and concerns how lighting is calculated across the surface of the polygon. A polygon can be flat shaded and textured, flat shaded and untextured, smoothly shaded and textured, or smoothly shaded and untextured.
- The README mentions that it uses both (new) fixed point as well as soft floating point.
Unless I'm mistaken, the PS1 just plain doesn't support perspective correction. All texture mapping is done in hardware using a very not-programmable GPU; there'd be no way to do perspective correction, decent frame rate or not, outside of software rendering the whole thing (which would be beyond intractable).
The common workaround for this was, as suggested, tessellation - smaller polygons are going to suffer less from affine textures. Of course that does up your poly count.
- It notes in the Known Issues section that "Tessellation is not good enough to fix all large polygons".
Maybe it just needs more tessellation or something else is going on, because you're right - even as someone who grew up on the PS1 and is accustomed to early 3D jank, it looks painfully janky.
- Last sentence of the first paragraph says it’s Snowboard Kids 2.
- That frontend seems to have things that aren't hosted on Wikimedia Commons, whereas I think OP's link is Wikimedia-exclusive and more reliable.
For example, Network (1976) - one of my favourite films - isn't listed on the Wikimedia page, but it's listed on the WikiFlix frontend. I was a little surprised to see that, since AFAIK it's still under copyright. Clicking through, it's trying to embed a copy from the Internet Archive, from which it was taken down because, yes, it's still under copyright.
- Managers everywhere love the idea of AI because it means they can replace expensive and inefficient human workers with cheap automation.
Among actual people (i.e. not managers) there seems to be a bit of a generation gap - my younger friends (Gen Z) are almost disturbingly enthusiastic about entrusting their every thought and action to ChatGPT; my older friends (young millennials and up) find it odious.
- Unreadable AI slop. If there's anything of technical interest in here, it's buried too deep underneath the parade of LLM clichés and self-aggrandizing marketing drivel.
- > Also the phonetic simplicity of Japanese is likely to have been caused by an Austronesian substrate related to that of the aborigine Taiwanese people.
That's being asserted with too much confidence, I think. While I was aware some kind of Austronesian connection has been suggested, as far as I know there's zero actual consensus among linguists on any kind of relationship between Japanese and any other language family. Like, there's theories relating Japanese to everything from Korean to Turkish to Greek floating around - but nothing to my knowledge that we should really be describing as "likely" at the point, even a connection with the grammatically extremely similar Korean.
Now that said, I don't know a lot about the Austronesian languages or this particular hypothesis. I did find an article about a possible Austronesian substratum ("Does Japanese have an Austronesian stratum?" by Ann Kumar), but it seemed mostly preoccupied with drawing that connection through similarities in vocabulary rather than phonology. Do you have pointers to scholarly sources on the subject?