Live data from Hacker News

Visual Studio for Mac

msdn.microsoft.com

271–280 of 435 posts

Re: Visual Studio for Mac

#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 hate Java. Hope this and more steps make it easy to use C# and deploy in non-MS environments.

Re: Visual Studio for Mac

#273

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…

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

While this some truth in it, it is not what I took away from the discussion. Most people complain about the following:

* "I expected more."

* "I expected the price for the same specs to drop or at least stay constant but not to rise."

* "I cannot use this machine to do the work in the way I do it currently. This and that port is missing."

While there is a great deal of hate towards Apple, the comments I've read here are not driven by hate but by disappointment. The old MBP lineup was very good for these people. They like them very much. Some love Apple, some don't care but they all agree that the old hardware is very solid for a reasonable price.

I really do think that the new MBPs are good machines for >90% of the current MBP users. A bit more expensive but not too unreasonable given that most are locked into the Apple ecosystem. Some may need some adapters for things like digital cameras, projectors, monitors, USB sticks, keyboards etc. but that doesn't really matter to a true Apple customer. Most of the time the machine is used without those devices.

What Apple should worry a bit about, though, is, that the top 1-3% users are now looking for other hardware. But who am I to worry about Apples strategy. Probably they don't need those few powerusers anyways in their future business model. I don't even hold Apple stock currently. My old MBP runs fine still and I'm not locked into their ecosystem. I can move onto the greener lawn at any time.

Re: Visual Studio for Mac

#274
post #249

Earlier quoted context omitted.

Except that WinForms doesn't work on UWP applications other than via Project Centipede and is officially on support as it was communicated at BUILD 2014.

Of cause. My point is that so many business applications are Windows Forms, and will continue to be so for many years to come. Removing WinForms will disenfranchise a large group of developers, that for one reason or another, it could just be stubbornness, won't switch. Microsoft will sooner kill of WPF than WinForms, to not lose those developers. At least that's my belief. But we're talking for desktop applications…

I only use Windows Forms for legacy applications.

As for the official statement, here is the InfoQ overview of BUILD 2014.

https://www.infoq.com/news/2014/04/WPF-QA

"Windows Forms is continuing to be supported, but in maintenance mode. They will fix bugs as they are discovered, but new functionality is off the table. Oh, they stress that it isn’t called “WinForms”."

As I don't have time to search for the video on Channel 9.

The Roadmap for WPF

https://blogs.msdn.microsoft.com/dotnet/2014/11/12/the-roadm...

Re: Visual Studio for Mac

#279

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…

I, too, miss the good old days of splitting bytes into nibbles. Sometimes I program a microcontroller just to feel the walls moving in.

Software today is designed the way it is because developer time matters more than hardware specs. Getting the software to run and onto market is much more important than memory footprint. Very few companies worry about hiring an assembly programmer to quench out 10% performance. They don't even use C/C++ because it's that irrelevant. Before those programmers even finish the market has moved on and the product is obsolete.

People want the RAM because it is cheap and they can put it to good use for their data mining, video editing, virtual machines or whatever.

Re: Visual Studio for Mac

#280

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…

I interacted with one last week. That interaction confirmed everything I said earlier about the MBP (horrible keyboard, bad choices about ports, etc.).

I've been around the consumer tech industry a long time. I've shipped a considerable amount of consumer computing gear and am very familiar with the design process and the many tradeoffs that happen when you take something from a cool idea to heavy in someone's hands. One of the places I did this was Apple, in fact.

Apple seems to have decided to shift the market for the MBP by making tradeoffs that don't target any of the professionals I know.

I also know that (a) my predictions about the hardware were correct, and (b) none of the professionals I know plan to buy one, beyond the one or two samples we're getting into our group just to make sure we're making the right decision.

And now we're looking at Linux laptops in a serious way.

Professionals, yup.

Post reply on HN