Hacker Newsnew | past | comments | ask | show | jobs | submit | vanderZwan's commentslogin

It also means people with color vision deficiencies like me don't struggle distinguishing all the hues.

> Perhaps none of us have in that Forth doesn't have much of a large dataset to train from?

Well, being terse as heck is the point of Forth so of course the dataset isn't large /j.

More seriously, I think the bigger issue is that Forth isn't exactly uniform. It is so moldable that everyone has their own style


phreda4 has been doing cool stuff with ColorForth-likes for ages and for some reason barely gets any attention for it. Always brings a smile to my face to see it submitted here

Sounds like I should try this together with ametameric, which I've been using since I have protanomaly

[0] https://ctx.graphics/terminal/ametameric/


I'm not sure if our convention for hexadecimal notation is old enough to have been a consideration.

EDIT: it would need to predate the 6-bit teletype codes that preceded ASCII.


I don't really follow Racket, but I recall that few years ago one apparently fairly significant contributor within their community wrote a blog post about Racket having a Missing Stair problem involving another even more significant (possibly foundational) contributor.

I'm a complete outsider, cannot find that blog post any more, and also just not invested in the language at all, so I'm hesitant draw conclusions about the validity of any of the accusations that were thrown back and forth at the time, but it seems pretty obvious to me that it's inevitable that the community will end up being split after an event like that.

https://en.wikipedia.org/wiki/Missing_stair



if it's Felleisen, then i'm surprised. i've met him on a conference for a couple of days about a decade ago, and my memory is of a nononsense guy with whom our vision of programming resonated a lot.

i was coming from the CL side of the isle, i hadn't known his work prior to that.


Haha, right? I remember meeting up with some friends after school back in 1996 at the home of the one kid whose dad was a surgeon, and him showing off their Pentium Pro with a mindboggling 32 MiB of RAM! And then we tried playing SimIsle! Which actually managed to run on their computer! Very, very slowly! Unbelievable! :)


> Yeah, I'm sure the reason stated by the customer support is the real one, and not the lack of profitability from that tool among a shift of focus towards AI[0] as reported everywhere.

Yeah, although "finished" software is antithetical to this always have new features to push onto your customers subscription model, so it's not entirely unrelated.

Having said that I still find it strange. I can imagine it might not be able to ride on the AI bubble, and perhaps animators are especially vocal about not wanting AI in their tools. But even so, why would that make Adobe Animate unprofitable? They do have a subscription model, and customers, so people are paying for this product.

Compared to other digital art, the data for vector animation takes relatively little space to store. It also requires much less resources to render than other forms of video, and rasterized video output should compress really well compared to alternatives, especially with modern codecs that are not only optimized for regular film. So surely it shouldn't be that expensive to maintain for them compared to all their other projects.


> But even so, why would that make Adobe Animate unprofitable?

Sorry, I wasn't precise with my wording. What I meant to say was "less profitable than the perceived AI opportunities they could do with the same engineers".


Ah, ok. Even then switching Animate into "maintenance mode" should be doable on a shoestring budget methinks but whatever, the more Adobe hurts itself the better tbh.


A mere 69, but I wonder if I would do better in my native language. Also, once I discovered it accepts extinct animals I went all in on dinos and other extinct animals, that's like half of my score.


I too feel like Emscripten is doing way more than it should for the vast majority of actual use-cases for WASM on the web out there. It's too heavy to install, too much of a hassle to get running, produces way bigger output than it should if the main target is a website, and adds needless friction by being largely oblivious to how the web works from the C++ side of things. The shared memory architecture + batched calls also aligns with hunches I had about unlocking fast WASM for web dev. So this sounds extremely interesting!

Coi looks pretty nice! But honestly I think WebCC might actually be the thing I have been waiting for to unlock WASM on the web. Because if I understand correctly, it would let me write C++ code that compiles to tiny WASM modules that actually integrates with generic JS code very efficiently. Which would make it much easier to add to existing projects where there are some big bottlenecks in the JS code.

Looking forward to giving it a spin!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: