My journey with Rust in 2017 — The good, the bad, the weird
1–10 of 27 posts
Re: My journey with Rust in 2017 — The good, the bad, the weird
#21. Why are you're learning a language at the same time you're trying to launch an MVP? And a fairly involved language such as rust.
2. You're complaining about windows32 API being slow, but blaming it on .NET ("I don’t know if it was attributed to Windows or the application programmers, but I attributed Windows’ built-in functions with being slow and having shitty PDF output, which is why I refused to use anything related to Win32 or .NET").
Windows API is C (or internally C++).
3. Is display a bottleneck? I never developed GIS applications, but your display is 2D and doesn't have to be real-time. I would assume that the "back end" of the program is doing most of the calculations, and the display just outputs it (not like, say, a 3D game where the rendering engine does a significant chunk of its own work).
Re: My journey with Rust in 2017 — The good, the bad, the weird
#3I am wondering why the author didn't opt for a language/platform with a mature PDF and GUI library?
If I read the article correctly, it would have halved his development time...
Re: My journey with Rust in 2017 — The good, the bad, the weird
#4I started a reading the article expecting a critique of Rust, and I'm halfway through and it feels like I'm reading 2014-esque React philosophies on UI management.
Re: My journey with Rust in 2017 — The good, the bad, the weird
#51. Why are you're learning a language at the same time you're trying to launch an MVP? And a fairly involved language such as rust. 2. You're complaining about windows32 API being slow, but blaming it on .NET ("I don’t know if it was attributed to Windows or the application programmers, but I attributed Windows’ built-in functions with being slow and having shitty PDF output, which is why I refused to use anything re…
I did not get that as well.
Windows does not have PDF generation, its support has been recently introduced in Windows 10.
So most likely it was a third party library.
EDIT: It was actually introduced in Windows 10, not 8.
Re: My journey with Rust in 2017 — The good, the bad, the weird
#6Software taking half an hour to generate a PDF probably has nothing to do with the performance differences between bare metal and garbage collected languages.
Re: My journey with Rust in 2017 — The good, the bad, the weird
#71. Why are you're learning a language at the same time you're trying to launch an MVP? And a fairly involved language such as rust. 2. You're complaining about windows32 API being slow, but blaming it on .NET ("I don’t know if it was attributed to Windows or the application programmers, but I attributed Windows’ built-in functions with being slow and having shitty PDF output, which is why I refused to use anything re…
I did not get that as well. Windows does not have PDF generation, its support has been recently introduced in Windows 10. So most likely it was a third party library. EDIT: It was actually introduced in Windows 10, not 8.
> Windows does not have PDF generation, its support has been recently introduced in Windows 8.
does not compute
Re: My journey with Rust in 2017 — The good, the bad, the weird
#8Earlier quoted context omitted.
I did not get that as well. Windows does not have PDF generation, its support has been recently introduced in Windows 10. So most likely it was a third party library. EDIT: It was actually introduced in Windows 10, not 8.
> Windows does not have PDF generation, its support has been recently introduced in Windows 8. does not compute
OP was most likely using Windows 7 or earlier, from what I could understand.
Re: My journey with Rust in 2017 — The good, the bad, the weird
#91. Why are you're learning a language at the same time you're trying to launch an MVP? And a fairly involved language such as rust. 2. You're complaining about windows32 API being slow, but blaming it on .NET ("I don’t know if it was attributed to Windows or the application programmers, but I attributed Windows’ built-in functions with being slow and having shitty PDF output, which is why I refused to use anything re…
I did not get that as well. Windows does not have PDF generation, its support has been recently introduced in Windows 10. So most likely it was a third party library. EDIT: It was actually introduced in Windows 10, not 8.
Where's the Win8 PDF generation? I can't find it on MSDN. Unless we're talking about GDI print -> target "print to PDF"?
Re: My journey with Rust in 2017 — The good, the bad, the weird
#10Earlier quoted context omitted.
I did not get that as well. Windows does not have PDF generation, its support has been recently introduced in Windows 10. So most likely it was a third party library. EDIT: It was actually introduced in Windows 10, not 8.
Where's the Win8 PDF generation? I can't find it on MSDN. Unless we're talking about GDI print -> target "print to PDF"?
I was wrong. Actually it was only introduced in Windows 10.