201–210 of 365 posts
How would I even host a website at home? 20 years ago I knew how to get a fixed IP from my local ISP but I don't know how to do that anymore.
You can use dynamic DNS if the IP address you're getting is a public one.
Earlier quoted context omitted.
I think he is talking about badly written JS code serving the APIs and the overhead of it. Of course it's hard to debate whether JS, Java or PHP is most inefficient in that regard.
I strongly believe that the efficiency of an API is 1% down to the language it's coded in, and 99% down to who coded it.
ICANN should make a .solar extension with the caveat that you have to provide evidence yearly that all IPs mapped by the domain were running on solar power
Earlier quoted context omitted.
> you could hack around that by using Disqus But that's not actually solving the problem, it's just offloading it. Not to mention that you're selling your community to yet another tracking company, and jacking up user page load time.
>> by Disqus or something depends on what you want, the low end is incoming comments as emails and putting them semi-manually into an iframe on the unchanged static article page. Doing it myself at https://blog.mro.name/2019/05/wp-to-hugo-making-of/ and sacrificed commenter speed. Others may easily be more sophisticated than above brutalist solution. But still: comments in iframes align well with static sites IMO. Ed…
Today that’s cloudflare but in the past it was varnish.
Otherwise it is very dynamic. Different users have access to different content so we generally can’t cache full pages at the edge for authenticated users.
Earlier quoted context omitted.
I think he is talking about badly written JS code serving the APIs and the overhead of it. Of course it's hard to debate whether JS, Java or PHP is most inefficient in that regard.
I strongly believe that the efficiency of an API is 1% down to the language it's coded in, and 99% down to who coded it.
As another commenter pointed out, Lead-Acid batteries are terrible for this. They are fine for backup power supplies that you don't expect to actually use more than a couple of times a year, but discharging them too much will completely kill them, and even if you keep a margin and discharge them to only 30%, the number of cycles is quite limited (1500 to 3000 cycles quoted in [1] seems a bit optimistic, probably depe…
Earlier quoted context omitted.
Riiiiight. I'm sure it has nothing to do with a complete lack of competition (cf. how in communities where Google Fiber showed up, the incumbents were suddenly quite capable of getting gigabit fiber to households, and for a price that was competitive with Google Fiber, and a fraction of the price they were charging for inferior service before Google Fiber's arrival). I'm sure it also has nothing to do with the billio…
Lack of competition is due to regulatory capture. Local governments often disallow competition in the ISP space.
We need new laws, and smaller companies.
This is a fascinating site beyond the power indicator. For example, a recent article discusses low-tech solar panels: > ... To start with, ever since the 1950s, solar panels have been unfit for recycling, resulting in a waste stream that ends up in landfills. This waste stream will grow significantly during the coming years. Solar panels are discarded only after at least 25 to 30 years, and most have been installed o…
I've been watching videos of the technique. It's almost as relaxing as watching a professional butcher dismantle a cow.
Earlier quoted context omitted.
And, heck, there's a solid argument that server-side rendering is more environmentally efficient, since the work is done in a data-center, which can (1) utilize caching to avoid re-doing work and (2) be built in an optimal location for electricity generation.
Conversely, you are losing the distributed computing gained by rendering on the client, and therefore need a bigger server to scale when needed. And HTTP caching can and should be used for API responses as well.
Sure, most clients may already be adequately provisioned, but only because so many websites with bloated Javascript have forced their hand...
Earlier quoted context omitted.
[citation needed] Websites have become significantly more complex in the last two decades.
Let’s look at Twitter for a real-world example. The core concept of it hasn’t changed, it still just has to display a blurb of a few hundred characters at most. Back in the day this was achieved by server-side-rendered HTML and a simple form POST. I don’t have the numbers for the page back then but I’d estimate it at 100KB - nowadays it’s a multi-megabyte-sized pile of shit that often fails at its primary purpose of…