281–290 of 327 posts
FYI, from the announcement. Probably the most important part at the end, italicized by me. Also note (elsewhere) that licenses are MIT and Apache2: .NET Core Tools Telemetry The .NET Core tools include a telemetry feature so that we can collect usage information about the .NET Core Tools. It’s important that we understand how the tools are being used so that we can improve them. Part of the reason the tools are in Pr…
After so many years microsoft finally presenting their tools in a more moden way. Never been a huge fan of .NET but i can't deny is a great tool hopefully people try it out on more platforms.
I still can't shake the feeling that their naming is just confusing. I still am not sure what exactly is .NET and what's not.
The main limitation has always been the need for a Windows host. I've never considered running a Windows-based server for Internet deployment of an app. However, .NET has managed to persist, and if MS is serious about making it cross-platform, I'm going to seriously consider it for my next project.
Earlier quoted context omitted.
It's still extremely buggy. Very difficult to get a .NET MVC app up and running (they're not using the term WebAPI anymore).
I also think they've made a terrible decision, the first-class support for DI is a bad direction which has made many simple concepts like config settings into absolute farces that take 5 lines of code. It's code "purity" over usability. It's putting the core dev team's principles over their customers actual need, completely violating KISS, DRY and YAGNI. DI really is our generation's factories. I'm already seeing pro…
Then maybe those programmers should go back to JS ES5?
Does anyone know if the changes planned to project.json are included in this?
Damn, I wanted to learn more so clicked Learn -> Get started with .NET Core and ... 404 Not the best start :-/ https://docs.microsoft.com/en-us/dotnet/core/index
Thats https://docs.microsoft.com/en-us/dotnet/articles/core/index
Earlier quoted context omitted.
You can go ahead with PostreSQL if you use Entity Framework and Code First approach. I used it many times and I was able to quickly jump from PostreSQL to MS SQL and back. It just works. With EF I don't see any reason why I should tie to any particular SQL database
Personally, I prefer writing SQL by hand. That way I know exactly what will happen in a query. A database really is an important component of a system and shouldn't be treated like a dumb data store where you just throw in any stuff you like through an ORM and hope it sticks there somehow.
Earlier quoted context omitted.
You reported the issue 11 days ago. I'm surprised they just announced it with such a basic use case being broken. It doesn't bode well for F# as a first class citizen in their ecosystem.
F# is not a first class citizen. They pay it lip service because it's a far more advanced language and makes MS look like they're on the cutting edge. Plus the team that made it is responsible for dragging the CLR into the modern era (or into the 60s) by bringing generics. And showing off important features on .NET such as quoted code, async workflows, F# interactive. But a simple look at tooling and language announc…
https://fsharp.tv/gazettes/f-the-most-highly-paid-tech-world...
Earlier quoted context omitted.
The Story of the Ribbon video about Microsoft and data driven design. https://www.youtube.com/watch?v=Tl9kD693ie4
The Ribbon is, in my opinion, the use interface equivalent of a broken pull tab on a can of corn. I know it is there, I know that I'm supposed to use it, but I can't because it is broken.
Earlier quoted context omitted.
F# is not a first class citizen. They pay it lip service because it's a far more advanced language and makes MS look like they're on the cutting edge. Plus the team that made it is responsible for dragging the CLR into the modern era (or into the 60s) by bringing generics. And showing off important features on .NET such as quoted code, async workflows, F# interactive. But a simple look at tooling and language announc…
> The results of the 2016 Stack Overflow Developer Survey are in! F# came out as the single most highly paid tech worldwide and is amongst the third top paying techs in the US https://fsharp.tv/gazettes/f-the-most-highly-paid-tech-world...
That's fine, but let's not think that this will produce tooling anywhere nearly as refined as C#'s stuff. Take F# interactive v the C# one. F# has like a decade lead. Yet the C# interactive editor is smooth, polished, even has VS project integration, something the F# team had thought of doing many years ago.
Non F#-team members[1] have said that internal politics are the issue here. To the point where some books were ... edited ... to paint C# in a better light, relatively. MS's marketing reflects this. My guess is they're too proud to admit their flagship language from their high-profile hire was shown up by what was a research project. And that the CLR's arguably biggest tech advantage over the JVM (generics) was also only done through the intense efforts of MSR; that MS Corp was against it.
It's sad, because MS is in a position to really elevate the world's programming consciousness/ability by really promoting F#, yet it's still a novelty for, as MS has said "scientific and engineering" applications. Yet, apart from tooling/legacy, F# handles every case C# does in a better way. At worst, it's C# with lighter syntax.
Oh well. At least it's there, works, and has some level of support. Only reason I consider using .NET these days.
1: The F# folks are amazingly polite and I've never heard them even hint at a complaint about MS.