shanemhansen

I've been using evolution for the last few years. It has a EWS (exchange web services) client that works really well for me at $BigCorp. I think I've had one or two crashes total, compared to outlook which crashes almost daily.

Prior to that I used gmail. When I used thunderbird it often seemed to spend all of it's time indexing. It has some nice plugins though.

Upvoted because I agree with your overall point:

> 100% telecommuting doesn't work for a lot of people, maybe even the majority of people.

You're probably getting downvoted (I had the urge myself) by the minority of people who find it to be an excellent fit. Maybe in previous generations we would have been sheepherders, cowboys, or explorers. Or maybe monks. I work remotely and I like social interaction, just much less than most people. If working in an office gives you 10/10 in social interaction, my preferred number is probably a 2. I'd be unhappy with a 1 but much more unhappy with a 10.

Maybe others feel like me. Or maybe given the presence of always on google hangouts and facebook messenger and slack and irc, they feel plenty social.

I consider lack of being face-to-face to be a legitimate drawback of my job, but it's waaay less of a drawback than being forced to live in a "tech hub" or have a commute. The power of being able to hire people who live more than 30 minutes away from your office is incredible.

I think that within a datacenter, a bunch of microservices make sense. When communicating with a customer, you want to craft just the data they need and minimize roundtrips.

GraphQL seems to be a great candidate for bridging this gap. I recommend using graphql to allow clients can use to make "One Special Bigger Request" which then gets split into multiple requests on the backend.

> bringing the low performers up to average, but at the cost of handcuffing your top performers.

Sounds about right. If you view humans as interchangeable resources then predictable performance is good. Most businesses don't need or benefit from a Linus Torvalds to build their CRUD app.

Apache has historically been a giant swiss army knife that will do just about everything you could want, from redirect databases to cgi to php interpreters to crazy auth setups. It did all that while still being a reasonably good workhorse for static file serving (when properly turned and using the right worker model, event rather than threaded or process).

Nginx seems to have a different model. It does support a number of features but from what I can see it focuses on composing functionality with HTTP rather than adding more plugins.

Nginx seems to do a great job at being a load balancer and cdn-lite, and it seems like that's what the market wants out of a web server.

I don't work there or have a ton of details, but twitter has paternity leave and I was unofficially told that "untracked PTO" was more like "5-6 weeks". Which as an american seems perfectly generous.

Thanks for sharing. Seeing a working emacs clone that compiles to a 66k executable is pretty awesome.

I think databases have been so wildly successful because they were actually based on some reasonable research about data access models and set theory. I encourage anyone who wants to criticize the relational model to start with E.F. Codd's "A relational model of data for large shared data banks".

Random nit: is it just me or is the font rendering pretty terrible in the "web" screenshot?

I don't know if Mark was paid last time I saw him drop by the office, but I imagine he planned on making some money.

I work for a fortune 50, Canonical does a decent job competing there.

I can't tell you how happy I am to see convergence dying. My desktop is not just a big phone and people put out some atrocious user interfaces in the name of "convergence".

WRT to unity, at least it's improved. Ubuntu w/ unity currently has the best multi-monitor multi-dpi user experience I've seen on linux. I have a retina laptop with 2 external displays and ubuntu unity is the only thing that just works out of the box.

I suspect more people on this site wanted to grow up to be code breakers and spies than porn purveyors.

This happened to me. I left a new XP pluggged in, behind a nat, and first thing in the morning I had a virus.

I don't think users enjoy the return of loading gifs quite as much as SPA developers think they do.

User focused metrics:

1. It's a user facing bug if I have to purchase a bigger laptop because someone decided to get the smallest element of a list by typing list.sort()[0].

2. It's a user facing bug if the use of my app heats up their phone, drains the battery, and leaves someone stranded w/o a way to get safely get home on a friday night.

3. It's a business facing bug if my AWS bill is in the hundreds of thousands per month when I could be paying a mere 10s of thousands. (This is more common than you'd think)

4. It's a user facing bug if a sudden increase in traffic (due to my product being featured somewhere) takes down my services and results in lost sales and brand damage.

I understand your point, it's not necessarily a problem if a backend feed is taking 45s instead of 30s, or if the the text input subroutine for an interactive app allocates.

As far as I can tell as a software developer and daily computer user, people aren't erring on the side of making their software too fast.

I remember customer support doing co-browsing back in 2008. Hopefully the mechanisms have gotten a little less hacky over the years.

Pretty neat project. I for one am happy to see more OCaml in the wild. Minor nit: they mispelled jscaml as "jcaml" here https://github.com/facebookexperimental/JSCaml/blob/master/R...

Clojure does allow type annotations that are used to avoid reflection. https://clojure.org/reference/java_interop#Java%20Interop-Ty...

    (defn len2 [^String x]
      (.length x))

I feel like the question answers itself. Turing complete. Decidable. Pick one.

TSLA is up over a 5 year period, a 1 year period, and 25% in the last 3 months alone. As far as I can tell the only people who learned a hard lesson were those who bought in the last week or so. I believe the lesson they learned is: past performance does not guarantee future results.

> its not rocket science.

They have that too!

I find this happens quite a bit in any organization that needs to develop competence in an area they aren't already experts at. One of the first companies I worked for was trying to get good at product management. They kept hiring a bunch of smooth talking inexperienced people who crashed and burned spectacularly. They didn't know enough about product management to hire good product management.

I really like reading the go std lib and runtime source.

The dynamic languages people are always saying programmer time is more important than computer time. Yet they put out an editor that is wasteful with both.

I run a web server who's number one job is to add negative overhead to most requests (CDN). As an example of how much I care about overhread: a while back one of the biggest bottlenecks preventing us from saturating a 10 gigabit NIC when serving from cache was that our cache get allocated rather than providing a view into the bytes.

I'll probably still be upgrading. go1.8 has some nice performance improvements overall. Specifically the codegen improvements help in HTML parsing and image resizing.

If I'm still upgrading, I have to wonder how many people out there are pushing Go's net/http harder than I am?

Personally I'd consider using uber again. If everyone hates uber and refuses to use them, then they aren't customers and uber has 0 incentive to listen to them.

If a bunch of people delete the uber app, and the CEO takes positive action, then I think we should reward good behavior and consider reinstalling it.

You're getting downvoted, but over the last decade I've seen a pretty high number of STEMers that seem to confine their logical reasoning skills to very specific domains.

Example (I'll let you be the judge of which one is being irrational): I know STEMers who are adamant atheists. I also know STEMers who are pretty devout and think that science supports all of their beliefs.

For a less controversial example just look at the sheer amount of fashion trends that sweep through the programming community. Pushing those trends is literally a core function of this website. Just like many people in america jump from fad diet to fad diet , and we jump from fad framework to fad framework. The number of software engineering decisions we make that are based on actual software engineering research is vanishingly small.

Fellow STEMers please understand that you (and me) are human and very likely just as irrational and emotional as any other group of people. Ignoring that fact will lead to a false sense of superiority.

Theoretically science is supposed to be that paragon of reasoning where we attempt to falsify our beliefs and thereby make the more correct ones stronger, but my interaction with the academic world has made me realize that science is again mostly about developing relationships so that your papers will be favorably reviewed, publishing junk to make sure your boss thinks you are productive, and researching whatever the people paying your bills are interested in researching.

Walmartlabs offers 3 days of paid VTO (volunteer time off). I'm not sure if political work would actually count, I believe it has to be a 501c3 charity in one of 5 pretty broad categories (hunger, poverty, women's rights, etc).

I wonder how it would compare to the fasthttp libary https://github.com/valyala/fasthttp

I don't suppose the hand tuned microhttp parser supports h2?

Pipelining is a dead technology that was never really alive. For those who aren't familiar with it, it's based on a http "hack" where after http/1.1 was released and response end could be signaled via something other than EOF on the tcp connection they figure you can send n requests in a row and receive n responses in a row. This was in the days where good manners required you make no more than 2 simultaneous requests to a server.

Nobody ever really supported it, and the lack of support for out of order responses meant that any one slow request could slow down everything else. The h2 model allows at least hundreds of simultaneous requests and responses multiplexed over one TCP stream.