1,684 karma · joined June 18, 2020
This is why billions of dollars are going into storage and transport for renewable energy (batteries, hydrogen, and some outliers like methane and ammonia). Creating any new energy demand, be it flexible or constant, only increases the total amount of renewables we need.
> our entire grid could be renewables in excess of peak demand
Are you hypothesizing about a world where we have more renewables than we can consume at all times? Sure, I guess mine away in that world. In this world, though, it's doing measurable damage.
The main tenets of apps that are resilient to bot spam are 1) scalability, so that they can handle huge quantities of traffic and bot-generated content, and 2) the ability to differentiate high quality from low quality content (regardless of whether it was created by a human). Ironically, AI is probably the solution to the second problem.
For some reason, the thing that still feels the coolest was the RC hovercraft (converted from RC airplane parts) that a friend and I made for a science fair. It was a bit silly because it wasn't cordless, but that attribute doubled as a nice safety feature given that this was being piloted in a gymnasium full of kids.
I wonder if any builders are using this approach - solder in the crawl space and behind drywall, but shark bite in accessible areas.
Also, I have to admit, as much as I love what this company is doing, both the R1 line and the Amazon van look totally cartoonish to me.
The first lesson to learn is that construction doesn't happen behind a laptop or on a phone. From your user's perspective, time spent fiddling with your app is time not spent on real work. So naturally you focus on selling to the "office workers" who spend more time on planning and administration. The problem with that segment is that the tools they already have are good enough. Construction projects always take far longer and cost far more than expected because of what's happening in the field, not because of what's happening in the office, so software simply isn't a bottleneck in this industry. The fact that your tool was specifically designed for their use case, or has an AR feature that allows them to walk the site virtually, or whatever -- it's cool, and you can get a few sales that way, but it's not going to result in better project economics, so it's not going to revolutionize anything.
- As important as reducing our use of fossil fuels is, using less energy is not a solution to the problem of a non-renewable energy system. In that sense, it wouldn't meet the criteria for someone who wants to work on a climate solution.
- While WFH drastically reduces auto emissions, it increases gas & electricity use in the home.
- Zoom is not a mission-driven company and (to my knowledge) their KPIs are not directed at or correlated with their GHG footprint; I would think they see themselves as productivity software, not climate software.
- If Zoom never existed we would be working from home at the same rate, using any of hundreds of other video conferencing apps. In carbon offset terms, their impact does not provide additionality.
Browsers impose a limit on concurrent requests (usually 6 per hostname) for a reason - HTTP requests, be they too many or too large, are one of the largest performance problems in a typical site. Just because it's easy to fire-and-forget an HTTP request doesn't mean it doesn't have a performance impact, especially in apps that are already network-chatty. I think you know this because you go on to list "the volume of data we're transferring" as a performance bottleneck, and obviously that's done through HTTP requests. Also, in the real world analytics installations virtually always include installing a third party library i.e. google analytics, so you're taking hits to download the library, interpret the source, run the code alongside your app, usually in the same thread, all before you've fired any of those HTTP requests.
> A/B tests just means settings/feature flags and metrics
I'm aware of the definition. If you are implying that conditionally loading settings or feature flags and tracking associated metrics doesn't have a performance impact, I would disagree. It is usually possible to implement a given A/B test with minimal performance impact, but in practice these are absolutely a contributor to the kind of bloat I'm frustrated with.
> sessions are recorded since ever with zero performance penalty
It sounds like you're talking about logs. I'm talking about "session replay" features provided by companies like FullStory and Sentry that allow you to replay every mouse move and keystroke of your users.
> It's trendy to shit on the status quo but it also is low-effort and lacks any insightfulness.
By this point in your comment I think you forgot what we were talking about. I was arguing that the architecture of modern SPAs shouldn't bear the blame for bad performance; my point being that whether or not we continued to use server-generated HTML we would still be suffering from similar problems of bloat today. The "status quo" that I'm shitting on is taking lazy approach to performance management and injecting way too much cruft; unless you work for an analytics provider I'm not sure why you would be opposed to that stance.
I attempted to build a startup product using a vanilla JS SPA when I was a founding engineer, and the result was predictable: it worked great for me, but nobody I hired wanted to learn some random guy's vanilla JS codebase. I've since resigned myself to using React simply because that's what developers expect, despite all the headaches.
For what it's worth, we ended up migrating to Mithril in the V2 of that startup's product. We all enjoyed Mithril and it scaled really well for us, but my team did have some apprehension about their React skills falling behind.