121–130 of 177 posts
I remember when Microsoft teamed up with IBM on OS/2, so I'd predict that Microsoft comes out with its own brand of Linux within 5 years. That will give them time to learn what they need to include/exclude and support.
Earlier quoted context omitted.
C# and .Net the framework is objectively 'good'. ASP.Net MVC, is very subjective. It definitely is very 'weird' from the perspective of being on a static language platform but embracing 'magic' over standard type safety. I will give you routing though, i dont really think it 'sucks' but i have lead development teams using MVC for years... whenever a new developer who isnt familiar comes on board, the most significant…
It's not a problem of learning curve, it's that when you come from something like Jersey, it feels very limited.
Earlier quoted context omitted.
Our Dynamics reseller was adamant that we run it in-house. You could run it on Azure, but we don't recommend it. It's just not there yet.
I wonder if that is really true or: 1) The reseller doesn't know how it runs over Azure (I had this with vendors sticking to in-house Sharepoint vs Sharepoint online mostly from a "we don't know how" angle we found out) or 2) Does the reseller also make money from in-house vs on Azure? Like, their hardware? Anything like that? Just curious. I mean, he could also honestly think that Azure isn't there yet either. I cou…
I've seen folks spend 3-4x more money (almost all of the excess to the SAN vendor) to get a VMware setup (because snapshots and VMotions) with the same reliable I/O a commodity Dell server with a 4-disks SAS Raid-10 and a decent RAID controller can deliver, not even talking SSDs here.
A cloud provider that offers Linux and Windows, this is cutting edge.
Sure, it's not cutting edge, but it's one of a bunch of signs recently that Microsoft has turned over a new leaf in the last few years. Visual Studio's page now mentions Git, a GPLed piece of software built for Linux kernel development. They've come a long way from "GPL is cancer!"
They laid a lot of groundwork for mistrust, so they'll have to undo that, and it won't be quick or easy IMO.
Earlier quoted context omitted.
It's not a problem of learning curve, it's that when you come from something like Jersey, it feels very limited.
Jersey is a framework for REST services, the equivalent would be MS Web API, not ASP.NET MVC.
Earlier quoted context omitted.
With their release of CoreCLR[1], which combined with the class libraries, I think there is a lot of reason to look at .NET on UNIX. The implementation includes the same JIT and GC that the .NET framework uses, it just cuts out a bunch of bits that likely wouldn't be relevant to people developing server backends (WPF, AppDomains, etc.). For server stuff, .NET is now close to the level of openness and compatibility th…
You may be right, I don't know. I suppose the acid test is when YC companies start posting for front-end developers with C#, .NET and UNIX experience versus what's required today, i.e. either node.js, django, ruby, etc.
Earlier quoted context omitted.
Ubuntu was made the default instance on EC2 (even though EC2 is built on RHEL/CentOS/XenServer). That's were Canonical began to gain traction regarding installs, yet they still can't find a way to get users into support contracts en masse like Red Hat has been able to.
> Ubuntu was made the default instance on EC2 Citation needed. If Amazon Linux is still the default, you're wrong. It is based on CentOS, uses RPMs and yum.
I'm not fooling myself into seeing this as anything but a "you scratch my back, I'll scratch yours" setup. RedHat is getting a ton out of this, and so is Microsoft. Who's the main target for Azure? Enterprise companies who trust Microsoft implicitly. When an exec comes to the head of IT and says "we need to be on the cloud! I read about it!", Azure eases the transition by being able to go to vendor you've already bee…
I don't know about that, it all seems fairly logical. Don't forget that Microsoft is primarily a "business business" rather than a software business (ie. optimizing for business longevity above all else).
Microsoft appears to have practically perfected the game of "maintaining vendor lock-in in an otherwise open ecosystem". That game requires "giving in" at times, when it is no longer viable (in the long term) to compete with other options.
A good example of this is the open-sourcing of .NET. I don't believe for a second that this was a change of heart of a developer or even a team - it is far more likely that Microsoft is realizing the increasing shift away from Windows and .NET, and towards more 'open' platforms (whether Python, Node.js, Ruby, Golang, or whatever else).
It is in their best interest to make .NET open-source, as it allows them to maintain their foothold in the application development community - it still has direct integration with the rest of their products (and thus incentivizes picking MS as a vendor), but can now compete on openness.
You can see something similar for Windows 10, and it being given away for free. Both OS X and Linux are increasingly eating away at Windows' marketshare. By offering it for 'free' to existing Windows users (ie. nearly everybody), they can attempt to win users back, as it is now offered at the same price (in the eyes of the consumer).
Throughout the existence of Microsoft, they have consistently pushed the boundary of vendor lock-in and marketshare, trying to keep it as closed as possible but as open as necessary. The more recent decisions from Microsoft are not surprising to me at all - they are simply the result of a rapidly changing computing landscape. Microsoft hasn't changed, their environment has.
Earlier quoted context omitted.
With all due respect: I don't buy it. That isn't how the technology works. Compilation in particular would never even hit the hypervisor layer regardless of which one you were utilising. It is CPU/memory bound. The difference between hypervisors for IO is tiny. They're all slower than native, but vary very little between one another. That's why the manufacturers have all almost given up trying to use performance for…
You're missing something very significant: Compilation jobs involve a lot of forking. Forking, memory accesses, and TLB differences across various VM architectures can have an enormous impact on performance. For example, we found two orders of magnitude performance difference between PV and HVM on ec2 on fork-heavy CI jobs. A difference between 3 and 30 minutes. This difference is trivially reproducible by measuring…
also note that fork() involvs "lots of" io computations which could also be a driver problem and they evolved in newer kernels, too. and also fork() could syntactially be different on hosts with ballooning and hosts without. especially on kvm.
edit: as of today we switched to hvm instances (however we are on many many micros so that performance boost is likewise zero) on our inhouse hardware we are varying between kvm and vmware. however I dislike vmware more and more. vcenter is just unusable (flash) and consumes a shitload of memory. so mostly we use vmware api calls which makes vmware unnecessary somewhat. also we sell our software as a appliance with a xenserver host and mostly we tested our software an all ends and we are mostly disk io driven and that barely changes between them. there are some aspects that could improve performance but that depends more on how you configured your virtual disk.
Earlier quoted context omitted.
Jersey is a framework for REST services, the equivalent would be MS Web API, not ASP.NET MVC.
That's really a weird way of thinking about it. As something like Dropwizard demonstrates, it's a very good base for a web framework. Take Spring's routing, if you prefer, even that is better.