aayyyyyyy i got a shout-out in alex miller's #clojure conj talk, design in practice in practice. that feels incredible.
| Keybase | https://keybase.io/noahtheduke |
| Cohost | https://cohost.org/noahtheduke |
| https://twitter.com/noahtheduke |
Noah Bogies
- 59 Followers
- 177 Following
- 53 Posts
Clojure programmer, netrunner player and http://jinteki.net lead dev, avatar by ICELEVEL, he/him
@borkdude haha that's very good.
@plexus @nikitonsky tbh, i don't need a fork. i think the core team does a great job of working on big ticket items. i'd just like them to move a little quicker for the rest of the stuff. be more open to external contributions for "low hanging fruit" and to stop treating it like rich's personal/side project (the core of "open source is not about you"). it's a serious language relied on by many companies with real money. i think it should be treated as such.
@swannodette i'm sorry, i don't know what that list means or how to interpret it
@swannodette hard to say. i benefit from transducers because of the underlying changes, but i have yet to write one for any specific purpose and if they were in a library instead, i wouldn't use it. i've never deliberately used a future and don't see any reason why i would. i'm never going to use the new stateful stream seq functions. should those be excluded from the language?
the beauty of any general purpose language is that you can choose which parts to use to accomplish your goal.
@swannodette @nikitonsky Ah sure.
isn't that true of every feature? how many folks will use the discard reader? or core.asyc.flow? or transducers? if a vocal subset of the user-base is saying "this feature will directly benefit our experience with and usage of the language" and they're willing to implement and maintain it, why the reticence?
@bbatsov @nikitonsky @jack @pmonks i don't necessarily need new features, but i'd love to see existing bugs fixed and implementations refined. when something like "improve the error message of deref on non-deref objects" (CLJ-1162) has been stagnant for 12 years because a library relied on implementation-defined behavior, that points to an unhealthy development system.
@swannodette @nikitonsky no one's painting it as an easy feature. folks are saying that if there's communal desire for a specific feature (calling features you don't like "pet features" feels rude) and willingness to supply the effort to implement and support those features, it still feels bad to be gated by the whims of one or two people.
@amy i love são paulo, beautiful city.
YouTube
@tati welcome to the club. it's so so good