Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio for Mac

msdn.microsoft.com

Post reply on HN
Print view View original

161–170 of 435 posts

Re: Visual Studio for Mac

#161

Post by mcintyre1994 »

kriro wrote: post #73

Most interesting part for me: """For the functional programmers among you, it includes excellent F# support, powered by the same F# compiler used in Visual Studio.""" I've heard that F# is great from multiple people I trust a lot (and a quick cross check showed it does indeed look very cool) so I might give it a try once this is released. I do some C# development (Unity Engine stuff) on my Powerbook so this is also g…

F# is well supported by Visual Studio Code (with the Ionide plugin) too if you want to try it sooner.

Re: Visual Studio for Mac

#162

Post by rahoulb »

cm2187 wrote: post #25
SiVal wrote: post #17

So Microsoft is treating the Mac more seriously as a professional platform while Apple is treating it less seriously? I'm not saying this in a snarky way; I mean it literally as a change of corporate strategies in both companies. Microsoft seems to be saying, If you are a pro mainly using the Mac for professional work, we want to do a better job of empowering you, and Apple seems to be saying, If you are a pro mainly…

People aren't going to do development on a tablet or a smartphone anytime soon.

iPad Pro using MOSH into a Linux box running tmux and vim. A great development environment for me - 11 hour battery life, built in LTE connection, huge screen that I can layout how I want, easy to carry around with me and I can use it for drawing and sketching UI concepts for my clients before I start on any work.

I don't use it 100% of the time (I also have a desktop machine) but it works extremely well and offers me things that a laptop cannot.

EDIT: It also doesn't have an Escape key - but I use Ctrl-C in VIM as I don't have to move from the home position then

Re: Visual Studio for Mac

#163

Post by hvidgaard »

mobiuscog wrote: post #81
ubernostrum wrote: post #77

Earlier quoted context omitted.

Meanwhile, a "pro" user who's actually used the new Macbook Pro weighs in: http://www.huffingtonpost.co.uk/thomas-grove-carter/one-prof... Spoiler alert: he doesn't agree with the assessment of HN users who haven't actually used it.

Except he's coming at it with a strong bias: No matter what you think the specs say, the fact is the software and hardware are so well integrated it tears strips off "superior spec'd" Windows counterparts in the real world. This has always been true of Macs. Having used both lines of machines for many years, if I want raw power and 'specs' I use the PC.

His argument falls short the second you want to use non optimized software - he even touches upon this, but "I understand people need to use programs from other developers, but at some point they need to play catch up". This is rather difficult to take seriously. So you can efficiently do what Apple say you can do, but nothing else? That might work in his line of work, but it doesn't for the rest of the world.

Re: Visual Studio for Mac

#164

Post by wluu »

kriro wrote: post #73

Most interesting part for me: """For the functional programmers among you, it includes excellent F# support, powered by the same F# compiler used in Visual Studio.""" I've heard that F# is great from multiple people I trust a lot (and a quick cross check showed it does indeed look very cool) so I might give it a try once this is released. I do some C# development (Unity Engine stuff) on my Powerbook so this is also g…

This will essentially be a rebranded Xamarin Studio and tweaked to look more like VS for Windows. And Xamarin is basically based off MonoDevelop.

Re: Visual Studio for Mac

#165

Post by erikbye »

Nilzor wrote: post #97
erikbye wrote: post #65

Earlier quoted context omitted.

You do know the difference between a text editor and an IDE? That's the difference between VS Code and VS.

Do YOU know the difference? Would it hurt to be more concrete? I'm going to venture a guess based on my assumptions, which are probably wrong, but then we can at least start a discussion: -VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another -VS Code doesn't support runtime debugging (breakpoints) -VS Code doesn't have a visual editor -VS Code doesn't ha…

It would not hurt, but it would be an arduous and unnecessary task. Most people know the difference, and if you do not, you can read the Wikipedia article on IDE. There is no need to have a discussion on the differences, it is not remotely interesting or fruitful.

Re: Visual Studio for Mac

#166

Post by joeblau »

madeofpalk wrote: post #39
SiVal wrote: post #17

So Microsoft is treating the Mac more seriously as a professional platform while Apple is treating it less seriously? I'm not saying this in a snarky way; I mean it literally as a change of corporate strategies in both companies. Microsoft seems to be saying, If you are a pro mainly using the Mac for professional work, we want to do a better job of empowering you, and Apple seems to be saying, If you are a pro mainly…

If we're comparing Apples-to-Apples (seriously, pun not (originally) intended), Apple continues to rev on the XCode IDE every year adding more features to it. Most recently, they added a nifty visual memory debugger[1] and have taken another stab at device & certificate provisioning. [1]: http://useyourloaf.com/blog/xcode-visual-memory-debugger/

You're right, Apple is revving Xcode, but feature wise and bug wise, Xcode needs serious TLC especially on their Swift side. The regressions that are introduced every version don't help and tools like Interface builder, while seemingly helpful, usually make development within teams worse. I still use Xcode every day, but it defiantly needs hardening.

Re: Visual Studio for Mac

#167

Post by WildGreenLeave »

static_noise wrote: post #118
ubernostrum wrote: post #77

Earlier quoted context omitted.

Meanwhile, a "pro" user who's actually used the new Macbook Pro weighs in: http://www.huffingtonpost.co.uk/thomas-grove-carter/one-prof... Spoiler alert: he doesn't agree with the assessment of HN users who haven't actually used it.

That article is a typical example of "If it suits me, it must suit everybody." and your post is a good example for the no-true-Scotsman-fallacy of "Noone who _really_ used it dislikes it." All I really know about this is how I feel about it and I must admit that I am going to go back to the PC world when the time comes to replace my current MBP. The offerings in the PC world are not perfect for me but they suit me be…

Agreed, I love my Macbook Pro (2015 edition), however if I have to replace it in a few years I'm not buying the current Macbook Pro, instead I'll look for a comparable Windows laptop and put Linux on it. (If only there was a real Macbook competitor out there)

Re: Visual Studio for Mac

#168

Post by pschastain »

adamlett wrote: post #149
jmkni wrote: post #116

Earlier quoted context omitted.

If I'm debugging in an IDE or through a browsers developer tools, I absolutely use the function keys to step through/into/out of code. What should I do instead? Serious question.

Are you kidding me? How can you not see that this is nothing more than an arbitrary habit that you've grown comfortable with? Imagine the function keys had never existed to begin with. Don't you think we would have come up with a different way of stepping through code with a debugger? I understand that it's annoying to have to change your habits, but you're a developer for crying out loud: Your job is literally to ch…

> an arbitrary habit that you've grown comfortable with

You mean a workflow?

Who are you (or anyone else) to decide what works best for me? Am I not capable of making my own decisions? Do I really need a hardware company making those choices for me?

Re: Visual Studio for Mac

#169

Post by ubernostrum »

static_noise wrote: post #118
ubernostrum wrote: post #77

Earlier quoted context omitted.

Meanwhile, a "pro" user who's actually used the new Macbook Pro weighs in: http://www.huffingtonpost.co.uk/thomas-grove-carter/one-prof... Spoiler alert: he doesn't agree with the assessment of HN users who haven't actually used it.

That article is a typical example of "If it suits me, it must suit everybody." and your post is a good example for the no-true-Scotsman-fallacy of "Noone who _really_ used it dislikes it." All I really know about this is how I feel about it and I must admit that I am going to go back to the PC world when the time comes to replace my current MBP. The offerings in the PC world are not perfect for me but they suit me be…

That article is a typical example of "If it suits me, it must suit everybody."

99.9%+ of criticism of the new MBP has been of the form "Without ever interacting with one, I can tell it is unsuitable for me and therefore is unsuitable for anyone, anywhere, in any professional purpose, ever".

no-true-Scotsman-fallacy of "Noone who _really_ used it dislikes it."

More like "people are pre-emptively concluding, without ever having so much as been in the same room as a new MBP, that it is the antithesis of everything they need from a computer".

Which is, to put it bluntly, idiotic. I've suggested in the past that this feels less like "I have legitimate criticism of this product" and more like "I hate the manufacturer, always have hated and always will hate the manufacturer, and see this as a convenient cover for venting my hatred of the manufacturer". Notice how much of the criticism veers quickly away from specific aspects of the product and into "this is classic Apple", "this is how Apple treats users", "this is what's wrong with Apple", "Apple abandoning a key segment again", etc.

Re: Visual Studio for Mac

#170

Post by ldev »

Nilzor wrote: post #147
lloeki wrote: post #130

Earlier quoted context omitted.

Disclaimer: I'm not using the C# extension > VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another F2 "Rename Symbol" (works on Go with gorename). Can't imagine using Roslyn doesn't (or won't soon enough) allow the same. From the readme: Great C# editing support, including Syntax Highlighting, IntelliSense, Go to Definition, Find All References, etc. > VS…

>Obviously VS Code is not an IDE (as VS is) OBVIOUSLY? :D VS Code starts looking more and more like an IDE to me :-) Still looking forward to hear what people define as an IDE! Thank you for your detailed response by the way, not picking on your post, just curious what everybody finds so "unIDEish" about VS Code.

I stands for "Integrated" in IDE. Project generation, code inspection, source control, database access, refactoring, debugging, test running, etc are integrated.

Visual Studio Code generates project via third party tool - dotnet new. Refactoring, code completion is done via third party tool - Roslyn (?). Etc. It's an editor with plugins. Unlike Visual Studio or Jetbrains Rider.

Post reply on HN