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

371–380 of 435 posts

Re: Visual Studio for Mac

#371

Post by wlll »

grandalf wrote: post #346
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…

Do most developers really need anything with a CPU more powerful than an iPhone 5 to build apps or web pages? In most cases if they do they're doing it wrong.

It helps. No reason to artificially limit processing power available. If I spend seconds more waiting for my Go command line program to compile, or Rails to boot up, or a complex web page to load, or my VMs to respond, or Elasticsearch to boot etc. etc. it all adds up. It's time that I can spend doing other stuff.

Re: Visual Studio for Mac

#372

Post by chocks »

kenrick95 wrote: post #271
chocks wrote: post #268

link seems to be down - "We're sorry, the page you requested cannot be found"

I think it was an accidental post ahead of official announcement at Connect(); event on 19 November. Google cached version: https://webcache.googleusercontent.com/search?q=cache:Vk2On-...

cool. Thanks!

Re: Visual Studio for Mac

#374

Post by module0000 »

muninn_ wrote: post #202
brazzledazzle wrote: post #182

Earlier quoted context omitted.

I don't care about the touch bar and while I'm miffed about the magsafe I can deal with shelling out extra for accidental damage insurance. Personally my disappointment is with the specs which no time with the machine will change. The mac I'm currently using was purchased 3 years with 16GB of RAM and if I replace it I will be stuck with the same capacity. I imagine there are a lot of "Pro" market segments that are we…

The ram you were using 3 years ago is a lot slower than the ram they have put into the new MacBook pros. So there is that benefit at least. 32 GB is a lot of ram. What do you do where you need that much ram in a laptop? Is that the limiting factor in performance for you versus another component? Have you considered a desktop/tablet combo or anything like that?

There are a lot of use-cases for >16GB of RAM, but I'll share mine specifically. I develop network appliances for a "medium-to-large" enterprise. Specifically, these network appliances provide BGP, stateful packet filtering, and the other network services provided by our company's products.

When working on these appliances, I tend to spawn hundreds(close to 1000, but not more on my laptop due to RAM) of VM's, and each VM has between 4 and 48 virtual networks. Then all the appliances begin working, advertising and responding to BGP updates, setting up and tearing down VPN tunnels, and other test scenarios.

Right now, when I want to do this for network spec'd above size , I can't use my laptop. I end up having to provision hosts in one of our data centers just to get my work done. If my MBP had 20, 24, or 32GB(best!) of RAM, that wouldn't be the case. Maybe in 4 or 5 years, 32GB wont' be enough either, but right now I'm only concerned with the immediate. If the MBP's had grown in maximum memory(like other laptop vendor's models), this would have been a great improvement to my workflow, and allowed me to keep it local.

There are probably tons of more common use-cases for wanting all that RAM out there, but that one in particular is mine.

Re: Visual Studio for Mac

#375

Post by nkurz »

josephg wrote: post #242
brazzledazzle wrote: post #182

Earlier quoted context omitted.

I don't care about the touch bar and while I'm miffed about the magsafe I can deal with shelling out extra for accidental damage insurance. Personally my disappointment is with the specs which no time with the machine will change. The mac I'm currently using was purchased 3 years with 16GB of RAM and if I replace it I will be stuck with the same capacity. I imagine there are a lot of "Pro" market segments that are we…

I've spent the last 4 years doing development from a 2012 macbook air with 8 gigs of ram. Its been totally fine, except when I've got a million chrome tabs open. (Declaring bankrupcy and closing them all at once feels great though.) The posted article is about a mac version of visual studio. Coincidentally, visual studio only runs in 32 bit mode and hence can only make use of 4 gigs of ram total: https://blogs.msdn.m…

The atari 2600 had 128 bytes of RAM, and played all sorts of cool games.

I assumed first that this must be a typo for "128 kilobytes". But no, you are completely correct: 128 bytes. Wow!

Atari 2600 Teardown: https://www.ifixit.com/Teardown/Atari+2600+Teardown/3541

Re: Visual Studio for Mac

#376

Post by gurkendoktor »

ubernostrum wrote: post #169
static_noise wrote: post #118

Earlier quoted context omitted.

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 ev…

> 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".

Many of the complaints are about plain old hardware specs, especially RAM and the USB-C connectors. You don't need to hold a MacBook in your hands to understand how much RAM it has and how many dongles you'll need to buy. Same for complaints about the price.

Re: Visual Studio for Mac

#377

Post by module0000 »

josephg wrote: post #242
brazzledazzle wrote: post #182

Earlier quoted context omitted.

I don't care about the touch bar and while I'm miffed about the magsafe I can deal with shelling out extra for accidental damage insurance. Personally my disappointment is with the specs which no time with the machine will change. The mac I'm currently using was purchased 3 years with 16GB of RAM and if I replace it I will be stuck with the same capacity. I imagine there are a lot of "Pro" market segments that are we…

I've spent the last 4 years doing development from a 2012 macbook air with 8 gigs of ram. Its been totally fine, except when I've got a million chrome tabs open. (Declaring bankrupcy and closing them all at once feels great though.) The posted article is about a mac version of visual studio. Coincidentally, visual studio only runs in 32 bit mode and hence can only make use of 4 gigs of ram total: https://blogs.msdn.m…

VM's! We need the memory for VM's! Not all developers are "web developers", some of us make real things that those web devs take for granted.

Re: Visual Studio for Mac

#378

Post by robert_tweed »

bluetwo wrote: post #365
robert_tweed wrote: post #323

Earlier quoted context omitted.

Since popular HN submissions will often hug the site to death, a nice feature would be to automatically check the top 3 caches (archive.org, Coral, Google) immediately on submission, before the page goes live on HN. If the cache doesn't 404, the content could be quickly parsed to check it matches the submission and, if so, automatically include the cache link at the top of the submission page. This would save people…

Or, they could just have a live link AND a cache link and let people click what they want. A story with a cache link is likely to be upvoted more, encouraging people to do it.

I wasn't suggesting only displaying the cache link, but rather providing a list of alternate links (if available - not all sites allow archival, or the cache might be stale) so they are always there at the top of the page.

It's not exactly clear what is best netiquette regarding linking because larger sites that rely on advertising and can handle the traffic will welcome more clicks, but smaller sites would rather be cached. Better for HN not to encourage or discourage either, but give both options and let the readers decide.

Re: Visual Studio for Mac

#379

Post by dangero »

dep_b wrote: post #282
joeblau wrote: post #166

Earlier quoted context omitted.

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.

There goes good ol' anti Interface Builder rant again. The real problem is that Interface Builder is too easy to use while there's real depth and challenges to using it just like with doing everything in code. - Don't throw all your screens into one file, you can even use one screen per file just like xibs - Use code to style items and create controls you use more than once - Render all the controls in code dynamical…

IB is still not a good tool when there are a lot of people working on a project because the files do not merge easily.

I've had several people at Apple tell me they generally don't use interface builder internally.

Re: Visual Studio for Mac

#380

Post by zgramana »

thebeardedone wrote: post #38
jpalomaki wrote: post #15

Interesting, but I can also see some risks with their approach. Now they have three different Visual Studios with completely different technology stacks. 1) Visual Studio for Windows (C++, I assume?) 2) Visual Studio Code (Javascript, Atom) 3) Visual Studio for Mac (C#)

Hmm I have been googling for the last 15 minutes to find the difference between visual studio and visual studio code and cant seem to find a concrete answer. I thought yours was actually a hint at what it is aimed for but when you go to: http://code.visualstudio.com/ it actually says it supports c++,c#... I still dont get what the difference is.. Having only ever developed on linux I am actually slightly excited to u…

Lot of overlap, but VS Code has a much bigger ecosystem/community. Xamarin/Visual Studio has advanced debugging features like thread inspection, "immediate" console for executing commands while the program execution is paused, profiler, App Store submission, and stuff like T4 templates, etc.
Post reply on HN