discordianfish

All I can say right now is that it's dirt cheap for bare metal. Scaleway was already the cheapest option for bare metal and this looks like a significant performance bump.

Doesn't do anything on my ubuntu / chromium system.

Hahaha. "Europe's first Digital and Personalized Shopping Service"

Oh really? I didn't know that namespaces is linux are the openvz changes. Thought they were a completely new implementation mostly driven by Google?

Very well sums up my experiences working in the Berlin startup scene.

I'd add that, in my opinion, there is also a lack of appreciation for good engineering in many of the few existing startups. You could almost say even software startups don't consider themself technology companies. The implementation of the product is just something that somebody needs to do and often gets outsourced to some agencies.

In general the focus is on the founders more than it's on the teams. Ultimately that also shows in salaries. Startups are considers something for junior engineers that accept worse pay because they are doing something hip.

Yeah right.. "If you don't like the web, go somewhere else!!11"

It simply selects for people who can write a simple code unaided in an interview situation while somebody is watching every letter you type. Many people don't have a problem with that, others have.

This is so german of you!

This is a very interesting attack vector. There are many situations where less privileged users can inject stuff into an nginx config.

I agreed, would at least consider it a bug if not a security issue.

Playing devils advocate here.. Couldn't you argue a driverless car simply needs less space to guarantee the same/better safty for the cyclist?

They also miss out on the dog fooding aspect. They target enterprise customers who run probably run gitlab on bare metal. By doing the same, you experience what your customers do and have much closer feedback loops on any issues that might especially affect bare metal.

Regarding managed dedicated.. I had very bad experience with rackspace in that regard, which is why we moved AWS. At another job we had our own DC suite but had some company taking care of initial cabling as well as remote hands from the datacenter. If I ever do bare metal again, that's why I would do.

A friend of mine once found a Windows 98 copy on an 'empty' still wrapped CD-R.

Everybody's modern linux stack is built on 40 year old design and assumption. While it's remarkable how well these work so many years later, I welcome that somebody like Google tries something new.

Don't Google, Apple, Facebook and friends all say the same?

> Gitlab's compensation policy is pretty much intentionally designed to not pay people to live in SF.

What do you mean? They pay people in SF much more than in other cities because the high cost of living. I'd consider working for Gitlab if I would live in SF, living in Berlin it's not an option.

Checklists are great if you have them and often you should create one even during an outage but other times you waste time. It's really hard to balance fixing things quickly and not breaking more.

There isn't a silver bullet anyway, it's layer on layer of operational best practices what makes you resilient against such issues.

At my first job, we had a sun box running that was booted once and never rebooted until being decomissioned around 5 years later.

Yes, I personally prefer that too. But I understand if facebook decided this is too much to ask for their users.

Agree, also think it's likely this is an intentional trade off: Alice sends Bob a message but Bob's phone is broken, so he gets a new one. The message is marked as not delivered. Since Bob's old keys are lost, WhatsApp needs to generate new ones. The trade off here allows in this scenario to accept new keys transparently.

Not ideal from a security perspective but what would be the alternative? Bob meeting Alice so they can compare fingerprints? Bob sending Alice a PGP signed message?

If you deploy in containers, it's not. But yeah, that comes with it's own challenges.

In my experience with ansible, salt and chef their key selling point compared to bash script is composibility and abstracting away the underlaying distribution. The later one is so leaky it's not very useful. Composibility is possible but the building blocks lack any opinionated structure, so everyone re-invents the wheel anyway.

Today I wouldn't use any of those anymore and, as you suggested, use shell scripts in a immutable infrastructure fashion (aka, reinstall system when changes are needed).

I like opinionated software. If scrollback is better implemented on a different layer, leaving it out is reasonable. But I'm not using tmux because I use i3 as wm which does all the tiling/splitting. Now using a new tmux instance for each of my terminal (can be dozens) only for scrollback seems not the right way though. Any recommendations what would be The Right Way here? Anything that only implements scrollback maybe?

Surprised people consider tabs and scrollback similarly basic features. As someone using only basic linux terminal emulators like x/u/aterm or urxvt its interesting to see that people consider tabs a basic feature, while I don't know a single term without some scrollback. Really makes you realize how different people's expectations are.

> Whatever the case is, even though I know null about the project, I can easily say that Leah Rowe, whoever she might be, is apparently toxic for the project.

So you don't know anything about the project beside that their main/core maintainer accuses GNU project to have fired a trans person and therefor she doesn't want to work there anymore.

Call me SJW or Gutmensch but if that makes you 'easily say' that she is 'apparently toxic', you are a prime example for what is going wrong in tech.

Looking at how one-sided the discussion here but especially on reddit is should be worrying.

Not saying it's the case, we all don't know, but if the accusations are right, it's absolutely reasonable to not want to work with these people. You can say all you want about being professional and not having politics influence your technical decisions, but that's easy to say if it's not your life style choices that are discriminated against.

Agree, that sentence doesn't make sense. But I think the point is simply that accessing data doesn't have any overhead, so you benchmarking your disks. Given the design, that seems likely.

> Also - what's the protection mechanism for files? If there is none, I literally have no idea what the purpose of this FS is. Under what circumstances would I need a giant slow data storage tier that has no redundancy to speak of?

Caches, that's what makes me interested in this (having to cache lots of images). We're using mogilefs for this currently.

> And I'm sure he's particularly sensitive to these problems right now.

Why do you believe that?

While I appreciate the transparency, I don't think such large salary differences are reasonable especially with remote work. In the end you compete globally for remote employees and it possible to work remote for SV companies and get somewhat similar salaries than the onsite employees.

...and of course is living much more expensive in SV but I don't see why that should be "subsidized". No harm in people realizing that it's freaking crazy to pay that much rent.

I understand the general privacy concern but what exactly is the critic here? That facebook aquires data from external source? Aren't those external source the real problem?