Ask Slashdot: What Are Your Experiences With Online IDEs For Web Development? 168
Qbertino writes: I'm toying with the thought of moving my web development (PHP, HTML, CSS, JavaScript with perhaps a little Python and Ruby thrown in) into the cloud. The upsides I expect would be: 1) No syncing hassles across machines. 2) No installation of toolchains to get working or back to work — a browser and a connection is all that would be required. 3) Easy teamwork. 4) Easy deployment. 5) A move to Chrome OS for ultra-cheap laptop goodness would become realistic.
Is this doable/feasible? What are your experiences? Note, this would be for professional web development, not hobbyist stuff. Serious interactive JS, non-trivial PHP/LAMP development, etc. Has anyone have real world experience doing something like this? Maybe even experience with moving to a completely web-centric environment with Chrome OS? What have you learned? What would you recommend? How has it impacted your productivity and what do you miss from the native pipelines? What keeps you in the cloud, and enables you to stay there? Are you working "totally cloud" with a team and if so, how does it work out/feel? Does it make sense? As for concrete solutions, I'm eyeing Cloud9, CodeAnywhere, CodeEnvy but also semi-FOSS stuff like NeutronDrive. Anything you would recommend for real world productivity? Have you tried this and moved back? If so, what are your experiences and what would need to be improved to make it worthwhile? Thanks for any insights.
Is this doable/feasible? What are your experiences? Note, this would be for professional web development, not hobbyist stuff. Serious interactive JS, non-trivial PHP/LAMP development, etc. Has anyone have real world experience doing something like this? Maybe even experience with moving to a completely web-centric environment with Chrome OS? What have you learned? What would you recommend? How has it impacted your productivity and what do you miss from the native pipelines? What keeps you in the cloud, and enables you to stay there? Are you working "totally cloud" with a team and if so, how does it work out/feel? Does it make sense? As for concrete solutions, I'm eyeing Cloud9, CodeAnywhere, CodeEnvy but also semi-FOSS stuff like NeutronDrive. Anything you would recommend for real world productivity? Have you tried this and moved back? If so, what are your experiences and what would need to be improved to make it worthwhile? Thanks for any insights.
IDE's suck as soon as you want to use another lang (Score:2, Insightful)
Just stick with text editors... or be forever dependant on you web based IDE.
Re: (Score:2, Interesting)
oh ok, grandpa. time for your nap.
seriously, it's so odd that people into computers are so "stuck in their ways" and cling to old technology.
Re: (Score:2)
When it ain't broke, why "fix" it? What boggles me is that everyone sees something new and thinks "improvement". If what you have does 90% of what you need 99% of the time..... how much change and overhead is justified to fill that gap?
I want my code on local storage, doesn't matter what I am doing. I want the tools I use to update my code on local storage as well. I care less about whether I can fully test locally. I care a lot less about wiz-bang editor features.
IDEs are nice, but, syntax hilighting and c
Re: (Score:2)
What cracks me up are the supposed benefits. Perfect for people who already got all those benefits from OOP, then from XP, then from Agile, etc. The listed benefits are exactly the things it actually sucks at.
"Syncing is easy... because you're not allowed to do it, you just twiddle your thumbs until the network traffic resumes. Easy-peasy, you're welcome." Uhm, no. I'm old enough to have lived that. Thin clients were good, because thick clients were out of our price range, and allowed us to share a larger s
Re: (Score:2)
> My second thought is, "do they know that managing a private cloud configuration is harder than managing a workstation, and generally requires sysadmin skills?"
But that is the whole point....since its offered to you as a service, you don't need any of that. They want to lock you in to trusting them to do all that work competently and to respect the privacy of your data, and trusting them to not go under/shut their servers off tomorrow.
Its all about lock-in, in the name of providing convenience.
Re: (Score:2)
Right, but the "as a service" case is mostly a fail. Anybody old enough to have used thin clients can understand this.
Once the service you're using is unusable for a couple days because some script kiddie decided to DDoS it, then you'll find out you need your own cloud to work in the cloud.
They want to lock you in, but they can't actually keep you there. Cloud services will be around "forever," but not every use case will outlast the buzzword phase. For companies that paint themselves into a corner with thi
Re: (Score:2)
" A cheap tablet computer has enough processing power for software development now. "
True. The iPad3 was the first tablet to be faster than a Cray X/MP which was the machine I had wet dreams about when I was a student.
You really do have a supercomputer in your pocket.
Re:IDE's suck as soon as you want to use another l (Score:4, Insightful)
But to me, there is no killer feature here. The closest thing to killer feature is nearly instant developer environment replacement. If my kids spill a drink on my work laptop or it's stolen, if I have a recent full disk image backup it will take me a few days to get back up and running. I have to buy the same hardware, and then put the backup image on the storage, and then I'm back to work. If I don't have a recent full disk image backup then I have to buy some kind of replacement and spend another day getting it ready. With a fully web-based IDE the loss of hardware is a ten minute annoyance - just boot up any other machine with a web browser, log back in, get back to work.
Re: (Score:2)
> But to me, there is no killer feature here. The closest thing to killer feature is nearly instant developer environment replacement.
Exactly, and....big whoop. Oh wow you saved time...um on average once every couple of years per dev?
90% of this issue is already solved by using revision control with a remote repository. Now all you need is to reinstall your dev tools and clone a repo....at most you lost back to your last push.
Re: (Score:2)
Re: (Score:2)
I would agree with the web based editor being suck squared, but sometime using a terminal for everything because "I hatez them GUI thingz" is bull.
And yes, I have someone working like that with me. His productivity is...problematic.
Re: (Score:2)
Sorry, Cowherd, you gotta log in to use the "grandpa" line around here. Get to back of the line, pokey.
Re: (Score:2)
Sorry, Cowherd, you gotta log in to use the "grandpa" line around here. Get to back of the line, pokey.
Yer dern tootin'. Besides, it takes us old folks a while to get our clay tablets out to start cuneiforming our responses.
Re: (Score:2)
Old tools and old methods are known and you can rely on them to do the work, why change at all? There has to be enough benefit to change to something new.
Especially in this era of "oh, new and shiny!" where things come and go every week, every month, every year. You can't even rely on most of the things that a company as huge as Google does because they have discontinued most of them within a really short time frame.
Re: (Score:2)
Gosh, to make those whippersnappers stop making up fake "syndromes" to name-call him with, waaaaaaah! Oh, wait, grandpa does not care what you think he has already lived a little and knows better.
People were already laughing at me for using emacs in the late 90s, and none of them ever had a point other than "haha, kitchen sink." One secret of software, unused capabilities that don't have buttons on the screen can be safely ignored forever. It isn't like an oversized hand tool that weighs more because it has
Re: (Score:2)
The problem with emacs and Vim isn't what they can do, it's the learning curve. IntelliJ, Visual Studio, KDevelop, Eclipse, Netbeans, etc... etc... have a learning curve that looks like a slope. Barebones Emacs and Vim usage is an easy slope, but if you want to be highly productive it's like rock-climbing.
Or to put it another way, once in a while at work we pair together over a screen-sharing application. Whe
Re: (Score:3)
Right, but are the previews you're talking about for changes in one file?
With an IDE, you have single files "open" in tabs or windows, if you're doing a global replace you can choose to replace everything with no preview, or it has to step through each one and open the file, show you the preview, and you click yes/no.
With sed, I dump all the proposed changes to a scrolling buffer, and can review them all at once, one per line. Then I re-run the command to make the changes for real.
If you have thousands of c
Re: (Score:2)
The audio advice for the IDE is relatively rare. "It would be faster if you did Ctrl-Alt-____" every few minutes because most of the navigation is visual. Mouse wheel to scroll. Right click for options. etc... etc... A novice can still work pretty quickly with only occasional prompting. With Vim, everything except typing actual text is a funky command, so unless you want to watch someone navigate one keystroke at a time with
Re: (Score:3)
No, I've been using emacs for nearly 20 years and I'm not a "wizard" at all. I use less chords than I have fingers. The whole concept that programmer efficiency is based on things your GUI does for you is specious, as is the claim that emacs is difficult. You're not a crippled infant your first hour or week or year using emacs. You type in your code, it is pretty straightforwards. Learning features is for petty details like changing the colors of the syntax highlighting; things you learn over time, that may
Re: (Score:2)
But with respect to emacs or Vim, if you're only using it like Windows Notepad, then you are nowhere near as productive as someone in an IDE. You can get work done, and in your free time you can use Vim only knowing 'i', 'Esc:q!', and 'Esc:wq' (or 'Esc:ZZ') and just typing away in insert mode. But if you want to work anywhere near as quickly as someone with an IDE, you'll need to learn navigating by word ending and begin
Re:IDE's suck as soon as you want to use another l (Score:4, Funny)
Once you start using an IDE forever will it dominate your destiny. Consume you it will.
Hrmmmm.
Re:IDE's suck as soon as you want to use another l (Score:4, Insightful)
Once you start using an IDE forever will it dominate your destiny. Consume you it will.
There is more truth in this than most people would be comfortable admitting.
Re: (Score:3)
IDE's were nice when they were optional. Combining a text editor, a make facility and a debugger in a nicely integrated package does make life a little easier. The problem is that IDE's enable complexity - and without a good reason, complexity is a bad thing. IDE's have enabled the migration from comprehensible programs to micro services with myriad triggers tied to tidbits of code. And in the case of web apps, those tidbits are divided between CSS, JavaScript, tons of JavaScript libraries, and whatever
Re: (Score:2)
A well designed IDE can be a good learning environment. A poor one is much worse than a text editor, and can leave you feeling trapped.
FWIW, back when I used FOXPRO (before MS bought it) they had a good IDE, so there is(was) an existence proof.
OTOH, even if you know the language backwards and forwards, some purposes can benefit from an IDE. E.g., for importing graphics or sounds. But again, a poorly designed IDE is worse than not having any at all.
The problem is that most IDE designers have the wrong ide
no (Score:5, Interesting)
A move to Chrome OS for ultra-cheap laptop goodness would become realistic.
That sounds like a cruel thing to inflict on your developers. Especially since it prevents them from running a local backend server on their own machine. Annoying.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Exactly what I was thinking. Hiring skilled people and paying them a reasonable salary to get work done for you only to handicap them with a terrible working environment is just silly. Qbertino really needs to read http://www.joelonsoftware.com/... [joelonsoftware.com] and think about the impact of giving his developers an ultra-cheap environment. Heck, go to the library and check out Peopleware as well. The library is even cheaper than ultra-cheap and a thoughtful read through that book will help him use his resources more
Re: (Score:2)
Heck, go to the library and check out Peopleware as well. The library is even cheaper than ultra-cheap and a thoughtful read through that book will help him use his resources more effectively.
And the OP is nothing if not cheap.
I opted for cloud storage over cloud development (Score:3)
I've played with a bunch of them. Cloud9 was my favorite of them, but I ran into challenges when I wanted to play experiment with AngularJS. I ended up preferring to work with Brackets and pointing it at a Google Drive folder. Obviously, I'm not a professional developer. I just experiment, play, learn, and write a web app on occasion. Others in this thread will likely have better advice.
I have no idea (Score:5, Funny)
I've switched to SATA years ago.
Too slow (Score:3, Informative)
What cloud? (Score:2)
No (Score:2, Redundant)
Not great... (Score:3, Interesting)
Here you go, here's all my stuff... (Score:2)
Re: (Score:2)
It doesn't have to be a service, though, doe sit?
It could be something you put in-house and thus can access via a HTTPS site from anywhere. Be able to work from home without needing specialist tools installed, and utilize the power of your servers to do, e.g. distcc, rather than your workstation.
I'd quite like an "OwnCloud" version of Eclipse. Then I could quite literally log on and code from anywhere without needing to replicate what is quite a complicated multi-platform, multi-language, highly integrate
Re: (Score:2)
Re: (Score:2)
It's one of those scenarios where a virtual desktop infrastructure would serve the need most appropriately.
BTW, at last check I preferred seafile over owncloud, though I would wonder if owncloud has improved enough over the year to rethink that.
Re: (Score:2)
Re: (Score:2)
My problem was mostly limitations around non-admin people needing to nag me for a lot of stuff that under seafile they could do for themselves. Like creating their own groups and such (which I might have missed something, but seafile was more straightforward).
Of course, Seafile's LDAP support won't do paged queries, which is a pain. And the developers seem clueless or holding back for their commercial version...
Re: (Score:2)
a git repo (Score:5, Insightful)
Re: (Score:2)
Re: (Score:2)
If you work on multiple computers (such as a laptop and a workstation), you may want to sync continuously A la Dropbox.
But then you get last change wins stopming changes over each other.
I even know people who keep their git repo inside Dropbox -- I know, it sounds stupid.
It really, truly does!
Re: (Score:2)
Re: (Score:2)
OK, it't not the most terrible idea, but still seems a bit pointless.
You probably don't understand their use case. This is a single person, working both from a workstation (when they are at work) or from a laptop (when they telecommute, or are away, or...). At any point in time they may have to leave the workstation in a hurry, and they want to resume coding on the laptop as if they were on the same computer.
How much of a hurry? There's probably enough time to do a git commit -am unfinished && git
Re: (Score:2)
Re: (Score:2)
Git stashes (I believe) cannot be pushed to another computer, so they are useless for this purpose.
Huh, I thought they could, being just another node in the tree. Looks like I was mistaken.
Re: (Score:2)
Yeah, but the poster isn't saying that a cloud IDE would be great because it requires a browser and Internet connection; he's saying it would be great because that's all it would require.
I agree that a SaaS IDE doesn't seem very compelling for a traditional development team using modern tools, which largely have solved the problems he's referring to. But I suppose there are some scenarios where it would be useful, e.g. a virtual, part-time team where people who work in different places contribute on an occ
It takes a village (Score:2)
Re: (Score:2)
Actually your vote would count. If you said 'no', no amount of ISP, cloud, etc provider enthusiasm is going to enable you to get your work done.
Too slow! (Score:2)
I evaluated a few, not for very long admittedly, but found all of them to be too slow.
Fundamentally, doing this stuff professionally means your workstation and tooling (ide or editor or whatever) needs to be an extension of you for you to be able to function efficiently and keep a good flow going. Some of this is muscle memory on keyboard layout and shortcuts, most of it (imo) is responsiveness and ui latency. If the ui cant respond faster than you notice it then it just hurts too much to create stuff ef
Re: (Score:2)
Question about syncing hassles (Score:2)
: 1) No syncing hassles across machines.
What do you mean by that? Syncing what?
Source goes in source control, so that should take care of the "syncing hassles" regardless of what IDE is used. I'm unclear how online IDEs work with source control. I am trying to think of what other things you are talking about syncing.
Re: (Score:2)
He means, "make all the stuff flow over the wires on its own because I don't know how to set up git hooks, ssh, or a VPN"
I still use MS expressions (Score:2)
It is free for designing.
What about SSH+vim...? (Score:2)
No holy wars please. s/vim/$YOUREDITOR/g
If you're using a LAMP stack mainly (which it seems you are), the option of SSH and using a command line text editor could be of interest.
That being said, if you can create a dev environment that matches your production, why not git around? Where has this workflow failed you previously? Surely also you are developing on multiple servers for different projects, and there are things you do common to all servers?
For my sites I use generally two git repos - one for my to
Re: (Score:2)
No need for holy wars, as an emacs user if I'm stuck editing over ssh I switch to vim.
Of course, if I'm using a LAMP stack (or similar) then I wouldn't be developing over ssh, I'd be doing that locally and using source control and a modern deploy tool, which would use ssh under the hood. If I'm using an editor over ssh, it would imply either an emergency hotfix (eek) or a sysadmin task, and in both cases mode-based editing shines.
I don't understand (Score:5, Funny)
I thought everyone just worked on their production code on the live web server like I do...?
Re: (Score:2)
I hope that was sarcasm.
Re: (Score:2)
I hope that was sarcasm.
Mostly.
Re: (Score:2)
If it works for Slashdot ...
Re: (Score:2)
I thought it was called "the nineties."
Re: (Score:2)
I thought everyone just worked on their production code on the live web server like I do...?
cPanel code editor, baby! I got your "professional" right here!
CodeAnywhere (Score:2)
Re: (Score:2)
>> I felt a bit uncomfortable storing SSH credentials "in the cloud" as these are the "keys to the kingdom" for the servers I manage.
Only a bit uncomfortable? You should NEVER put the keys to your production environment in the cloud. If something requires that, then find an alternative,
Do not do that (Score:4, Informative)
I tried a few different ones but (Score:2)
Personally I always find running something in a browser less than ideal compared to an app running locally, so my bias was a factor, but even allowing for that, all the online IDEs I found/tried were far clunkier usability-wise, far slower and obviously less secure than using something running locally.
They're okay (Score:2)
However, I find with my dyslexia I just don't enough bang from them.
Cloud 9, AWS/Bitnami (Score:2)
I've been dabbling with this myself lately, for multiple reasons.
I'm currently using Cloud9 and frankly I can't tell much difference performance or feature wise (but I don't extensively use all the bells and whistles in any IDE anyway).
Cloud9 is cool because while you can use their servers to really quickly bring up dev environments, you can also just as easily SSH into your own box (I'm using AWS with Bitnami distros) for flexibility and security. You get convenient access to the files in the IDE just like
I'd say don't bother. (Score:3)
Don't bother and here's why:
1) No syncing hassles across machines.
Use a decent version control system. If there are no collisions, the syncing is trivial. If there are collisions then te web based system won't help you either.
2) No installation of toolchains to get working or back to work - a browser and a connection is all that would be required.
Figure out what packages you need. Then type:
sudo apt-get install a b c d e etc moar lolz hax package
into a file and save it on your github account. Then on any new machine, grab that line and run it as root. You don't need anything more than an internet connection to do that either, and it'll install a full-strength dev system with almost on effort.
It's generally a good idea to have this, it means you can set up a new laptop or desktop and be up and running in a few minutes.
Plus once you're set up you don't even need an internet connection.
3) Easy teamwork.
How is it easier than a version control system?
4) Easy deployment.
Doesn't that rather depend on what's being deployed and where? Either way though, it's not hard to set up a git repo (e.g. on githup) with testing, continuous integration, automatic deployment and all that stuff.
5) A move to Chrome OS for ultra-cheap laptop goodness would become realistic.
Are the cheap chromebooks substantially better than the cheap modern take on netbooks with Linux installed? You can still run chrome on the latter if you like, but get the benefit of much more flexibility.
Bear in mind that anything done in a web browser takes approximately 1.434762139548e+37 more CPU resoures than a corresponding native program. For example compare Atom to uh... just about anything really. If you're going to be doing "big" stuff in the browser then a weak laptop will get really annoying. For example google docs on my venerable eee 900 is now horrendous and barely usable where as LibreOffice is still fast and snappy.
vim of course loads instantly still.
Cheap tools (Score:3)
Visual Studio FTW (Score:4, Informative)
I know I'll get modded down for this, but usually only take web development projects that let me write in Visual Studio. Why?
1) People who are looking for C#-based projects have MONEY (they have to to afford non-Express SQL Server) and often pay their bills on time
2) Unit testing is easy to do...and my clients usually happily pay for a full test suite as a self-documenting quality check on my code
3) Expectations of bleeding-edge look-and-feel are often lower, which means I spend more time on the app and less time on browser-specific rendering and Javascript BS
For my own use (my marketing sites) I tend to build on frequently-updated web portal tools (often in PHP/JS/TS) and only do a few tweaks around the edges in a text editor like Sublime because just about all of what I need to interact with the rest of the world has already been written by somebody else.
Re: (Score:2)
Have you tried VS Code (https://code.visualstudio.com/) over Sublime? It's cross platform (Win, OSX, and Linux) and free. Plus, it recognizes your SLN solution. It's based on the same code that runs on TFS Online (it's actually a web application that runs in NWJS (formerly Node-Webkit - http://nwjs.io/ [nwjs.io]).
PythonAnywhere (Score:2)
I have used PythonAnywhere for a couple of years. Obviously it's Python only (duh), but would say the experience has generally been excellent.
The ability to use two accounts on the service, using one as a development server, and the other as a deployment one is fabulous. It's also really cheap, and the reliability and support is first rate.
I do not work for them!
Happy user of Koding.com (Score:2)
Penny wise... pound... what was that again? (Score:2)
What does a decently-spec'd MBP or non-Apple equivalent and a mid-grade commercial IDE cost these days? $2k at the most?
Even if you are hiring 18-year-olds in rural South Dakota, you are looking at $50k a year ($35k salary + other direct costs), the $2k is *nothing*. 16GB laptops, SSDs, giant screens, and huge backup arrays are close to nothing.
Don't be that cheap guy. Don't work for that cheap guy. If you are you own boss and are the one cheaping out on your own self... look in a mirror, do a Stuart Sm
Don't do it. (Score:2)
I mean, if you're just doing your own personal projects, that's one thing, but if you're doing real hardcore team-level website/app development where there's a significant amount of work, division of work between team members, etc. then go on AWS or wherever, set up a trac server, install git and set up a git repo that's linked to your trac server, get Eclipse, install the mylyn plugin, etc. If you want to go whole hog set up a docker container that has a copy of your web server environment in it for local
Are You Poor? (Score:2)
Why do you think ultra-cheap laptop goodness is a good thing? Whenever I've dealt with cheap laptops, they are usually slow, not very durable (random crap breaks on the case in 2 years) and generally annoying to use (keys stick, the screen resolution is tiny, the built in mouse/trackpad sucks.) As a developer, I tent to buy a high end laptop (or two) and then use it every day, carrying it around in my backpack, for three years, or more, before I have problems.
Unless you are poor, I don't really see why poi
Cloud9 and ChromeOS (Score:3)
I mostly use the exact setup you're talking about. I can't really speak to the "teamwork" aspects; for that I generally use CollabEdit [slashdot.org], which is simpler for one-off collaboration. I got a Chromebook because I was planning on being in fairly impoverished areas in Central America for months or years, and I wanted a laptop that I was not going to worry about breaking. It works pretty well, all things considered. It's relatively simple to install a 'real' linux distro via crouton [github.com] and get access to all the normal linux goodies. One specific advantage to ChromeOS is that it keeps track of what apps you have installed, and if you ever have to replace the unit, you can just sit at the new one, type your login info, and in about two minutes the new machine will have exactly the same stuff the old one did.
Having your development tools/files in the cloud means that they are inaccessible to you without an Internet connection, however, you don't need much of a net connection to be able to work: for Cloud9 there's an initial download of I believe about 1 MB for the editor, and actually editing code is possible down to a hundred bytes per second. Creating a local repo from a GitHub or Bitbucket repository is very simple, and each coding workspace gets its own little virtual machine, so you can install gems, run tests, and do anything you'd normally do. It also saves process state, so you can start (e.g.) pry, fool around with the interpreter, close the window, and the next time you start, pry will still be running. It actually saves quite a few brain cycles: you have less effort to figure out what you were doing the last time. Code completion and refactoring support exists, but is not what you would call world-class, more like SublimeEdit than intellij.
I have been using cloud9, but I have shopped around for various online editors at times, and so far I have not found any particularly compelling reasons to switch. I do not miss setting up a new chroot or container for a new project, or worrying about syncing code between workstations. Also note that there are online IDEs which can be run on your own private server (Cloud9 among them), for a hybrid approach, and of course there's nothing wrong with emacs over ssh if it comes down to it. At this point I doubt I would go back to a "real" IDE unless required to by an employer.
Lack of linting and debugging. (Score:2)
I have tested all of them in the past. Some have moved in a direction that I don't think is right for a PHP developer. They are essentially moving to sandboxed virtual environments where they want you to develop on that virtual box.
I have been keeping my eye on codeanywhere as I believe it is going in the right direction. However with the lack of PHP (or any language) linting, it is useless. For those of you that don't know, linting is essentially the highlighting of syntax errors in your code. I believe th
Cloud? (Score:2)
Cloud, schmoud.
cPanel's code editor is my main tool!
How about Sage (Score:2)
Rather than using a pseudo-commercial IDE with limited functionality, you could use a free cloud based Linux machine courtesy of the Sage cloud: cloud.sagemath.com.
The terminal they provide isn't the greatest, but with tmux and screen, plus vim, you should be able to easily create a decent multi-terminal programming environment, in addition to getting a couple of GB of free storage. Recently they have introduced a pay model under which network access costs $7/mo. This seems cheap to me. I doubt that they
GIT & Eclipse + RSE (Score:3)
I do "cloud development" all the time. I spin up servers with ansible so they have GIT, latest source, and my login keys, and I use Eclipse/SSH with the Remote System Explorer (RSE) extension to develop, and more ansible/GIT to save the changes back to the repo and deploy to the rest of the cloud.
I've tried docker and various other deploy systems, but most of the time what you want is a carefully versioned Debian stack install with you source slapped on top, and there's nothing hard about that once you've got your workflow sorted.
Oh, you mean, is there a way of developing totally in a browser without local software installs to a professional standard and level of tooling?
Um, no. Not yet. Which is a shame. There are a few specific tools, (I've written a few) but not a whole "IDE".
(Unless as one wag suggested you count the cPanel text editor, which you really shouldn't. It tops out after about 1000 lines, for a start :-)
I've actually attempted such a thing a few times, and the main problem is that putting a full GNU compiler on the internet is a great way to have your box burned to the ground through makefile exploits. Compilers don't like being put in sandboxes either.
Professional Developer Tried Cloud Development (Score:2)
I have tried to go the cloud route route for development with a Chromebook. (I have tried both web development and general programming using remote services.) For development, it might work five years from now, but it does not work today (for me) for professional development.
The first problem is availability. Even the best services are not "always on." Part of this is on the service provider, part is on their service provider, and part is on your own local Internet provider. I always have deadlines for
Re:Betteridge (Score:5, Interesting)
If it is for a professional environment, you have a few bucks to burn getting a decent IDE. Stop being so cheap.
If you mean to do it anyway, why not install Crouton on your Chromebook, and then run Linux like a "normal" person?
If you are stuck on using the cloud, for a professional project, read the license agreement like a hawk. Make sure that you're not giving a free copy of all of your work to some random stranger on the web.
Re: (Score:2)
random stranger? No, I'd expect them to be well-financed, entrenched, and have contracts to legally share my work with all their big-name third party partners.
Re: (Score:3)
Re: (Score:3)
I saw no reference to MongoDB, so it can't be web-scale.
Re: (Score:2)
Re:Do people 100% trust server credentials to clou (Score:4, Insightful)
Re: (Score:2)
It works well entirely because R is not an application language; it is used for snippets, mostly one-off. You don't need all that normal dev process stuff.
The downsides of the "cloud" of course include syncing hassles across machines, installation of toolchains to mitigate problems of offline access, difficulty of teamwork with new team members (even an inability to work with many intending team members, because they won't use those tools and can't choose a professional tool), difficulty of deployment when
Re: (Score:2)
An "intending team member" that won't use the tool because he or she is stubborn isn't worth having on your team, and is thus not a lost. To be fair, though, an "intending team member" that won't use the tool because the tool cuts their productivity down by 10% or 30% or 80% even after climbing a fair bit
Re: (Score:2)
Many professionals consider it an important part of their career to learn and become proficient in various tools. It isn't "stubborn" to want to use something out of that set of tools, not only because it is what you've already invested time in, but because your proficiency will also be advancing as you continue to work with those tools. Who is being stubborn, the person who wants to use "one of the common professional tools that can do the job well," or the person who wants the whole team to only use their
Re: (Score:2)
So if a potential new employer asks you to try something out, the sensible action is to give it a try and account for the fact that some of your initial slowness is unfamiliarity. Then you have to evaluate whether you can ever be as efficient as you were w
Re: (Score:2)
It is easy to measure if it is stubborness, or sticking with proficient tools.
You start from, why are you wanting them to change? Who is it about? Is their tool not actually proficient at the task they want to use it for, or is somebody else simply asserting that they should use a different tool?
Most of that we can answer just by looking at the claimed reasons for the change, without even having to accuse the old codger of being stubborn.
If git didn't work because he used nano, that would be a concern. But
Re: (Score:2)
Newsflash: Wayland already missed years and years of deadlines to take over the world. ;)
And it is an optional replacement. Many of us who use existing features will not switch to software that leaves them out. Kids can have all the new toys they want, but they won't be able to take away what us old fogies already have. Such is the nature of Software Freedom.
Re: (Score:2)
Only if you're stuck on Linux. Many of us quite enjoy working with a variety Unix environments, and there is no systemd here either!