4 ms·

The cloud is going to change a lot of stuff, file-system based code might be gone, code-in-database is already halfway here ... opportunity

krasin 7y ago
I agree with the first half of the statement: we indeed do not have a cloud-first version control system. It could bring some real benefits of tight integration with continuous build and other things considered to be essentials nowadays. I don't see files going anywhere. I would like to listen to examples of "code-in-database is already halfway here", if you happen to have them.
- dustingetz 7y ago
  My startup is one http://www.hyperfiddle.net/ http://www.hyperfiddle.net/ Others are https://darklang.com/ https://darklang.com/ and https://www.unisonweb.org/ https://www.unisonweb.org/ and of course scripting google sheets with javascript Low-code is very suddenly going to be a big thing in the next couple years and when it happens there are now 750M more "coders" and those types of people are not interested in git pull --rebase --fucked --whatdidido
  - krasin 7y ago
    Thank you, very interesting pointers!
- wtetzner 7y ago
  Of course, you could probably build some pretty convenient cloud-syncing tech on top of Git without a ton of effort.
agumonkey 7y ago
tree diff over graphql
- dustingetz 7y ago
  Yes great point - also git for data and databases e.g. Datomic
  - agumonkey 7y ago
    immutable graph series ftw
rhabarba 7y ago
"The cloud" is still file-system based - and it CAN and WILL disappear over night.
jerf 7y ago
I'll believe it when I see it and it's an actual improvement. It's not like "cloud" is some sort of Platonic embodiment of goodness and anything that is "cloudier" than an alternative is automatically better. All the attempts to put code in "databases" I've ever seen make easy things sorta easy and make medium things way harder and you can just forget about hard things; if I can't do the equivalent of "perl -pi -e 's/OldVariable/NewVariable/g' then it just isn't going to displace a file system for me. Not because I need that exact commmand or perl, but for what it represents, the ability to just do things to my code as needed, without needing to wait for someone to implement an API or sluggishly do it over a network. Another example would be just throwing a code analysis tool at my code without needing some sort of permission from my "cloud code provider". File systems haven't been disappearing, they've just been getting hidden from users. I have seen exceedingly little evidence that anything beyond merely hiding them is actually happening in the industry. "Stick all the files in databases" seems to be seeing no penetration beyond music collections, which at this point, I think we can call a "mere use case" rather than the vanguard of a revolution, since it's a good 10-15 years old minimum.

krasin 7y ago

I agree with the first half of the statement: we indeed do not have a cloud-first version control system. It could bring some real benefits of tight integration with continuous build and other things considered to be essentials nowadays. I don't see files going anywhere. I would like to listen to examples of "code-in-database is already halfway here", if you happen to have them.

dustingetz 7y ago
My startup is one http://www.hyperfiddle.net/ http://www.hyperfiddle.net/ Others are https://darklang.com/ https://darklang.com/ and https://www.unisonweb.org/ https://www.unisonweb.org/ and of course scripting google sheets with javascript Low-code is very suddenly going to be a big thing in the next couple years and when it happens there are now 750M more "coders" and those types of people are not interested in git pull --rebase --fucked --whatdidido
- krasin 7y ago
  Thank you, very interesting pointers!
wtetzner 7y ago
Of course, you could probably build some pretty convenient cloud-syncing tech on top of Git without a ton of effort.

agumonkey 7y ago

tree diff over graphql

dustingetz 7y ago
Yes great point - also git for data and databases e.g. Datomic
- agumonkey 7y ago
  immutable graph series ftw

rhabarba 7y ago

"The cloud" is still file-system based - and it CAN and WILL disappear over night.

jerf 7y ago

I'll believe it when I see it and it's an actual improvement. It's not like "cloud" is some sort of Platonic embodiment of goodness and anything that is "cloudier" than an alternative is automatically better. All the attempts to put code in "databases" I've ever seen make easy things sorta easy and make medium things way harder and you can just forget about hard things; if I can't do the equivalent of "perl -pi -e 's/OldVariable/NewVariable/g' then it just isn't going to displace a file system for me. Not because I need that exact commmand or perl, but for what it represents, the ability to just do things to my code as needed, without needing to wait for someone to implement an API or sluggishly do it over a network. Another example would be just throwing a code analysis tool at my code without needing some sort of permission from my "cloud code provider". File systems haven't been disappearing, they've just been getting hidden from users. I have seen exceedingly little evidence that anything beyond merely hiding them is actually happening in the industry. "Stick all the files in databases" seems to be seeing no penetration beyond music collections, which at this point, I think we can call a "mere use case" rather than the vanguard of a revolution, since it's a good 10-15 years old minimum.