Twitter | Search | |
James Long
Finally launched ! Created . Ex-Mozilla.
17,158
Tweets
867
Following
19,464
Followers
Tweets
James Long 8h
Replying to @styfle
this is fired when a github *release* is made, not based on branches or anything, so neither service has a way to automate that. although I think once github actions comes out that will enable these custom flows on hosts
Reply Retweet Like
James Long 8h
Replying to @retornam
no, just using a simple webhook. I'm assuming github actions could replace this hook though
Reply Retweet Like
James Long 8h
Replying to @jlongster
I'm usually a fan of simple backend servers to serve dynamic content, but I get it. generating a site allows you to pull content in from tons of places (slow) but since you only do it once it's OK
Reply Retweet Like
James Long 8h
Replying to @jlongster
feels good to automate things: created a webhook that github fires which kicks a netlify build which rebuilds the gatsby site. This means when I publish a new version the release notes on the site are automatically updated (pulled from github releases):
Reply Retweet Like
James Long 8h
Wrote my first AWS lambda function AMA
Reply Retweet Like
James Long 10h
one theory is that dev mode is slow enough that it kicks in the heuristic to abort rendering more often?
Reply Retweet Like
James Long 10h
definitely potential, for some strange reason when I compiled my app in production mode those UI improvements were lost. didn't have time to look into it, but async mode is early so I decided to wait
Reply Retweet Like
James Long 13h
Replying to @steida
is it just the SSL error you see? netlify hasn't generated a cert yet...
Reply Retweet Like
James Long 13h
Replying to @steida
Still? switched DNS to host on netlify and might have been propagating
Reply Retweet Like
James Long 16h
fwiw I added a warning to my example repo. Looking back not sure I would have posted it like this, should have made the dangers more clear (forgot how careful I've been to avoid problems)
Reply Retweet Like
James Long 17h
There's little danger in that though as the server only exposes their data, nothing else. They can also run arbitrary node code locally, it's the same thing
Reply Retweet Like
James Long 17h
That's true. Remember in my case there is no untrusted JS code being pulled in in the frontend either. It's entirely local. But you've reminded me how careful you have to be.
Reply Retweet Like
James Long 17h
Sandboxing the backend would be nice, but in the current state, how is security any different than running node on a server? You don't want users to do any of this there either, but nobody is saying node is highly insecure for cloud servers
Reply Retweet Like
James Long 17h
Replying to @arcanis @rauchg and 5 others
I've used it before too, but sqlite performance determines the entire performance of my app and I've fine-tuned queries to run within 20 microseconds, and fine-tuned disk IO. skeptical the web can deliver the same
Reply Retweet Like
James Long 17h
Yeah, that's a big deal
Reply Retweet Like
James Long 17h
I like the idea that has been talking about to run a "backend" process as a shared/service worker that all tabs talk to. Would give a similar feeling, though dock/menu is harder but I'm not convinced full Electron is needed for that
Reply Retweet Like
James Long 17h
That's fair, which is why I barely use any dependencies in the backend process. You can throw npm out without throwing out node.
Reply Retweet Like
James Long 17h
In my opinion, if you can do everything in a renderer process, it should probably just be a web app and run in the browser. What advantages do electron bring by that point?
Reply Retweet Like
James Long 17h
Absolutely, the closer it gets to providing all the right desktop APIs the more I'll consider it! Historically the web has failed to provide on these fronts though so I'm pessimistic
Reply Retweet Like
James Long 18h
What do you use for Hyper? it's a local app by definition so you've gotta expose desktop functionality somewhere
Reply Retweet Like