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

401–410 of 435 posts

Re: Visual Studio for Mac

#401

Post by marmaduke »

stinos wrote: post #239
marmaduke wrote: post #138

Earlier quoted context omitted.

mac has word, osirix and freesurfer etc but I agree about posture

Not sure why you get downvoted for what is imo an ok reply? Only Osirix is strictly OSX and even though I haven't used it I'm pretty sure there are viable linux/windows alternatives for that and the other software you mention. Anyway, next time I see someone in a situation as I pictured I'll just ask why they chose the Macbook

Osirix is the only FDA approved software of its kind (MRI, 3D reconstruction, database), as far as I know.

Mac is the only platform where you can run freesurfer and word natively.

I didn't notice the downvotes..

Re: Visual Studio for Mac

#402

Post by badminton1 »

Clane wrote: post #119
badminton1 wrote: post #67

Earlier quoted context omitted.

does it support reverse debugging yet?

What I want to know as somebody trying to learn C/C++, is Xcode good for somebody who is wanting to try their hand at bare metal stuff? I always hear how bad it is outside of app dev. but can it help me be productive compared to CLI environment or just using a text editor with nifty add-ons?

Instruments, included with Xcode, is a really good tool. I used instruments for profiling and finding memory leaks... I think it was great... except for the lack of reverse debugging which is pretty much necessary these days.

I recommend this video to see some good example about reverse debugging with gdb. https://www.youtube.com/watch?v=713ay4bZUrw

Re: Visual Studio for Mac

#403

Post by zmarty »

danielhooper wrote: post #340
JonnieCache wrote: post #246

Earlier quoted context omitted.

The people who make film/game soundtracks need a LOT of ram, and fast disks, because they're using terabytes of samples in each project. Also massive has pretty low requirements. The main gripe musicians have with apple is the new OSX breaking their setup every year. The sandboxing in el capitan was particularly disastrous.

> because they're using terabytes of samples in each project. This is beyond hyperbole.

Not true, I work with projects where each minute of video is 8 GB. Multiply that with 100 or 120 and you are pretty much at 1 TB.

Re: Visual Studio for Mac

#404

Post by [deleted] »

danielhooper wrote: post #340
JonnieCache wrote: post #246

Earlier quoted context omitted.

The people who make film/game soundtracks need a LOT of ram, and fast disks, because they're using terabytes of samples in each project. Also massive has pretty low requirements. The main gripe musicians have with apple is the new OSX breaking their setup every year. The sandboxing in el capitan was particularly disastrous.

> because they're using terabytes of samples in each project. This is beyond hyperbole.

[deleted]

Re: Visual Studio for Mac

#405

Post by mcintyre1994 »

ciaranm wrote: post #347
mcintyre1994 wrote: post #157

Earlier quoted context omitted.

You can change that setting, and I imagine most developers who rely on function keys do, so no I'm not already doing that.

Well then it's still exactly the same? You can either press fn or change your preferences. You opted for the latter. Do that again?

So the touchbar has a setting where it behaves precisely like the current MBP? Esc, row of 12 keys, which are either f1-f12 or media with a setting, and are toggled between with fn? That's strictly worse if I only ever use it like that because it's the same but with soft keys, but sure that's basically the same.

Re: Visual Studio for Mac

#406

Post by ickler8 »

jsingleton wrote: post #181
maykr wrote: post #23

So as for now it is the rebranded and polished Xamarin Studio - hopefully, they have improved it's usability as in the past it was pretty lacking compared to VS 2013/2015

As I understand it, Visual Studio for Mac is simply a re-branded Xamarin Studio and will continue to be. It includes the improvements they had planned for the next release but I doubt they will do a rewrite. I actually prefer Xamarin Studio over Visual Studio (on Windows) in some respects. For example, the Xamarin.Forms XAML previewer is much better. Looking forward to a full designer. P.S. I've got a four part blog…

Visual Studio for Mac is a re-brand of Xamarin Studio. However, perhaps more importantly than the software itself, opening the Visual Studio brand to the mac environment signals Microsoft's commitment, yet again, to meeting developers in their chosen environment. Xamarin Studio is also based on MonoDevelop, so maybe this could accelerate a VS linux port, if they're so inclined.

Re: Visual Studio for Mac

#407

Post by ickler8 »

alex4Zero wrote: post #30
maykr wrote: post #23

So as for now it is the rebranded and polished Xamarin Studio - hopefully, they have improved it's usability as in the past it was pretty lacking compared to VS 2013/2015

I think Microsoft will end-of-life Xamarin Studio and will convert it to Visual Studio brand with just support of OSX and Linux

Thats what this move is. VS for Mac is a rebranded Xamarin Studio.

Re: Visual Studio for Mac

#408

Post by dep_b »

joeblau wrote: post #364
dep_b wrote: post #282

Earlier quoted context omitted.

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…

I've been using Xcode since iOS 2 and once Apple introduced IB for iOS, I was all for it. There are a bunch of challenges with IB that are outside of the solutions you proposed. How do you fix these issues? - Fixing misplaced views when transitioning from retina / non-retina screens or even different retina screen resolutions. Reasoning: When I worked at Amazon this was extremely annoying - You didn't even have to to…

> Fixing misplaced views when transitioning from retina / non-retina screens or even different retina screen resolutions.

No solution. Non-retina users should carefully commit :(

> Rendering Snapshots

I don't think I understand the problem. Nothing is stopping you from rendering just one of the view controllers alone?

> Setting all properties via IB

I'm doing more and more in code nowadays, including constraints that are also rendered in IB. Makes it easier to change things like ratios or heights all across the app.

Interface Builder then glues it all together and I can throw in some one-off items.

Re: Visual Studio for Mac

#409

Post by dep_b »

dangero wrote: post #379
dep_b wrote: post #282

Earlier quoted context omitted.

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.

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

I heard the same claims about Swift. I have no idea what to believe.

Re: Visual Studio for Mac

#410

Post by softweyr »

module0000 wrote: post #363
wolfgke wrote: post #210

Earlier quoted context omitted.

Why do you assume that software developers don't need more power and/or CUDA cores, too? Development does not only consist of web development.

"Web developers" should compile a browser(like Chromium) every so often, to provide themselves a reminder of the massive gap between what they do, and what "developers" do. Those CUDA cores and more CPU are very important to non-web-developers.

I've never needed a CUDA core at all, but then again I'm only a lowly kernel and network stack developer.
Post reply on HN