Alternatives to Android SDK logo

Alternatives to Android SDK

Android Studio, Ionic, React Native, Flutter, and Xamarin are the most popular alternatives and competitors to Android SDK.
26.7K
20.3K
+ 1
799

What is Android SDK and what are its top alternatives?

Android SDK is a set of tools and libraries provided by Google to develop applications for the Android platform. It includes tools for debugging, compiling, and testing Android applications. Key features of Android SDK include a comprehensive set of APIs for accessing Android platform features, a powerful debugger, and an emulator for testing applications on different devices. However, one limitation is that it can be complex for beginners to set up and use.

  1. React Native: React Native is a popular open-source mobile application framework created by Facebook. It allows developers to build cross-platform mobile applications using JavaScript. Key features include a large community of developers, hot-reloading for faster development, and reusable components. Pros include a faster development cycle and the ability to share code between iOS and Android apps. One con is that performance can sometimes be slower compared to native apps.
  2. Flutter: Flutter is Google's UI toolkit for building natively compiled applications for mobile, web, and desktop from a single codebase. Key features include a rich set of pre-built widgets, high-performance rendering engine, and hot reload for quick updates. Pros include fast development time and a smooth, native-like user experience. A con is that it may require learning Dart programming language.
  3. Xamarin: Xamarin is a Microsoft-owned framework for building cross-platform mobile applications using C#. Key features include access to native APIs, sharing code across platforms, and a large library of plugins. Pros include strong integration with Visual Studio and the ability to reuse existing C# skills. Cons may include a learning curve for C# developers new to mobile development.
  4. Ionic: Ionic is a popular framework for building hybrid mobile applications using web technologies like HTML, CSS, and JavaScript. Key features include a large library of UI components, a command-line interface for building and testing apps, and cross-platform compatibility. Pros include quick development time and a familiar web development environment. Cons include potential performance issues compared to native apps.
  5. NativeScript: NativeScript is an open-source framework for building truly native mobile applications using JavaScript or TypeScript. Key features include access to native APIs, a rich set of plugins, and support for Angular, Vue.js, or JavaScript frameworks. Pros include near-native performance and the ability to share code across platforms. A con is that it may require more manual configuration compared to other alternatives.
  6. PhoneGap: PhoneGap, now known as Apache Cordova, is an open-source framework for building hybrid mobile applications using web technologies. Key features include access to native device APIs, a large plugin ecosystem, and support for multiple platforms. Pros include quick development time and easy integration with existing web technologies. Cons may include potential performance limitations compared to native apps.
  7. Corona SDK: Corona SDK is a cross-platform framework for building 2D games and applications using Lua scripting language. Key features include a robust physics engine, real-time simulation, and a large collection of plugins and modules. Pros include fast development time for game development and easy deployment to multiple platforms. A con is that it may not be as suitable for complex, high-performance applications.
  8. Unity: Unity is a popular game engine that can also be used for building mobile applications on multiple platforms. Key features include a powerful graphics engine, support for 2D and 3D development, and an extensive asset store. Pros include a visual editor for easy development and support for multiple platforms. Cons may include a steeper learning curve compared to other alternatives.
  9. Qt: Qt is a powerful framework for building cross-platform applications using C++ or QML. Key features include a large library of components, native look and feel, and support for multiple platforms. Pros include high performance and the ability to create desktop applications in addition to mobile apps. A con is that it may not be as beginner-friendly as other alternatives.
  10. Kotlin Native: Kotlin Native is a technology that compiles Kotlin code to native binaries, allowing developers to build cross-platform native applications. Key features include seamless interop with native code, efficient memory management, and lightweight executables. Pros include the ability to share code between different platforms and high performance. A con may be the limited community support compared to other alternatives.

Top Alternatives to Android SDK

  • 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. ...

  • Ionic
    Ionic

    Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript. ...

  • 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. ...

  • Xamarin
    Xamarin

    Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language, to create mobile applications for the industry’s most widely-used mobile devices, including Android-based smartphones and tablets, iPhone, iPad and iPod Touch. ...

  • Corona SDK
    Corona SDK

    It is a cross-platform framework ideal for rapidly creating apps and games for mobile devices and desktop systems. It builds rich mobile apps for iOS, Android, Kindle and Nook. Build high quality mobile apps in a fraction of the time. ...

  • 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. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

Android SDK alternatives & related posts

Android Studio logo

Android Studio

25K
19.9K
361
Android development environment based on IntelliJ IDEA
25K
19.9K
+ 1
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

Gustavo Muñoz
Senior Software Engineer at JOOR · | 8 upvotes · 444.6K 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
Julien DeFrance
Principal Software Engineer at Tophatter · | 8 upvotes · 443.9K 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
Ionic logo

Ionic

9.4K
8.5K
1.8K
A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
9.4K
8.5K
+ 1
1.8K
PROS OF IONIC
  • 248
    Allows for rapid prototyping
  • 228
    Hybrid mobile
  • 208
    It's angularjs
  • 186
    Free
  • 179
    It's javascript, html, and css
  • 109
    Ui and theming
  • 78
    Great designs
  • 74
    Mv* pattern
  • 71
    Reuse frontend devs on mobile
  • 65
    Extensibility
  • 31
    Great community
  • 29
    Open source
  • 23
    Responsive design
  • 21
    Good cli
  • 14
    So easy to use
  • 13
    Angularjs-based
  • 13
    Beautifully designed
  • 12
    Widgets
  • 11
    Allows for rapid prototyping, hybrid mobile
  • 11
    Typescript
  • 10
    Quick prototyping, amazing community
  • 10
    Easy setup
  • 8
    Angular2 support
  • 7
    Fast, easy, free
  • 7
    Because of the productivity and easy for development
  • 7
    Base on angular
  • 7
    So much thought behind what developers actually need
  • 6
    Super fast, their dev team is amazingly passionate
  • 6
    Easy to use
  • 6
    It's Angular
  • 4
    UI is awesome
  • 4
    Hot deploy
  • 3
    Material design support using theme
  • 3
    Amazing support
  • 3
    It's the future
  • 3
    Angular
  • 3
    Allow for rapid prototyping
  • 3
    Easy setup, development and testing
  • 3
    Ionic creator
  • 2
    User Friendly
  • 2
    It's angular js
  • 2
    Complete package
  • 2
    Simple & Fast
  • 2
    Fastest growing mobile app framework
  • 2
    Best Support and Community
  • 2
    Material Design By Default
  • 2
    Cross platform
  • 2
    Documentation
  • 2
    Because I can use my existing web devloper skills
  • 2
    Removes 300ms delay in mobile browsers
  • 1
    Responsive
  • 1
    Native access
  • 1
    Typescript support
  • 1
    Ionic conect codeigniter
  • 1
    Fast Prototyping
  • 1
    All Trending Stack
CONS OF IONIC
  • 20
    Not suitable for high performance or UI intensive apps
  • 15
    Not meant for game development
  • 2
    Not a native app

related Ionic posts

Fernando Albertengo

I'm currently doing some research to build a full cross-platform system that our personnel will use for various management and selling purposes, this is just a first step to migrate (and clean, lots of cleaning) a gigantic and obsolete system made in Java 7 with a nightmarish coupling between logic and view layers.

Since the system itself is considerably large, we are currently migrating the essential modules of its logic to an ExpressJS driven Restful API.

As a complementary project, I must find a way to share the highest possible amount of view code while achieving said cross-platform capacity.

My approach is the following:

  • Angular 7+ and Ionic 5 for Android and iOS.
  • Angular 7+ for the web.
  • Angular 7+ and Electron for Desktop.

While Angular is the common part, and considering that Ionic can work on any platform, i'm wondering what is the best way to achieve a non-conflicting integration of Electron.js to the very-commonly-used Angular+Ionic Stack for both Mobile and Web development?

I've stumbled with a quite good template build called Polyonic but I would love to hear more about the matter before taking such a long-lasting decision.

See more
Bhupendra Madhu
Web Developer at Ecombooks · | 8 upvotes · 526.7K views

I want to learn cross-platform application frameworks like React Native, Flutter, Xamarin, or Ionic, and I'm a web developer. I can learn other programming languages as well. But I'm confused about what to learn, which framework is best, and which framework will last long as the application grows further into complexity.

See more
React Native logo

React Native

33.2K
28.8K
1.1K
A framework for building native apps with React
33.2K
28.8K
+ 1
1.1K
PROS OF REACT NATIVE
  • 213
    Learn once write everywhere
  • 173
    Cross platform
  • 168
    Javascript
  • 122
    Native ios components
  • 69
    Built by facebook
  • 65
    Easy to learn
  • 45
    Bridges me into ios development
  • 39
    No compile
  • 39
    It's just react
  • 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

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 4M 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

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

See more
Flutter logo

Flutter

16.5K
16.1K
1.2K
Cross-platform mobile framework from Google
16.5K
16.1K
+ 1
1.2K
PROS OF FLUTTER
  • 142
    Hot Reload
  • 121
    Cross platform
  • 104
    Performance
  • 89
    Backed by Google
  • 73
    Compiled into Native Code
  • 59
    Fast Development
  • 58
    Open Source
  • 53
    Fast Prototyping
  • 49
    Single Codebase
  • 48
    Expressive and Flexible UI
  • 36
    Reactive Programming
  • 34
    Material Design
  • 30
    Dart
  • 29
    Widget-based
  • 26
    Target to Fuchsia
  • 20
    IOS + Android
  • 17
    Easy to learn
  • 16
    Great CLI Support
  • 14
    You can use it as mobile, web, Server development
  • 14
    Tooling
  • 13
    Debugging quickly
  • 13
    Have built-in Material theme
  • 12
    Good docs & sample code
  • 12
    Target to Android
  • 12
    Community
  • 11
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 10
    Easy Testing Support
  • 10
    Written by Dart, which is easy to read code
  • 9
    Real platform free framework of the future
  • 9
    Have built-in Cupertino theme
  • 9
    Target to iOS
  • 8
    Easy to Unit Test
  • 8
    Easy to Widget Test
  • 1
    Large Community
CONS OF FLUTTER
  • 29
    Need to learn Dart
  • 10
    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 · 4M 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
Jose Luis Alvarado Ramirez

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
Xamarin logo

Xamarin

1.3K
1.5K
785
Create iOS, Android and Mac apps in C#
1.3K
1.5K
+ 1
785
PROS OF XAMARIN
  • 121
    Power of c# on mobile devices
  • 81
    Native performance
  • 79
    Native apps with native ui controls
  • 73
    No javascript - truely compiled code
  • 67
    Sharing more than 90% of code over all platforms
  • 45
    Ability to leverage visual studio
  • 44
    Mvvm pattern
  • 44
    Many great c# libraries
  • 36
    Amazing support
  • 34
    Powerful platform for .net developers
  • 19
    GUI Native look and Feel
  • 16
    Nuget package manager
  • 12
    Free
  • 9
    Backed by Microsoft
  • 9
    Enables code reuse on server
  • 8
    Faster Development
  • 7
    Use of third-party .NET libraries
  • 7
    It's free since Apr 2016
  • 7
    Best performance than other cross-platform
  • 7
    Easy Debug and Trace
  • 7
    Open Source
  • 6
    Mac IDE (Xamarin Studio)
  • 6
    Xamarin.forms is the best, it's amazing
  • 5
    That just work for every scenario
  • 5
    C# mult paradigm language
  • 5
    Power of C#, no javascript, visual studio
  • 4
    Great docs
  • 4
    Compatible to develop Hybrid apps
  • 4
    Microsoft stack
  • 4
    Microsoft backed
  • 3
    Well Designed
  • 3
    Small learning curve for Mobile developers
  • 2
    Ionic
  • 2
    Ability to leverage legacy C and C++
CONS OF XAMARIN
  • 9
    Build times
  • 5
    Visual Studio
  • 4
    Price
  • 3
    Complexity
  • 3
    Scalability
  • 2
    Nuget
  • 2
    Maturity
  • 2
    Build Tools
  • 2
    Support
  • 0
    Maturidade
  • 0
    Performance

related Xamarin posts

Greg Neumann
Indie, Solo, Developer · | 8 upvotes · 1.5M views

Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

See more
Bhupendra Madhu
Web Developer at Ecombooks · | 8 upvotes · 526.7K views

I want to learn cross-platform application frameworks like React Native, Flutter, Xamarin, or Ionic, and I'm a web developer. I can learn other programming languages as well. But I'm confused about what to learn, which framework is best, and which framework will last long as the application grows further into complexity.

See more
Corona SDK logo

Corona SDK

17
37
5
Cross-platform development platform for 2D apps and games
17
37
+ 1
5
PROS OF CORONA SDK
  • 3
    Also potentially build for OS Apple
  • 2
    Lua code better than java code
CONS OF CORONA SDK
  • 4
    Not Very popular
  • 2
    Very Poor System

related Corona SDK posts

JavaScript logo

JavaScript

354.8K
269.7K
8.1K
Lightweight, interpreted, object-oriented language with first-class functions
354.8K
269.7K
+ 1
8.1K
PROS OF JAVASCRIPT
  • 1.7K
    Can be used on frontend/backend
  • 1.5K
    It's everywhere
  • 1.2K
    Lots of great frameworks
  • 897
    Fast
  • 745
    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
    Setup is easy
  • 12
    Future Language of The Web
  • 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
    Everyone use it
  • 9
    Expansive community
  • 9
    Easy
  • 9
    Can be used in backend, frontend and DB
  • 8
    Easy to hire developers
  • 8
    No need to use PHP
  • 8
    For the good parts
  • 8
    Can be used both as frontend and backend as well
  • 8
    Powerful
  • 8
    Most Popular Language in the World
  • 7
    Evolution of C
  • 7
    Hard not to use
  • 7
    Versitile
  • 7
    Its fun and fast
  • 7
    Supports lambdas and closures
  • 7
    Love-hate relationship
  • 7
    Photoshop has 3 JS runtimes built in
  • 7
    Nice
  • 7
    It's fun
  • 7
    Popularized Class-Less Architecture & Lambdas
  • 7
    Agile, packages simple to use
  • 6
    Can be used on frontend/backend/Mobile/create PRO Ui
  • 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
  • 5
    Client processing
  • 5
    Everywhere
  • 5
    Scope manipulation
  • 5
    Function expressions are useful for callbacks
  • 5
    Stockholm Syndrome
  • 5
    Promise relationship
  • 5
    Clojurescript
  • 5
    What to add
  • 4
    Only Programming language on browser
  • 4
    Because it is so simple and lightweight
  • 1
    Easy to understand
  • 1
    Test
  • 1
    Test2
  • 1
    Subskill #4
  • 1
    Easy to learn
  • 1
    Hard to learn
  • 1
    Not the best
  • 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 · 11.3M 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
Git logo

Git

293.8K
175.9K
6.6K
Fast, scalable, distributed revision control system
293.8K
175.9K
+ 1
6.6K
PROS OF GIT
  • 1.4K
    Distributed version control system
  • 1.1K
    Efficient branching and merging
  • 959
    Fast
  • 845
    Open source
  • 726
    Better than svn
  • 368
    Great command-line application
  • 306
    Simple
  • 291
    Free
  • 232
    Easy to use
  • 222
    Does not require server
  • 27
    Distributed
  • 22
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Role-based codelines
  • 11
    Disposable Experimentation
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Github integration
  • 3
    Easy branching and merging
  • 2
    Compatible
  • 2
    Flexible
  • 2
    Possible to lose history and commits
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 1
    Light
  • 1
    Team Integration
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Easy
  • 1
    Flexible, easy, Safe, and fast
  • 1
    CLI is great, but the GUI tools are awesome
  • 1
    It's what you do
  • 0
    Phinx
CONS OF GIT
  • 16
    Hard to learn
  • 11
    Inconsistent command line interface
  • 9
    Easy to lose uncommitted work
  • 7
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    When --force is disabled, cannot rebase
  • 2
    Ironically even die-hard supporters screw up badly
  • 1
    Doesn't scale for big data

related Git posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 10M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Tymoteusz Paul
Devops guy at X20X Development LTD · | 23 upvotes · 9M views

Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

See more