Was really interested in just the Sqlite portion, and am so glad you showed ignoring designating types for the field. You have likely saved me many future minutes! Thank you.
@mrrolandlawrence2 ай бұрын
wow a blast back to dBase III and Clipper days ;)
@DavisTibbz2 жыл бұрын
Good presenter! 😃
@_alexlazar_7 ай бұрын
Great talk
@int4_t2 жыл бұрын
golang laptop leak???
@Osmanity3 жыл бұрын
I like the "programming style" of powerpoint, any one know how or where to get this type of powerpoint style?
@chrispowell55986 жыл бұрын
Awesome thanks! Any more information on Gomobile?
@dn54266 жыл бұрын
Looks like "eliasnaur" took over the development. github.com/golang/mobile/commits/master github.com/golang/mobile/commits?author=crawshaw
@YoloMonstaaa4 жыл бұрын
3:58
@constantinegeist18549 ай бұрын
24:24 "I can scale my server until I hit a limit" if you multiply your server N times and put a simple proxy in front of it which redirects traffic "tenant => server" (with some kind of in-memory tenant table), then you can scale further. So far doesn't sound like rocket science to me tbh.
@DaDa-gr7cyАй бұрын
That way you potentially running multiple instructions at the same time which is fine when you have 1 database instance.If you multiply the database N times. then its rocket science
@probinebusiness43676 жыл бұрын
live coding is really different from live copying
@pimbrouwers10046 жыл бұрын
I know in my bones that the concept presented here about 1 process programming makes a ton of sense. I just don't get how I practically implement it, for say a simple REST API reading from a SQLite database.
@benjaminjones96263 жыл бұрын
It comes with time don't worry about it. This level of engineering happens when you start to understand that reliable software is a many-thousand-hour exercise not a late night and a red bull away - and believe me the feeling is miserable because simultaneously you'll understand all those cool apps you always wanted to build aren't actually worth the time.