171–180 of 187 posts
Earlier quoted context omitted.
Chris Coyier is pretty well known in the front end community. He created CSS-Tricks and co-founded CodePen. If anyone can claim to be an expert it's him. But if you're just trying to have a laugh at CSS - well, that's fine too I guess.
I didn't mean to belittle they guy at all, but the title "CSS expert" looks ironic to me, just like "SEO expert"
You don‘t need your own AWS account to use Lambda functions.
I compiled a landing page example with Mailchimp mailing list signup a while ago:
I use Netlify for all my static sites and it's been amazing. All I have to do is push and they take care of everything else, I can't understate how much I love the product. If you want to check out a live deployment, my website https://www.stavros.io/ is on Netlify. I especially like how they provide forms, lambdas and very easy testing by just pushing to another git branch. I don't see why anyone would use Github/Gi…
The ability to be able to publish using a simple `git push` and let them do all the work (including assets minification and bundling) is nothing short but amazing. Their dashboard is also really cool. Having the possibility to test a merge request without disrupting the live site, lock a deploy to a specific commit, or see the deployment live. It's simply amazing.
And their customer support is also great. Just yesterday I had a problem with Hugo not compiling my SCSS on their hand and I had two people trying to help me super quickly.
Netlify is a service I can't stop praising because they're just great on all fronts.
Netlify is great. I have 5 sites there. All for free. My only concern is that it's too good to be true. I hope nothing changes for the worse (i.e. they get bought and cripple the free tier).
I knew nothing about Netlify before this post, so this is a purely generic, rational note: yes it will. You lure in customers with an attractive free tier and then change it so you can monetize at least some of them and be profitable. Choosing the right business model however, is what I think shows the true character of the company’s leadership. Unfortunately greed usually wins. But enjoy the product while it lasts.…
It still sounds to good to be true, but I just wanted to point out that they charged for their service when they were much smaller.
Earlier quoted context omitted.
It's as difference from that as Dropbox is from mounting an NFS share on your computer.
Could you elaborate on the difference here? Mounting an NFS share is almost universally easier, in my experience.
I think the commenter is referring to this infamous thread: https://news.ycombinator.com/item?id=9224
Having spent the last few days trying to get Cloudfront with Lambda@Edge working, I'm excited to see this. Cloudfront is a mess and clearly Lambda@Edge is "cutting edge" at AWS (where cutting edge means "full of bugs")
You might want to try Cloudflare Workers instead. (disclaimer: I work at Cloudflare)
So much praising so little talk about its limits. I consider myself to be kinda stick in a Rails way of thinking. But most projects I touch heavily depend on a backend, database, or raw computing power. Everything that doesn't fall in those categories is something I create static (ex nanoc.) i just build out locally push to my git and let a post-commit hook do the Copy pasta. My static Web server runs without attenti…
- the "static webserver"
- the sandbox for commit hooks
- instant CDN & cache-busting
- 1-click domain setup
- 1-click SSL setup
- git-branch powered a/b testing
- git-branch powered deploy previews
- Functions-as-a-service deployment and routing
and that's the free tier
Earlier quoted context omitted.
You might want to try Cloudflare Workers instead. (disclaimer: I work at Cloudflare)
I assumed they were for service workers with SPAs. Not the case? The AWS landscape is so massive it's hard to understand what everything does. I'll check out CloudFlare workers, thank you.
Do workers somehow operate inside your AWS stack via distributions of CloudFront? If not, that's probably not going to work, we have so much in S3, etc.
But, if that assumption is incorrect, can you point me to a document that suggests a transition path?
May not be widely known, but a startup named Divshot launched what feels to me now like an identical service to Netlify, just a few years earlier. Existed ~2012-2015. They were acquired by Google and their product was converted into Firebase Hosting. I haven't tried it, though: https://firebase.google.com/docs/hosting/
I was gonna come here to bring this up as well. FYI to any readers: Firebase Hosting has nothing to do with the other Firebase stuff. In fact, I personally dislike their live database quite a bit. If you want to host a simple static site with HTTPS, Firebase Hosting really makes it incredibly easy. My only complaint is that they don't let you view access logs. Here's the official response [0] from the Firebase team a…
I certainly hope that you don't feel the need to move to something else when your application scales / gets more complex -- our whole mission is to make it so you don't have to. Feel free to reach out to me on Twitter (@mbleigh) if you have specific questions/concerns.