What is Adobe ColdFusion and what are its top alternatives?
Top Alternatives to Adobe ColdFusion
- Lucee
It is a light-weight dynamic CFML scripting language for the JVM that enables the rapid development of simple to highly sophisticated web applications. ...
- PHP
Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...
- Visual Studio
Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications. ...
- 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. ...
- PyCharm
PyCharm’s smart code editor provides first-class support for Python, JavaScript, CoffeeScript, TypeScript, CSS, popular template languages and more. Take advantage of language-aware code completion, error detection, and on-the-fly code fixes! ...
- 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. ...
- Xcode
The Xcode IDE is at the center of the Apple development experience. Tightly integrated with the Cocoa and Cocoa Touch frameworks, Xcode is an incredibly productive environment for building amazing apps for Mac, iPhone, and iPad. ...
- PhpStorm
PhpStorm is a PHP IDE which keeps up with latest PHP & web languages trends, integrates a variety of modern tools, and brings even more extensibility with support for major PHP frameworks. ...
Adobe ColdFusion alternatives & related posts
- Interoperable with Java1
- Weak type system1
related Lucee posts
PHP
- Large community945
- Open source808
- Easy deployment762
- Great frameworks481
- The best glue on the web385
- Continual improvements234
- Good old web182
- Web foundation144
- Community packages134
- Tool support124
- Used by wordpress34
- Excellent documentation33
- Used by Facebook28
- Because of Symfony23
- Dynamic Language21
- Cheap hosting16
- Very powerful web language14
- Easy to learn14
- Fast development14
- Awesome Language and easy to implement14
- Composer12
- Because of Laravel10
- Flexibility, syntax, extensibility10
- Easiest deployment8
- Fastestest Time to Version 1.0 Deployments7
- Worst popularity quality ratio7
- Short development lead times7
- Readable Code7
- Most of the web uses it6
- Faster then ever6
- Fast6
- Simple, flexible yet Scalable5
- Open source and large community5
- I have no choice :(4
- Has the best ecommerce(Magento,Prestashop,Opencart,etc)4
- Is like one zip of air4
- Open source and great framework4
- Large community, easy setup, easy deployment, framework4
- Easy to use and learn4
- Cheap to own4
- Easy to learn, a big community, lot of frameworks4
- Great developer experience3
- Hard not to use2
- FFI2
- Interpreted at the run time2
- Great flexibility. From fast prototyping to large apps2
- Used by STOMT2
- Fault tolerance2
- Safe the planet2
- Walk away2
- So easy to learn, good practices are hard to find20
- Inconsistent API16
- Fragmented community8
- Not secure5
- No routing system2
- Hard to debug1
- Old1
related PHP 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.
















Our whole Node.js backend stack consists of the following tools:
- Lerna as a tool for multi package and multi repository management
- npm as package manager
- NestJS as Node.js framework
- TypeScript as programming language
- ExpressJS as web server
- Swagger UI for visualizing and interacting with the API’s resources
- Postman as a tool for API development
- TypeORM as object relational mapping layer
- JSON Web Token for access token management
The main reason we have chosen Node.js over PHP is related to the following artifacts:
- Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
- Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
- A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
- Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
Visual Studio
- Intellisense, ui303
- Complete ide and debugger243
- Plug-ins164
- Integrated103
- Documentation92
- Fast36
- Node tools for visual studio (ntvs)35
- Free Community edition31
- Simple24
- Bug free17
- Made by Microsoft7
- Full free community version6
- JetBrains plugins (ReSharper etc.) work sufficiently OK5
- Productivity Power Tools3
- Vim mode2
- VIM integration2
- Cross platform development1
- The Power and Easiness to Do anything in any.. language1
- I develop UWP apps and Intellisense is super useful1
- Bulky14
- Made by Microsoft13
- Sometimes you need to restart to finish an update3
- Only avalible on Windows3
- Too much size for disk1
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.
- 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
- Kotlin5
- Free for open-source development, students and teacher5
- All5
- Free If you're a Student5
- Cross platform4
- IDE4
- ERD Diagrams4
- Base for Android Studio4
- Database/Code integration4
- Special icons for most filetypes in project list3
- Free3
- 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
- Vim support3
- Column Selection Mode3
- Supports many frameworks3
- Built-in web server3
- Live Templates3
- Scala support3
- Just works2
- Integrated Ssh/Ftp Managers2
- Full support2
- Task managers2
- Diff tools2
- File Watchers2
- Support for various package managers2
- Integrated Code Linting2
- Its fake intellisense is better than real IntelliSense2
- Clean UI2
- Open source2
- So modernised2
- Efficient, one Stop solution2
- A lot of plugin2
- 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.
- Smart auto-completion105
- Intelligent code analysis88
- Powerful refactoring74
- Virtualenv integration57
- Git integration50
- Support for Django20
- Multi-database integration9
- VIM integration7
- Vagrant integration4
- In-tool Bash and Python shell3
- Plugin architecture2
- Docker2
- Debug mode support docker1
- Perforce integration1
- Emacs keybinds1
- Slow startup8
- Not very flexible5
- Resource hog4
- Periodic slow menu response2
related PyCharm 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 am a QA heading to a new company where they all generally use Visual Studio Code, my experience is with IntelliJ IDEA and PyCharm. The language they use is JavaScript and so I will be writing my test framework in javaScript so the devs can more easily write tests without context switching.
My 2 questions: Does VS Code have Cucumber Plugins allowing me to write behave tests? And more importantly, does VS Code have the same refactoring tools that IntelliJ IDEA has? I love that I have easy access to a range of tools that allow me to refactor and simplify my code, making code writing really easy.
- Android studio is a great tool, getting better and bet173
- Google's official android ide101
- Intelligent code editor with lots of auto-completion36
- Its powerful and robust25
- Easy creating android app5
- Amazing Layout Designer3
- Great Code Tips3
- Great tool & very helpful3
- Built in Emulator2
- Easy to use2
- Keyboard Shortcuts are Amazing Out of the box2
- Cc1
- Slow emulator4
- Huge memory usage4
- Complex for begginers2
- No checking incompatibilities2
- Using Intellij IDEA, while Intellij IDEA have too1
- Lags behind IntelliJ IDEA1
- Slow release process1
related Android Studio posts
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.
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.
- IOS Development129
- Personal assistant on steroids32
- Easy setup29
- Excellent integration with Clang17
- Beautiful2
- Built-in everything1
- Con0
- Massively bloated and complicated for smaller projects6
- Horrible auto completiting and text editing3
- Slow startup1
- Very slow emulator1
related Xcode posts
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.
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/
- Best ide for php286
- Easy to use233
- Functionality219
- Plugins165
- Code analysis161
- Integrated version control87
- Great php ide for mac76
- All-round php ide73
- Local history62
- Themes53
- Best PHP IDE18
- Database control11
- Easy to find anything and everything in your code10
- Best inspection variable9
- Best bebugging9
- UX7
- Great frameworks integration7
- PHPUnit integration7
- Getting Better7
- Command line integration7
- Performance6
- Coolest IDE6
- Composer integration6
- Best ide for advanced php and symfony5
- Real time code validation5
- Neat does the job and easy5
- Easy to use and github interaction5
- It has no match. it filled one of the biggest void4
- Cross platform4
- TypeScript support4
- Great refactoring support4
- Best ide for php4
- Code indexing4
- Fast and relevant auto-complete4
- Debugger for Javascript3
- Good3
- Very good3
- Integration with Vagrant and Docker3
- Debugging in the Just-In-Time Mode2
- Awesome debugging features2
- Perfect locahost / host sync2
- Uses a lot of memory14
- Does not open large files10
- Slow9
- Uses Java machine8
- No way to change syntax highlight for files without ext3
- No save prompt or asterisk on file change2
related PhpStorm posts
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!
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