ohyesyodo

You are probably getting downloads from the fact that your response did not make any sense.

I'm not sure if you are trolling, but you left out the actual transform. In my experience, XSLT feels optimized towards transforms, which most other languages aren't. I also dislike XSLT, but whenever I do things like this in Python, C# or C++ it tends to get more messy then my XLTS when the transforms are nontrivial.

Okay, so what am I supposed to use if I want to transform a XML file from one format to another because two different systems needs XML for input /output and they have different fixed formats?

This is just an incorrect assumption in my opinion. Say you are running on Microsoft Azure for example. There are no uptime SLA unless you run your service on at least two machines, because machines needs to reboot, be upgraded etc.

Also, if you take a look at perf when running PG on for example Azure or EC2, you will realize that IO is pretty slow but nodes are cheap. So you want to scale out early.

Running stuff on a single machine sounds like a perfect single point of failure to me. The actual size of the data does not affect wheter single point of failures are acceptable in a business.

I've seen so many people recommend PGSQL, saying its very simple, but when actually asked about how to set up a simple cluster which fulfills the absolutely basic requirements, then everyone just responds somethin similar to what you wrote. I find it very annoying to be honest.

Tell me how to set up a PG cluster where nodes can come and go as they like (for example without the need to reseed databases when they come online) in less than 30 minutes.

Turns out this was exactly what happened - they applied a buggy patch to all data centers at once by mistake.

The last two times there was a big issue the same thing happened with the status dashboard (it became inaccessible). I remember the same issue when the certs expired 1,5 years ago. I really like Microsoft and was convinced "you" would somehow isolate the dashboard and host it separately, but it turns out I was wrong. Do you happen to know the reasons for hosting the status dashboard inside of Azure? It seems so counter-intuitive to me. Or is it actually hosted externally but died due to the load when the issue started to appear?

The OP mentions that Microsoft representatives gave info via public forums. When the issue appeared I looked in different places trying to find info, but only I found was a statement saying that We are aware of issues. I looked at Azure twitter/blog, ScottGu twitter/blog, Hanselmans, MSDN forums. I also tried this forum and reddit. Do you know where I should have gone to receive details?

How about not rolling out a patch to all data centers at once?

What I've seen from their patching of ordinary machines, I would say its pretty far from controlled or well thought through. Their patching has led to our machines becoming unavailable before, despite that we have multiple machines in the same availability set. We've been in contact with support to describe what happens and have gotten an Oh, its by design-response back.

Hmm. You should be using CNAME records rather than IP addresses. Or are you using the new fixed IP features?

Just apply same buggy network patch to all DCs at once? They use software networking so causing something like this should be easy. Or mess up network routing for *.blob.core.windows.net which pretty much all of Azure relies on.

Status page is completely broken. I have been refreshing for an hour and seen like 5 different variants of information and all have been incorrect.

According to status page a fix has been applied, but DNR is still down. Maybe they have to spin up a couple of VMs..

If you dont care about robustness, not losing data, etc there are a lot of great databases out there.

It's not SQL Server, it's SQL Database. There are many large differences between the two.

A 50GB database with 10GB of RAM usage and 2 cores costs 700USD/Mo with SQL Database. This is replicated twice within DC. Double that price if you want georedundancy. Their entry level costs less but is also unusable for most real applications

I'm sure you are not the only one, but why wouldn't the prison do that?

I visited the site on my Windows Phone 8.1, and the page is rendered incorrectly. There's white text on white background, different text sections overlapping eachother, columns being one word wide and lot of more things. According to other comments here, it is unusable on iphone and broken on android as well. According to issues in their tracker, it does not work on Windows 8/Firefox and Ubuntu/Firefox.

It also renders incorrectly on Chrone om Windows 8 (on my laptop, at least).

If you're creating a new CSS framework, publish it and fail to mention that it's work in progress and it only works on a limited set of platforms (like what), you have wasted my time.

I really hope developers doesn't expect to only get constructive feedback when doing something like that.

I've been writing c++ on and off since Visual Studio 6. I would be glad to see it move faster. I don't have to learn all esoteric things - I can pick and use parts which I like, such as auto, for-each, smartptr, lambdas and so on. There was a version 2003 and then C++11. Almost a decade later. How can that possibly be too fast?

I generate a one-time card number for each online purchase. Only valid for a specific time and up to a specific account. Supporter by some banks. Pretty good solution in my opinion.

I will say huge props when they actually remove it. Not when they just remove the fallback.

Email configuration on Windows Phone is very confusing in my opinion.

Your last sentence is the answer to the first.

Hmm I could live a year off my savings, but shouldn't you be insured? If I lose my job tomorrow I get 3500 USD/month for a year. I pay 10 USD/month for this insurance. (Backed by the government). Don't you normally do it like this in the US? Where I live all people get an insurance like this. Or is this pretty much the same as social security?

Trying to be ironic? That page does not present an easy way to set up what I asked for.

No. He said that it was the 'default' way of doing it. Yes, it has happened X times, that does not mean it's the default way of doing it. Maybe there's some other method which is done a lot more often and hence should be considered the 'default' way.

Source for that?

There are robust ways to do this. The fact that some choose to implement their own buggy protocols for it does not mean that I do not want it. I use automatic failover with SQL Server today (and has been for years). I don't like the idea of getting up in the middle of the night to acknowledge some hardware error to initiate a failover.

Synchronous replication with automatic failover?

Can't agree. You don't need a ton of data to run into perf issues if you are running on slow commodity hardware for example in Azure. Nor does the lack of synchronous replication with automatic failover make your job easy. Considering the lack of features in PG in this area, running it in Azure seems like a no go to me. We currently had to pick SQL Server which has failover and so on which works great but costs a lot.

They already do I think? At least the default subreddit list (or whatever it calls - the subreddits shown top of screen) includes swedish subreddits when I'm not logged on.