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!
It's like if an university released an app for it's student body, they were forced to allow anybody to sign up to the university with Apple pay. And give Apple 30% of the tuition.
… that does not follow. Apple's definitions aren't based on whether a good is free. It's based on whether the service is delivered without real-world interaction by the user.
Tuition at a brick-and-mortar college? No cut.
On-demand video service with tutorials? They get a cut.
I’m zeroing in on the “real” here. Email is an indispensable service, just like paying tuition. The idea that “it’s on the internet so it doesn’t count” is... farcical coming from the biggest tech company (or one of the largest browser vendors, whichever seems more relevant) ever.
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
Throwing all the baby out with the bath water is something engineers consistently overvalue in business when there are other middleground trade-offs to choose from.
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.
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.