• It makes me sad to see AWS continue to grow. I get that it’s cheap and easy, but it’s also proprietary with vendor lock in as far as I understand. I’m sure a lot of it is driven by middle managers chasing buzzwords and marketing though. If I’m wrong, please let me know, but I have a pretty low opinion of all of he proprietary cloud vendors.

    • dandelionOP
      53 years ago

      Agreed. I felt bad seeing those numbers about AWS (and Microsoft Github). And looking at some open source software, it looks like more and more often support for Amazon S3 is baked in, and the first entry in their howtos. I would not mind a world wide boycott of Amazon products.

      • I’m with you there! It’s actually not that hard to avoid Amazon products, at least directly (I’m sure may websites I visit use AWS though). I think the only thing I ordered off of Amazon in the last couple years was a part for my furnace because nobody in town had any stock at the time.

        Maybe it’s just my perception, but I see a lot of young developers fully embracing things like AWS, VS Code, Chrome, etc. There’s a lot of history to show the dangers of proprietary lock-in, but it seems the younger folks either don’t know it, or think it’ll somehow be different this time around. MS is already releasing proprietary, VS Code only plugins, and it makes me sad to see so many open source projects recommend it as an editor. Very similar to your observation with S3.

        I love that I get to write code for a living. I basically get paid for my hobby, and fortunately I works for a good small company that affords a lot of freedom. The industry as a whole is heading into a depressing direction though. I hope the pendulum swings back the other way soon!

        • dandelionOP
          3 years ago

          Good for you! :) btw They are recommending VS Code ? I’ve read that some coders opt for the MIT licensed version, and apparently that IDE is very good : https://vscodium.com though probably a matter of taste and work flow. Some programmers probably will always use Emacs because they are so familiar and skilled with it. I agree on embracing so much closed source software being very bad, in a few years time Google Chrome might be so dominant that Google can “rule” the web.

          • LSP implementations mostly seem to come with a VS Code plugin primarily, and only sometimes will reference how to use the LSP client in other editors. I mean, it makes sense in a way, since VS Code is sort of the flagship LSP client, and authors can’t exactly support every editor people might use. But I can’t help but see it as being free promotion for Microsoft and creating optics to new developers that VS Code is the best or only editor to use.

            I see VSCodium a lot like Chromium. It’s open source with a permissive license, but at it’s core it’s still promoting the product and interests of companies that are bent on control. Last I tried VSCodium I had trouble running some plugins, since they seemed to require the official Microsoft release. Maybe there’s a way around that, but I wasn’t interested in putting in too much effort. :) And with Microsoft having closed sourced their new Python language server, it just leave a sour taste.

            That said, LSP has been amazing!!! I get fairly good language support in Emacs for very little effort now! So that’s one good thing to come of this.

            I just wish these companies were ok making a living with open protocols instead of using trickery and lock-in to maximize market capture… but that’s capitalism for ya.