221–230 of 280 posts
Earlier quoted context omitted.
Unix philosophy does not work on the web because even with all the talk about micro services, you can not easily chain or combine web tools together.
But why write code on the web? If you are typing you are already on a computer
Why are people building these verticals? What happened to Unix philosophy? Build tools that do simple things, and make composition do the work for you. I don't see why anyone needs an online IDE. Much less one interfaced with Gitlab. What next, invent a new cpu too?
Unix philosophy does not work on the web because even with all the talk about micro services, you can not easily chain or combine web tools together.
Wow, very cool. Lots of new players in this space: https://repl.it , https://glitch.me , and now GitLab (and I'd be surprised if GitHub doesn't follow in tow). Cloud9's acquisition really left a big hole in the market. AFAIK there's still nothing out there that gives you a decent code editor (edit multiple files, have multiple tabs open, etc) that also gives you access to a Linux shell and ability to expose ports lik…
You missed https://code.xyz ! We just announced our $2M fundraise from Stripe (totalling $4M to date) [1]. :) [1] https://stdlib.com/blog/stripe-code-xyz/
Earlier quoted context omitted.
One day, I can toss out all my expensive hardware and do my job with a hi-res Chromebook and steady wifi.
One day you might not have a choice because the desktop is so locked down.
People should stop digging themselves deeper into Apple's and Microsoft's ecosystems that are getting more and more locked down by the year.
Earlier quoted context omitted.
You missed https://code.xyz ! We just announced our $2M fundraise from Stripe (totalling $4M to date) [1]. :) [1] https://stdlib.com/blog/stripe-code-xyz/
I think leading with the fundraising amount isn't the best way to plug around HN.
Earlier quoted context omitted.
How long until the email client is also part of Gitlab?
Honestly, I bet they'll do a chat system next to try and replace Slack. One that comes with a @gitlabot which triggers CI/CD using DMs and hashtags.
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.
Hey there. I'm the developer who made the POC. My original idea came after watching non-technical people try to make changes to the readme. They would have to ask for a lot of help to get the terminal open or use a GUI. When really all they wanted to do was make a quick change. The idea is that there's a lot of different users using git and I want to make it accessible for everyone.
Earlier quoted context omitted.
But why write code on the web? If you are typing you are already on a computer
Lots of companies do their development work on per-developer remote VMs, especially for resource-intensive applications that need nontrivial configuration-management setup for databases, message queues, etc. that they depend on. Currently your choices are emacs/vim over SSH or sync from your local machine (where the code intelligence / debugging integration probably doesn't work as desired). A web IDE allows an arbit…
VNC isn't the right way to go in these cases. If a company is asking its developers to do remote work over VNC, and they aren't a three-person company struggling with financial and administrative resources, what they need is an IT manager and/or a build system engineer, not a web IDE. We already have plenty of IDEs that can't hold a candle to Visual Studio, the umpteenth one BUT ON THE WEB is pretty much the last thing we need.
Why are people building these verticals? What happened to Unix philosophy? Build tools that do simple things, and make composition do the work for you. I don't see why anyone needs an online IDE. Much less one interfaced with Gitlab. What next, invent a new cpu too?
Just because it's unified at the presentation layer doesn't mean its design doesn't follow the Unix philosophy. The problem is that even if the web was composable (`gitlab.com | jenkins.com | tee cloud.google.com aws.amazon.com`), it probably wouldn't be accessible to most users. Unix philosophy is great for system builders, but system users want the car, not the tools and parts.
This kind of ‘user centric’ justification is rubbish and we all know it.
What this is, pure and simpe, is ‘throw it at a wall and see what sticks’.
Maybe people will like it and they’ll run with it, or maybe people will hate it and it’ll get binned.
Fair enough; but its got zippo to do with user quality of life or what users actually want; its just easier to justify value by adding features than fixing existing ones.
‘Speculative development’
Bitbucket does this all the time as well; its super annoying.
If you want to improve user quality of life, you know what you need to do?
Ask users what they want. ...and listen.
Earlier quoted context omitted.
Just because it's unified at the presentation layer doesn't mean its design doesn't follow the Unix philosophy. The problem is that even if the web was composable (`gitlab.com | jenkins.com | tee cloud.google.com aws.amazon.com`), it probably wouldn't be accessible to most users. Unix philosophy is great for system builders, but system users want the car, not the tools and parts.
Says who? This kind of ‘user centric’ justification is rubbish and we all know it. What this is, pure and simpe, is ‘throw it at a wall and see what sticks’. Maybe people will like it and they’ll run with it, or maybe people will hate it and it’ll get binned. Fair enough; but its got zippo to do with user quality of life or what users actually want; its just easier to justify value by adding features than fixing exis…