Is there some way to create this kind of experience without having to change RSS readers? Is there a service that allows you to easily create RSS feeds for websites without them? I'd rather go with a more unix "do one thing and do it well" philosophy for something like this.
I started out with NNW and am back on it now. After Google killed Reader I went to Feedly, then tried a few self-hosted solutions and, in the end, NNW is just the easiest solution for me since I'm in the Apple ecosystem.
Maybe instead of housing life, civilizations develop Dyson's spheres to house data centers. Solar panels on the interior, thermal radiators on the exterior and the data centers make up the structure in between. Combine that Von Neumann probes and you've got a fun new Fermi paradox hypothesis!
Don't combine it with von Neumann probes and you've solved the Fermi paradox: a civilization that puts that much work into computing power is either doing the equivalent of mining crypto and going nowhere, or is doing AI and is so dependent on it that they inevitably form a vast echo chamber (echo sphere?) that only wants to talk to itself (itselves?) and can't bear to be left out by adding the latency unavoidably added by distance.
tl;dr: civilizations advanced enough to travel between stars end up trapped by the resources and physics required to keep up with the Joneses.
I don’t agree with that external analysis (cnbc is saying it’s lower than their expectations). This is a gen 1 product for super fans that they want to evolve into a mainstream one.
Precisely! Can’t recall the last time they added a feature I wanted, so I just stick with the oldest version that is still supported. Upgrading is more likely to break things than provide anything I actually need.
People get very annoyed and less productive when they have to relearn a large portion of their workflow. A carpenter uses the same tools the same way for fifty years, but someone working with software in any capacity has their tools replaced with new ones every few months and has to learn first how they differ and then how to get them to mostly do the same things as they old tools.
> After the user downloads 2MB of JavaScript, waits for it to parse, waits for it to execute, waits for it to hydrate, waits for it to fetch data, waits for it to render... yes, then subsequent navigations feel snappy. Congratulations.
In my experience, a lot of SPAs transfer more data than the front-end actually needs. One team I worked on was sending 4MB over the wire to render 14kb of actual HTML. (No, there wasn't some processing happening on the front-end that needed the extra data.) And that was using graphql, some dev just plunked all the fields in the graphql query instead of the ones actually needed. I've seen that pattern a lot, although in some cases it's been to my benefit, like finding more details on a tracking website than the UI presented.
even for "downloads 2MB of JavaScript", it is often simply because the site is badly written (e.g. not careful about managing dependency), not necessarily because "JAVASCRIPT BAD".
Just look at the source code of amazon.com. It's a mess. But I bet it is more of an organizational problem than a tech stack problem, for a website worked on by literally hundreds of teams (if not more) where everyone crams their little feature in the website home page
> it is often simply because the site is badly written
I find that some techs tend to cause badly written code. I have junior coworkers that can write clear Python after a short intro, but can't write clean R after a year using it daily. I don't know if it is caused by the philosophy behind the language, the community, the tutorials and docs...
reply