Announcement

Collapse
No announcement yet.

CSharpWebExpress and Making Bridge.Net More Popular

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    CSharpWebExpress and Making Bridge.Net More Popular

    Hello everyone,

    First, I would like to say that Bridge.Net is a fabulous product and I think that it should be much more popular.

    The main barrier to greater acceptance of Bridge.Net, I think, derives from the different cultural biases of desktop developers and web developers.

    Corporate desktop development has centered around Microsoft technologies for a long time now. In the past decade or so, the majority of new development uses Visual Studio and probably CSharp (although VB.Net is still in use). Desktop developers think in terms of widgets for their GUI.

    Web developers, in general, have followed a totally different learning curve and are very dismissive of Microsoft technologies. A typical Web developer is comfortable with Linux, probably uses a Mac or Linux PC, knows PHP, Ruby, Python (maybe Java) and immediately jumps to writing HTML/CSS when asked to create a GUI for a web application.

    So, here is the cultural disconnect.

    A developer using Visual Studio with Bridge.Net starts a project and presses "build". Of course, it works great but the output is JavaScript. And to use this JavaScript, he is going to have to use it within a framework - maybe ExtJS, React.js, Vue.js, or something else.

    I think that most desktop developers become very uncomfortable at this point.

    On the other hand, if a Web developer wanted to create JavaScript, he would use something like JetBrains WebStorm to do it, Or maybe, he is using Ruby-on-Rails or PHP Laravel with some add-ins that build the JavaScript for him.

    The cultural clash happens because MS developers are uncomfortable with Web technologies and Web developers don't want to use MS technologies.

    Bridge.Net is first and foremost a Microsoft-oriented technology.

    What I have attempted in CSharpWebExpress is to present Web components as CSharp widgets - you never have to interact with the underlying HTML, CSS, or JavaScript to build an application unless you explicitly want to.

    Given that there may be 2 million or so currently active CSharp developers and perhaps 3 billion+ HTML5 capable user devices, I think that there is potentially a huge market for Bridget.Net. Particularly given the recent sea-changes in Microsoft with regards to open source and Web development in general.

    #2
    Just if anyone wanted his example application is here: https://github.com/pdfisk/csharp_web_express_demo_app

    I agree with you, I also have been working on UI Frameworks:

    https://github.com/samuelGrahame/ExpressCraft
    https://github.com/samuelGrahame/ClassicForms

    Comment

    Working...
    X