kungfooguru

I think if you aren't going to simply "ignore versions", like we do in rebar3 and took from maven (we used cargo and maven/leiningen as the gold standards when working on rebar3) then taking the latest makes more sense. A patch version must be important enough to release instead of waiting for the next minor release, which I think says something about taking the latest.

But that is only if versions are used this way at all, I've found, at least in the Erlang world, the model of taking the first "version" found in the dep tree and locking to it to work well. In that case a patch version is not considered special anyway.

Right, I think earlier Kafka it was actually the position as well, but then they moved to the current method.

'priv' is an Erlang/OTP application's directory for files that are part of an application but not source or compiled beams.

It is infuriating that anyone finds this to not be appropriate. Nvidia is the one that sells products and doesn't bother to care enough for their Linux users to work with the community. If you want Nvidia proprietary driver to work with Sway complain to Nvidia for how they've handled their driver for Linux for years.

We need more projects to do what Sway and Kwin have done.

Yes, it undermines the strike. Strikes are supposed to disrupt.

Trump plans to increase access to education and drastically reduce poverty? I had no idea... Also surprised those are bad things.

http://revista.drclas.harvard.edu/book/poverty-reduction-ven...

Yes, I blame the distros. Should have always just used release bundled as target systems. Though releases weren't always so easy to build with Erlang before relx and rebar3 (full disclosure: I'm biased on that).

I also played around with an idea of bunding the release into a self extracting bundled executable too https://gist.github.com/tsloughter/d62aad6d67b263e69275376b1...

The tools (relx, exrm) can do that.

You can include any erts in your target system, so you can take one built on linux, copy it to your mac and use it only at the time when you construct the release tarball.

Missing Alpaca, https://github.com/alpaca-lang/

Sounds similar to what Netezza did with FPGA's but here with GPUs. So they may hit patents they say they are unaware of...

The OTP team and the community have made a concerted effort to work more together that has been in the process for years now. Even the community based build tool rebar3 is being adopted into the official Erlang/OTP ecosystem.

Oh, my bad :)

Seeing the section "How to Start" I can't help but mention it doesn't include "How I Start: Elixir" :) http://howistart.org/posts/elixir/1

That is my point.

Seeing lots of comments about cost of Heroku. An easy way to get that down is to not use Ruby.

Yea, not having OTP to create proper structure, instead having goroutines and channels created and destroyed all over the place, really hurts readability.

But OTP isn't really possible either because Go lacks links and monitors.

Plus not being asynchronous and no distribution (wouldn't want to go over the network with sync channels anyway)...

He said at Google not the community. I wouldn't doubt there is a difference.

Nothing new. Just use the right variant for your use case: https://en.wikipedia.org/wiki/Universally_unique_identifier

Oops, yup. Meant to make it explicit since you can also do: ?MODULE:Function(X)

You can pass functions. The article was saying not to nest function calls.

Right, you can pass a function:

final_function(fun() -> maybe_function(X) end)

or

final_function(maybe_function, X)

if final_function does:

final_function(Function, X) -> Function(X).

There is no point.

Reading anything from them always reminds me of TempleOS. There are some hilarious gems if you skim it, like "Urbit is highly intolerant of computation error, for obvious reasons, and should be run in an EMP shielded data center on ECC memory."

I'm a long time Erlang programmer and still prefer Erlang. But anyone who asks about web programming I point to Phoenix. So if you are doing a web app, or have a web component, I'd suggest Elixir and Phoenix for that part :)

Erlang developer tooling does need work. But we are getting there, we have a new build tool http://www.rebar3.org/ that also combines forces with Elixir for the package management https://github.com/hexpm/rebar3_hex

Hm, wonder if samclemens reads Marxmail.... Louis sent this out a couple hours before you posted it here so thought it might be the case :)

Even when it is as simply as technology putting someone out of work it is a joke to then tell them, "It is ok, you and your fellow workers may be out of work but ultimately the unemployment level won't rise, so chill out."

This is especially condescending before the creation of unemployment insurance and the welfare state. You can't feed your family with without your job.

Those ease the pain, ultimately a democratic economy is needed so technology cuts the amount of work we all have to do.

He is high level and in the Vancouver office.

Everyone I've known who worked on AWS in Seattle have sounded exactly like the NYTimes article (so no, it isn't just the e-commerce side) and I've never heard any positive feedback.

These posts cover some of that:

http://blog.erlware.org/some-thoughts-on-go-and-erlang/

http://vagabond.github.io/rants/2015/06/05/a-year-with-go/

You mean damn those Greeks wanting to run their own lives? Something that was violently crushed and kept through an oppressive military junta?