5 ms·
It's not only an awesome technical achievement, but it has also so much potential to be useful. And yet, something at the back on my head is screaming: WARNIN
by BiteCode_dev 5y ago
It's not only an awesome technical achievement, but it has also so much potential to be useful.
And yet, something at the back on my head is screaming:
WARNING!
I have the intuition that, on the long run, using more and more tools that are not on your own machine will create a dependency on systems big companies control. And something tells me we are going to pay for it in the end.
So I'll stay away.
Maybe I'm getting paranoid, but I don't regret not having ever created a Facebook account, or not getting on the 2010 hype train of magical SAAS services like Firebase that lock you in eventually.
We'll see in 10 years I guess.
- deleted 5y ago[deleted]
- blumomo 5y agoOn your site. Never going to use these tools.
- idle_zealot 5y agoThis is running on your machine though. The browser downloads vscode as a SPA-style thing, and runs the editor in the browser sandbox, and can edit local files/directories.
- BiteCode_dev 5y agoSure. And the google map api is free to use, you can send tweet using sms, facebook doesn't show ads and web services never change policies once they get enough users. Good thing it's running on your machine and you can see and control when it updates.
- nbzso 5y agoThis is my personal opinion. I don't imply in any way or form that my point of view is right. You can down-vote, call me names, or ignore what I am sharing. I don't care. Since Apple CSAM attempt, something at the back of my head screamed: Regroup. React. Change. Now. Two months after Apple's "postponing for better implementation": My company runs on Arch/Manjaro (over old MacBooks Pro without T chip, custom PC's, etc). There is no iPhone in sight - my colleagues/employees found personal alternatives. I use DeGoogled Android device for banking app and flip phone. Designers are with powerful Linux boxes: Windows VM - mainly Figma (I don't like it, but this is production standard now) and Affinity Designer/Photo. We use mainly Vim/Emacs/VSCodium/Sublime. Vendor lock-in is inevitable, SaaS business logic is based on this premise. I don't care how cool it is, or how 'trendy', there is no way my company production code to be served as a "free petrol" for some monopolistic/"good intention" scheme which will feed AI advancements geared towards removing of skilled professionals. I don't like SaaS apps direction at all. We have powerful hardware now, there are proven ways of collaboration with FOSS, moving everything in the browser is utterly insane. I cannot hide how I feel about the lack of critical thinking in designers and developers today. They are always ready to jump on the bandwagon just to feel 'cool and important'. Call me crazy, or paranoid. In 5 years time all will be transparent and obvious even for the most "optimistic" ones.
- pjmlp 5y agoWe are back at UNIX/VMS/mainframe timesharing infrastructure. SaaS direction is the only way people have found out to extract money from open source tooling that devs don't want to pay for, it is either SaaS or hardware, so there you have it.
- nbzso 5y ago> We are back at UNIX/VMS/mainframe timesharing infrastructure. It is worst. We are in the new times of "surveillance economy", "data hoarding", politically driven business decision making, 4th industrial revolution, real-time data driven "psyops" and "marketing", "AI advancements", you will own nothing and you will be happy. I will gladly return to UNIX/VMS times with low connectivity, real human connections and minimal dark patterns in design and product implementation:)
- ramses0 5y agoIt's already that way. It's immensely hard to "develop on an airplane / desert island". eg: even documentation is at best something like "dash" => https://kapeli.com/dash https://kapeli.com/dash ... forget about anything more complicated than SQLite, and if you're lucky docker-compose for occasionally connected use. My experience? Chromebook / Crouton, usually offline with occasional network access. I ended up leaning hard towards SPA's + javascript, with most of the documentation being "legit" available. (JS, HTML, CSS, DOM, etc.) ...occasionally researching + pulling in libraries on occasion.