3 ms·

My startup is based on Windows, the .NET Framework, ASP.NET for Web pages, and ADO.NET for interacting with SQL Server. For the programming language, I'm using

by graycat 10y ago

My startup is based on Windows, the .NET Framework, ASP.NET for Web pages, and ADO.NET for interacting with SQL Server. For the programming language, I'm using Visual Basic .NET -- as Kernighan and Ritchie, IIRC, stated in their C, the lanugage has an idiosyncratic syntax, which it turns ou I don't like. Since C# borrows some of that syntax, I prefer the more traditional (like PL/I, Pascal, Fortran, Algol, etc.) syntax of Visual Basic .NET. When I selected this collection of tools, I seemed to see that there were some big, famous, successful, busy Web sites using these tools. So far, I'm pleased with these tools but would like much better technical writing in the documentation. Some things about the tools are really nice. So far my code is about 100,000 lines of typing and about 25,000 programming language statements. I typed in all the code using my favorite text editor (KEdit) and have made no use of Visual Studio or any other integrated development environment. For me, KEdit and Rexx as a scripting language work fine. For a scripting language, I may convert over to Microsoft's Power Shell, but I see no big need to do that now. For organizing my work, I make heavy use of the Windows NTFS hierarchical file system -- it looks terrific, like some of Microsoft's and/or the industry's best software. For the CORE, I have no more than 15 seconds of understanding what the heck that is. AFAIK, I won't be using the CORE, whatever the heck it is.

nicostouch 10y ago
Congratulations on completely failing to answer the question.
- graycat 10y ago
  The question was about .NET Core, and I wrote about .NET which likely is closely related. It is likely that my use of .NET is also use of some of what is in .NET Core. So, I answered based on what I know about .NET which should be relevant to the question. Others can be more clear on what is the same, similar, or different between .NET and .NET Core. Then the parts of .NET Core that are also in .NET can get something of a clean bill of health from me.
  - frik 10y ago
    .NET core is a complete rewrite with incompatible API, it has little to do with the old .NET legacy framework. That's MSFT, one days hip API is tomorrows legacy cruft, you better stay on the edge or choose a stable non-MSFT open source solution.
    - graycat 10y ago
      Gads: I'm ordering the parts for my first server computer and about to put my code into alpha test, and already my tools are obsolete? Gads! Sounds like .NET Core is aimed mostly just at the Linux world or the mobile world or people who want to be able to run the same code on both Linux and Windows. But I'm staying with Windows desktop and Windows Server -- already spent too much on getting good enough with Windows. I have to suspect that Microsoft will continue to support Windows developers, including with VB.NET. If all Microsoft does with VB.NET is fix bugs, then fine with me. I'm not sure I have yet found a bug; so, fixing bugs in VB.NET should be easy enough for Microsoft. I'm not really a programmer; instead I'm an applied mathematician and business man who also writes software. Since this thread is about startups, the core of my startup is some applied math I derived -- and then programmed, with a Web site for the users. I would guess that if Microsoft wants all their major languages to run on both Windows and Linux, then that will be a lot of work and something for the future that I don't have to worry about. While I don't like the C# C-like syntax, I could use C# if I needed to. IIRC there is a source code translator from VB --> C# and, maybe, if possible, in the other direction. So, I could convert my code to C#. I suspect that I'm not the only developer who wants to continue with VB.NET and the .NET Framework as they have been for some years now. If the .NET Core is not relevant to such developers, then so be it, and that's not a good reason for Microsoft to abandon their old developers.
DaiPlusPlus 10y ago
For the past couple of years, VB.NET is becoming a deprecated second-class citizen language. While VB is supported by DNX, it isn't supported by ASP.NET Core (which can run on either DNX or the full NetFx). So you might want to consider your future language decisions in light of this.
deleted 10y ago
[deleted]

by graycat 10y ago

nicostouch 10y ago

Congratulations on completely failing to answer the question.

graycat 10y ago
The question was about .NET Core, and I wrote about .NET which likely is closely related. It is likely that my use of .NET is also use of some of what is in .NET Core. So, I answered based on what I know about .NET which should be relevant to the question. Others can be more clear on what is the same, similar, or different between .NET and .NET Core. Then the parts of .NET Core that are also in .NET can get something of a clean bill of health from me.
- frik 10y ago
  .NET core is a complete rewrite with incompatible API, it has little to do with the old .NET legacy framework. That's MSFT, one days hip API is tomorrows legacy cruft, you better stay on the edge or choose a stable non-MSFT open source solution.
  - graycat 10y ago
    Gads: I'm ordering the parts for my first server computer and about to put my code into alpha test, and already my tools are obsolete? Gads! Sounds like .NET Core is aimed mostly just at the Linux world or the mobile world or people who want to be able to run the same code on both Linux and Windows. But I'm staying with Windows desktop and Windows Server -- already spent too much on getting good enough with Windows. I have to suspect that Microsoft will continue to support Windows developers, including with VB.NET. If all Microsoft does with VB.NET is fix bugs, then fine with me. I'm not sure I have yet found a bug; so, fixing bugs in VB.NET should be easy enough for Microsoft. I'm not really a programmer; instead I'm an applied mathematician and business man who also writes software. Since this thread is about startups, the core of my startup is some applied math I derived -- and then programmed, with a Web site for the users. I would guess that if Microsoft wants all their major languages to run on both Windows and Linux, then that will be a lot of work and something for the future that I don't have to worry about. While I don't like the C# C-like syntax, I could use C# if I needed to. IIRC there is a source code translator from VB --> C# and, maybe, if possible, in the other direction. So, I could convert my code to C#. I suspect that I'm not the only developer who wants to continue with VB.NET and the .NET Framework as they have been for some years now. If the .NET Core is not relevant to such developers, then so be it, and that's not a good reason for Microsoft to abandon their old developers.

DaiPlusPlus 10y ago

For the past couple of years, VB.NET is becoming a deprecated second-class citizen language. While VB is supported by DNX, it isn't supported by ASP.NET Core (which can run on either DNX or the full NetFx). So you might want to consider your future language decisions in light of this.

deleted 10y ago

[deleted]