Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
seancorfield
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
seancorfield
7y ago
Spec has numerous uses. We use it heavily in production for data validation/conformance: https://corfield.org/blog/2019/09/13/using-spec/
62.
▲
by
seancorfield
7y ago
First off, the history is NOT purged. It's just not searchable beyond 10,000 messages. Pay for a month (if you can afford it!) and you'll see the entire history available. Further, the cost is $6.67/month -- substantially les
63.
▲
by
seancorfield
7y ago
I'm an admin on the Clojurians Slack workspace where we have about 15,000 members, of whom about 1,400 or so are considered "active" for Slack's purpose -- which is still an unaffordable amount for an open source communi
64.
▲
by
seancorfield
12y ago
This comment, whilst perhaps accurate in and of itself, is missing the point of his article I think... He's saying that a small, simple, imperative core is easy to understand (and the rest of the language is built on that), whereas mor
65.
▲
by
seancorfield
14y ago
There are already web and mobile versions of apps like Photoshop etc. Adobe themselves created an online image manipulation program and there are several really good iPad apps too. So, yes, it's likely.
66.
▲
by
seancorfield
14y ago
This made me go check our Clojure code base at work: including comments, docstrings and whitespace, our functions average about 11.5 lines each (and I know we could clean up some of our earlier code to reduce that average). So, yeah, I'll c
67.
▲
by
seancorfield
15y ago
Others have pointed out that you need to understand sequences and other basic Clojure stuff first but perhaps my "real world Clojure" blog post series will give you a quick tour of the sort of things you're looking for? http://corfield.org
68.
▲
by
seancorfield
15y ago
Glad you liked Chas's interview style! Length is a tricky one. I rarely get time to listen to a whole hour in one go so I actually prefer 20-30 minute episodes. Looks like the average length of all the podcasts I have in iTunes (427 episode
69.
▲
by
seancorfield
15y ago
"Am I wasting my time trying to get software just right?" Don't we all want to "get software just right"? "Is it worth my time to learn Clojure or Haskell, when I don't even know what I'll use it for?" Reasonable question. Pick a project, c
70.
▲
by
seancorfield
15y ago
I'm curious why you feel you can't create spike solutions in Clojure?
71.
▲
by
seancorfield
15y ago
I just went back and looked at the code overhead of using actors over what it might look like with 2.9's parallel collections and the difference would be about 25-30 lines so I don't think that counts as a potentially "large code reduction"
72.
▲
by
seancorfield
15y ago
Ah, I see. No, we have another language in the mix which is not relevant to this discussion. The "One True Language" comment was a bit tongue in cheek since I doubt we'd really end up with just a single language across all tiers. I had init
73.
▲
by
seancorfield
15y ago
Thanx for taking the time to give some background. I posted the anecdote on the Clojure list just by way of sharing some of the progress we were making with Clojure. If someone had actually asked me, I'd have probably said "No, don't post t
74.
▲
by
seancorfield
15y ago
Not sure what you mean - if code is statically type safe, it will also be dynamically type safe. Moving from Scala to Clojure is not really affected by the type system.
75.
▲
by
seancorfield
15y ago
No, we didn't hit the OoM regularly until we had more traffic as we moved more sites onto the new system and it wasn't clear that there was an admitted problem with the Scala actors at first either. These days folks seem much more comfortab
76.
▲
by
seancorfield
15y ago
I think you're striving for absolutes where only relatives exist. You're right that I said 3-4x in one place and 2-3x in another. Sorry. It's a gut feeling. Is it 2x, 3x, 4x? One of those. Any of those depending on the code. Somewhere in th
77.
▲
by
seancorfield
15y ago
Your math is a bit off: Scala can be _up to_ 10x more concise than Java. This specific Clojure code was either 3x or 4x more concise than this specific piece of Scala code (based on char count or line count). My experience over the last few
78.
▲
by
seancorfield
15y ago
15 hours = 2 x 7.5 hours - 2 days? (seems like basic math to me :) Akka is _not_ a language - I'm not sure where you got that impression? (please explain so I can respond to it - no judgement). Based on the Akka documentation (pre-1.0), it
79.
▲
by
seancorfield
15y ago
"widely published performance and memory problems with scala actors" - remember the code dates back to November 2009 when that was not common knowledge...
80.
▲
by
seancorfield
15y ago
I'd have to ask how much Scala and how much Clojure you know to challenge my statement about the equivalence of the code and the reduction in size? (no offence intended - a genuine question) I like Scala. I'd hoped it would become my compan
81.
▲
by
seancorfield
15y ago
It's Clojure, not "closure". Yes, switching to Akka would almost certainly have solved the OoM problems. That's the whole point. We had to switch from the original code. The choices were: move to Akka, wait for 2.10 (when Akka replaces the
82.
▲
by
seancorfield
15y ago
The original Scala code was written back in November 2009. Akka wasn't really the "accepted production solution" back then. There's no question that it is _today_. We used actors to create a pool of workers in order to run some slow process