anonacct37

I've found it's a common recruiter tactic to try and wring some sort of concession for you based on your address. In just tell them no. They aren't competing with the gas station down the street from my house they are competing with the Twitter office down the street from theirs.

It's possible my career has taken a hit due to being remote for the last few years but I get paid around $400k and I live in a nice little COL place.

It's remotely possible I could rate 2x that if I was in the valley, but it's by no means guaranteed. I could also make the same or less.

chroot is a filesystem namespace, and containers are basically just that plus some other namespaces. Prior to containers getting really popular I was using debian's schroot project and prior to that I was using solaris zones. There were other similar technologies prior to that but I wasn't really technical or even alive at the time. It's not new.

Here's what's made them so popular lately IMO. Docker improved the usability by adding the container registry and adding some better tooling around running a container.

Compare installing schroot plus configuring a new container plus running debootstrap plus potentially configuring lvm/btrfs/directory snapshotting to:

docker run ubuntu:lts /bin/bash

I think you make a good point, but actually AWS is where Amazon makes most of their profit. Can they call themselves a technology company?

Google and their cloud offerings are a little different. For the most part Google is an advertising company with expensive hobbies but it's always possible they'll figure out how to add another 800lb gorilla to their portfolio.

I've actually never run into a problem debugging go binaries with gdb. Which is weird because everyone's always told me it doesn't work. I'm sure there are edge cases but over the last 5 years or so my experience has been pretty good.

emacs + gud mode is a great experience for go debugging. I've even used it to debug low-level issues like plugin loading and verification.

I'm really excited about this both for the improved long tail latency as well as (what I believe is) a new way of handling this problem.

I'm not aware of another M:N threading model that handles preemption this way with signals. Erlang accomplishes it with reduction budgets and reduced performance.

If you look at the history of what happens to first movers you'll see it's pretty occurrence. Reality has no constraint to be sensible.

Not really. They seem bright but I don't think their competencies have much overlap with walmart's problems, at least from a technical perspective.

[edit]

I'd like to revise my answer. I answered your question thinking in terms of systems integration. However it's quite possible Mark Lore will be a much more effective CEO than the person he replaced.

I work for walmart ecommerce. There are some legitimate reasons for their issues. I could talk about them in depth (turns out when you crush the competition with the world's best logistics technology you end up with a whole bunch of systems from the 70s/80s that are hard to update). Walmart was literally using the internet before most companies even knew it was a thing, and unfortunately their internal network reflects that. Another example is inventory management and sales reporting. When these systems were built there was nothing like them in the world to centrally manage inventory and availability and create feedback loops. But in 2018 going to the back office to get a 100 page printout generated by a mainframe once a day hurts more than it helps. It's like we climbed mount everest and got farther than anyone before us before building a camp, and now we're kind of stuck in it and by the way people have found even better routes since then.

But anyways, customers don't care. It's not their problem. I've had orders cancelled for no real reason so I just give up and buy it on amazon. I've had search so bad I can't even find what I'm looking for so I just give up and buy it on amazon.

And I'm somewhat incentivized to want to think the shopping experience is good.

> This is "Arch is unstable" thing is very much a myth pushed forward by people who only dabbled with Arch once or twice then had it break, then completely dismissed it as unstable.

This accurately describes my experience. I stopped using Arch around the time git broke when I updated. I'm not clear what mistake I made. What level of Arch intermediate or expert level Arch knowledge is required to keep git working?

Load testing can be hard. Wrk works for me for the most part but it's not ideal for complex flows (say e-commerce trying to simulate a real browse and checkout complete with typeahead search).

However the smarter apps can have problems too. I've pinned all available cores on fairly beefy machines because they are gunzipping bodies (behaving more like a real browser).

If you are at a scale where you need really good testing I recommend that you think of wrk results as comparable to a unit test and something like jmeter as comparable to an integration test. It's not worth the effort for most companies but where I work we serve a decent amount of traffic and downtime costs 6 figures per minute so good performance engineering and good business overlap.

We use wrk since we are often load testing fairly simple services, occasionally with some Lua for cache busting. It's a great tool. Would love if it supported http2 since I work on CDN type stuff where that matters.

I love your 2nd approach (advertising). Any pointers to how to get started?

We can discuss what they are doing and also vote with our money.

I'd hate to be kicked out of a shop because I'm reading a book. Or not talking. As you said: maybe it's their right to require socializing, but that doesn't make it a good idea.

> There is no need to win arguments.

This is the mark of someone who has figured out an incredibly valuable truth about interacting with people.

There's alot of fear around the possibilities of flapping routes, but alot of real world data seems to show it doesn't happen seem to impact web traffic that often.

People often mix and match anycast/Geo DNS and anycast/unicast http.

Some even go a step further and, for video files, anycast to a node that 302s to it's own unicast address.

Don't use them unless you have to. The vendor lock-in is strong.

> designed so that a mediocre programmer can produce passable code

That's a little unfair, if accurate. Even the best of us are mediocre programmers when fixing a bug in the middle of the night or diving into a new code base.

You might as well say (and some do) that Haskell is for mediocre programmers because good programmers don't make type mistakes.

> a compiler that tells them off for not properly commenting their code

Are you still talking about go and if so would you mind sending a link because as someone who has written it professionally since pre-go1.0 and contributed multiple changes to the go repo I haven't the faintest idea what you are talking about.

> The social health issue is one for all companies that compete in the social media space to figure out.

Our traditional media organizations haven't figured this out in millennia. I'm not that hopeful. It's a fundamental conflict of interest between selling ads and creating informed citizens.

Some will tell you that's why they have the "church and state". I don't know. I'm not sure it's an effective policy and with native advertising the point is moot because they've given up on even the pretense.

> This has enabled the release broken of software,

Yes.

> that over time becomes better.

Debatable.

You're trying to make it sound like an overly complicated and not that likely situation. It's quite simple: money is free speech and legislators are listening. It's absolutely, 100% the case that tax laws are written to favor large businesses.

https://www.vox.com/policy-and-politics/2017/11/7/16618038/h...

Good point. People voluntarily parted with money to pay for the first.

The second company, well if you take a minute to read this article it explains the price society pays for the second policy: https://www.nytimes.com/2017/09/03/upshot/to-understand-risi...

I'm not really defending the first example, but america has a bit too much "privatize profits, externalize losses" for my taste. These policies do have impacts on the life of the median american.

I feel like the phrase "coupon abuse" is madeup crap. A Business gives discounts in order to (hopefully) make more money, then try to ensure that we all see people who actually use those discounts as "abusers".

Don't fall for it.

It's not that complicated. If you are a business, don't sell stuff at a loss. If you want to sell stuff at a loss to drive traffic to your store, you're going to take a loss. Don't blame your customers.

It's been my experience that people are less open to hacking CentOS/RedHat. It's pretty much you get what you get and changing anything makes it unsupported which defeats the purpose of using an enterprise distribution. That's not my opinion, it's what seems to be the community's opinion when you bring up things like using non-stock kernels.

I've been remote for a few years. I've negotiated remote offers from many bay area a companies. This is a pretty standard piece of hr bullshit you should ignore. The correct answer is to hold your ground.

If for some reason that doesn't work out, you've discovered that the company values you less based on your zip code which is something you definitely want to find out before you're relying on them for your livelyhood.

Yes I'm using gopherjs. It actually performs really well. For a taste check out this article on raw numeric perf where gopherjs beats native go. Of course there's a catch/explanation but it's interesting to see how well it can perform even on tight numeric loops.

https://medium.com/gopherjs/surprises-in-gopherjs-performanc...

I think the change is going the other direction. Native code and clean libs that don't depend on window/document globals are coming to the web via projects like this and the other 1/2 dozen ways the browser now has of running gcc/llvm target output.

I'm actually building my latest project this way. Not using this project though.

I actually really enjoy it. I have all of my go test stuff running in subpackages, and a fairly thin main package that hooks my models up to vue.js and builds some frappe charts. I very much enjoy taking the workflow I use to build efficient services and using it to build my simple frontends.

two-way data binding on a go struct is actually kind of magical and not something you could really go without javascript since (I assume) it relies on Object.observe and go doesn't really have properties. Goroutines and channels in javascript are also really magical.

> If Cloudbleed has taught us something, it's that cloudfare idea of "fully encrypted" doesn't fully include what's happening inside their own (virtual) walls.

I think that's a little unfair. Cloudbleed specifically referred to an application that parsed HTML. There's a pretty big logical dependency between "able to optimize our HTML" and "can see our HTML". I feel like the field of homomorphic encryption and HTML parsing is... non-existent.

Thanks, that's the exact info I was looking for.

I've unfortunately been bitten before by choosing json as a serialization format, specifically in go, due to JSON performance dominating processing.

No criticism though, JSON is the right choice for many types of APIs.

Any performance numbers?

You seem to think terrible design is a blocker to adoption.

Are you acquainted with Javascript or windows?