Compared to Elastic's Cloud offering Apex Logs would be roughly half the cost. I forgot to mention in the post that it's 100% serverless, so there's nothing to maintain and no need to resize clusters as you grow.
Kibana definitely has the edge right now when it comes to charting, but I would say if you're just looking for a simple and clean logging solution Apex Logs would be a nicer experience. If you try it out definitely let me know if you have any feedback!
I suppose it depends, but throwing out node and migrating everything to Go was one of the better choices we made at Segment, before the platform grew too large.
Personally I think css utils are better suited for layout related stuff, acting more like layout primitives (hbox, vbox) etc since those tend to be pretty ad-hoc.
As far as concrete UI components go, I'm not sure this technique is any better, especially since you often need pretty ad-hoc styling with pseudos etc.
I think if CSS had built-in mixin support you could have the best of both worlds pretty easily, still crossing my fingers we get that some day, would be nice to drop all these build systems.
Facebook pays for this kind of stuff? Why not spend the time incorporating a decent language instead of trying to fix the fragmented hot mess that is js
There's inherent value in supporting something with money though, it's likely to actually stick around and improve, rather than some hacky OSS project that will die in a few months.
Great job, this looks awesome! I wish something polished like this was around when I started my stuff. I'm not sure how I feel about Tailwind being almost 1mb of CSS :D, but it's probably worth all the time you save, especially for apps the size isn't such a big deal.
These days I think most people deploy static sites to a CDN, they get you such great performance I can't imagine not using a CDN, my site loads in 10ms in London for example.
You can definitely do that, but I find this appealing for development, just write some routes as you normally would and the templates all re-render etc, no need for watching file changes and re-compiling. But you're right, if you have a 404 template for example you have to `curl ... > build/404.html` which is a bit lame.
Yeah it doesn't work if you're relying on JS for interactions and layout, but wget's crawling technique works great if you're happy with using server-side rendering for content.
GitHub stars will pay your rent if you sell out the hype to a VC instead of building a real company. I can definitely name a few startups that have almost no product, certainly not technically challenging or particularly well built ones, but they've made many millions in VC funding solely from GH star hype.This industry is a bit of a joke that way, but it works.