Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab Web IDE

about.gitlab.com

Post reply on HN
Print view View original

61–70 of 280 posts

Re: GitLab Web IDE

#61

Post by qop »

tootie wrote: post #45
pomber wrote: post #39

> We are planning for an even better experience in the future: one where we can integrate and support more advanced features, such as a live environment to test your code against This. Please. I'm playing with a similar concept for GitHub: https://twitter.com/pomber/status/1003416752146075648

One day, I can toss out all my expensive hardware and do my job with a hi-res Chromebook and steady wifi.

That's really what I hope the future is.

I'm shocked Google hasn't tripled their efforts to make the chromebook a code editor masterpiece. You'd think they'd have spearheaded it themselves.

Now I'm keeping my eyes on Microsoft bringing arm64 hardware in the game. 20+hr battery life + wifi means I could just work wherever I want during the day and then go home at night and charge. Adventure coding, EVERY DAY! That'd be so awesome.

Re: GitLab Web IDE

#62

Post by RussianCow »

bhhaskin wrote: post #47
TooBrokeToBeg wrote: post #42

Earlier quoted context omitted.

Integrated with Git/Gitlab.

Right, but so does Atom. Atom is a text editor, not an IDE.

The line is pretty blurry these days. If you install enough extensions, it's very difficult to differentiate between Atom/VS Code and a "real" IDE.

Re: GitLab Web IDE

#63

Post by hessart »

jay-anderson wrote: post #48
tcfunk wrote: post #16

Earlier quoted context omitted.

Asking the important questions.

While it may not have been a serious question, vim key bindings (or emacs or whatever) are important to many people. You spend so much of your time in your editor/ide and become expert in it. Learning to work in another one is painful before you're properly productive again.

Seriously, how hard can it be? It's not like it's a completely new form of interaction. Vim and emacs are the ones that are exceptions in regard to UX.

Re: GitLab Web IDE

#64

Post by adamrezich »

Anyone remember back when Heroku had something sort of like a primitive version of this? Whatever happened to that? I spent many a high school lunch break in the library teaching myself how to make Rails apps using it

Re: GitLab Web IDE

#65

Post by pknopf »

ssijak wrote: post #17

What is the use for this? I mean how many people actually use such tools for actual day to day dev? Maybe for some quick edit if you don`t have laptop/computer at hand, but otherwise I see no real advantage of this.

We are in the process of using GitLab for managing our design history files (DFHs) for our medical devices.

This will make it easier for non-techies to edit product requirements, without deep knowledge of git.

Re: GitLab Web IDE

#66

Post by TeMPOraL »

cabaalis wrote: post #14

I'll admit I'm a very poor "look and feel" person. But am I the only one who thinks that the zooming images on this webpage are hostile to the user? (1) The zoom animation takes too long, I want to see the screenshot (2) After zooming, it's still difficult to read to my 33-year-old eyes. I want a fullscreen image. (3) After finishing squinting at the screenshot, I scroll down to read more text only to have that text…

Yup, this is very bad.

That said, I find all JS-based "zooming" of images bad. The simplest behaviour is the best here - just make the thumbnail a link to raw image directly. If you absolutely have to have that JS-based gallery, then for goodness' sake, don't do it with CSS background shenanigans - use the tag, so that "right click + view image" works.

(To be fair to Gitlab, in this article "view image" works, and can be used to see images in full resolution.)

Alas, I'm pretty sure that half of this breakage are designers cargo-culting trends instead of focusing on usability; the other half is user-hostile designs purposefully making it harder for regular users to get to the URL of the actual image.

Re: GitLab Web IDE

#67

Post by BoysenberryPi »

cabaalis wrote: post #14

I'll admit I'm a very poor "look and feel" person. But am I the only one who thinks that the zooming images on this webpage are hostile to the user? (1) The zoom animation takes too long, I want to see the screenshot (2) After zooming, it's still difficult to read to my 33-year-old eyes. I want a fullscreen image. (3) After finishing squinting at the screenshot, I scroll down to read more text only to have that text…

This seemed rushed out in an attempt to capitalize on their positive PR as of late.

Re: GitLab Web IDE

#68

Post by voxadam »

dillonb wrote: post #7

But does it have Vim keybindings?

What we need is a web deliverable (i.e. not a "web technology based" Electron desktop app) Neovim frontend. Something like a Wasm & WebGL based UI layer connected via msgpack to the editor core that's running in a sandbox on GitLab's infrastructure.

I'm truly sorry if the above drivel is either impossible or insane; as an embedded guy this is most definitely way outside my wheelhouse. I should get back to repairing my oscilloscope.

Re: GitLab Web IDE

#69

Post by adtac »

hessart wrote: post #63
jay-anderson wrote: post #48

Earlier quoted context omitted.

While it may not have been a serious question, vim key bindings (or emacs or whatever) are important to many people. You spend so much of your time in your editor/ide and become expert in it. Learning to work in another one is painful before you're properly productive again.

Seriously, how hard can it be? It's not like it's a completely new form of interaction. Vim and emacs are the ones that are exceptions in regard to UX.

I use qutebrowser (has vim-bindings), sway wm (I've customised it to have vim-bindings), zsh (with vim-bindings), weechat (with vim-bindings), mutt (still getting started with mutt, but it has vim-bindings too), and vim itself. These are pretty much the only pieces of software I interact with, so you can imagine how central vi/vim-bindings are in my life.

Re: GitLab Web IDE

#70

Post by theptip »

ssijak wrote: post #17

What is the use for this? I mean how many people actually use such tools for actual day to day dev? Maybe for some quick edit if you don`t have laptop/computer at hand, but otherwise I see no real advantage of this.

> how many people actually use such tools for actual day to day dev

According to an Xoogler acquaintance, he used a web IDE for all his development; I'm not sure how widespread this is in Google, but the answer to your question could be "lots".

(Any Googlers want to chime in with estimates on % of devs using web IDEs?)

Post reply on HN