What is GoLand and what are its top alternatives?
Top Alternatives to GoLand
- Java
Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! ...
- 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. ...
- 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. ...
- Golang
Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. ...
- Visual Studio Code
Build and debug modern web and cloud applications. Code is free and available on your favorite platform - Linux, Mac OSX, and Windows. ...
- IntelliJ IDEA
Out of the box, IntelliJ IDEA provides a comprehensive feature set including tools and integrations with the most important modern technologies and frameworks for enterprise and web development with Java, Scala, Groovy and other languages. ...
- WebStorm
WebStorm is a lightweight and intelligent IDE for front-end development and server-side JavaScript. ...
- Visual Studio
Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications. ...
GoLand alternatives & related posts
Java
- Great libraries589
- Widely used442
- Excellent tooling400
- Huge amount of documentation available388
- Large pool of developers available332
- Open source204
- Excellent performance200
- Great development155
- Vast array of 3rd party libraries149
- Used for android148
- Compiled Language60
- Used for Web49
- Managed memory46
- High Performance45
- Native threads44
- Statically typed43
- Easy to read35
- Great Community33
- Reliable platform29
- Sturdy garbage collection24
- JVM compatibility24
- Cross Platform Enterprise Integration21
- Universal platform20
- Good amount of APIs20
- Great Support18
- Great ecosystem14
- Lots of boilerplate11
- Backward compatible11
- Everywhere10
- Excellent SDK - JDK9
- Static typing7
- It's Java7
- Better than Ruby6
- Portability6
- Mature language thus stable systems6
- Cross-platform6
- Long term language6
- Clojure5
- Used for Android development5
- Vast Collections Library5
- Most developers favorite4
- Old tech4
- Javadoc3
- History3
- Testable3
- Great Structure3
- Stable platform, which many new languages depend on3
- Best martial for design3
- Faster than python2
- Type Safe1
- Verbosity32
- NullpointerException27
- Overcomplexity is praised in community culture16
- Nightmare to Write14
- Boiler plate code11
- Classpath hell prior to Java 98
- No REPL6
- No property4
- Non-intuitive generic implementation2
- There is not optional parameter2
- Code are too long2
- Floating-point errors2
- Returning Wildcard Types1
- Java's too statically, stronglly, and strictly typed1
- Terrbible compared to Python/Batch Perormence1
related Java posts











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
When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.
Node.js
- Npm1.4K
- Javascript1.3K
- Great libraries1.1K
- High-performance1K
- Open source801
- Great for apis485
- Asynchronous475
- Great community420
- Great for realtime apps390
- Great for command line utilities295
- Node Modules81
- Websockets81
- Uber Simple68
- Great modularity59
- Allows us to reuse code in the frontend58
- Easy to start42
- Great for Data Streaming35
- Realtime32
- Awesome28
- Non blocking IO25
- Can be used as a proxy18
- High performance, open source, scalable17
- Non-blocking and modular16
- Easy and Fun15
- Easy and powerful14
- Same lang as AngularJS13
- Future of BackEnd13
- Fullstack12
- Fast11
- Scalability10
- Cross platform10
- Simple9
- Mean Stack8
- Easy concurrency7
- Great for webapps7
- React6
- Friendly6
- Typescript6
- Fast, simple code and async6
- Easy to use and fast and goes well with JSONdb's5
- Fast development5
- Control everything5
- Great speed5
- Scalable5
- Its amazingly fast and scalable5
- It's fast4
- Isomorphic coolness4
- Easy to use4
- Less boilerplate code3
- Easy to learn3
- Easy3
- Great community3
- Not Python3
- Sooper easy for the Backend connectivity3
- Performant and fast prototyping3
- Blazing fast3
- TypeScript Support3
- Scales, fast, simple, great community, npm, express3
- One language, end-to-end3
- Npm i ape-updating2
- Event Driven2
- Lovely2
- Bound to a single CPU46
- New framework every day43
- Lots of terrible examples on the internet37
- Asynchronous programming is the worst30
- Callback23
- Javascript18
- Dependency hell11
- Dependency based on GitHub11
- Low computational power10
- Very very Slow7
- Can block whole server easily7
- Callback functions may not fire on expected sequence6
- Unneeded over complication3
- Unstable3
- Breaking updates3
- No standard approach2
- Bad transitive dependency management1
- Can't read server session1
related Node.js posts
When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?
So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.
React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.
Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.











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
Python
- Great libraries1.1K
- Readable code944
- Beautiful code833
- Rapid development777
- Large community682
- Open source426
- Elegant385
- Great community278
- Object oriented268
- Dynamic typing214
- Great standard library75
- Very fast56
- Functional programming51
- Scientific computing43
- Easy to learn42
- Great documentation33
- Matlab alternative26
- Productivity25
- Easy to read25
- Simple is better than complex21
- It's the way I think18
- Imperative17
- Very programmer and non-programmer friendly15
- Free15
- Powerfull language14
- Powerful14
- Machine learning support13
- Fast and simple13
- Scripting12
- Explicit is better than implicit9
- Clear and easy and powerfull8
- Unlimited power8
- Ease of development8
- Import antigravity7
- Print "life is short, use python"6
- It's lean and fun to code6
- Great for tooling5
- I love snakes5
- Flat is better than nested5
- Although practicality beats purity5
- High Documented language5
- Python has great libraries for data processing5
- Fast coding and good for competitions5
- There should be one-- and preferably only one --obvious5
- Rapid Prototyping4
- Readability counts4
- Web scraping3
- Now is better than never3
- Great for analytics3
- Plotting3
- Lists, tuples, dictionaries3
- Socially engaged community3
- Complex is better than complicated3
- Multiple Inheritence3
- Beautiful is better than ugly3
- CG industry needs3
- No cruft2
- Many types of collections2
- Easy to learn and use2
- Special cases aren't special enough to break the rules2
- If the implementation is hard to explain, it's a bad id2
- If the implementation is easy to explain, it may be a g2
- List comprehensions2
- Generators2
- Simple and easy to learn2
- Easy to setup and run smooth2
- Import this2
- Powerful language for AI1
- Because of Netflix1
- A-to-Z1
- Only one way to do it1
- Can understand easily who are new to programming1
- Flexible and easy1
- Better outcome1
- Batteries included1
- Good for hacking1
- Should START with this but not STICK with This1
- Pip install everything1
- It is Very easy , simple and will you be love programmi1
- Powerful0
- Still divided between python 2 and python 351
- Performance impact29
- Poor syntax for anonymous functions26
- GIL21
- Package management is a mess19
- Too imperative-oriented14
- Dynamic typing12
- Hard to understand12
- Very slow10
- Not everything is expression8
- Indentations matter a lot7
- Explicit self parameter in methods7
- No anonymous functions6
- Poor DSL capabilities6
- Incredibly slow6
- Requires C functions for dynamic modules6
- The "lisp style" whitespaces5
- Fake object-oriented programming5
- Hard to obfuscate5
- Threading5
- Circular import4
- The benevolent-dictator-for-life quit4
- Official documentation is unclear.4
- Lack of Syntax Sugar leads to "the pyramid of doom"4
- Not suitable for autocomplete4
- Meta classes2
- Training wheels (forced indentation)1
related Python posts











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
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
Golang
- High-performance531
- Simple, minimal syntax387
- Fun to write354
- Easy concurrency support via goroutines295
- Fast compilation times267
- Goroutines189
- Statically linked binaries that are simple to deploy177
- Simple compile build/run procedures148
- Backed by google134
- Great community131
- Garbage collection built-in50
- Built-in Testing42
- Excellent tools - gofmt, godoc etc41
- Elegant and concise like Python, fast like C38
- Awesome to Develop34
- Used for Docker25
- Flexible interface system24
- Deploy as executable22
- Great concurrency pattern22
- Open-source Integration19
- Fun to write and so many feature out of the box16
- Easy to read15
- Its Simple and Heavy duty14
- Go is God14
- Powerful and simple13
- Easy to deploy13
- Concurrency11
- Best language for concurrency11
- Rich standard library10
- Safe GOTOs10
- Clean code, high performance9
- Easy setup9
- Hassle free deployment8
- High performance8
- Simplicity, Concurrency, Performance8
- Single binary avoids library dependency issues7
- Used by Giants of the industry7
- Simple, powerful, and great performance6
- Cross compiling6
- Very sophisticated syntax5
- Garbage Collection5
- Gofmt5
- WYSIWYG5
- Excellent tooling5
- Widely used4
- Kubernetes written on Go4
- Keep it simple and stupid3
- No generics2
- Operator goto1
- You waste time in plumbing code catching errors41
- Verbose25
- Packages and their path dependencies are braindead22
- Dependency management when working on multiple projects15
- Google's documentations aren't beginer friendly15
- Automatic garbage collection overheads10
- Uncommon syntax8
- Type system is lacking (no generics, etc)6
- Collection framework is lacking (list, set, map)2
- Best programming language1
related Golang posts











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
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
Visual Studio Code
- Powerful multilanguage IDE331
- Fast295
- Front-end develop out of the box186
- Support TypeScript IntelliSense153
- Very basic but free138
- Git integration120
- Intellisense103
- Faster than Atom75
- Better ui, easy plugins, and nice git integration49
- Great Refactoring Tools42
- Good Plugins41
- Terminal40
- Superb markdown support36
- Open Source35
- Extensions31
- Awesome UI26
- Large & up-to-date extension community26
- Powerful and fast23
- Portable21
- Best code editor18
- Best editor17
- Easy to get started with16
- Crossplatform15
- Good for begginers15
- Built on Electron14
- Lots of extensions14
- Open, cross-platform, fast, monthly updates14
- All Languages Support13
- Extensions for everything13
- Extensible12
- "fast, stable & easy to use"11
- Git out of the box11
- Useful for begginer11
- Ui design is great11
- Easy to use and learn11
- Faster edit for slow computer11
- Totally customizable11
- Great community10
- Powerful Debugger9
- SSH support9
- Great language support9
- Fast Startup9
- It has terminal and there are lots of shortcuts in it9
- Works With Almost EveryThing You Need9
- Can compile and run .py files8
- Python extension is fast7
- Features rich7
- Great document formater7
- She is not Rachel6
- He is not Michael6
- Awesome multi cursor support6
- Very proffesional5
- Easy azure5
- Language server client5
- Extension Echosystem5
- SFTP Workspace5
- VSCode.pro Course makes it easy to learn5
- Has better support and more extentions for debugging4
- Excellent as git difftool and mergetool4
- Virtualenv integration4
- 'batteries included'3
- Better autocompletes than Atom3
- Supports lots of operating systems3
- Has more than enough languages for any developer3
- Emmet preinstalled3
- More tools to integrate with vs3
- VS Code Server: Browser version of VS Code2
- CMake support with autocomplete2
- Light2
- Microsoft2
- Customizable2
- Fast and ruby is built right in2
- Big extension marketplace1
- Slow startup44
- Resource hog at times27
- Poor refactoring20
- Poor UI Designer13
- Microsoft13
- Weak Ui design tools11
- Poor autocomplete10
- Poor in PHP7
- Huge cpu usage with few installed extension7
- Super Slow6
- Microsoft sends telemetry data5
- No Built in Browser Preview3
- No built in live Preview3
- Very basic for java development and buggy at times3
- No color Intergrator3
- Poor in Python3
- It's MicroSoft2
- Bad Plugin Architecture2
- Electron2
- Terminal does not identify path vars sometimes1
- Powered by Electron1
related Visual Studio Code posts
























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.
I've been in the #frontend game for about 7 years now. I started coding in Sublime Text because all of the tutorials I was doing back then everyone was using it. I found the speed amazing compared to some other tools at the time. I kept using Sublime Text for about 4-5 years.
I find Sublime Text lacks some functionality, after all it is just a text editor rather than a full fledged IDE. I finally converted over to PhpStorm as I was working with Magento and Magento as you know is mainly #PHP based.
This was amazing all the features in PhpStorm I loved, the debugging features, and the control click feature when you click on a dependency or linked file it will take you to that file. It was great.
PhpStorm is kind of slow, I found that Prettier was taking a long time to format my code, and it just was lagging a lot so I was looking for alternatives. After watching some more tutorial videos I noticed that everyone was using Visual Studio Code. So I gave it a go, and its amazing.
It has support for everything I need with the plugins and the integration with Git is amazing. The speed of this IDE is blazing fast, and I wouldn't go back to using PhpStorm anymore. I highly recommend giving Visual Studio Code a try!
- Fantastically intelligent299
- Best-in-class ide242
- Many languages support190
- Java156
- Fast121
- Code analysis82
- Reliable78
- Out of the box integration with maven, git, svn76
- Plugin architecture64
- Integrated version control61
- Code refactoring support12
- Best java IDE11
- Local history7
- Integrated Database Navigator6
- Built-in terminal/run tools6
- Code Completion6
- All5
- Base for Android Studio5
- Kotlin5
- Free for open-source development, students and teacher5
- Free If you're a Student5
- Database/Code integration4
- Cross platform4
- IDE4
- ERD Diagrams4
- Free4
- Vim support3
- Column Selection Mode3
- Server and client-side debugger3
- More than enough languages for any developer3
- Typescript support3
- Multicursor support3
- Reformating Code3
- Intuitive3
- Command-line tools3
- Android Integration3
- Out Of The Box features3
- Special icons for most filetypes in project list3
- Supports many frameworks3
- Built-in web server3
- Live Templates3
- Scala support3
- A lot of plugin2
- Just works2
- Integrated Ssh/Ftp Managers2
- Full support2
- Task managers2
- Diff tools2
- File Watchers2
- Support for various package managers2
- Integrated Code Linting2
- Clean UI2
- Open source2
- So modernised2
- Efficient, one Stop solution2
- Works fine with mac os catalina2
- Large footprint required to really enjoy (mem/disc)18
- Very slow14
- Bad for beginners7
- UI is not intuitive6
- Not nearly as many tools to integrate as vs code5
- Constant reindexing4
- Needs a lot of CPU and RAM power3
- Built in terminal is slow2
- Doesn't work that well with windows 10 edu2
- Ruby is a plug in1
- Pesky warnings increase with every release1
- AAD0
related IntelliJ IDEA posts
UPDATE: Thanks for the great response. I am going to start with VSCode based on the open source and free version that will allow me to grow into other languages, but not cost me a license ..yet.
I have been working with software development for 12 years, but I am just beginning my journey to learn to code. I am starting with Python following the suggestion of some of my coworkers. They are split between Eclipse and IntelliJ IDEA for IDEs that they use and PyCharm is new to me. Which IDE would you suggest for a beginner that will allow expansion to Java, JavaScript, and eventually AngularJS and possibly mobile applications?
I use Visual Studio because it provides me best default configuration for development. Less choice helps me concentrate on the product. In a sense it is iPhone of software development for me. When my laptop broke, I just download latest version of VS and start coding without any configuration. For sure it has best editor in terms of perceived responsiveness. Could not say the same for IntelliJ IDEA unfortunately.
- Intelligent ide187
- Smart development environment128
- Easy js debugging108
- Code inspection97
- Support for the Latest Technologies95
- Created by jetbrains55
- Cross-platform ide53
- Integration36
- Spellchecker30
- Language Mixing/Injection24
- Debugger11
- Local History10
- Web developer can't live without this8
- Fast search7
- Git support7
- Angular.js support6
- Sass autocompletion6
- Better refactoring options5
- FTP5
- There is no need to setup plugins (all from the box)5
- Show color on the border next to hex string in CSS5
- Smart autocompletion5
- JSON Schema5
- Awesome5
- Built-in js debugger5
- Running and debugging Node.js apps remotely5
- Easy to use4
- A modern IDE stuck in the 90s4
- TypeScript support4
- Smart coding assistance for React4
- Node.js integration4
- 1114
- Protractor support out of the box4
- Intelligent4
- Paid but easy to crack4
- Dart support3
- Solid intelligent features3
- Great app3
- Integrated terminal3
- Vagrant and SSH Console3
- Free for students3
- Unused imports inspection3
- Docker intergration3
- Remote Files Syncronization2
- Grate debug tools for React Apps2
- Easier to keep running than eclipse2
- Auto imports1
- Vim support1
- Rename helpers1
- Auto refactoring helpers1
- Less autocompletion1
- GIT partial commits1
- Paid4
- Expensive1
related WebStorm posts
When I switched to Visual Studio Code 12 months ago from PhpStorm I was in love, it was great. However after using VS Code for a year, I see myself switching back and forth between WebStorm and VS Code. The VS Code plugins are great however I notice Prettier, auto importing of components and linking to the definitions often break, and I have to restart VS Code multiple times a week and sometimes a day.
We use Ruby here so I do like that Visual Studio Code highlights that for me out of the box, with WebStorm I'd need to probably also install RubyMine and have 2 IDE's going at the same time.
Should I stick with Visual Studio Code, or switch to something else? #help
We use Prettier because when we rebooted our front-end stack, I decided that it would be an efficient use of our time to not worry about code formatting issues and personal preferences during peer review. Prettier eliminates this concern by auto-formatting our code to a deterministic output. We use it along with ESLint and have 1st-class support in our WebStorm and Visual Studio Code editors.
Visual Studio
- Intellisense, ui303
- Complete ide and debugger243
- Plug-ins164
- Integrated103
- Documentation93
- Fast37
- Node tools for visual studio (ntvs)35
- Free Community edition32
- Simple24
- Bug free17
- Made by Microsoft7
- Full free community version6
- JetBrains plugins (ReSharper etc.) work sufficiently OK5
- Productivity Power Tools3
- Vim mode2
- VIM integration2
- I develop UWP apps and Intellisense is super useful1
- Available for Mac and Windows1
- The Power and Easiness to Do anything in any.. language1
- Cross platform development1
- Bulky15
- Made by Microsoft13
- Sometimes you need to restart to finish an update4
- Too much size for disk3
- Only avalible on Windows3
related Visual Studio posts











Secure Membership Web API backed by SQL Server. This is the backing API to store additional profile and complex membership metadata outside of an Azure AD B2C provider. The front-end using the Azure AD B2C to allow 3rd party trusted identity providers to authenticate. This API provides a way to add and manage more complex permission structures than can easily be maintained in Azure AD.
We have .Net developers and an Azure infrastructure environment using server-less functions, logic apps and SaaS where ever possible. For this service I opted to keep it as a classic WebAPI project and deployed to AppService.
- Trusted Authentication Provider: @AzureActiveDirectoryB2C
- Frameworks: .NET Core
- Language: C# , Microsoft SQL Server , JavaScript
- IDEs: Visual Studio Code , Visual Studio
- Libraries: jQuery @EntityFramework, @AutoMapper, @FeatureToggle , @Swashbuckle
- Database: @SqlAzure
- Source Control: Git
- Build and Release Pipelines: Azure DevOps
- Test tools: Postman , Newman
- Test framework: @nUnit, @moq
- Infrastructure: @AzureAppService, @AzureAPIManagement
.NET Core is #free, #cross-platform, and #opensource. A developer platform for building all types of apps ( #web apps #mobile #games #machinelearning #AI and #Desktop ).
Developers have chosen .NET for:
Productive: Combined with the extensive class libraries, common APIs, multi-language support, and the powerful tooling provided by the Visual Studio family ( Visual Studio and Visual Studio Code ), .NET is the most productive platform for developers.
Any app: From mobile applications running on iOS, Android and Windows, to Enterprise server applications running on Windows Server and Linux, or high-scale microservices running in the cloud, .NET provides a solution for you.
Performance: .NET is fast. Really fast! The popular TechEmpower benchmark compares web application frameworks with tasks like JSON serialization, database access, and server side template rendering - .NET performs faster than any other popular framework.