uDontKnowMe

You can get a pretty long way but there are still things that need to be improved over time. For example Clojure still 7 years after the java 8 release doesn't have great integration with java 8 functional interfaces, which is a pretty big detriment to java interop. I saw this patch which seems to have been submitted by a community member https://clojure.atlassian.net/browse/CLJ-2637 (not sure if the author is a core contributor or what), but even after month no comment from Rich or anyone else on the team to indicate if this is a good idea, if they'd let it in or what.

I would agree here that the combination of being "closed to collaboration", the slow pace of development lately, and really infrequent communication from the sole owner/leader/BDFL does send a weird vibe and raises some concern regarding what direction the language is going to be going in in the future.

That's great to hear! I get the same feeling towards the Clojure community as well, some of the friendliest, smartest and most helpful people hanging out at the Clojure watering holes (in comparison to other languages I've worked with). I also am constantly in awe of the output of the Clojure world. There are like 3 or 4 great podcasts going, so many cool projects being worked on, especially for a community which seems to be sadly so small.

Reddit started out as a text-based discussion forum for use on desktop and has slowly morphed into endless-scroll-of-images/gifs/streams on mobile.

What does the Apache Foundation do/provide/give these projects if no funding is involved? Is it just like a governance thing like "if this project falls into an abandoned state, we'll oversee the process of transferring ownership to any interested and credible parties interested in taking over"?

Python's cool, but "right tool for the job" and all that. Just dive in with the Java or Scala api's and you'll have a better time :-).

Totally agreed! Flink is way underrated.

No, I think they're looking for people who are intrinsically motivated by the drive to do a professional job applying their craft, rather than to use a project as an opportunity to experiment with technology that they want to learn for their own curiosity or career trajectory.

In the same way, when you hire a contractor build you a garage, you look for someone who will use their experience to build a good garage with the best materials and techniques keeping in mind the priorities of the owner, like maintainance, cost, appearance, resalability, etc. You don't want someone showing up who just views your garage primarily as an opportunity to learn about this new construction material they've heard about that doesn't help you.

Thanks Adam, I love the podcast!

I disagree that UX can't play a role in this aspect of Reddit. Old reddit was a lot more insightful and had higher quality content and discussions, because the UX was geared towards that. Now the UX is heavily geared towards mindless scrolling of a feed on your phone, and so that is the kind of content you get.

Just look at Hacker News, it is upvote/downvote-based, but it has way better quality discussion than anywhere on (new) Reddit. Maybe comparable to some of the best subs 10 years ago, and that's because Hacker News has the same UI reddit had 10 years ago.

>Using it only on "bad guys" is a recipe for the government punishing people that disagrees with them.

Indeed that's exactly how it is being used if it's true that they throw the book at public figures for making political statements like Wesley Snipes.

I appreciate the ability to select and move already drawn components, I believe this was missing in the original version which kept me from using it. Thanks team!

Well it's easy enough to think of a situation where you would use a date as a primary key, for example time series data.

There are actually a fair number if you go looking, in my opinion Lemmy seems to be the best alternative these days and seems to get at least a bit of traffic.

This was some comfort years ago, but these days, the vast majority of reddit users are mobile and new-reddit, whose UX's favor more meme/video mindless scrolling and throwaway comments. So while the old reddit experience is there in looks it feels more hollow nowadays. You go into a common interest subreddit and where 8 years ago you might have found interesting discussions now it's all memes, inspiration photos, etc.

There is a subreddit about this: r/RedditAlternatives. Trouble is, most of them end up being dominated by the alt-right/hate mobs.

Interesting that you want something that is specifically not just a reddit knock off. I actually think that a Reddit knock off focussed on discussion (say, like hacker news, but with subreddits) would do well.

I don't literally read aloud the document but I do end up going through and paraphrasing what each section says. I don't think people are generally embarrassed they haven't read up in advance, they'll show up like "okay so what is this all about?".

I do include 'Summary' paragraphs at the top that provide a TL;DR for an entire 1-ish page doc. I think people will usually open the doc for a few seconds maybe and then brush it off because the general team culture is that all important information will be passed verbally anyways so no point reading now.

Actually I guess I would like to encourage the entire team to do a bit more of this practice of writing things down. For instance, tickets are usually just ~3 word titles with no context or specifics. It's only once the team meets and verbally describes what the tickets mean, that the work can actually be done. I've noticed this sort of culture at multiple companies now actually.

What does one do when they live by this philosophy of documenting everything and making sure knowledge is captured, but your team mates just refuse to volley the ball back? I find myself documenting how the software works, writing up proposals with beautiful diagrams etc, but my teammates won't take the simple step to even read the dang thing without scheduling a meeting with me to spoon feed / read it aloud to them.

Would have to disagree here. Just raising the bar higher for publishing at all doesn't increase quality of libraries available. Consider how open source in general really became much more the norm after Github made it trivially easy to publish and collaborate on code.

As in Scala:

    // define a type alias
    type UserId = Long

    // can be used as a regular type
    val userId: UserId = 123L
    val userIds: List[UserId] = List(1L, 2L, 3L)

Or maybe CockroachDB?

What would you use instead of Cassandra for multi-DC replication?

IMO it would also be really nice to have non-string keys in objects, like:

{ [1, 2]: "a", [3, 4]: "b" }

I don't know Clojure or PHP completely fluently, so sorry if it's a stupid question, but why did you want to create a new language inspired by Clojure rather than a dialect of Clojure itself for PHP (in the same way as there is ClojureScript for JS and Clojure.NET for .NET)?

Yep this is a huge cultural problem with the Scala community. On paper and in marketing material, Scala is flexible enough to empower you to slip into mutable/OOP style or more FP style. But in practice the pure FP enthusiasts are the ones who totally dominate the ecosystem (aside from Haoyi Li). You simply cannot just ignore the Haskell Larpers/Wannabe's and get on with it, because they infect all the community watering holes like Reddit, Gitter and Discourse. Every time one talks about using non-pure-FP features of the language, they have to go through the same tired patronizing lectures about how "yes I know this is not 'safe'" and "yes I know what I'm doing" and "I'm very sorry that I am not as smart as you smart FP people" before you can actually talk about what you want to talk about.

Couldn't they expand outside of the anglosphere? Basically 99% of reddit is English, unlike Facebook etc.

I follow Clojure quite closely and am a huge booster of it, I even donate to a few projects, but I do think that the attitude of the community seems a bit too dismissive of questions about its adoption in the face of what seem to be pretty clear trends. A quick look on any job search site will show you that there are more positions asking for Elixir, and about 20x as many postings mentioning Scala. Of the positions I find on LinkedIn, even maybe half of the positions mentioning Clojure are mentioning it generally as in "experience with FP languages like Haskell/Elm/Clojure/Scala is a plus" rather than directly seeking Clojure devs. It's also lost about 80% of its search traffic in the last 3 years according to Google Trends (https://trends.google.com/trends/explore?date=all&q=%2Fm%2F0...).

It looks like despite how awesome Clojure is, there is something keeping it from achieving growth in adoption and the community should look at how to address that rather than look the other way.

I have worked in multiple Scala shops and contributed at the highest levels to the Scala ecosystem and my experiences confirm that this rotten attitude is very real and increasingly the norm, as everyone but the fanatical FP-ers have long-since moved on to other more professional/productive circles.

With the exception of shops using Scala exclusively for Spark, someone entering the ecosystem can expect to be constantly talked down to if you dare to use something deemed by the FP hivemind to be evil (so, anything other than pure, immutable, FP-style with all side effects controlled, no exceptions or nulls, no inheritance (only typeclasses), etc). They'll be derided and skoffed at constantly for being "just a java++ programmer".

Meanwhile, for all their smugness, the FP community has achieved nothing at all that has reached beyond to the world outside of Scala. The projects successful in bringing in developers to Scala have been decidedly in the disparaged lightly-FP/"Java++" style: Spark, Kafka, LinkerD (1.X -- they rewrote 2.X in Go/Rust), Flink, Akka, PlayFramework, Twitter's stack, Prisma, etc. Shockingly, the predominant view among these delusional pure-FP-obsessives, which usually goes unchallenged, is that the creators of Spark don't know anything about Scala or are bad engineers!

Scala 3 is a joke and will do the exact opposite of the stated goals from years back. It was supposed to streamline and simplify the language, remove gotchas, add a few high-impact simple features like Union types and trait parameters. Now it's a grown into a monstrosity of complicated features that your average dev will never use. Rather than streamline and simplify Scala 2's issues with having dozens of ways to do the same thing, it introduces multiple new dimensions by which people can do things in multiple ways (legacy implicit system vs new "given" syntax; braces syntax vs indentation-based).

Control structures helpful for imperative programmers are being removed (you cannot early return from a for loop without a huge hassle), `do-while` is removed, etc. These breakages were not pushed back against because the only people still around are FP'ers who don't want people using loops in the first place.

New type-system features are being added without even knowing if there's a possible use-case. The whole thing is a mess.

I'm continually impressed by the stuff that comes out of the Clojure community. They really seem to punch above their weight in terms of useful output, novel ideas, interesting projects/products. Much more so than say Scala or Kotlin which enjoy a lot more industry adoption.

Scala doesn't compile to WebAssembly