attilagyorffy

This is very exciting. The music landscape is just as chaotic as it was back in 2007 (when CBS acquired Last.fm) if not even more complex these days. Can't wait to see what's next. <3

If we have high availability connectivity for servers, I feel like corporations should also consider applying the same principles for inter-personal communication. A distributed and encrypted protocol with a similar feature set to Slack would come handy. Any suggestions?

there's currently no post on openssl.org but i expect them to publish one soon. Also, now with all the OpenSSL sh*tstorm this year, I really wonder if LibreSSL is vulnerable to this security problem...

I vaguely remember something around a potential fix but I lost track of it. The strange thing is that this appeared yesterday. I haven't had time to actually test this, am just looking to see what the community knows, whether someone could confirm this.

I've found this on isssource and am surprised that it has not spread like wildfire. If the claims are true then this is an issue that should be taken seriously. Posting here for discussion.

This really is a more complex question then it may seem. One of the reasons I haven't yet upgraded my production system is because I want to be able to keep my system up-to-date. Now, having to manually patch the FreeBSD source tree once a new upgrade lands is a bit of a pain. The point of the article is really about exploring where we are and where the FreeBSD community is headed.

I know this is just nitpicking but you may want to use capital V instead: `ssh -V`.

And indeed the SSH command originates from OpenBSD and uses LibreSSL 2.1.8.

ha, funnily just one day before code freeze of freebsd 11 :) nevertheless it's great that freebsd is getting more attention these days.

I've been a Rails developer for 10 years now and I have to say it is still my favourite tool of choice (yes even in 2016). There are other interesting tools and frameworks out there (I'd love to put my hands on Phoenix and Elixir if I had the time) but for now I have to be honest: When I start a new client project I have to consider a few things:

* Using a well-known framework is favourable over new shiny toys in a commercial system

* An ecosystem that has good 'defaults' is essential. A single web framework won't do everything for you. You need stuff around that for testing, deployments, etc.

For mainly the reasons above Rails is still my primary tool of choice. Yes, it has pinpoints but the reasons above far outweigh the new and shiny.

if you can make this work in a way that it's capable of reinstalling a precise snapshot (like using a Gemfile.lock in Ruby's Bundler world) and keep it stable then I once again will have faith in JS package management.

my thoughts exactly. whilst i don't care about Salesforce's CRM, i wouldn't want MS to put their hands on heroku. Once MS bought one of my favourite companies (Rareware, now Rare as part of MS Game Studios), effectively they killed creativity. I'm not saying that MS is necessarily evil, all I'm saying is that I've seen this once and I have been really disappointed.

I'm a little bit disappointed that the TLD is .PIRATE instead of .YARR

https://github.com/npm-ruby/npm-ruby - Bringing npm functionality to Ruby applications

That's also a good solution I think. One of the main advantages of using containers though is real portability. This means in theory you could just push your container in development into production without too much hassle and making administrators nervous :) That's not the same level of portability a full VM would give you.

Admittedly this is more of a discussion about containers and security than npm itself but I'm interested in discovering the options out there. I may attempt to move all my stuff to containers for a bit and write about my findings.

This is exactly why i think modern kernel level security layers, such as FreeBSD jails (or Docker/LXC) were born. Provided your app runs within a jail, it wouldn't matter much anymore:

> Once inside the jail, a process is not permitted to escape outside of this subtree

You could also develop within isolation, therefore your development env would be safer and even similar to a production environment. Needless to say, that has additional benefits.

I use Ubuntu for convenience and because that's the distro that I am the most familiar with. I know that Ubuntu is a Debian derivative but I tend to use Ubuntu because of the wide range of community resources.

I personally haven't had significant performance regressions. I tend to disable only the modules that I am sure are not going to be necessary.

Also, Tinycore linux might be great but I would like to use Ubuntu for convenience and keep my existing additional scripts and provisioning profiles compatible.

I'll have a look at Tinycore Linux though, thanks for mentioning.

Great idea! I personally haven't had any experience with the cloud images so far but now that I looked at them I really like your idea. +1