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

331–340 of 435 posts

Re: Visual Studio for Mac

#331

Post by youdounderstand »

ygra wrote: post #112
NicoJuicy wrote: post #96

Earlier quoted context omitted.

It's merged to Xaml not? And what do you want more for WPF? PS. According to me it was difficult to port the Graphic part of WPF to Linux/Mac.

XAML is just a way of writing object graphs in XML. It is not tied to WPF or anything (heck, we use it to represent user data and style information within GraphML). And yes, XAML is used by more than WPF at this point (Silverlight, UWP, and possibly more).

The markup is a pretty small part of XAML/WPF. The actual framework, controls, and rendering are the bulk of it.

Re: Visual Studio for Mac

#332

Post by vetinari »

coldtea wrote: post #220
sundvor wrote: post #177

Earlier quoted context omitted.

As a touch typist, can you please explain how that would work for me?

As a touch typist, can you please explain how function keys are particularly relevant to touch typing? Stepping through the debugger is not typing, and function keys change role according to the selected app anyway. And when they are system function keys (brightness, volume, etc) they are even more irrelevant to typing and/or touch typing. Besides, there's nothing particularly hard about finding a touch based F6 key…

There are many applications, that do use F-keys for shortcuts.

Not only debuggers, like others mentioned. But also some popular file managers (windows: Far, Total Commander; linux and osx: Midnight Commander).

When using these applications, I can copy files using F5 - and I know it is F5 without looking, because it is in the middle and has an empty space to the left. Similarly with F8 (delete) - in the right region, has space to the right.

With touch strip, you pretty much have to look away from the screen, onto the strip.

Re: Visual Studio for Mac

#333

Post by stephenr »

mmarx wrote: post #298
ubernostrum wrote: post #237

Earlier quoted context omitted.

IIRC the explanation is really "this is what Intel's stuff is supporting, and we're stuck with what Intel supports", and it would've been potentially another year or more of no MBP refresh if they waited for Intel to get there.

> IIRC the explanation is really "this is what Intel's stuff is supporting, and we're stuck with what Intel supports" All of the available CPUs support 32 GB; the i7s in the 15" model even support 64 GB. [0] http://ark.intel.com/products/91156/Intel-Core-i5-6360U-Proc... [1] http://ark.intel.com/products/88967/Intel-Core-i7-6700HQ-Pro...

They support > 16GB if you use DDR4. LPDDR3 is limited to 16GB.

Given that Apple maximises for long battery life/power efficiency/thin-ness (where heat = bad), I think they made the right decision.

There are very few people who genuinely need more than 16GB of RAM in a laptop computer.

Would I get 32GB if it was available? Yes. It would make my work a little easier (multiple VM environments), but it's hardly the end of the world on 16GB.

Re: Visual Studio for Mac

#334

Post by adamlett »

tw04 wrote: post #322
adamlett wrote: post #149

Earlier quoted context omitted.

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…

It kind of is... this reminds me very much of moving from a blackberry to an iPhone. Sure, the features of the iPhone were great, but for my (at the time) primary purpose of using the device for sending emails, it as a MASSIVE step backwards. I could touch type nearly as fast on a blackberry as on a regular keyboard. Moving to a touchscreen meant I had to look at the screen while typing. It slowed me down tremendousl…

It's an interesting comparison, but IMO not that apt. Going from a physical keyboard to a touch screen, something is definitely lost (even though much is also gained). The removal of the function keys will at worse force people to memorise different hot keys (any reason why the number row could not serve the same purpose exactly as well?), and at best it will make providers of IDEs and other productivity software revisit old assumptions, and improve the usability of their software.

Re: Visual Studio for Mac

#335

Post by 0xFFC »

delegate wrote: post #188

This is nice of course, but without C++ support it has very little appeal to me. I don't want to learn C# to write iOS apps. I might learn it just for fun, but I will continue writing the iOS apps with Swift/Objective-C and C++. C++ support is the weak spot of Xcode and so far I haven't found a suitable IDE for C++, except maybe Qt Creator and several IntelliJ-based IDEs, which are ok but not on par with Visual Studi…

Me too exactly, If I am doing something open source, then I use Emacs, but for developing projects I have windows machine just for visual studio.

Re: Visual Studio for Mac

#336

Post by arenaninja »

This is a huge step forward, as this means I don't have to buy a new laptop just to work with C# (I've been waiting for Black Friday just for this).

I wonder if this means SQL Server Express is coming as well, but that doesn't matter as much to me since I think Entity Framework takes care of working with a different database engine

Re: Visual Studio for Mac

#337

Post by acdha »

wolfgke wrote: post #210
intoverflow2 wrote: post #171

Earlier quoted context omitted.

Weirdly from your list software developers are the only ones the New MBP can serve. It's got plenty of power to run XCode or a web dev environment. Engineers, CAD, musicians, 3D artists all need more power than it provides and increasingly need CUDA cores.

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.

How many developers need more capacity than the new MacBook Pro but still less than the largest laptops offer? The few non-gamers I know who are still CPU/GPU-limited are using clusters of machines because no single machine is large enough and in most cases it's significantly cheaper to rent capacity for the few times when they need it rather than pay up-front for something which will be idle a fair percent of the year.

Re: Visual Studio for Mac

#338

Post by littlegreenb18 »

Clubber wrote: post #290
anupshinde wrote: post #272

This is great news! I was a c# developer for many years and absolutely loved it. But then I gave up the Microsoft ecosystem 7 years back just because it felt like a lock-in and also a bit backward compared to non-MS tech. But in the past one year, Microsoft has got me in again: a. Moved to TypeScript from JavaScript (including my hobby projects) b. Moved to VSCode from Sublime c. C# is a great language and I just hat…

C# is a lot different today than it was 7 years ago. You might be in for a shock. The nice thing is you can develop it today as you did 7 years ago, but with heavy use of lambdas and var, it reads almost like another language.

7 years ago was 2009. var, lambdas, and linq were already in pretty heavy use by then. The biggest change since then is the dynamic language runtime, but I don't really see that used much in c#.

Re: Visual Studio for Mac

#340

Post by danielhooper »

JonnieCache wrote: post #246
7Z7 wrote: post #223

Earlier quoted context omitted.

>..musicians,.. I'm running a Logic set up on my 2012 MBP, and I've never felt limited by its capabilities. I've been running Macs for music production for almost 20 years, and in my experience they have all at some point not had quite enough in the bag to let me do what I wanted of them. This is the first one (now fours years old) that has stayed ahead of my needs. I can run multiple copies of Massive, and rows of W…

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.

Post reply on HN