1,791 karma · joined October 5, 2007
My website: mikegioia.com
[ my public key: https://keybase.io/mikegioia; my proof: https://keybase.io/mikegioia/sigs/mhXGRcd_QeoctAluifTMQlJYa8rQaKTrO19NzI4bjtg ]
We've started doing something similar with our front-end apps, but it's not placeholders. Our router is set up to store page markup (indexed by DOM node ID) at the end of every page request. So for the dashboard, we'd save something to localstorage with the key "APPNAME.domstate.dashboard":
{ '#nav': $nav.html(),
'#header': $header.html(),
'#main': $main.html()
...
}
We compile HTML templates for every root page (in this case dashboard). On every new page load, the template is set up to look for the domstate in localstorage before it downloads any JS and bootstraps the application.Since the HTML files are aggressively cached by the browser, and since the localstorage injection happens first, we can re-render the last version of that page for the user before the new data is re-populated. It works pretty well, but the drawback is you may see content flicker when it updates.
The Nokia n900 was the last "openish" phone to come out and they stopped making those in 2011 when, guess what, they were bought by Microsoft.
Every time I'd open a support ticket I felt like I was a second-class citizen or that the issue I raised wasn't important to them. Continual, multiple years or bad support from them. I get that we were paying $25/mo but I just couldn't deal with it anymore.
I've been really impressed with Gitlab and we use that as a backup right now but I really think I'll be moving all of our repos over to them. Plus, you can even host your own Gitlab server.
I have to admit that I did not do any web development
...
I also know about it from interaction with frontend
developers themselves and from toying around it
Do you believe that people who have never done something are capable of understanding it well enough to have the abrasive and ignorantly arrogant stance as your own? You either do and are ignorant, or you don't and are a hypocrite. From startups to the Fortune 500, hundreds of
thousands of developers *trust us*.
Trust you to what? Pull the rug out at some point? Why they even put that word on the HP is a separate question.First off, Mozilla didn't have FF "fall into their lap" from Netscape. Netscape spun it off and gave birth to Mozilla. They absolutely do not consider Firefox legacy software and you'll need to back that up somehow for me to believe it.
They may very well be a better company at $2M than they are at $300M, but the back half of your comment sounds bitter and angry at what appears to be Mozilla's recent announcement on Thunderbird.
Are you suggesting to have a slave ready to become master in the 2nd datacenter? If that's the case, my main area of uncertainty is: if you promote a slave to master in a 2nd datacenter and that new master accepts writes, you then have a brutal problem of propagating writes to the old master when he comes back online.
The whole thing may exceed my capability right now but I think having a disaster recovery is far better than a mirror now that I think through it.
Edit: how about a response instead of downvotes?
The short of it is that I run the following. (I know this repo has our public keys, but if you clone it you can totally run this as well to see what's going on).
./bin/root-ca.sh
./bin/tls-ca.sh
./bin/client.sh
The first command will create the Root Certificate Authority in your tiered system. The second one will create a TLS Certificate Authority underneath the Root. This TLS CA is for issuing certificates (like browser client certificates, or email S/MIME certificates). Finally, the last script will walk you through creating one of these client certs.The client.sh script will generate a .p12 file that you can import into Keychain or your browser's certificate store. The only other step is to import the Root certificate (mine is TeachBoostRootCA.crt in the ca folder) into Keychain and/or your browser.
If you're curious, take a look at the config file in the top level directory. This has all of the naming conventions my repo uses but if you clone this, clear the 'ca', 'certs', and 'crl' folders, then you can have free reign on running your own Certificate Authority. The scripts will walk you through everything but if you have any questions don't hesitate to open a GH issue on that repo and I'll get back to you there.