Amazon passwords:
https://github.com/search?utf8=%E2%9C%93&q=filename%3Aaws.ym...
Intel open sourced Stephen Hawking’s speech system
21–30 of 66 posts
Re: Intel open sourced Stephen Hawking’s speech system
#22Amazon passwords: https://github.com/search?utf8=%E2%9C%93&q=filename%3Aaws.ym...
wtf
Re: Intel open sourced Stephen Hawking’s speech system
#23Re: Intel open sourced Stephen Hawking’s speech system
#24Amazon passwords: https://github.com/search?utf8=%E2%9C%93&q=filename%3Aaws.ym...
wtf
think sagivo meant to respond to https://news.ycombinator.com/item?id=10072738
Re: Intel open sourced Stephen Hawking’s speech system
#25Re: Intel open sourced Stephen Hawking’s speech system
#26WinForms is still a great way to write desktop software if you don't need all the features of WPF, I just started a new project with it and have been really productive.
WinForms is still the easiest way to write desktop software quickly and easily. If you don't need a fancy UI for customer facing work, its a great platform for internal use.
Re: Intel open sourced Stephen Hawking’s speech system
#27WinForms is still a great way to write desktop software if you don't need all the features of WPF, I just started a new project with it and have been really productive.
WinForms is not simple. There are so many core classes that have counterintuitive edge-cases and overcomplicated behavior, and so many things you'd expect to work by default don't.
Databinding is a complete trainwreck, the Combo-box class is horribly overcomplicated by its double-duty as text-entry and drop-down-list, the DataGridView is a complete beast of leaky abstractions, and the layout engine completely falls apart if somebody alters the DPI unless you obsessively test DPI alterations yourself.
I don't blame Microsoft for any of this - it was 2000 and they were making a wrapper around some terrifying legacy code.
But this thing should have been tossed in the dustbin of history a long time ago.
Re: Intel open sourced Stephen Hawking’s speech system
#28Fun fact: the latest version of this software uses SwiftKey under the hood - http://swiftkey.com/en/blog/swiftkey-reveals-role-professor-... (Disclaimer: I used to work for SwiftKey)
As a loyal SwiftKey on Android user, the prediction engine for SwiftKey is unnervingly good. Glad to see it's put to a better use than helping me write Facebook and HN posts.
It begs the question though, why isn't there a proper SwiftKey keyboard for Windows? The OSK on 8.1 is awful compared to SwiftKey on Android. The Windows 10 is a improvement, but I'd still pay for a better one.
Re: Intel open sourced Stephen Hawking’s speech system
#29WinForms is still a great way to write desktop software if you don't need all the features of WPF, I just started a new project with it and have been really productive.
WinForms is still the easiest way to write desktop software quickly and easily. If you don't need a fancy UI for customer facing work, its a great platform for internal use.
... for some definition of "easiest." Maybe I would agree if you don't need to support a custom look-and-feel (Win32-looking apps don't really fly anymore), responsive layout, high DPI, touch/pen input, system theme colors, accessibility, localization, and haven't learned XAML.
WPF and UWP apps are both far easier.
Re: Intel open sourced Stephen Hawking’s speech system
#30WinForms is still a great way to write desktop software if you don't need all the features of WPF, I just started a new project with it and have been really productive.
WinForms is not simple. There are so many core classes that have counterintuitive edge-cases and overcomplicated behavior, and so many things you'd expect to work by default don't. Databinding is a complete trainwreck, the Combo-box class is horribly overcomplicated by its double-duty as text-entry and drop-down-list, the DataGridView is a complete beast of leaky abstractions, and the layout engine completely falls a…
Sure. But - serious question - what offering from Microsoft would you replace it with?