330 karma · joined April 11, 2012
On the plus side there were some nice memory improvements for Meeseeks in OTP 21.
The better handling of malformed HTML by default is the much bigger deal.
Maybe the firmware update has a bug, but it's very suspiciously timed. Notice that the OP is dated April 2, while 1.1.1.1 was released April 1.
This video also supports that guess: https://youtu.be/hHhm0bfdj-4?t=10m14s
In Clojure you can still stick something in an atom or volatile and easily update it in place... doing that is a lot more involved in Elixir.
Source?
For example- https://tomjoro.github.io/2017-02-09-ecto3-mongodb-phoenix/
There's not really an Elixir equivalent of Clojurescript to Clojure (there is an Elixirscript, but it's a work in progress and I'm curious whether it can ever capture the nice experience of using the Erlang VM). I've seen interest in the Elixir community in Elm and Bucklescript(OCaml) and other compiled-to-js languages, but I think a lot of people just use JS.
The language and Erlang's virtual machine are generally a joy to work with, and I have no regrets pushing past the syntax.
I don't necessarily feel that this is a problem with the language (though the current macro system doesn't seem simple or easy) but rather that this is a problem with the youth of the language.
The Closure compiler seems like a wonderful thing, but you really want to be able to use advanced compilation and that makes interop with other libraries... confusing (at least while you're getting started). This makes it a lot harder to just jump in and get started by calling on host (Javascript) libraries to get stuff done. Combine this with the fact that there aren't so many pure ClojureScript libraries and wrapper-libraries available (relatively speaking), and productivity is a bit stunted.
All of that said, I think ClojureScript has as much potential as Clojure on the JVM and I look forward to things improving as the ecosystem matures. It is wonderful to write Clojure and control the client, and I think that those people who can fight their way through (what I found to be) the unfortunately steep getting-started curve will have a hard time going back to vanilla JS.
focus Oh look, a big picture on the right.
down I wonder what that picture is about.
left and up Hey! Another picture!
down Part of another picture!
left and up What are these little things on the left? Meh, too small to my eye which have just scanned big pictures and headlines. Ignore.
weird left to right diagonal thing between 2nd and 3rd column as I scroll down
I'm all for responsive but readable is good too.
All the same, I am more and more convinced that subscription funded, high-quality digital content production is the correct path for the future.
CLR - https://github.com/richhickey/clojure-clr JS - https://github.com/clojure/clojurescript Python - https://github.com/halgari/clojure-py Lua - https://github.com/raph-amiard/clojurescript-lua C - https://github.com/schani/clojurec
(Sorry, couldn't resist.)
He is suggesting that people who have they money and desire to pay for something that makes their lives a bit more pleasant are the kind of people advertisers wish to get their ads in front of the most.
Not all advertising is about clicks- tv advertisement was built around getting information in front of eyeballs.
Does anybody know why an Oxford comma would be a signal that the quote isn't from the WSJ?
I've always found that using an oxford comma ("red, black, and blue" instead of "red, black and blue") is just common sense.
Separation by comma is a concrete indication that the items on the list are separated, which is useful in situations where the last two items could mean something different if not separated ("black and blue" has it's own special connotations, whereas "black, and blue" doesn't).
"Nobody wants to read your shit" (unless you give them an good reason to do so).
That's not assuming people are sheep. That's assuming that people are self-interested. And much of the time they are.
So even if you ignore everything else the author wrote (which you seemed to, since you're arguing that HN articles are popular because they're interesting, and the author's answer number two included making the writing interesting...), there is a valuable lesson present.
If you want people to read your writing, write something that will appeal to somebody (say... your audience). It isn't even difficult to give somebody a good reason to read what you wrote: if they find it interesting, that's a reason; if they find it entertaining, that's a reason; if they get to escape their lousy life for 25 minutes, that's a reason. This is hardly revolutionary advice, but it is a good reminder.
But not everything is worth writing.
I would not even begin to disagree with you about the merits of beautiful prose, but would the article have been anything more than a collection of entertaining images and vitriol if the author hadn't been skewering a very real and obvious and silly trend?
Most of us have probably shaken our heads at some startup name or another, or rolled our eyes at a particularly unbearable lump of marketing-speak. So underneath all those pretty words and images lies a sentiment we understand and can sympathize with.
If you want your blog READ instead of skimmed for buzzwords and facts, write things worth writing.
Which is not to say that #222 wouldn't be easier on the eyes.
Because he chose a more widely known (albeit fictional) example, more people are able to better grasp the idea he is presenting. It's just good communication.
The headlines are obvious when I arrive at Hacker News. There is a lot of noise between me and the headlines when I arrive at Hacker News Two.
I am going to stick with the original.
Assuming this isn't a community of those who come out of the womb enlightened, aren't most of us living in some state of foolishness?
I suppose it might be possible to sustain a community by continuously attracting new enlightened individuals, but wouldn't it be more practical to do what most societies do and teach (at least some of) the fools until they aren't fools any longer?