111–120 of 207 posts
Love the idea that a Netscape-legacy language has traction there. I hope they don’t return to their pre-Nadella practices.
This is great news. Microsoft is adopting/forking Rust. That means Rust will be supported for all eternity.
Or at least Microsoft Visual R++
One reason of why I'm using Rust is because it's built by a group of people that I like, and Microsoft is not on that list.
However, I always keep a open-mind, I mean, I don't see anybody will be hurt if Microsoft become a direct contributor of Rust language itself. In fact, I could like Microsoft a bit if they did invest in Rust. I hope they do that instead of trying to fork things/build something alike (if that's the case here) (I watched their intro, their design is different than Rust and I somehow like what they did there).
Earlier quoted context omitted.
Microsoft already contributes to the Rust project; for example, Azure sponsors our CI.
Lol, they host our data so therefore they contribute. That is some next level Stockholm Syndrome.
This is great news. Microsoft is adopting/forking Rust. That means Rust will be supported for all eternity.
I really like the idea of implementing mutability control at the level of a collective as opposed to a single object. A great many transactions are multi-object. Love the idea that a Netscape-legacy language has traction there. I hope they don’t return to their pre-Nadella practices.
[1]: https://github.com/rust-lang/rust/issues/53488
[2]: http://smallcultfollowing.com/babysteps/blog/2018/04/16/rust...
Earlier quoted context omitted.
Microsoft already contributes to the Rust project; for example, Azure sponsors our CI.
Lol, they host our data so therefore they contribute. That is some next level Stockholm Syndrome.
(And this is just the most obvious and clear way that they support Rust, it’s not limited to that.)
Earlier quoted context omitted.
Why F# was needed in the first place? OCaml[1] is vastly superior, and doesn't require .NET since can be compiled into the native code. Just in the need of the better Windows platform support. And they add more features with time than F# devs.
I can add F# projects to existing solutions and use F# in some places, C# in others, and C++ in still others, heck even VB.NET can come by for a drink if I'm feeling shameless and not needing to keep up appearances. OCaml cannot do that. I say this as someone who currently is finishing a year of F# study with plans to study Rust in 2020 and OCaml in 2021.
Earlier quoted context omitted.
Big companies are not autonomous and do not make their own decisions, individual people working at those companies do. I think it’s safe to say that anyone working there today has nothing to do with the time periods you’re referencing, so I don’t know why you would consider decades old issues to be relevant today.
There was a medium post about Microsoft's culture and their inability to move on past Gates and Balmer about 6 weeks ago [1]. According to that article you are objectively wrong in saying "it’s safe to say that anyone working there today has nothing to do with the time periods you’re referencing". The article claims that the majority of the power within Microsoft still lays precisely in the hands of people who worked…
One example: "Microsoft is killing it. Revenue is up. Stock is up. Industry stature is up. The places where Microsoft finds itself thriving all have one thing in common: key made-men were pushed aside for better people."
Midori v2? http://joeduffyblog.com/2015/11/10/objects-as-secure-capabil...
This is great news. Microsoft is adopting/forking Rust. That means Rust will be supported for all eternity.
It is not like that. C was supported before GCC project also but it was not of any use because it wasn't widely used. Either we need open source alternatives or there must be competition based on open standards.
I’m pretty sure you’ve got your history backwards. GCC was created specifically to fill the need for a free C compiler for GNU. By that time C was already popular by association with Unix.