As soon as a credit card is in the relationship exploration and experimentation is over for me.
My local Linux machine may go on fire but it will never send me an invoice no matter what I do.
101–110 of 202 posts
As soon as a credit card is in the relationship exploration and experimentation is over for me.
My local Linux machine may go on fire but it will never send me an invoice no matter what I do.
Developing on a cloud VM is all fun and games until the connection drops. Will it some day be possible to have a reliable connection everywhere all the time? I donno.
There are things you can still do offline of course. But it gets inconvenient pretty quickly. There's not a whole lot of offline development happening anymore.
So, in the rare case the connection drops, you have a coffee break, and then you reconnect. If that's a regular thing in your life, change your internet provider or networking equipment.
First, > I never ever again want to think about IP rules. I want to tell the cloud to connect service A and B! Dear God this 1000 times. My eyes bleed from IP-riddled firewalls foisted upon my soul by security teams. If I could also never NAT again, that'd be nice. > Why do I need to SSH into a CI runner to debug some test failure that I can't repro locally? Hey I can answer that one. Because an infra team was tasked…
A nice problem to have, I only know the opposite side. Developer laptop being twice the speed of CI.
Interestingly, at Google the typical developer workflow (google3) is very cloud native. Most devs write code in VS code in the browser. Many (most?) devs don't have a physical desktop any more, just a cloud VM. The code lives in a network mounted filesystem containing a repository. The repository is hosted remotely (everyone can see edits you make to any file nearly immediately). Builds are done remotely with a share…
MS have done a fantastic job of getting developers everywhere hooked on VS Code, whether they are writing for the Windows ecosystem or not.
Earlier quoted context omitted.
Think the point is that as I am writing software, I don’t care about any of that. I expected an opinionated environment when I first heard the word cloud 2 or so decades ago; I wanted to put my code in cvs (git now) and that’s it; I don’t want to think of anything outside that. Especially security or scaling. I ran 1000s of physical Linux servers over the decades using chroots when it was not fashionable to have cont…
Quoted post unavailable.
It's crazy and destructive that we are still using the unix paradigm in the cloud. In the 70s we have transparent network fileststems, and by the 80s I had a more advanced cloud-native environment at PARC than is available today.* The Lispms were not quite as cloud native as that, but still you could have the impression that you just sat down at a terminal and had immediate window into an underlying "cloud" reality,…
I completely understand what you're saying. I'm sort of reminded of how the US government is the worst (except for all the rest), when having an absolute ruler should be so MUCH more efficient. Problems would be fixed by fiat. Or maybe, why does lisp persist with its horrible user-unfriendly syntax? :) I guess we will just have to invent it. (and you should do your part by reminding people with examples of old system…
why persists lisp if user-unfriendly else horrible syntax?
sounds more like python :)
Interestingly, at Google the typical developer workflow (google3) is very cloud native. Most devs write code in VS code in the browser. Many (most?) devs don't have a physical desktop any more, just a cloud VM. The code lives in a network mounted filesystem containing a repository. The repository is hosted remotely (everyone can see edits you make to any file nearly immediately). Builds are done remotely with a share…
I've also switched all my dev work to Gitpod a year ago and I don't want to go back to developing locally anymore. I curse and swear every time I need to work on a project locally.
For example, a web dashboard project with its own backend that also communicates with an API, which is a separate project.
Does Gitpod (or Codespaces) support projects (repositories) that work together?
Why not iCloud and OneDrive as they exist today? The problem is that sharing is very primitive and basic on those systems. There's no way for someone to build an Instagram or FaceBook on iCloud.
Earlier quoted context omitted.
Okay, tell me how you do it much better in k8s
you could easily imagine some Python-esque shell language (xonsh?) and have that be: print(os.path.exists("ssh://user@rsync.net:fileThatExists")) A boolean, a still (relatively) terse line of code. And when you end up wanting to do something even a bit more complicated it'll be a smooth gradient of difficulty. As with every discussion around shells, though, the amazing terseness of scripts is great, but every form of…
It's crazy and destructive that we are still using the unix paradigm in the cloud. In the 70s we have transparent network fileststems, and by the 80s I had a more advanced cloud-native environment at PARC than is available today.* The Lispms were not quite as cloud native as that, but still you could have the impression that you just sat down at a terminal and had immediate window into an underlying "cloud" reality,…
> The damned thing even ran sendmail
and?
> Cloud computing really still it "somebody else's computer."
That's the definition of 'the cloud'. Unless you run it locally in which case it's your computer. What's your point.
> There's no "OS" (in the philosophical sense) for treating remote resources truly abstractly
It's unclear what you're asking for. Treating stuff truly abstractly is going to get you appalling and horribly variable scalability. If you're aware of that, why don't you tell us what you want to see instead.
Edit: ok, this is from gumby, now I recognise the name. This guy actually knows what he's talking about, so please tell us what things you would like to see implemented.