831 karma · joined November 21, 2014
I get that their duty is to their shareholders, but you have to draw a line at some point. I wouldn't want to work on tools of violence.
Try entering "undo" on Google Translate and see what it looks like in Dutch.
I worked on an anesthesia machine where the control systems were implemented with micro controllers and RTOS. The UI was Windows Embedded running on a separate x86 board and the whole thing would still safely operate even if the UI subsystem crashed. There were completely mechanical backup controls too.
But RDP solves different problems. I do UI development and use RDP to connect to my work box from home. It's also used on Windows Server for Citrix-type scenarios.
Seems silly to have one set of API's for small touch devices and a completely different one for large mouse-driven devices. Shuts the door to large touch devices and small mouse-driven devices.
iPad Pro is already awkward. At that size, a mouse would be nice, along with lots of other desktop UX paradigms.
> What has Microsoft shown with their multi-paradigm direction?
Seems to be working. Windows Shell, modern Office, Edge, and Xbox dashboard are all using the same UI framework.
Still supports C++ ;)
Promises are already there.
But but but telemetry is evil!
> many UX studies have shown that this applies to only a tiny percentage of users
Ironic because that's exactly the kind of thing telemetry is excellent for proving. It's quite useful for informing and providing quantitative feedback on UX.
What software dev doesn't think logs and crash dumps are useful?
Paying based on usage solves that tragedy of the commons problem and works for utilities.
What about people that produce heroine? Run casinos? Magic weight loss pills? Free-to-play games?
Still big in medical devices too, embedded or not.
*edit: ~16 MB for .Net Native, ~10 MB for C++ using latest VS2015 targeting x86.
Not going to matter for most apps, but for system UI that has to run on multi-user servers it does ;)
Contracts and some of the stuff in the new Core guidelines take it further.
Everyone's needs are different obviously. The stuff I work on has tons of users and start up perf and minimal memory usage are primary requirements. Most of our bugs are nullptr access violations or straight up programming errors that C# doesn't shield you from either.
Modern C++ is pretty nice if your team is ready to embrace it and leave old styles behind. I still use C# for utilities and prototypes but for production stuff, users' time is more valuable than mine.
Also really excited for co-routines. I never liked using promises.
Wow, had no idea ranges and contracts are on the table too. With all this stuff, C# is really losing its appeal.
Takes this to another degree for .Net. Enables deeper static analysis to catch more programming errors before runtime.