Played around with a bit. In my experience compared to a configured vim:
- once you have your local language servers available it works quite nicely out of the box. syntax highlighting, file finder, lsp navigation, formatting, etc. just works
- its fast
- i really like having the order of selection->action instead of action->movement
- im still missing some features like a navigation tree and a quickfix list or something to do project wide find/replace.
I've been a mac user for 12 years, have my current retina macbook for 4 years, consider myself a pro user and want to buy a new "mobile computer". I'm no longer considering buying an apple macbook. OS X is great but with these prices I can no longer validate it's value anymore and looking into buying an xps.
Yeah they've completely lost me with this update. Want a 15" model with 16GB RAM and a 512GB SSD (i.e., something that will last a reasonable amount of time)? Toss in AppleCare and you're looking at $3K. I have a mental barrier at around the $2200 mark -- I could afford it, but I just can't justify spending that much on a laptop with fairly pedestrian specs.
SOAP and WCF is a very scary thing. We're in the financial industry and many of the systems we integrate with use .NET and SOAP/WCF.
Although Visual Studio does all the heavy lifting for us via 'Add Service Reference', the sheer amount of boilerplate code generated when integrating a SOAP service is terrifying and bloated. We hope to migrate to ASP.NET 5 but we're not sure how well connectivity with SOAP services will be supported. One of our partners actually requires us to host our own SOAP service based on a spec they provide.
.NET WCF to another WCF integration is fine, but if you try and hook a .NET SOAP webservice to one written in Java, and you'll have pulled all of your hair out after two weeks. The reverse is just the same. They all have slightly different implementations of the specifications.
Make that one week if you have to start dealing with the monster that is called WS-* a.k.a. WS-WTF.
I like how both the student and the Startup hacker mess up bounds-checking, except the student doesn't realize it in the initial case, and the hacker misses it as the codebase gets progressively larger and he or she gets more tired.