3 ms·
Carbon API is so old that this pretty much isn't issue. You have to google explicitely for "Carbon API" for it to show up. Whether even now, "carbon programmi
by KptMarchewa 4y ago
Carbon API is so old that this pretty much isn't issue.
You have to google explicitely for "Carbon API" for it to show up.
Whether even now, "carbon programming" or "carbon code" give results for Carbon language - and some other non-c++ libs named Carbon.
Even "carbon" by itself gives me some Carbon language links.
- tgv 4y agoI suppose you’re using google as a search engine?
- scotty79 4y agoDon't forget they named language go, while language named Go! already existed. They just don't care. https://en.m.wikipedia.org/wiki/Go!_(programming_language) https://en.m.wikipedia.org/wiki/Go!_(programming_language)
- Optimal_Persona 4y agoAt least they didn't name it after a very popular existing language and then tack "script" on the end...
- shagie 4y agoIn defense of the name... it's how an applet could interact with the page surrounding it (and vice versa) https://docs.oracle.com/javase/tutorial/deployment/applet/invokingJavaScriptFromApplet.html https://docs.oracle.com/javase/tutorial/deployment/applet/in... https://docs.oracle.com/javase/tutorial/deployment/applet/invokingAppletMethodsFromJavaScript.html https://docs.oracle.com/javase/tutorial/deployment/applet/in...
- hn_throwaway_99 4y agoAt first I wanted to disagree (I remember the whole "Cocoa or Carbon" dilemma for Mac developers in the early 00s), but then I just realized that I'm old. Carbon (the Mac API) only existed to enable developers to more easily port Mac 8/9 applications to OS X, which was over 20 years ago. The Carbon API was officially discontinued in 2019 with Catalina. The Carbon API served its purpose, it's now officially "dead", so I agree - I don't see much of an issue with giving a new technology the same name.