Earlier quoted context omitted.
What? Doesn't even make sense. Why would lacking a physical desktop cause developers to make bad software?
Many developers in now and before like to have their own desk/space it helps them think. Getting ride of that space or changing may not be optimal for many developers I've worked with.
We are still early with the cloud
71–80 of 202 posts
Re: We are still early with the cloud
#72Earlier quoted context omitted.
I don't use k8s or whatever garbage gets thrown around nowadays. I well remember my disgust when I learned AWS was just using UNIX virtual machines or whatever, rather than something simple, such as allowing people to run little functions floating in the void. I know nothing about AWS, but I've not been mistaken, right?
Well AWS has been quite clever, using both Xen originally and also now KVM VMs, but everything else is based on that yeah. But that's gotten really complex over the years. They now use a container execution environment called firecracker or something that is open sourced and might be totally separate from their virtualized environment - or at least on top of it where they do let you just run little jams. Cloud isn't…
I ran 1000s of physical Linux servers over the decades using chroots when it was not fashionable to have containers yet with db clusters because I don’t want my laptop to be different than my servers and I don’t want to think or worry about scaling.
We have aws Lambda now, but it is too expensive and, for me, not trivial enough. It actually requires too much thinking (architecting) to make something complex with it and a lot of that is about money; you can stumble into bills that require at least a kidney to settle.
So I still run my own servers, these days with openfaas. With many scripts, it is almost painless and costs almost nothing (we provide for millions of users for a less than 200$ a month in total). But it still is not the dream: I still cannot just forget about everything hosting and abstractions still leak enough but at least I don’t spend more than a few hours a year on it and I don’t go bankrupt like can happen with Lambda.
We are building our own language and runtime (lisp like with types) to fix this: after 40 years of programming, I am pretty much fed up with having computing power and loving programming but having to deal with all this pointless (for programmers!) stuff around it: we went backwards, at least somewhat.
Re: We are still early with the cloud
#73It'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,…
It just went away due to Microsoft crowding it out.
Re: We are still early with the cloud
#74Earlier quoted context omitted.
"It's crazy and destructive that we are still using the unix paradigm in the cloud." # ssh user@rsync.net "test -f fileThatExists" #echo $? 0 ... from my cold, dead hands ...
Quoted post unavailable.
The great thing about Linux as the base layer is that it allows a commodity common ground with a very capable system that also facilitates more specialized layers to be implemented on top of it.
Re: We are still early with the cloud
#75Earlier quoted context omitted.
Having heard complaints of Google developers, the problem with this is the limitation of Chromium and the browser more generally. Browsers are utterly terrible at letting users script their own shortcut etc.
It's perfectly possible and in fact quite pleasant to work with intellij inside google. At least for JVM languages. Disclaimer: I work for google
Re: We are still early with the cloud
#76Earlier quoted context omitted.
Quoted post unavailable.
That is far, far more than transferring a byte of data. It's not the future though of course, this was well established in the 80s, it just so happens that it's a decent model for managing remote machines that outlasted over-engineered distributed designs like Plan9, VMS, MOSIX, etc. It's much more meaningful and useful than "something simple" "running little functions floating in the void" which just sounds like som…
Educate me.
It's much more meaningful and useful than "something simple" "running little functions floating in the void" which just sounds like some vapid marketing pitch.
That was a quick response to what I thought would be better than administrating a UNIX system on an Amazon machine. Don't be an ass. I've no experience with the real distributed computing systems created before UNIX.
The great thing about Linux as the base layer is that it allows a commodity common ground with a very capable system that also facilitates more specialized layers to be implemented on top of it.
No, that's the vapid marketing pitch. The Linux kernel randomly kills processes when it starts exhausting memory. It's garbage.
Hey, Brainfuck also facilitates more specialized layers to be implemented on top of it. Now, what's stupid about doing that, however?
Re: We are still early with the cloud
#77Earlier quoted context omitted.
> Since reading the blog post's mention of Repl.it I went and downloaded their new Iphone app and used Modal.com to spin up 30-40 containers from a script doing sentiment analysis on ~30k movie reviews: IPhone processors run billions of cycles every second and are capable of running billions of instructions every second. I'm amazed that we've gone from "Run doom on my toaster", to "I can spin up 30-40(!) containers t…
I think related to the article, this would fall under the lift and shift concept the author described. What the author really wants is a transformative experience around developing in a way that is cloud native. So don’t apt install packages on your alternative iPhone which has a Linux container option built into the OS. Instead, tap a few buttons to say you are developing a webapp with a node backend, Postgres db, a…
Every business is unique and there isn't a universal generalisable useful solution here which is also simple. Hence why Platform teams exist.
Re: We are still early with the cloud
#78Saying that Spotify is "producer-friendly" must be couched in the context of the times. 100% of $0 is still $0, and at the time most people were just pirating music so you weren't making anything off of recordings. If Spotify wanted to give you literally fractions of a cent instead of $0, you were going to take that. I wouldn't say it was ever really friendly to producers...mostly to consumers and, in order to be fri…
Spotify pays up to 70% of their revenue to copyright holders. So, your beef should be with them, not Spotify. Which you should already be aware of if you truly are a music producer. However, it costs you nothing to bash Spotify. It may cost you your career to bash the actual greedy leeches who control the money flows in music.
until spotify pays from MY subscription the artists I listen to, they will not see money from me. bandcamp all the way.
Re: We are still early with the cloud
#79Interestingly, 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…
Re: We are still early with the cloud
#80Earlier quoted context omitted.
It's perfectly possible and in fact quite pleasant to work with intellij inside google. At least for JVM languages. Disclaimer: I work for google
Wait, I remember Google gave up supporting IntelliJ around 2011, leaving only one full-featured IDE, Eclipse, as the only option. Did it change since 2011?
The Perforce plugin is Piper compatible, and works really well.