5 ms·

I spent a lot of the earlier parts of my life hating MS, however later after working at a .NET shop and with the late developments at the company, my love for M

by zghst 10y ago

I spent a lot of the earlier parts of my life hating MS, however later after working at a .NET shop and with the late developments at the company, my love for MS is becoming near-infinite. Reactive is definitely the way to go

mmgutz 10y ago
It's strange but I went the other way. I started hating MS because of working in .NET. Basically, if something wasn't blessed by MS, it wasn't used. There were open source MVC projects but since MS only blessed ASP.NET forms back then, you couldn't convince managers to use MVC. Same with IoC. Same with ORMs I do like the new Microsoft. VS.Code is hands down the best all-around editor right now. TypeScript is awesome sauce.
- bobwaycott 10y ago
  I started here, too. First production app was an early C# ASP.NET OSHA safety management and training platform for Mohawk carpets, built from the ground up back in 2007-08. Experienced all these headaches. Next major project was Python-based. Never went back to .NET.
  - NicoJuicy 10y ago
    Asp.net forms was a monster. Asp.net Mvc was not
    - bobwaycott 10y ago
      The MVC variety was barely getting started when I was working at the time.
- shouldbworking 10y ago
  VSCode and Typescript are stellar. In the case of Typescript, possibly industry-changing long term. However, the .NET stack still suffers greatly from what you mentioned. The Microsoft world is like the Oracle world, you either use their stuff for everything or never touch it. I'm confident that .NET core will change this when it's mature enough, but that's still ~2 years away.
  - KurtMueller 10y ago
    > In the case of Typescript, possibly industry-changing long term. I feel that way about a related Microsoft product, F#. It's too bad that it doesn't get the same amount of love as Typescript. I think it's more powerful yet just as easy to use in almost every way - I never knew how powerful or expressive algebraic data types could be until I used F#.
    - NicoJuicy 10y ago
      Too bad nobody gives an example. Check out http://fsharp.github.io/FSharp.Data/ http://fsharp.github.io/FSharp.Data/ for an example why f# is 'powerful'
    - mattferderer 10y ago
      Repeating myself a bit in this thread. If you love F#, try checking out Fable &/or Reason. Fable compiles F# to JavaScript and Reason is Facebook's attempt at OCaml to JavaScript. F# !== Ocaml but F# == Ocaml
- daxfohl 10y ago
  I've gone, and continue to go, both ways simultaneously. They put a lot of effort into creating awesome experiences to bring developers on board. They also run a business that caters to clients who need "enterprisey" stuff backwards compatible with COBOL.NET or whatever and try to push that along with the good stuff. So it goes. I can't complain too much.
- scalatohaskell 10y ago
  > There were open source MVC projects but since MS only blessed ASP.NET forms back then, you couldn't convince managers to use MVC. Same with IoC. Same with ORMs but that's not really Microsoft's fault

by zghst 10y ago

mmgutz 10y ago

It's strange but I went the other way. I started hating MS because of working in .NET. Basically, if something wasn't blessed by MS, it wasn't used. There were open source MVC projects but since MS only blessed ASP.NET forms back then, you couldn't convince managers to use MVC. Same with IoC. Same with ORMs I do like the new Microsoft. VS.Code is hands down the best all-around editor right now. TypeScript is awesome sauce.

bobwaycott 10y ago
I started here, too. First production app was an early C# ASP.NET OSHA safety management and training platform for Mohawk carpets, built from the ground up back in 2007-08. Experienced all these headaches. Next major project was Python-based. Never went back to .NET.
- NicoJuicy 10y ago
  Asp.net forms was a monster. Asp.net Mvc was not
  - bobwaycott 10y ago
    The MVC variety was barely getting started when I was working at the time.
shouldbworking 10y ago
VSCode and Typescript are stellar. In the case of Typescript, possibly industry-changing long term. However, the .NET stack still suffers greatly from what you mentioned. The Microsoft world is like the Oracle world, you either use their stuff for everything or never touch it. I'm confident that .NET core will change this when it's mature enough, but that's still ~2 years away.
- KurtMueller 10y ago
  > In the case of Typescript, possibly industry-changing long term. I feel that way about a related Microsoft product, F#. It's too bad that it doesn't get the same amount of love as Typescript. I think it's more powerful yet just as easy to use in almost every way - I never knew how powerful or expressive algebraic data types could be until I used F#.
  - NicoJuicy 10y ago
    Too bad nobody gives an example. Check out http://fsharp.github.io/FSharp.Data/ http://fsharp.github.io/FSharp.Data/ for an example why f# is 'powerful'
  - mattferderer 10y ago
    Repeating myself a bit in this thread. If you love F#, try checking out Fable &/or Reason. Fable compiles F# to JavaScript and Reason is Facebook's attempt at OCaml to JavaScript. F# !== Ocaml but F# == Ocaml
daxfohl 10y ago
I've gone, and continue to go, both ways simultaneously. They put a lot of effort into creating awesome experiences to bring developers on board. They also run a business that caters to clients who need "enterprisey" stuff backwards compatible with COBOL.NET or whatever and try to push that along with the good stuff. So it goes. I can't complain too much.
scalatohaskell 10y ago
> There were open source MVC projects but since MS only blessed ASP.NET forms back then, you couldn't convince managers to use MVC. Same with IoC. Same with ORMs but that's not really Microsoft's fault