How do you deal with bots?

NX means not executable, so some bytes are excutable, some are non excutable. so some are instructions for the processor and others are data. Sometimes those are mixed and the cpu pukes out a bunch and restarts interpretation. most of the time those are normal. keep it normal and go fast.

As an american with a degree and years of experience and even a PhD, it is hard to move jobs.

It isn't a maths paper, so the conventions are different.

It isn't since there is not much about what it is!

The first sentence of the main site is "D2: Declarative Diagramming - A modern language that turns text to diagrams", followed by multiple code snippets and the resulting diagrams.

I click the thingy and don't see that, I know D2 as the big language split for Dlang, I click around, I still can't tell what this is.

It's diagramming software? Like plantuml or mermaid? It says it right on the tin and with all the examples.

Oof, maybe don't. A lot of them are written directly for children, which they mostly work for, but only later bits have stuff mostly for adults and are vaguely worth analysing.

Don't what? I enjoy a lot of media written for children. Trollhunters / Tales of Arcadia, Miraculous Ladybug, Max Steel, My Little Pony (G4), Sonic Prime, etc. Though I tend to prefer media that respects intelligence rather than pure babyslop.

Max Steel in particular was so untargeted to adults that it's nearly lost media. I'm so glad for whoever managed to collect it and upload it to YouTube while it was still available.

Don't spend too much time on what was at the moment not meant for adults, like there is alot of other art to look at and interpret. It was more of a don't get crazy into it, my own Dad got super weird into interpreting things he thought he found in Doctor Who. It was both sad and weird. Just maybe don't dwell to much on things people didn't also give much thought to.

Not crazy into it, just generally appreciative of media with internally-consistent science or magic.

Doctor Who is definitely the last thing I would dub as "internally-consistent". It's a serial--and the duct taped seams show--sometimes glaringly so.

But, every now and then, the writing CLICKS and you get genuine emotional ART--generally as a monologue.

I will admit a fair bit of enjoyment comes from the TARDIS Technical Index: https://whoniverse.net/tardis

I think the existence of enough technical information for such an index to even be possible is what I mean by internal consistency. Not the absence of plot-holes or ret-cons.

A lot of shows simply aren't very technical.

Doctor Who is the opposite of Star Trek. It makes little attempt at internal consistency. It helps that time travel plays a large part in it. That said, it's been unwatchable for quite a while.

Disallowing smc is a significant perf/power win. For cpus that run a large variety of large code (e.g. a web browser or ux stack), being able to cache a large instruction footprint and fetch/decode it quickly is important. Having to have the icache snoop data writes and entangle the i-fetch with the store buffer machinery would be a huge penalty to pay for a niche use case. Unlike loads, which are a small fraction of instructions to disambiguate with stores, you'd have to disambiguate every single instruction.

JIT is important to Apple platforms, and they seem to manage to make it work well enough even with the need for explicit invalidation.

FWIW if you look at WebKit/JavaScriptCore, the trend has been towards less-frequent code modification, e.g. inline caches are mostly no longer repatched inline. Whole-function reoptimization is still worth the overhead of sys_icache_invalidate() + `ISB`'ing everyone involved, but at smaller granularities not so much.

I love you, keep it up dude. Exactly the kinda shit I would say if I didn't want to lose more fake internet points now.

So that is only true because we do it, there is a world where we optimize differently and that self modifying version works better, reread the synthesis kernel thesis(one, it is super easy, two they did this), we could have hardware that does this. Because we don't have hardware that does this we don't

L take. RAM is too slow for self-modifying code to be anywhere but F tier. This isn't 6502 land.

But it could be, there are bits about doing computation in RAM, self modifying code could work.

If DRAM gets the ability to modify itself (computations), it doesn't eliminate the cache layer between the CPU and DRAM. For the CPU to see updated DRAM values it has to bring in the DRAM to cache. Now, if that's a large amount of data, like 1MByte of computations, it's worth it, but for a couple of source/destination addresses in code, probably not. There's also the fact instruction and data caches are separate.

Now, if the RAM in the CPU cache gets computational ability as well, that all changes, but not sure really that would be better than SIMD/SEE/AVX stuff or expanding what can be done with the new tile registers Intel's rolling out.

Well it was a hot take.

Are you unaware that you can write code to RW memory, remap it to RX and then run it? That's how all JIT works these days.

(Or did you confuse cache flushing with TLB flushing? The remap does the latter, not the former.)

Yeah, that works okay, but really is a you shouldn't, with pipelining you lose all the predictive decoding. The Synthesis kernel did some cool ass shit with this, but failed in other architectures due to pipelining, which speeds up shit, but change the opcodes(with other instructions(ie selfmodyfing code)) and shit gets flushed.

> What did they actually do to kill it?

They did Wayland instead, that killed X11 since X11 windows and such can be spawned under Wayland. but wayland isn't x11 so people miss shit and wish it was there.

Well it is open source, so if enough people miss it, they are free to keep it going, isn't how it always gets talked about?

Except the reality never plays that way, unless we are talking about tiny projects.

Lets see for how long xlibre keeps going.

Ages ago Redhat people wanted to stop supporting X11 since it was old and harder to maintain with all the weird extensions and it being older C code. They wanted to move to Wayland and people claim that maybe in maintaining X11 Redhat also made some changes that made X11 worse. You can find all kinds of discussion of why Wayland is bad or why X11 is bad and Wayland is the one and only future. Now things are settled and Wayland won.

Firefox is the best of a bunch of bad options, but isn't above critique. It does suck when they do anticonsumer stuff and shove weird stuff like pocket in, but you can't leave which makes it similar to the democratic party where you can't really do anything, but they keep making really poor decisions.

The similarity goes deeper since they're funded by the very thing they claim to oppose.

Pocket was awesome. I am sad it’s gone and even though I found replacements I just don’t use them as much as pocket.

I've found Raindrop to be a better stand in, but I jumped ship from Pocket a long time ago.

Firefox have forks like Zen which allow you to have the best of both worlds.