apeacox

watched them live last year in Teatro Antico di Ostia, wonderful show to see them live, worth the ticket price.

I also remember your articles on Linux&C about buffer overflow, sockets in C, etc... ;-)

Not a monopoly, but a walled garden.

Exactly, they aren’t exposed outside. That’s why you can “potentially” add rules to route request from the outside to an internal host:port, even 80/143. On the LAN you would still able to connect to router admin.

DNAT. You map one/more ports from your router exposed on internet to ip:port of the local app.

However, http/https ports are already used on routers to offer an admin web GUI. It’s technically possible to circumvent this with some ad-hoc firewall rules, but it depends if the router admin UI let’s you do that.

Maybe something like https://dev.to ? I really enjoy that community.

Other than going deeper with Elixir knowledge on new problems (see below), I learned and brought in production the followings:

## DevOps

* AWS Cloudflare and Lambda (with Go)

* Kubernetes

* Ansible and Terraform

* deploys from gitlab/bitbucket pipelines

* production/dev setup with Docker and docker-compose

## Patterns

CQRS and Event Sourcing

I’m going to continue on these paths during 2019, maybe with some new stuff as well.

Yes, you can definitely connect manually through telnet (I did it back in the old days). The only problem is it will not stay connected too much, because you should also reply to server's PINGs at regular time intervals otherwise you'll get disconnected.

> This could have been avoided, but the time to avoid it was perhaps in the early 2000s.

there were protests, from Seattle '99 until Genova '01, where many different groups merged into a single protest agaist that kind of globalization. but after 9/11 everything almost vanished in the name of worldwide anti-terrorism.

I suppose through some kind of machine learning, given the fact that they have a miriad of data of any kind.

It might look like a funny experiment/excercise for someone at Google.

I'm hosting Gitea on a $5/month DigitalOcean box, I had to setup disk snaposhots and db backups for security.

It's running since a year, never had a problem with it. It only consumes 20MB of RAM and is extremely fast. Easy to deploy (I've used ansible)

Hopefully without mining and selling user data. This might be the real killer feature.

Read books and articles. Read and write a lot of code by trying to solve a problem. When you have a problem, study to solve it in the best way possible (that even means rewriting from scratch if you think so). Try to deploy a complete product online in some way, even the simplest one. This should help finding the spot that fits better for you. For example, working on frontend or backend, focusing on security or UX... there are a lot of specific topics you might want to dive into based on your tastes. After some time, you’ll be able to drive your knowledge by your own. Asking now will not help that much.

Good luck ;-)

You’re just trying to impose your opinion. Speaking about sex or even a love relation is not shitty. If you’re triggered with it, all I can do is avoiding to talk about it in front of you in person. In all other cases it’s your problem, not mine.

Maybe it’s creepy for you or a bunch of others. I find it funny, at least until it’s used with caution and in the right contexts. We’re adults, sex and technology (along with a lot of other things) are parts of our life, I really don’t see the problem here.

But gmail doesn’t make any differences between user.name and username.

I used to add i18n on rails apps only when needed, because it forced to create a decent yaml schema for translations (how/where to put keys in the right namespace can be hard).

Instead, Elixir/Phoenix uses gettext, you wrap strings with a gettext call, then you run a task and it generates all the files ready for translation. This means I can still use a main language and translate it if needed, without touching the codebase.

I hope they’ll bring some fix for battery drain as soon as possible.

Even if you can potentially run several instances per server (with enough ram), I think that an usable one should run on a dedicated server. Considering that a Rails app doesn't run like a webserver with php installed, just like you can do with WordPress or php apps in general. Also, I suppose 1gb is required to run the instance, but it isn't known how many users can host decently.

I wonder how 2000 servers can host 800.000 users. It means that, on average, a server can host 400 users. I really appreciate this project for several reasons, but it (sadly) looks like a waste of resources with these numbers.

Kudos to ReactOS team! I've never used it in production, but I tried it several times during the years and I was always fascinated by the efforts made to improve this OS.

Yes.

I'm 40 and I've found out the hard way that 90% people under 35 adopt absolute statements for everything, as if they think they already know how the life, the world and the universe work. Good luck.

I don't get your point. The author just used some funny metaphore to explain how our brain works. And yes, our brain still works with ancestral habits, this is not a big news after all.

StackOverflow already covers a great part of the possible (most common) Ruby related questions. I'm not surprised there aren't so much new ones in the last 1-3 years. About job postings, I don't know, I still get an average of 3-5 ruby job opportunities per week from recruiters. The same goes for several ruby devs I know. On the other hand, I see a lot of people switching to other new languages/stacks for several reasons (some of which are mentioned in the article). I'm one of them, but I still use ruby when it might fit the job (or is a requirement).

Bulma is modular, and usually you end up with a ~20kb bundle

Interesting project. However, the size is still big and it doesn't use flexbox. I'll stick on bulma.io

For backend I'd surely use Elixir/Phoenix, that's what I've used in the last 2 years, after ~9 years of Ruby/Rails. Elixir and Phoenix are fast to bootstrap, easy to use and deploy, even for complex scenarios (background jobs, websockets, key-value store, etc). Even for quick prototypes, I find Elixir/Phoenix a lot simpler than Ruby/Rails.

For frontend, thus JS, I'd use Vuejs. I switched to it after some year with React. It's a perfect compromise between React and Angular.

Chomsky calls this *libertarian socialism (or anarchy in the Bakunin mean)

After 18 years of programming in a wide range of languages (almost 10 spent on Ruby/Rails) I surely agree that Ruby is a joy to use for many tasks. A different opinion goes to Rails: it's speed of development is inversely proportionate to the time taken to reach a messy codebase if you follow the infamous rails way. You need some decent design pattern to get something that is still usable after 6-12months of active development. Performances and speed can be important for many aspects, especially when there are alternatives that offer same speed of development consuming 10% of the resources needed by a ruby/rails app. Can you put a non trivial web app written in rails on a 512mb ram/1 core VPS for production (serving responses in microseconds, and consuming only a total of 50-60mb of ram)? That's what I did with 2 apps written in Elixir/Phoenix. The speed of development was the same (if not better!) than Ruby/Rails, the apps are running on cheap instances and can be scaled if needed. The hate toward rails: it's getting more crappy on each release. Several new additions (especially in the v5.x) are pretty wrong (eg: global shared variables). Yes, it's still a choice, but it has lost the real game-changing that was few years ago.