nathants

44 ms·

601.
by nathants 4y ago
this is a really great project. if you haven’t heard of libnetfilterqueue, this is what it’s for. it’s really good. tremendous thanks to the author for introducing me to it via this project. the main problem with libnetfilterqueue is that i
602.
by nathants 4y ago
email draft with attachment.
603.
by nathants 4y ago
mobile safari. is needed. yes.
604.
by nathants 4y ago
definitely try clojure. try clojurescript with shadow-cljs and reagent as well!
605.
by nathants 4y ago
other providers with an offering like workers+r2 would be great for the market.
606.
by nathants 4y ago
kagi search is best search.
607.
by nathants 4y ago
build webapps that you WANT to use from you phone. then actually use them from your phone. take notes on what is annoying, and fix it next time your at your desk. webapps suck on mobile when the builders don’t use them on mobile.
608.
by nathants 4y ago
aws is fine. just use the good parts, skip the rest.
609.
by nathants 4y ago
i find managing aws from a lambda with an aws sdk to be a good in between. trigger the lambda on events and/or a schedule. lock around dynamodb to ensure a single lambda at a time is mutating aws. example: https://github.com
610.
by nathants 4y ago
ec2 alpine on t3.small boots in 30 seconds. 45 seconds for spot. default-like vpc with public subnets and internet gateway is fine. zero trust. route53 health checks and returns up to 8 hosts in random order. to the gp’s point, using aws sd
611.
by nathants 4y ago
hawaii.
612.
by nathants 4y ago
arch and alpine edge.
613.
by nathants 4y ago
it’s just data though. json, yaml, xml, bytes in a file, they are all capable of representing the same data. why validate them all indifferent ways? their syntax is different, but their semantics, or some common subset, is identical.
614.
by nathants 4y ago
validating yaml, or any input data, is likely a good idea. does the validation have to be based on a human readable schema though? i’ve started manually validating yaml the hard way, and writing human readable but otherwise useless schemas.
615.
by nathants 4y ago
are you serious?
616.
by nathants 4y ago
this is excellent.
617.
by nathants 4y ago
a friend recently gave me this same advice, and it does seem like a good idea. i’ve been trying to rework my github readme’s to all start with why/what/how, and it's hard! they should be concise, and yet sufficiently explanat
618.
by nathants 4y ago
i've updated the readme with an attempt at better explanations.
619.
by nathants 4y ago
fair question. i've updated the readme. this is a project scaffold. it's the template from which i start all new services. clone the repo. change the name. deploy. start the dev loop. now you've got: - a fast, fun dev loop fo
620.
Show HN: Building services on lambda should be easy and fun(github.com)
6 points by nathants 4y ago|3 comments
621.
by nathants 4y ago
this is fantastic! simple map/reduce type abstractions over ec2 spot, lambda, and s3 are definitely the play. this is going to help a lot of people use more cheap vcpu billed by the second. i4i instances recently launched. so much fast
622.
by nathants 4y ago
on my own site, as static files embedded in a lambda zip like this: https://github.com/nathants/libaws/tree/master/examples/simp... will probably switch to cloudflare+r2 soon since egress is cheaper
623.
by nathants 4y ago
cloudflare r2. if your primary use case for dropbox is the same as mine: publicly shareable links to large files.
624.
by nathants 4y ago
or use an internet gateway?
625.
by nathants 4y ago
vendor lockin is fine. it’s like having a great employee, but not leveraging them fully because bus factor and cogs. you should be sad if a great employee leaves, or your vendor shuts down. choose both carefully, and trust them. my only exp
626.
by nathants 4y ago
definitely. some of the services are great. they are just a lot more expensive. in the context of making aws cheaper, avoiding services is the play.
627.
by nathants 4y ago
r2 is in public beta! it’s great.
628.
by nathants 4y ago
aws pricing is literally a catalog. what and how much you buy is kind of the whole thing. a subset of the catalog is good. aws core primitives are: - flexible - reliable - robust if your service succeeds, you will definitely want to move so
629.
by nathants 4y ago
aws can be so cheap. aside from egress bandwidth, it’s pricing is fantastic. crazy aws cost is always gonna be a case of your holding it wrong. either intentionally because it’s more fun, or accidentally. how to use aws well and cheaply: -
630.
by nathants 4y ago
https://nathants.com

More ›