Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
grantjpowell
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
by
grantjpowell
6y ago
I really like Fred (ferd) Hebert's take on erlang and concurrency and distribution problems (Earlier in the book he points out how concurrency and distribution are a similar type of problem). https://learnyousomeerlang.com&#
32.
▲
by
grantjpowell
6y ago
> They actually said that to me: it makes the code messy so they don't want to do it. I'm going to give one possible interpretation (my own) of the sentiment I believe the engineers were trying to get across with the statement
33.
▲
by
grantjpowell
6y ago
I've never really explored the native grep functionality, so its possible I'm missing something. The two features I really like about fzf are 1.) the preview window (visible here https://github.com/junegunn/fz
34.
▲
by
grantjpowell
6y ago
My observation is that I tend to like languages that I don't need powerful tools to work with. That seems to be a mark of a well designed language to me
35.
▲
by
grantjpowell
6y ago
Yeah, this exact flow was a pain for me in switching from vscode to vim full time. My flow now is to search for a bunch of instances using the fzf plugin ( https://github.com/junegunn/fzf.vim ) and open them into the qui
36.
▲
by
grantjpowell
6y ago
On the topic of language IDE support. One of the things I've noticed from working in a few languages professionally (Python, Ruby, Java, Elixir) is that the level of power required in an IDE seems to be a function of the language. My o
37.
▲
by
grantjpowell
6y ago
Elixir has an anonymous function short hand that makes the "partial application" use case pretty easy for me. &Compare.clamp(&1, some_min, some_max) The above creates an arity one function which puts the arg into th
38.
▲
by
grantjpowell
6y ago
> The features I've outlined don't make NBL a great language. I think a truly great language would support Erlang-style concurrency, would have a simpler syntax and a powerful macro system, and would probably have much better s
39.
▲
by
grantjpowell
6y ago
An Elixir convention I've seen is to put the thing you're operating on first, so that you can compose functions using the `|>` operator, which places the previous expression as the first argument of the function to the right. M
40.
▲
by
grantjpowell
6y ago
LFE is really cool, but I think the biggest thing that LFE has going against it in terms of mainstream/industry adoption is that Elixir is _roughly_ a Lisp (pretending it's not). LFE is competing against a language that has some _
41.
▲
by
grantjpowell
6y ago
The BEAM is great, but the Elixir language itself is really what spoiled me. After having written ruby for years, I really enjoy what the Elixir language has to offer. Pattern matching[0] and the pipe operator[1] eliminate a ton of intermed
42.
▲
by
grantjpowell
6y ago
Well this is mine — the BEAM, which already has Prolog-y (Erlang), Algol-y (Elixir) and Lisp-y (LFE) As a full time Elixir Dev, I actually consider Elixir to be a lisp (albeit, pretending it's not one). Elixir code is 100% e
43.
▲
Automation: A Failure Story
(medium.com)
3 points
by
grantjpowell
6y ago
|
0 comments
44.
▲
In Praise of Security Theater
(schneier.com)
2 points
by
grantjpowell
6y ago
|
1 comments