HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
darwin
plastic
JavaScript2015–2017
darwin / plastic

plastic

An experimental structural editor for ClojureScript

Developer Tools
Explore on GitHubRead Hacker News discussions
2Distinct people
7Mentions
0Explicit recommenders
150GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

An experimental structural editor for ClojureScript

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month7 dated mentions

Observed mentions: 2015-07-15 23:32:43 UTC to 2017-01-05 16:00:50 UTC.

0122015-07-01 00:00:00 UTC to 2015-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 20152015-08-01 00:00:00 UTC to 2015-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2015-09-01 00:00:00 UTC to 2015-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-01 00:00:00 UTC to 2015-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-11-01 00:00:00 UTC to 2015-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-12-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-01-01 00:00:00 UTC to 2016-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-01 00:00:00 UTC to 2016-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-03-01 00:00:00 UTC to 2016-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-01 00:00:00 UTC to 2016-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 20162016-05-01 00:00:00 UTC to 2016-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-01 00:00:00 UTC to 2016-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-07-01 00:00:00 UTC to 2016-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-01 00:00:00 UTC to 2016-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-09-01 00:00:00 UTC to 2016-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-10-01 00:00:00 UTC to 2016-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-11-01 00:00:00 UTC to 2016-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-12-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-01 00:00:00 UTC to 2017-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 2017

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 20152015-07-01 00:00:00 UTC2015-08-01 00:00:00 UTC101
Aug 20152015-08-01 00:00:00 UTC2015-09-01 00:00:00 UTC202
Sep 20152015-09-01 00:00:00 UTC2015-10-01 00:00:00 UTC000
Oct 20152015-10-01 00:00:00 UTC2015-11-01 00:00:00 UTC101
Nov 20152015-11-01 00:00:00 UTC2015-12-01 00:00:00 UTC101
Dec 20152015-12-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
Jan 20162016-01-01 00:00:00 UTC2016-02-01 00:00:00 UTC000
Feb 20162016-02-01 00:00:00 UTC2016-03-01 00:00:00 UTC000
Mar 20162016-03-01 00:00:00 UTC2016-04-01 00:00:00 UTC000
Apr 20162016-04-01 00:00:00 UTC2016-05-01 00:00:00 UTC000
May 20162016-05-01 00:00:00 UTC2016-06-01 00:00:00 UTC000
Jun 20162016-06-01 00:00:00 UTC2016-07-01 00:00:00 UTC000
Jul 20162016-07-01 00:00:00 UTC2016-08-01 00:00:00 UTC000
Aug 20162016-08-01 00:00:00 UTC2016-09-01 00:00:00 UTC000
Sep 20162016-09-01 00:00:00 UTC2016-10-01 00:00:00 UTC000
Oct 20162016-10-01 00:00:00 UTC2016-11-01 00:00:00 UTC000
Nov 20162016-11-01 00:00:00 UTC2016-12-01 00:00:00 UTC000
Dec 20162016-12-01 00:00:00 UTC2017-01-01 00:00:00 UTC000
Jan 20172017-01-01 00:00:00 UTC2017-02-01 00:00:00 UTC101

What Hacker News says

7 sources
dr_win·Jan 5, 2017
Selling macOS apps at https://www.binaryage.com. TotalFinder.app sales is what allowed me to work on my own projects full time. This is what I personally define as a success. I own 100% of my time and stuff I create. Since introduction of macOS system integrity protection sales have been poor. But luckily I made enough in previous years so I have pretty long runway to build something new. If you are interested how it got started you might want to read my blog posts from 2009 - 2011: https://blog.binaryage.com Have been investing heavily into Clojure(Script) tools and libraries over last 2 years: https://github.com/binaryage/dirac https://github.com/binaryage/cljs-devtools https://github.com/binaryage/chromex https://github.com/binaryage/cljs-oops https://github.com/binaryage/env-config https://github.com/darwin/plastic
In Ask HN: Successful one-person online businesses?
dr_win·Dec 3, 2015
Good points. I started with ClojureScript earlier this year and I agree with your article. But for me ClojureScript is still much better option than staying in JavaScript land. Performance will be solved over time with faster machines (I've purchased high-end iMac recently, so I don't feel such pain :-). Workflows for incremental compilation like Figwheel also help a lot. And I think there is a great promise that tooling will evolve quickly. I'm the author of cljs-devtools. I think for development it is perfectly fine to use Chrome Canary. Also I would recommend you to check out this article: https://github.com/binaryage/cljs-devtools/wiki/Figwheel-REP.... My public projects so far: https://github.com/binaryage/cljs-devtools https://github.com/binaryage/chromex https://github.com/darwin/plastic https://github.com/darwin/faceboard https://
Read the rest
github.com/binaryage/pure-frame
In What Holds Me Back from ClojureScript
dr_win·Oct 16, 2015
I'm a seasoned Javascript dev. I started using ClojureScript in January 2015 (switched from CoffeeScript). I have almost no experience with Java and JVM. Also I have not done anything in Clojure yet and nothing meaningful in Node.js. Did one SPA to learn ClojureScript and explore the landscape of ClojureScript libraries and web frameworks, Om in particular: https://github.com/darwin/faceboard I love the language. Its minimalism especially. I can use it everywhere where Javascript can be considered. For me this is another JavaScript language upgrade - much more significant than going from plain Javascript to CoffeeScript. I feel sorry that I have not discovered power of lisp earlier in my career. The community around ClojureScript is still pretty small, but it is a fruitful ground for new ideas. Over last few months I've learned a lot. The
Read the rest
value of immutability, many functional patterns, thinking in pure functions (that includes designing idempotent UI components thanks to React.js). The language is easy, but exploring and practicing those thinking patterns takes time. I feel that I'm still pretty much at the beginning, but I think it was worth it for me. If I'm going to use this language for next few years I want to invest into improving tooling around it. Beside cljs-devtools also started working on structural code editor in ClojureScript, it is an experiment right now, but in the long term it has an ambition to compete with LightTable: https://github.com/darwin/plastic The switch was pretty easy for me. I don't work in a team and I tend to work on experimental projects, so I don't have to persuade coworkers to try something new and I can take risks. And btw. I hack on Objective-C stuff for living. Made TotalFinder and TotalTerminal. And to finally answer your question: > How sane would it be to go full nodejs/CLJS instead of nodejs/JS? This is the default route for me now. And I hope it is sane. I see CLJS as an upgraded Javascript. Interoperability is not an issue. It is no problem to use existing JS libraries from ClojureScript and/or expose ClojureScript functions back to JavaScript. The issue could be that you don't get many contributions from JS devs in case of open-source. Also there could be performance implications. But you can always drop back to Javascript for performance critical code if needed. It would be just more work and dirty experience :) Also tooling and community support can be a consideration. If you are experienced in Javascript, in case of troubles you can definitely help yourself. But for beginners or intermediate people I can imagine looking for help could be a struggle. Javascript community is much bigger and had time to evolve tools or there is good incentive for other people to build good tools for this large community. With ClojureScript we have to wait few more years or better help make it happen.
In Chrome DevTools extension for ClojureScript

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.