text stringlengths 0 1.17k |
|---|
[1629.46 --> 1634.50] maybe you could tee it off by you know you mentioned the goal of you know programming being accessible to |
[1634.50 --> 1639.70] everybody but can you kind of give us what exactly is t edit kind of give us the high level overview |
[1639.70 --> 1644.90] let's let's start diving into some of the details around what it does and how it works and where you see |
[1644.90 --> 1651.94] it going sure so yeah js gets just a library it was just a means to an end and then t edit itself |
[1651.94 --> 1658.82] is the developer environment and the goal there is is i want to i'm thinking of two two main use cases |
[1658.82 --> 1664.26] one is me i like being a random machines like my chromebook pixel for example or who knows what else |
[1664.26 --> 1669.78] maybe my android tablet and i want to be able to do work there and then kids in my programming class or |
[1669.78 --> 1675.54] just anywhere who are learning i want them to be able to use any machine they have i chose chrome |
[1675.54 --> 1682.34] app for now because it's everywhere nearly if the machine has chrome it can run chrome apps |
[1683.38 --> 1688.82] so that's all laptops including chromebooks and desktops and there's a lot of chromebooks in schools |
[1689.62 --> 1694.26] i thought lots of kids had them maybe that's not true i don't know and then two the platform is |
[1694.26 --> 1699.14] very powerful it gives you primitives the web doesn't have i can access the file system i can make a |
[1699.14 --> 1704.26] web server i can get around the cores restriction and talk cross domain you have all these extra |
[1704.26 --> 1713.54] primitives that the browser doesn't have so the the chrome app that's in the the store right now |
[1714.26 --> 1721.62] is basically an ide that edits git repositories directly it does not edit files on disk and this |
[1721.62 --> 1724.82] is a very important distinction between t edit and all the other editors in the world |
[1724.82 --> 1731.38] in everything else git is a tool you use on the side that creates a working directory and then your |
[1731.38 --> 1736.10] editor works with those files on the hard drive and then when you go back to git you pull those files |
[1736.10 --> 1743.78] back into the git database whereas in t edit you never have a working directory ever you always work |
[1743.78 --> 1748.74] directly on the git database so it's a it's a it's a slightly different way of working |
[1748.74 --> 1756.10] does that make for a better user experience or more approachable than than the traditional way |
[1756.10 --> 1761.14] i'm still exploring that one of the things that i found that i like i really like so far is i found |
[1761.14 --> 1769.22] a way to make sub modules not suck really yeah because the concept is not wrong just the ux in the |
[1769.22 --> 1775.22] real git client is terrible it is horribly terrible and this is why people don't use sub modules because |
[1775.22 --> 1780.34] they'll bite you yeah i mean i've personally given up on them a while ago so i don't even know what |
[1780.34 --> 1784.66] the current state of sub modules is because i just nothing's completely just flush them from my brain |
[1784.66 --> 1792.50] no nothing's changed it's okay no one works on it as far as i know okay but like the main issues were |
[1794.10 --> 1799.46] one it doesn't record the branch you're working on like the way it's actually implemented is very |
[1799.46 --> 1805.38] simple in the tree blob for that file listing it's just type commit and then the hash is the |
[1805.38 --> 1810.90] hash in the other repo that's it no other context it just points to the hash in another repo and then |
[1810.90 --> 1816.58] in the root of your project there's a git modules file right that maps that path to a remote url and |
[1816.58 --> 1823.22] that's it so by default in the normal client you're in if you change anything you get thrown in a detached |
[1823.22 --> 1827.38] head state and then if you move some stuff right in the parent repo it'll revert your code without |
[1827.38 --> 1832.34] even warning you and your changes are gone and if right if you forget to push the sub module |
[1833.06 --> 1836.90] and then push the main one it'll point to a commit that doesn't exist on github and like it's a |
[1836.90 --> 1845.06] nightmare so how do you fix it so with t edit everything is one big continuous virtual file system |
[1845.94 --> 1852.34] and sub modules are just mapped in like you do an nfs or samba mount and you can just browse them as |
[1852.34 --> 1857.14] if they were local files and depending on which back end you're using it works really well i have a |
[1857.14 --> 1863.38] github back end that actually mounts the repos using github's rest api and uses github as the |
[1863.38 --> 1871.46] data store instead of a local data store i have a local cache to make it faster but all the real |
[1871.46 --> 1878.42] actions happen directly on github and so suppose i edit a file in a sub module i will then save that |
[1878.42 --> 1884.58] blob to github which gives me back a hash and then i modify the parent tree to say hey it points to this |
[1884.58 --> 1888.26] new hash and then i save that and gets new hash for the parent tree and i do this all the way up to |
[1888.26 --> 1894.10] the root tree and then once the root tree has a new hash i create a temporary commit pointing to that |
[1894.10 --> 1900.02] root tree and then in the parent repository i update the sub module entry to points to that new temporary |
[1900.02 --> 1906.74] commit and then this prop gets all the way up to the root so anytime you change anything in a |
[1906.74 --> 1914.42] t edit tree it's saved all the way up in all the parent repos and so if you knew the the hash to |
[1914.42 --> 1918.26] the temporary commit you could see all these temporary state of your files in github |
[1920.34 --> 1924.90] but that's all in the background like you don't actually see that temporary commit right since i don't |
[1924.90 --> 1930.26] actually move the reference i don't actually move head none of it's visible and in fact if you don't |
[1930.26 --> 1933.78] commit it within two weeks it'll probably get garbage collected by github's back end |
[1933.78 --> 1939.46] hmm so you don't want to be in this state for a long time like i i commit my code every day just |
[1939.46 --> 1945.30] because i don't trust my local machine and not eat my code right is this is this keying off of the |
[1946.82 --> 1950.58] just watching we'll link out to this too so if you're listening we'll we'll have this youtube |
[1950.58 --> 1955.94] video we're going to mention uh we mentioned earlier tim's awesome demo of this which it was |
[1955.94 --> 1962.82] very enlightening and mind-blowing but you said in the video uh it's always committing is that just um |
[1962.82 --> 1967.46] is that kind of like committing to your local git repository and then finally doing a final push |
[1967.46 --> 1973.78] whenever you want to do a commit of that code and is that kind of like a rebase of that or or |
[1973.78 --> 1977.62] whatever to kind of munch it into one commit is that what you're doing or is it something more unique |
[1977.62 --> 1985.38] than that no it's um so like like i said when i'm using the github back end your jsgit instance is a |
[1985.38 --> 1990.82] proxy to github there is no local database there is no clone there is no pool there is no fetch there is no |
[1990.82 --> 1997.70] push you are literally modifying your data on github directly like if you open up the terminal you can |
[1997.70 --> 2003.70] see rest calls just flying back and forth but it actually performs pretty well so how does that |
[2003.70 --> 2008.66] handle offline is it just queue them up and wait it doesn't or it doesn't okay i have a task for that |
[2009.30 --> 2014.66] okay because i want offline though right i mean you got a lot of this it's offline and secure i heard |
[2014.66 --> 2018.02] that a couple times in the video can you talk about that is that a good time to talk about that or |
[2018.02 --> 2023.54] uh sure so the backends there's lots of backends for jsgit there is no one back end the jsgithub |
[2023.54 --> 2028.34] back end is the one that live mounts github repos it's the one i use the most because i don't have |
[2028.34 --> 2035.70] push and pull implemented and so i can't sync and so i just use that one but once i implement the |
[2035.70 --> 2040.90] network protocols the other backends will work great there's an index db back end i was working on a web |
[2040.90 --> 2046.90] sql back end this morning there's i had a local storage one but i don't know if it's still maintained |
[2046.90 --> 2053.30] because there were some issues there mostly with just limited space if you're a node i have a back |
[2053.30 --> 2059.46] end that can that can read and write real git repos off disk so it implements that format that dot get |
[2059.46 --> 2065.30] folder i have the same thing for chrome apps because chrome apps can access the native file system so you |
[2065.30 --> 2071.14] can mount a native git repository using a chrome app edit it and t edit and then push it from the |
[2071.14 --> 2077.46] command line if you have node or if you have git so there's lots of backends and it's very flexible |
[2078.26 --> 2084.34] there was i had people talking to me one company thought about using s3 as a back end and all i |
[2084.34 --> 2090.26] really need is a key value store that's the bulk of what git needs for its storage so it's depends on |
[2090.26 --> 2097.54] what performance you want you can use anything as the back end yeah but yeah i haven't i haven't |
[2097.54 --> 2102.58] implemented push and pull fully yet i haven't implemented merge or diff because and those are |
[2102.58 --> 2106.82] being on the js get side right not on the t edit side yeah they're part of js get but t edit will use |
[2106.82 --> 2112.74] them it'll it'll expose interfaces for them and yeah that's that's where i was when i ran out of money |
[2112.74 --> 2118.02] i was i was implementing that stuff and then i couldn't get done so you mentioned you're you ran out of |
[2118.02 --> 2124.74] money where what is the state of this project right now i guess from uh obviously you're passionate |
[2124.74 --> 2129.86] about it so that that kind of goes without saying but you know are you out of money what's the next |
[2129.86 --> 2135.46] step to giving yourself the necessary time to keep building this and i guess what is your direction |
[2136.50 --> 2142.98] so i've got some consulting work till end of june and after that i'm going to take another run at it |
[2142.98 --> 2148.82] see how much i can get done and see if i can find more novel ways to fund it i don't know yet |
[2149.94 --> 2156.34] how i'm going to do that i'm just trying to survive and get there some some ideas i had was t edit |
[2156.34 --> 2162.02] consulting where people would want to use js get or t edit in their product and they could pay me to |
[2162.02 --> 2168.50] integrate it into their platform and i found some interest there from a few companies i could do |
[2168.50 --> 2174.10] one one thing i really want to do back to my original goal is i want to make games i want to |
[2174.10 --> 2179.94] make simple games make them open source and then write docs about how to write games so these kids |
[2179.94 --> 2186.34] can get into programming and i was thinking about maybe selling podcasts or tutorials because people |
[2186.34 --> 2191.06] seem to want to pay for that what i don't want to do is i don't want to charge for the code |
[2192.26 --> 2197.30] because i'm essentially writing infrastructure and infrastructure should not be for pay it should be freely |
[2197.30 --> 2200.50] available because it's just code it doesn't it's not like it cost me anything to copy it |
[2202.02 --> 2207.22] so i want t edit and js getting all the code itself to stay open sourced mit or apache something very |
[2207.22 --> 2213.94] very liberal and find other ways i've considered another fundraiser but like i said before i don't |
[2213.94 --> 2218.90] think that's sustainable yeah it's well especially if you've been through two and the second one |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.