1,940 karma · joined September 20, 2016
[ my public key: https://keybase.io/styfle; my proof: https://keybase.io/styfle/sigs/k5Jx2P3fJ9JOZsHyU2TLChLetDsvmL2mHK7wJMj-nKk ]
The solution, is to bump the version in the dockerfile, rebuild, and deploy.
This is especially useful when you want to test the latest version before deployment or when you need to deploy to many machines.
Conversely, using a VM and trying to patch it means the updates are not part of the normal development process so you would need to spin up a new VM to test before patching production VMs.
Now sysadmins and developers think differently so this is purely subjective (note I’m a dev), so surely there are merits to the other approach, but I prefer the container approach.
There were fraudulent credit card donations for $1 which became really obvious when the zip code was garbage.
The “solution” was to disabled the credit card page until the month of the fund raising event when it was enabled again in hopes of the scammers would not try during that month.
What you described is basically `hydrate` which is how to enable React event handlers like onClick after a server-side render.
https://github.com/styfle/react-server-example-tsx/blob/4586...
https://github.com/styfle/react-server-example-tsx/blob/4586...
[0]: https://github.com/styfle/react-server-example-tsx/blob/4586...
https://github.com/styfle/react-server-example-tsx/blob/4586...
That's why my friend started Market Wagon[0] which acts as a middle-man between farmers who have crops and people who want to buy the food. The experience is like shopping on Amazon but you're buying local.
> He currently works for Microsoft as the lead architect of C# and core developer on TypeScript.
I have another project[2] with 3% CTR.
[1]: https://github.com/styfle/copee
[2]: https://github.com/styfle/magnemite
Both have less than 200 impressions total.
The best way to describe it is something between a generic Google Ads network and a invite-only Carbon Ads network. And it's really meant to go in your README.md file.
So this results in a few things:
1. Broker. Sponsors can select which repos/languages/tech/etc they want to advertise to and developers can select which sponsors are relevant to them.
2. Transparent. Developers can see which ads a sponsor will display and how much they pay per click (usually $0.40). The ads are usually just text with a couple emoji that fit well into the README.md design and are loaded as an svg.
3. Limited. Sponsors pay a fixed amount so if a repo is really popular and displaying ads, it may stop displaying after the money is paid out to the developers. This means you may just get a generic ad that recommends using Code Sponsor near the end of the month, like this repo: https://github.com/styfle/geoslack
Caveats: it seems the Code Sponsor is not open source :(
I think the difference is Google wants other browsers to implement those APIs by providing a path to standardization.
SPDY was replaced with HTTP2.
NaCl was replaced with Web Assembly.
WebSQL was replaced with IndexedDB.
Chrome extensions kind of became Web Extensions.
I love this quote. I think I've heard it said a little differently but it is most definitely true if you work anywhere more than a year.
1. Does it sync deltas or do you have to import the whole table each time?
2. Does it listen for changes to a table or does it require a manual invocation?
3. Can you explain more about the algorithm/implementation?
Update Maybe this:
http://www.cvedetails.com/product/15031/Google-Chrome.html?v...
http://www.cvedetails.com/product/9900/Microsoft-Internet-Ex...
This is totally unacceptable. I started using ubuntu in production thinking it was "stable". After 6 months, the server wouldn't boot because of this reason. I don't think I ever manually installed updates. It just updated itself and broke itself.
PHP is great for marketing websites that don't need a lot of javascript.
But Node.js still wins for javascript heavy web apps. This is because you can write a js validator that will run on the client-side and server-side. Sometimes this is called Isomorphic JS (or Universal JS).
For example, this app[0] shows how to render React on the server and the client with shared props.
That being said, my personal website[1] still runs PHP and I'm glad I haven't taken on all the build dependencies of a modern web app just to host a simple blog.
We had a couple experiments at my company but going from 1.0 to 1.1 had breaking changes so we couldn’t upgrade easily.
The postMessage API provides a safer way for Windows/Tabs to communicate.
https://developer.mozilla.org/en-US/docs/Web/API/Window/post...
This example is quite interesting because javascript itself does not provide a way to check the type of an array, unlike a primitive. This is likely due to the fact that an empty array doesn't really have a type for it's items yet.
Here is an example where typescript can infer the type using the `typeof` runtime check but provide compile time checking.
https://www.typescriptlang.org/play/index.html#src=function%...
I’m actually dealing with this right now with a project[0] that was forked from an unmaintained repo that wouldn’t accept any pull requests.
I'm curious, were these implemented using a 3rd party library or developed in-house?
I ask because the article lists a couple things that could break such as drag 'n drop but I have not noticed anything breaking in my experience.