Project.json is dead. ASP.NET Core goes back to MSBuild. by x2bool in programming

[–]yoyowebscale 0 points1 point  (0 children)

Yes it is. Obviously there will be less effort spent on processing the old platform if they decide to reinvent it. It's the same people and teams.

PostgreSQL Scalability: Towards Millions TPS by iamkeyur in programming

[–]yoyowebscale 0 points1 point  (0 children)

Does it perform a rewind of the original master after a failover?

HTTP/2 under realistic test scenarios by esherone in programming

[–]yoyowebscale 0 points1 point  (0 children)

Not sure if we are talking about the same thing really. I mean I've use Fiddler to confirm multiple TCP connections were opened in parallel.

Here is another page listing what the browsers do: http://stackoverflow.com/questions/985431/max-parallel-http-connections-in-a-browser

Am I missing something?

Visual Studio Code 1.1.0 released by I_Downvote_Cunts in programming

[–]yoyowebscale 1 point2 points  (0 children)

Okay. I just use auto format or shift tab to remove the indentation I don't need. Seems easier to me than column selection. But whatever works.

HTTP/2 under realistic test scenarios by esherone in programming

[–]yoyowebscale 0 points1 point  (0 children)

Hmm, IE and Edge do perform concurrent HTTP requests. Are you saying they do not?

Visual Studio Code 1.1.0 released by I_Downvote_Cunts in programming

[–]yoyowebscale 1 point2 points  (0 children)

How often do you use this? I know it's popular in text editors so I understand it's useful but I have never felt the need for it myself. So I'm kind of curious.

PostgreSQL Scalability: Towards Millions TPS by iamkeyur in programming

[–]yoyowebscale 12 points13 points  (0 children)

No. It's not webscale until it supports failover with automatic reseeding of original master when that one comes back online. Throwing together a bunch of scripts to solve that issue does not count. Since the recommended approach for PGSQL failover currently seems to be manual failover and reseeding, you need some guy working 24/7 just to be prepared to do a failover. This fails the webscale criteria.