279 karma · joined May 21, 2016
I'm surprised that the machines are that large, there must be a bunch of people using the service nowadays :) I remember the setup being even smaller in previous blog posts. But I really like it. Small, easy to reason about. Makes debugging when stuff goes wrong quite easy.
I'm a bit surprised that there's no config management listed though - seems like it really is just Fabric + a bunch of scripts. But hey, if it works, great!
The thing that this allows (and the companies that inspired this stuff, e.g. GitPod) is to codify your development environment - similarly to what has been happening in the infrastructure world. And I'm not talking about editor configs, but the entire toolchain.
Of course, if you're just working on one main project, or a few with a shared toolchain, this won't be adding much value for you. But as soon as the matrix between development environments and projects get bigger, this becomes a huge productivity boost.
Think about a mobile (as in, moves around a lot) developer that uses many different devices - there's no additional work to keep those environments in sync, or set up a new one. It will just work in the browser.
Or a bigger company with many projects and many people (think devops) that need to jump into different projects all the time. I don't want to waste my time setting up the specific toolchain for that project, or even check it out - I can just open up a pre-configured, guaranteed-to-be-working dev environment in the browser in a few seconds and get going. This would by my personal use-case, and I'm super excited to see this happening.
I was already thinking about setting up GitPod for our company GitLab, but if GitLab manages to combine the GitLab CI/CD Runner Session feature with this IDE for background tasks (compilation, terminal, etc), you would get 90% of the awesome-ness of GitPod for free with your regular GitLab setup.
But yes, public university in Germany is really, really cheap.
You can also often apply to have the semester fee waived due to financial hardship or special circumstances, though I have no experience with that.
Never again.
Why is this not a firmware addition? Why is this windows only? Why the ILCE-5100, but not the ILCE-6000 which is _super_ popular? Why is the PlayMemories App stuff still a unusable mess?
Sorry, was maybe a nice idea in the beginning, but the execution is disappointing. I'll stick to my capture cards and stay on the lookout for a proper camera. The zcam e2-m4 is looking better every day I have to work with this stuff...
So, maybe some of the microsoft employees feel the same about Teams, and that's why they still use Slack? Interesting though.
I'm not against Docker, I run a whole cluster of Docker hosts as my job, but touting it as a solution to a hard install for a _php app_ is crazy.
Besides: You're cutting a whole lot of people off because this is apparently not installable on regular shared hosting, etc. Running a Container is even less of an option for these people. And then their only option is to use their hosted version, having to trust them.
Also: Running a Docker Container again requires me to add additional config, be it via labeling (when using reverse proxy with SD, e.g. traefik), or setting up a new nginx config file for that. No benefit in reality.
I'm not against having an additional Docker Image (I like those!) but these should only be considered a option for people who are looking for a Docker image explicitly.
Seriously, I hate this trend to bloat up websites with the rage of a thousand suns. There is absolutely no value, but it increases bandwith usage, load times and CPU/RAM usage. News websites having "fancy, modern" websites actually make me think less of them.
Fuck this web-bloat shit. The web is broken.
Shell Access, pretty much every common language available, service running, databases, mail, etc..
No bullshit hosting in germany, Pay what you want (1€/month minimum).
Absolute best, I'm hosting about 25 projects with them for various bands, etc. and haven't had any problems whatsoever.
It still doesn't solve the biggest problem the node.js and javascript ecosystem has IMHO: dependency hell, thousands of trivial packages, just utter chaos.