Looks very polished, congrats! I've been slowly working my way towards supporting C4 in Vexlio, since the interactive+layered view is nearly an exact fit for the interactivity model (https://vexlio.com/solutions/interactive-process-documentati... has a screencap).
One reason it's been lower on my list is that I haven't been able to get a handle on how much C4 is actually used in practice. Not necessarily the model itself, but the visual representation. Did you create this based on your own experience of using C4? I'd be curious for any anecdata you may have come across too.
Well, one notable difference between your examples of eliminated pathogens is that there is a food chain built on top of mosquitos. There are plenty of animals that eat both mosquito larvae (ex: tadpoles, some fish) and adults (ex: bats, dragonflies). I don't believe there is a similar food chain built on top of viruses.
I agree that many of the risks are hypothetical, but I disagree that we can simply dismiss them. Taking a decent amount of time to understand cause and effect on ecosystems seems like a perfectly prudent thing to me.
We wouldn't have to destroy all mosquitos, though. Only a few species that are carriers of human pathogens. Once they are gone, other, benign mosquitos will occupy their spot, and will be eaten by the same animals as before.
Such a vague blanket statement sounds like an article of faith and not an actual informed opinion about the specific species of mosquitos, the animals that eat them, and the fungibility of their food sources. Correct me if I'm wrong though.
The mosquito species in question is native to northern Africa, and is an invasive species pretty much everywhere else in the world, having only arrived 300-400 years ago.
While they don't age like living organisms, their outer protein coating wears away due to temperature and UV light, so like you said they sort of "degrade".
Poor fella... I tuned in at an awkward time apparently, right after the work in progress was painted over with an ugly brown:
> Catastrophe. The glaze pass with medium 0.35 over everywhere() at coverage 0.8 with a filbert 26 at pressure 0.44 laid an enormous broken "brick/cobblestone" texture over the entire painting. The medium made it too fluid and the brush's dry-brush pattern created a heavy reptilian texture, obliterating the picture. I need to undo this....
(project creator here) there was a session with space bunny where they kept mixing up x and y in a tool call and over and over they ended up with mysterious diagonal streak across the whole canvas which then they'd paint again then call the tool wrong again and so on, very sad
Pretty sure that earlier work did reach the light of day in the form of a set of GL extensions.
Also, his other work on polar stroking influenced one of the gpu-accelerated path renderers in Skia (graphics library powering Chrome and Android, among other things). See e.g. https://source.chromium.org/chromium/chromium/src/+/main:thi... where they refer to the same idea as radial stepping, or radial edges. Or if not the exact same idea, it's at least a similar idea of stepping in angle-space rather than purely in Bezier t-space or arc-length parameterized space.
There's a big gap between WASM has issues/limitations, and WASM "might as well not exist." NaCL was also Chrome-only IIRC, whereas WASM is a successful web standard (no small feat).
NaCL was further along in every meaningful dimension (the ability to run native software at native speeds) after a year or two of development, than WASM is today after a decade (and I think this will be true a decade from now).
So the upside of WASM according to you, is that it got greenlit by the standards committee chaired by companies whose business model would've been hurt the most by a competent in-browser sandbox.
For example, the Epic-Apple Fortnite battle couldn't even have happened. Epic would've shipped it on NaCL and users would've been just as happy, and Apple (or Google) would've had no way of enforcing their sandox.
Whew, thankfully we've been saved from that terrible fate of getting to publish and enjoy software without gatekeepers and appstores.
At least I hope you have something to gain from your opinion, as the rest of us certainly lost out.
It seems like you know quite a bit of the history here. Were you involved in some way? If so, I'm curious to know why you think NaCL did not achieve broad adoption? And what's stopping the world from catching up to your line of thinking and adopting a NaCL successor?
Portability isn't worth as much as it was advertised. There are a grand total of 2 relevant CPU architectures for consumers, ARM64 and x86_64. Shipping 2 binaries is just running the compiler twice.
On the client side, there's just a verifier, and then the runtime basically consists of branching to the first instruction and having at it. Near-native performance and instant startup, you can't do better than that.
PNaCL was proto-WebAssembly and suffering from the same issues. They actually shipped LLVM bytecode, and you had to compile the executable locally with the whole toolchain, leading to quite bad startup performance and a lot of baggage.
Turns out there's no such thing as portable VM assembly. You still have to ship a full compiler (well, JIT) and compile the WASM IR.
Browser vendors have spent uncountable amount of engineering resources on making yet another compiler (actually multiple, since afaik Chrome uses a tiered JIT for WASM), that's neither as good as the big boys, and neither as fast as just running the dang binary.
Linux distros are shipped as binaries yet you can still build them from source, and are certainly not controlled by one company, I don't see why that would be the case here.
Would you require every website to come with architecture-independent source code? What happens if it doesn't match the compiled binary? Or would the browser compile it every time?
The original premise of the argument was about WASM bytecode vs native assembly - bytecode is no more open or closer to the source code than x86 asm. Your questions are completely orthogonal to the argument, so please bring up relevant points.
> Just because you can do something well doesn't mean it's worth doing.
I'm not sure if there's more context to this quote, but on the surface: what a dismal take! Letting some measure of worth dictate what you do feels pretty limiting to me. I understand that he's not saying "make sure you attach worth to everything you do," but there's an implicit judgement process in what he's suggesting.
If you do something well, and you like doing that something, maybe you should enjoy doing it just for the sake of doing it.
I read it the opposite though; that it's the act of doing, not the (perfect) result, the thing that is valuable. e.g. it's better to paint a canvas badly because it's fun, than to have an AI generate a perfect image. It's not the image that is "well" that is worth it, it's you having fun while doing it that it's worth it.
I feel like you're conflating "having worth" (value) and "being worth doing" (it's good to do it) in here?
I know a few people who refuse to get jobs even though they are suffering financially because they can't find something they think is "worth" doing with their skill set.
I tried to tell them that having a job would mean they get to meet new people, they get to escape their financial despair, and that it would add structure and organization to their disheveled and disorganized lives. I explained that work itself has value for the worker outside of the simple return of the paycheck, the activity of being engaged completing a task having direct psychological impact on the task completer.
Both of their responses, taken months apart, boiled down to that if a day of work didn't make them so wealthy that they never had to work again it wasn't worth it for them.
I think your attempt at a counterpoint accidentally reinforced the main point: there are more criteria beyond simply being able to do something well that determine whether it's a good idea in the first place. I can make lead balloons faster and cheaper than anyone else but that's not enough to make it worth spending my one and only life making lead balloons.
Yes, and I even think this applies to generally valuable skills.
I can be really good at organizing projects, but I shouldn’t channel that into spending hours creating the perfect Jira template with 18 integrations just because I can do it well because that’s a lot of energy spent on something nobody may ever use.
Meanwhile that skill may very well be extremely valuable elsewhere.
True! And the point isn't that you shouldn't base whether you do something on how much economic value it produces.
I think the judgment is more that if you're doing something to produce some kind of outcome (e.g. work), don't get stuck on things that don't impact that outcome.
The point isn't that you shouldn't do things well. It's that just because AI makes it effortless to ship some random new thing nobody asked for, that doesn't mean you should ship it.
I think that calculus changes completely when you do things for fun, where the only outcome you're trying to produce is doing more of the activity.
If you're doing something for fun, the doing is itself the reward.
I don't think he's talking about personal fulfilment. His take is more simple. He's saying don't do the following: "I created a piece of software, and it works pretty good, but I have no customers. Should I work on coding to get it to work 5% better, or try to do some marketing? Well, I'm really, really great at coding, so let me do more of that."
One reason it's been lower on my list is that I haven't been able to get a handle on how much C4 is actually used in practice. Not necessarily the model itself, but the visual representation. Did you create this based on your own experience of using C4? I'd be curious for any anecdata you may have come across too.
reply