marktolson

That's essentially what we already do. My original point was based on the fact that the config changes all the time (as opposed to 4 times a year).

We edit yaml files everytime we update a service version, which happens multiple times per week? Is there a better way to deal with this?

Instead of referring to the version could you refer to the hash? Then a simple integrity checker could confirm file changes.

Simple way to learn is to load up an AKS cluster (free for the master, simple to follow tutorials online), then learn to create a deployment and link a service to it (just a yaml file). It's really only an extra step or two on running a docker container.

Look at China's GDP over the last 2 decades. It has grown exponentially. At this rate they'll surpass the US this decade or next. You cant just move manufacturing elsewhere. China have perfected low cost mass manufacturing. It's not just beacuse labour is cheaper. That used to be the case but now they are innovating at a huge scale.

I don't understand the hate for microservices on hn. I have found microservices are a great way to extend monoliths developed with legacy frameworks. There are so many pros with the cons easily avoidable with the right tooling / processes.

Windows has already lost out on the server game. Less desktop apps are being written each year with the move to mobile/web based apps. The desktop OS is largely becoming irrelevant.

What if outline.com simply did a GET request on the source from the browser, stripped out paywalls and ads and served the content from the source server. Is that still copyright infringement?

VanGo will succeed DUE to the sexism involved. Think about the moms weighing up their options when sending their kids to school:

1) Uber - random dude (most likely)

2) Another mom or at least a pre-screened woman

Not many moms will choose the uber for fear of appearing sexist.

How does a properly designed microservice architecture not achieve greater scalability over a monolith? Of course you can scale up a monolith but with microservices you can independently scale selected services thus increasing your benefit cost ratio.

I've been developing with .NET since 1.1. The initial appeal of ASP.NET WebForms was due to the fact that you could build software similarly to the way you build Windows desktop based apps. State was managed in an unmanaged environment. You didn't have to worry about varying browser capabilities / quirks due to the lack of standardisation at the time.

Fast forward a few years and all of a sudden you have browser standards and amazing MVVM frameworks. Everything you needed ASP.NET for was no longer required.

I still work on enterprise .NET systems and it's no surprise as to why startups look to alternatives. Sure the tooling is amazing but so are many of the other tools out there. After using simple web frameworks like AdonisJS I see no real reason for building your service layer (let alone your app layer) in .NET.

Wait so BAT with its $250M market cap has < 600 sites in the Alexa top 1 million??? That's like 6 hundreths of a percent. That's a terrible rate of adoption considering the hype behind BAT.

I wouldn't say excessive use of JS was the problem. JS provides the foundations to tons of extremely fast websites and should (in most cases) assist with improving performance. I'd blame the overall implementation / design which led to scaling and performance issues.

They give you $150 credit each month for 3 years upon signing up with bizspark with nothing to pay up front. Surely that justifies taking the time to check it out if you're already curious.

I used to share similar feelings when VB.Net was first introduced. I couldn't believe there was no VB 7 and Visual Studio .Net was the official replacement. Having worked with .Net, winforms, MVC, webforms etc for over 10 years now, there is absolutely no comparison between the latest versions of Visual Studio and the archaic tools from VB 6 days. Yes, VB 6 starts faster, but that's pretty much where the pros end these days.

Show HN links are supposed to link to the site, not to an article about the site.

Haha cheers! Yep I'll probably end up putting the filter list on the opening screen as you're not the first person to liken it to a round of penis roulette.

I'm not sure if anyone cares or you're just in it for the pics but I thought I'd describe how it works. The site doesn't just pull the top images from all subreddits. If that were the case you'd only see posts from the most popular subreddits. It creates random pools of subreddit groups based on the selected filter. It then cycles through those pools after exhausting the list of selected subreddits. This exposes the viewer to subreddits which may be less popular. There's a lot to discover. The average time on the site per visit is currently over 25 minutes.

This is amazing news. I have a image gallery site with ~500,000 images. It currently costs me $39 a month and now I'll get to spend even less, no idea how they do it.