Alternatives to Xamarin Forms logo

Alternatives to Xamarin Forms

React Native, Flutter, Android Studio, Android SDK, and JavaScript are the most popular alternatives and competitors to Xamarin Forms.
346
277
+ 1
5

What is Xamarin Forms and what are its top alternatives?

Xamarin Forms is a popular open-source framework for building cross-platform mobile applications using C#. It allows developers to write code once and deploy it across multiple platforms, including iOS, Android, and Windows. Xamarin Forms provides a rich set of UI controls, native API access, and a robust ecosystem of plugins and extensions. However, some limitations include slower performance compared to native development, a larger app package size, and limited access to platform-specific features.

  1. Flutter: Flutter is a UI toolkit from Google for building natively compiled applications across mobile, web, and desktop from a single codebase. Key features include hot reload, a rich set of customizable widgets, and high performance. Pros include fast development speed, beautiful UIs, and a large community, while cons include a steeper learning curve for beginners.
  2. React Native: React Native is a popular framework from Facebook for building cross-platform mobile applications using JavaScript and React. It provides a rich set of components, native API access, and a strong developer community. Pros of React Native include fast development cycles, code reusability, and a large ecosystem of libraries, while cons include some performance limitations and occasional platform-specific bugs.
  3. NativeScript: NativeScript is an open-source framework for building cross-platform native mobile applications using JavaScript, TypeScript, or Angular. Key features include direct access to native APIs, UI flexibility, and code sharing between platforms. Pros include native performance, a rich plugin ecosystem, and support for Angular and Vue.js, while cons include a smaller community compared to other frameworks.
  4. Ionic: Ionic is a popular framework for building cross-platform mobile apps using web technologies like HTML, CSS, and JavaScript. It offers a rich set of UI components, native API access, and support for Progressive Web Apps. Pros of Ionic include fast development cycles, easy learning curve for web developers, and a large developer community, while cons include performance limitations compared to native apps.
  5. PhoneGap: PhoneGap is a mobile development framework from Adobe that allows developers to build cross-platform apps using web technologies like HTML, CSS, and JavaScript. Key features include simple development workflow, access to native device features, and support for multiple platforms. Pros of PhoneGap include easy integration with existing web skills, quick development cycles, and a large plugin ecosystem, while cons include performance limitations and the need for a webview container.
  6. Xamarin.iOS/Xamarin.Android: Xamarin.iOS and Xamarin.Android are part of the Xamarin platform that allows developers to build native iOS and Android apps using C#. Key features include direct access to native APIs, high performance, and code sharing with Xamarin Forms. Pros include native performance, full access to platform-specific features, and a familiar C# development environment, while cons include separate codebases for each platform and a potential learning curve for C# developers new to mobile development.
  7. Unity: Unity is a popular game development platform that can also be used to build interactive 2D/3D applications for mobile, web, and desktop. Key features include a powerful graphics engine, cross-platform support, and a large asset store. Pros of Unity include high performance, realistic visuals, and support for AR/VR experiences, while cons include a steep learning curve for non-gaming applications and a larger app package size.
  8. Adobe AIR: Adobe AIR is a runtime environment for building cross-platform desktop and mobile applications using web technologies like HTML, CSS, and JavaScript. Key features include access to native device capabilities, easy deployment, and support for iOS, Android, Windows, and macOS. Pros of Adobe AIR include quick development cycles, easy integration with existing web skills, and support for a variety of platforms, while cons include occasional performance limitations and dependency on Adobe's infrastructure.
  9. Appcelerator Titanium: Appcelerator Titanium is a platform for building cross-platform mobile applications using JavaScript, XML, and Alloy MVC. It provides access to native APIs, a rich set of UI components, and support for code reusability. Pros of Appcelerator Titanium include code sharing between platforms, native performance, and a strong focus on enterprise applications, while cons include a smaller community compared to other frameworks and a potentially steep learning curve.
  10. Corona SDK: Corona SDK is a development platform for building 2D games and other interactive applications for mobile and desktop. Key features include a lightweight runtime, rapid development cycles, and support for Lua scripting. Pros of Corona SDK include fast development speed, high performance, and easy monetization options, while cons include limited support for complex 3D games and a smaller community compared to larger frameworks.

Top Alternatives to Xamarin Forms

  • React Native
    React Native

    React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native. ...

  • Flutter
    Flutter

    Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android. ...

  • Android Studio
    Android Studio

    Android Studio is a new Android development environment based on IntelliJ IDEA. It provides new features and improvements over Eclipse ADT and will be the official Android IDE once it's ready. ...

  • Android SDK
    Android SDK

    Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Python
    Python

    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best. ...

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • HTML5
    HTML5

    HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997. ...

Xamarin Forms alternatives & related posts

React Native logo

React Native

33.8K
1.2K
A framework for building native apps with React
33.8K
1.2K
PROS OF REACT NATIVE
  • 214
    Learn once write everywhere
  • 174
    Cross platform
  • 169
    Javascript
  • 122
    Native ios components
  • 69
    Built by facebook
  • 66
    Easy to learn
  • 46
    Bridges me into ios development
  • 40
    It's just react
  • 39
    No compile
  • 36
    Declarative
  • 22
    Fast
  • 13
    Virtual Dom
  • 12
    Insanely fast develop / test cycle
  • 12
    Livereload
  • 11
    Great community
  • 9
    It is free and open source
  • 9
    Native android components
  • 9
    Easy setup
  • 9
    Backed by Facebook
  • 7
    Highly customizable
  • 7
    Scalable
  • 6
    Awesome
  • 6
    Everything component
  • 6
    Great errors
  • 6
    Win win solution of hybrid app
  • 5
    Not dependent on anything such as Angular
  • 5
    Simple
  • 4
    Awesome, easy starting from scratch
  • 4
    OTA update
  • 3
    As good as Native without any performance concerns
  • 3
    Easy to use
  • 2
    Many salary
  • 2
    Can be incrementally added to existing native apps
  • 2
    Hot reload
  • 2
    Over the air update (Flutter lacks)
  • 2
    'It's just react'
  • 2
    Web development meets Mobile development
  • 1
    Ngon
CONS OF REACT NATIVE
  • 23
    Javascript
  • 19
    Built by facebook
  • 12
    Cant use CSS
  • 4
    30 FPS Limit
  • 2
    Slow
  • 2
    Generate large apk even for a simple app
  • 2
    Some compenents not truly native

related React Native posts

Collins Ogbuzuru
Front-end dev at Evolve credit · | 42 upvotes · 308.1K views

Your tech stack is solid for building a real-time messaging project.

React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

See more
Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 4.2M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Flutter logo

Flutter

17.1K
1.2K
Cross-platform mobile framework from Google
17.1K
1.2K
PROS OF FLUTTER
  • 144
    Hot Reload
  • 124
    Cross platform
  • 106
    Performance
  • 90
    Backed by Google
  • 74
    Compiled into Native Code
  • 62
    Fast Development
  • 59
    Open Source
  • 53
    Fast Prototyping
  • 50
    Single Codebase
  • 48
    Expressive and Flexible UI
  • 37
    Reactive Programming
  • 35
    Material Design
  • 31
    Dart
  • 30
    Widget-based
  • 26
    Target to Fuchsia
  • 21
    IOS + Android
  • 17
    Easy to learn
  • 16
    Great CLI Support
  • 15
    You can use it as mobile, web, Server development
  • 14
    Tooling
  • 13
    Good docs & sample code
  • 13
    Have built-in Material theme
  • 13
    Debugging quickly
  • 12
    Community
  • 12
    Target to Android
  • 11
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 11
    Written by Dart, which is easy to read code
  • 10
    Easy Testing Support
  • 10
    Real platform free framework of the future
  • 9
    Target to iOS
  • 9
    Have built-in Cupertino theme
  • 8
    Easy to Unit Test
  • 8
    Easy to Widget Test
  • 1
    Large Community
CONS OF FLUTTER
  • 29
    Need to learn Dart
  • 11
    Lack of community support
  • 10
    No 3D Graphics Engine Support
  • 8
    Graphics programming
  • 6
    Lack of friendly documentation
  • 2
    Lack of promotion
  • 1
    Https://iphtechnologies.com/difference-between-flutter

related Flutter posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 4.2M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more

The only two programming languages I know are Python and Dart, I fall in love with Dart when I learned about the type safeness, ease of refactoring, and the help of the IDE. I have an idea for an app, a simple app, but I need SEO and server rendering, and I also want it to be available on all platforms. I can't use Flutter or Dart anymore because of that. I have been searching and looks like there is no way to avoid learning HTML and CSS for this. I want to use Supabase as BASS, at the moment I think that I have two options if I want to learn the least amount of things because of my lack of time available:

  1. Quasar Framework: They claim that I can do all the things I need, but I have to use JavaScript, and I am going to have all those bugs with a type-safe programming language avoidable. I guess I can use TypeScript?, but that means learning both, and I am not sure if I will be able to use 100% Typescript. Besides Vue.js, Node.js, etc.

  2. Blazor and .NET: There is MAUI with razor bindings in .Net now, and also a Blazor server. And as far as I can see, the transition from Dart to C# will be easy. I guess that I have to learn some Javascript here and there, but I have to less things I guess, am I wrong? But Blazor is a new technology, Vue is widely used.

See more
Android Studio logo

Android Studio

25.4K
361
Android development environment based on IntelliJ IDEA
25.4K
361
PROS OF ANDROID STUDIO
  • 176
    Android studio is a great tool, getting better and bet
  • 103
    Google's official android ide
  • 37
    Intelligent code editor with lots of auto-completion
  • 25
    Its powerful and robust
  • 5
    Easy creating android app
  • 3
    Amazing Layout Designer
  • 3
    Great Code Tips
  • 3
    Great tool & very helpful
  • 2
    Easy to use
  • 2
    Built in Emulator
  • 2
    Keyboard Shortcuts are Amazing Out of the box
CONS OF ANDROID STUDIO
  • 4
    Slow emulator
  • 4
    Huge memory usage
  • 2
    Using Intellij IDEA, while Intellij IDEA have too
  • 2
    Complex for begginers
  • 2
    No checking incompatibilities
  • 1
    Lags behind IntelliJ IDEA
  • 1
    Slow release process

related Android Studio posts

Julien DeFrance
Principal Software Engineer at Tophatter · | 8 upvotes · 450.1K views

As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.

Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.

Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.

After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.

After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.

Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.

See more
Gustavo Muñoz
Senior Software Engineer at JOOR · | 8 upvotes · 448.2K views

In my modest opinion, Flutter is the future of mobile development. The framework is as important to mobile as React is to the web. And seeing that React Native does not finish taking off, I am focusing all my efforts on learning Flutter and Dart. The ecosystem is amazing. The community is crazy about Flutter. There are enough resources to learn and enjoy the framework, and the tools developed to work with it are amazing. Android Studio or Visual Studio Code has incredible plugins and Dart is a pretty straight forward and easy-to-learn language, even more, if you came from JavaScript. I admit it. I'm in love with Flutter. When you are not a designer, having a framework focused on design an pretty things is a must. And counting with tools like #flare for animations makes everything easier. It is so amazing that I wish I had a big mobile project right now at work just to use Flutter.

See more
Android SDK logo

Android SDK

27.1K
800
An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
27.1K
800
PROS OF ANDROID SDK
  • 289
    Android development
  • 156
    Necessary for android
  • 128
    Android studio
  • 86
    Mobile framework
  • 82
    Backed by google
  • 27
    Platform-tools
  • 21
    Eclipse + adt plugin
  • 5
    Powerful, simple, one stop environment
  • 3
    Free
  • 3
    Больно
CONS OF ANDROID SDK
    Be the first to leave a con

    related Android SDK posts

    Jesus Dario Rivera Rubio
    Telecomm Engineering at Netbeast · | 10 upvotes · 1.2M views

    We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

    Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

    We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

    You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

    See more
    Sezgi Ulucam
    Developer Advocate at Hasura · | 7 upvotes · 963.1K views

    I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

    The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

    See more
    JavaScript logo

    JavaScript

    363.5K
    8.1K
    Lightweight, interpreted, object-oriented language with first-class functions
    363.5K
    8.1K
    PROS OF JAVASCRIPT
    • 1.7K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.2K
      Lots of great frameworks
    • 898
      Fast
    • 746
      Light weight
    • 425
      Flexible
    • 392
      You can't get a device today that doesn't run js
    • 286
      Non-blocking i/o
    • 237
      Ubiquitousness
    • 191
      Expressive
    • 55
      Extended functionality to web pages
    • 49
      Relatively easy language
    • 46
      Executed on the client side
    • 30
      Relatively fast to the end user
    • 25
      Pure Javascript
    • 21
      Functional programming
    • 15
      Async
    • 13
      Full-stack
    • 12
      Future Language of The Web
    • 12
      Setup is easy
    • 12
      Its everywhere
    • 11
      Because I love functions
    • 11
      JavaScript is the New PHP
    • 10
      Like it or not, JS is part of the web standard
    • 9
      Easy
    • 9
      Can be used in backend, frontend and DB
    • 9
      Expansive community
    • 9
      Everyone use it
    • 8
      Easy to hire developers
    • 8
      Most Popular Language in the World
    • 8
      For the good parts
    • 8
      Can be used both as frontend and backend as well
    • 8
      No need to use PHP
    • 8
      Powerful
    • 7
      Evolution of C
    • 7
      Its fun and fast
    • 7
      It's fun
    • 7
      Nice
    • 7
      Versitile
    • 7
      Hard not to use
    • 7
      Popularized Class-Less Architecture & Lambdas
    • 7
      Agile, packages simple to use
    • 7
      Supports lambdas and closures
    • 7
      Love-hate relationship
    • 7
      Photoshop has 3 JS runtimes built in
    • 6
      1.6K Can be used on frontend/backend
    • 6
      Client side JS uses the visitors CPU to save Server Res
    • 6
      It let's me use Babel & Typescript
    • 6
      Easy to make something
    • 6
      Can be used on frontend/backend/Mobile/create PRO Ui
    • 5
      Client processing
    • 5
      What to add
    • 5
      Everywhere
    • 5
      Scope manipulation
    • 5
      Function expressions are useful for callbacks
    • 5
      Stockholm Syndrome
    • 5
      Promise relationship
    • 5
      Clojurescript
    • 4
      Only Programming language on browser
    • 4
      Because it is so simple and lightweight
    • 1
      Easy to learn and test
    • 1
      Easy to understand
    • 1
      Not the best
    • 1
      Subskill #4
    • 1
      Hard to learn
    • 1
      Test2
    • 1
      Test
    • 1
      Easy to learn
    • 0
      Hard 彤
    CONS OF JAVASCRIPT
    • 22
      A constant moving target, too much churn
    • 20
      Horribly inconsistent
    • 15
      Javascript is the New PHP
    • 9
      No ability to monitor memory utilitization
    • 8
      Shows Zero output in case of ANY error
    • 7
      Thinks strange results are better than errors
    • 6
      Can be ugly
    • 3
      No GitHub
    • 2
      Slow
    • 0
      HORRIBLE DOCUMENTS, faulty code, repo has bugs

    related JavaScript posts

    Zach Holman

    Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

    But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

    But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

    Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 13.1M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Python logo

    Python

    246.3K
    6.9K
    A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
    246.3K
    6.9K
    PROS OF PYTHON
    • 1.2K
      Great libraries
    • 964
      Readable code
    • 847
      Beautiful code
    • 788
      Rapid development
    • 691
      Large community
    • 438
      Open source
    • 393
      Elegant
    • 282
      Great community
    • 273
      Object oriented
    • 221
      Dynamic typing
    • 77
      Great standard library
    • 60
      Very fast
    • 55
      Functional programming
    • 51
      Easy to learn
    • 46
      Scientific computing
    • 35
      Great documentation
    • 29
      Productivity
    • 28
      Easy to read
    • 28
      Matlab alternative
    • 24
      Simple is better than complex
    • 20
      It's the way I think
    • 19
      Imperative
    • 18
      Very programmer and non-programmer friendly
    • 18
      Free
    • 17
      Powerfull language
    • 17
      Machine learning support
    • 16
      Fast and simple
    • 14
      Scripting
    • 12
      Explicit is better than implicit
    • 11
      Ease of development
    • 10
      Clear and easy and powerfull
    • 9
      Unlimited power
    • 8
      Import antigravity
    • 8
      It's lean and fun to code
    • 7
      Print "life is short, use python"
    • 7
      Python has great libraries for data processing
    • 6
      Rapid Prototyping
    • 6
      Readability counts
    • 6
      Now is better than never
    • 6
      Great for tooling
    • 6
      Flat is better than nested
    • 6
      Although practicality beats purity
    • 6
      I love snakes
    • 6
      High Documented language
    • 6
      There should be one-- and preferably only one --obvious
    • 6
      Fast coding and good for competitions
    • 5
      Web scraping
    • 5
      Lists, tuples, dictionaries
    • 5
      Great for analytics
    • 4
      Easy to setup and run smooth
    • 4
      Easy to learn and use
    • 4
      Plotting
    • 4
      Beautiful is better than ugly
    • 4
      Multiple Inheritence
    • 4
      Socially engaged community
    • 4
      Complex is better than complicated
    • 4
      CG industry needs
    • 4
      Simple and easy to learn
    • 3
      It is Very easy , simple and will you be love programmi
    • 3
      Flexible and easy
    • 3
      Many types of collections
    • 3
      If the implementation is easy to explain, it may be a g
    • 3
      If the implementation is hard to explain, it's a bad id
    • 3
      Special cases aren't special enough to break the rules
    • 3
      Pip install everything
    • 3
      List comprehensions
    • 3
      No cruft
    • 3
      Generators
    • 3
      Import this
    • 3
      Powerful language for AI
    • 2
      Can understand easily who are new to programming
    • 2
      Should START with this but not STICK with This
    • 2
      A-to-Z
    • 2
      Because of Netflix
    • 2
      Only one way to do it
    • 2
      Better outcome
    • 2
      Batteries included
    • 2
      Good for hacking
    • 2
      Securit
    • 1
      Procedural programming
    • 1
      Best friend for NLP
    • 1
      Slow
    • 1
      Automation friendly
    • 1
      Sexy af
    • 0
      Ni
    • 0
      Keep it simple
    • 0
      Powerful
    CONS OF PYTHON
    • 53
      Still divided between python 2 and python 3
    • 28
      Performance impact
    • 26
      Poor syntax for anonymous functions
    • 22
      GIL
    • 19
      Package management is a mess
    • 14
      Too imperative-oriented
    • 12
      Hard to understand
    • 12
      Dynamic typing
    • 12
      Very slow
    • 8
      Indentations matter a lot
    • 8
      Not everything is expression
    • 7
      Incredibly slow
    • 7
      Explicit self parameter in methods
    • 6
      Requires C functions for dynamic modules
    • 6
      Poor DSL capabilities
    • 6
      No anonymous functions
    • 5
      Fake object-oriented programming
    • 5
      Threading
    • 5
      The "lisp style" whitespaces
    • 5
      Official documentation is unclear.
    • 5
      Hard to obfuscate
    • 5
      Circular import
    • 4
      Lack of Syntax Sugar leads to "the pyramid of doom"
    • 4
      The benevolent-dictator-for-life quit
    • 4
      Not suitable for autocomplete
    • 2
      Meta classes
    • 1
      Training wheels (forced indentation)

    related Python posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 13.1M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Nick Parsons
    Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 4.4M views

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    Node.js logo

    Node.js

    189.8K
    8.5K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    189.8K
    8.5K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 805
      Open source
    • 487
      Great for apis
    • 477
      Asynchronous
    • 425
      Great community
    • 390
      Great for realtime apps
    • 296
      Great for command line utilities
    • 86
      Websockets
    • 84
      Node Modules
    • 69
      Uber Simple
    • 59
      Great modularity
    • 58
      Allows us to reuse code in the frontend
    • 42
      Easy to start
    • 35
      Great for Data Streaming
    • 32
      Realtime
    • 28
      Awesome
    • 25
      Non blocking IO
    • 18
      Can be used as a proxy
    • 17
      High performance, open source, scalable
    • 16
      Non-blocking and modular
    • 15
      Easy and Fun
    • 14
      Easy and powerful
    • 13
      Future of BackEnd
    • 13
      Same lang as AngularJS
    • 12
      Fullstack
    • 11
      Fast
    • 10
      Scalability
    • 10
      Cross platform
    • 9
      Simple
    • 8
      Mean Stack
    • 7
      Great for webapps
    • 7
      Easy concurrency
    • 6
      Typescript
    • 6
      Fast, simple code and async
    • 6
      React
    • 6
      Friendly
    • 5
      Control everything
    • 5
      Its amazingly fast and scalable
    • 5
      Easy to use and fast and goes well with JSONdb's
    • 5
      Scalable
    • 5
      Great speed
    • 5
      Fast development
    • 4
      It's fast
    • 4
      Easy to use
    • 4
      Isomorphic coolness
    • 3
      Great community
    • 3
      Not Python
    • 3
      Sooper easy for the Backend connectivity
    • 3
      TypeScript Support
    • 3
      Blazing fast
    • 3
      Performant and fast prototyping
    • 3
      Easy to learn
    • 3
      Easy
    • 3
      Scales, fast, simple, great community, npm, express
    • 3
      One language, end-to-end
    • 3
      Less boilerplate code
    • 2
      Npm i ape-updating
    • 2
      Event Driven
    • 2
      Lovely
    • 1
      Creat for apis
    • 0
      Node
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 45
      New framework every day
    • 40
      Lots of terrible examples on the internet
    • 33
      Asynchronous programming is the worst
    • 24
      Callback
    • 19
      Javascript
    • 11
      Dependency hell
    • 11
      Dependency based on GitHub
    • 10
      Low computational power
    • 7
      Very very Slow
    • 7
      Can block whole server easily
    • 7
      Callback functions may not fire on expected sequence
    • 4
      Breaking updates
    • 4
      Unstable
    • 3
      Unneeded over complication
    • 3
      No standard approach
    • 1
      Bad transitive dependency management
    • 1
      Can't read server session

    related Node.js posts

    Shared insights
    on
    Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

    I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

    For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

    1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

    2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

    3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

    See more
    Anurag Maurya

    Needs advice on code coverage tool in Node.js/ExpressJS with External API Testing Framework

    Hello community,

    I have a web application with the backend developed using Node.js and Express.js. The backend server is in one directory, and I have a separate API testing framework, made using SuperTest, Mocha, and Chai, in another directory. The testing framework pings the API, retrieves responses, and performs validations.

    I'm currently looking for a code coverage tool that can accurately measure the code coverage of my backend code when triggered by the API testing framework. I've tried using Istanbul and NYC with instrumented code, but the results are not as expected.

    Could you please recommend a reliable code coverage tool or suggest an approach to effectively measure the code coverage of my Node.js/Express.js backend code in this setup?

    See more
    HTML5 logo

    HTML5

    149.9K
    2.2K
    5th major revision of the core language of the World Wide Web
    149.9K
    2.2K
    PROS OF HTML5
    • 447
      New doctype
    • 389
      Local storage
    • 334
      Canvas
    • 285
      Semantic header and footer
    • 240
      Video element
    • 121
      Geolocation
    • 106
      Form autofocus
    • 100
      Email inputs
    • 85
      Editable content
    • 79
      Application caches
    • 10
      Easy to use
    • 9
      Cleaner Code
    • 5
      Easy
    • 4
      Websockets
    • 4
      Semantical
    • 3
      Better
    • 3
      Audio element
    • 3
      Modern
    • 2
      Portability
    • 2
      Semantic Header and Footer, Geolocation, New Doctype
    • 2
      Content focused
    • 2
      Compatible
    • 1
      Very easy to learning to HTML
    CONS OF HTML5
    • 1
      Easy to forget the tags when you're a begginner
    • 1
      Long and winding code

    related HTML5 posts

    Jan Vlnas
    Senior Software Engineer at Mews · | 26 upvotes · 434.1K views
    Shared insights
    on
    HTML5HTML5JavaScriptJavaScriptNext.jsNext.js

    Few years ago we were building a Next.js site with a few simple forms. This required handling forms validation and submission, but instead of picking some forms library, we went with plain JavaScript and constraint validation API in HTML5. This shaved off a few KBs of dependencies and gave us full control over the validation behavior and look. I describe this approach, with its pros and cons, in a blog post.

    See more
    Jonathan Pugh
    Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 3.1M views

    I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

    For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

    Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

    I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

    I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

    I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

    I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

    For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

    For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

    For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

    I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

    So that's my latest mobile stack. What tools do you use? Have you tried these ones?

    See more