oldmantaiter

Thiiss is reaelley good newes, my thirid genereatiiion keyeeboard . stiill has . isssuees

Off topic, but oh man does that website embody everything that is wrong with display advertising. Left the site open for 6 minutes: 8000 requests, 100MB transferred and a memory footprint of 700MB for that tab and climbing. Absolute garbage.

You might want to revoke that token...

If you have a local copy of the repo, you definitely could.

I know there are updates via the status page.

My main concern is that there've been a few RabbitMQ issues, network death, database issues, and now memcache? Must be some really bad luck.

There have been outages for 5 of the last 14 days, really considering moving to Gitlab or Gogs for our repos... not that I can't really complain because it is a free service.

Anyone here work at Atlassian that could shed some light on what's been going on? If it is just an unfortunate series of random outages, that's some really bad luck.

TL;DR Microservices have their place, and can be useful for certain environments, but they are not a fix-all.

They can be pretty nice for multi-tenanted development environments. Sure, you could use any of the other isolation techniques, but being able to provide an environment that can be started quickly (and somewhat easily depending on the rest of the services required). Not to mention that the popularity of container systems and their ease in understanding (Dockerfile vs RPM spec) means that other people can hack away at the dev environment without having to know the ins and outs of building proper packages (although they should learn).

Now, for a production environment, I would never move to a microservices architecture for the reasons listed in the article and my own dislike for adding overhead and complexity to solve "issues" that can be easily dealt with using tools that have existed for years (proper packaging with dependencies etc..).

Slick. It also points out how inaccurate GeoIP is depending on which data source was used for that IP (eg. where the ISP is registered vs. where the endpoint may physically be).

Using Docker as a local development system (especially with boot2docker on OSX creating a bunch of containers with different major versions of OS (el6/el7 for example) and being able to develop/test multiple apps at the same time is the only benefit I can justify for Docker.

But that's as far as I will take it, Docker is mainly used (from what I've seen) as a nice way to package something without having to write an actual package (RPM/deb) that will work across multiple platforms (for the most part). If you take the time to learn how to properly package your application, docker is unnecessary in almost every case.

I have a pretty messed up knee that gives me nightly pain. I find that Advil or Aspirin sometimes doesn't work so instead I smoke a little weed, the pain disappears and I can fall asleep (after the initial high wears off). As for productivity when I'm high, I would say that it can assist in working through an idea when stuck architecting something, but I always make sure to check my work the next day; naming variables or services after foods and characters on the TV show I might have in the background makes for a very confusing code base.

Considering the adoption and improvements, I'm on board with the "standardization" of distros with systemd.

Can't stand upstart and it's "Oh you wanted to restart your daemon, but I won't run the pre-start/post-start/post-stop actions you've configured me to", but that's just me.

All these comments about space junk, Spaceballs had it right with the giant cleaning lady in orbit. I think we should switch our focus to that instead.