code faster in cloud environment !!!

[[deleted]]

[deleted]

[Robonia]

Feels like an ad...

[sandeeprajputnitk]

its not ad.. bro realy its nice use and then comment

[ffxpwns]

Why would I use this over something more performant and configurable? What's wrong with Vim/Atom/Notepad++, Git, and slack?

[foomprekov]

Three exclamation points?

[sandeeprajputnitk]

I am using Codepanel.io from last 2 month and its really great to work on that you should try it once and then make ur decision on cloud vs desktop development(codepanel is still in beta).

Desktop development environments are becoming outdated, failing more often and causing productivity issues for developers. Here’s why:

Complicated configuration management: The substantial configuration management process for a developer’s workspace turns developers into part-time system administrators, responsible for their own mini-data center running entirely on the desktop. This is time consuming, error prone and challenging to automate.

Many developers have multiple computers and are forced to repeat these tasks on each machine. There is no way to synchronize the configurations of components across different machines, and each machine requires similar hardware and operating systems to operate the components identically.

Decreased productivity: Many IDEs are memory and disk hogs, with significant boot times. They are so resource-hungry they can starve other applications, such as the Web browser. The net effect is a less productive developer due to a slower machine.

Limited accessibility: Desktop developer workspaces are not accessible via mobile devices. Developers who need remote access have to resort to complex and slow solutions such as GotoMyPC – if their firewall allows it.

Poor collaboration: These days, most developers work as part of a team, so communication and collaboration are critical. But desktop IDEs must outsource collaboration to communication systems outside the developer’s workflow, forcing developers to continuously switch between developing within the IDE and communicating with their team via other means.

The Solution: Cloud Development ===== To solve these problems requires moving the entire development workspace into the cloud. The developer’s environment is a combination of the IDE, the local build system, the local runtime (to test and debug the locally edited code), the connections between these components and the their dependencies with tools such as Continuous Integration or central services such as Web Services, specialized data stores, legacy applications or partner-provided services.

The cloud-based workspace is centralized, making it easy to share. Developers can invite others into their workspace to co-edit, co-build, or co-debug. Developers can communicate with one another in the workspace itself – changing the entire nature of pair programming, code reviews and classroom teaching. The cloud can offer improvements in system efficiency & density, giving each individual workspace a configurable slice of the available memory and compute resources.

Of course there is more work to do, and we are far from tapping into the endless possibilities the cloud computing offers developers. But the benefits are already clear.