It seems we are moving to a world of magic, where developers will be alchemists, and only a handful of people will understand "physics" or "chemistry" and know what is actually going on in the cloud, serverless, fileless, functionless development. Since google translate and google maps, I always ask myself, what is the real price for this very convenient and engaging product.
Web-based editor
31–40 of 307 posts
Re: Web-based editor
#32It seems we are moving to a world of magic, where developers will be alchemists, and only a handful of people will understand "physics" or "chemistry" and know what is actually going on in the cloud, serverless, fileless, functionless development. Since google translate and google maps, I always ask myself, what is the real price for this very convenient and engaging product.
Re: Web-based editor
#33Re: Web-based editor
#34Earlier quoted context omitted.
An in-browser (neo)vim instance with a dotfiles repo integration would really be something.
Firenvim exists for in-browser neovim. I haven't used it. [0] https://github.com/glacambre/firenvim
I was thinking of something that would allow you to use any machine with a browser.
Re: Web-based editor
#35Great to see other development tool picking up the same usecase.
Re: Web-based editor
#36Am I alone in not jumping on the Visual Studio [Code] bandwagon? Other online editors have had "vim modes" for ages (e.g. Overleaf) and frankly I'm unlikely to write a chonking great script or project in a browser on Github -- a minor modification is much more likely. VS Code's codebase is huge . Will Github allow people to use other $EDITORs? (Yes, I'm aware this makes me sound like an old man!)
It was so sleek and lightweight at first it was really a pleasure to use. But performance and bugs seem to increase, even if you don't use many or any plugins at all.
Re: Web-based editor
#37Remember the typical Microsoft: "embrace, extend, extinguish" ...
> "Embrace, extend, and extinguish" (EEE) . . . is a phrase that the U.S. Department of Justice found that was used internally by Microsoft to describe its strategy for entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences in order to strongly disadvantage its competitors.
This is a completely valid reason to be concerned with these sorts of things now that GitHub is owned and operated by Microsoft. They continue these practices today, and GitHub is no exception.
Re: Web-based editor
#38It looks like this is actually just the editor from Visual Studio Online unless I've missed something. It's great, but if it were really Visual Studio Code that would be awesome and I'd be pleasantly surprised. (The difference being that if it's just the editor it misses out on all the compiler/analysis integrations. If Github were providing Linux containers in the cloud for working on projects - essentially the SSH…
Re: Web-based editor
#39Re: Web-based editor
#40Its scary we're heading towards a situation where everything is done in a browser. Maybe Chromeos really is the future.
I used to think this was pushed by some of the large tech companies that do not have a popular OS and are forced to turn the browser effectively into an OS. But both Github and VS code are owned by Microsoft now.
For many people internet connectivity and local computation power (within the browser) is now good enough to skip installations and updates all together.
It makes perfect sense for them to do this and in the end they are not giving up control if they still own the OS.
Microsoft can always the decide that "untrusted" websites (which, for example, are not "certified" by them) get blocked from using certain features.