After college I moved from the far western edge of one timezone to the far eastern edge of another zone. I grew up with 5-5:30pm sunsets in winter, and now I live with 4-4:30pm sunsets. I moved here 25 years ago, and every single year when November/December come around and I get those early sunsets I hate it. It's one of the reasons I'd like to move away from here.
I know it's just one person's opinion, but to me those extremely early sunsets in the middle of winter are a huge quality of life reduction.
I believe part of the problem is that if you're in the middle or western edge of your zone, the winter sunsets aren't so bad. I suspect a lot of people who would prefer DST year round live on the eastern edge.
I live in Atlanta (western edge of US Eastern time) and permanent DST sounds horrible - the sun would rise at 8:45 in early January. Honestly I'd prefer we be on permanent standard time. Call it permanent Central Daylight Time if you must.
On the other hand, I used to live in Boston (eastern edge of US Eastern time) and those 4:15 sunsets were pretty depressing. Permanent DST sounds reasonable there.
Nebula just had a major release that added IPv6 support for overlay networks. Hardly maintenance mode.
The main company working on it now seems to be adding all the fancy easy-to-use features as a layer on top of Nebula that they are selling. I personally appreciate getting to use the simple core of Nebula as open source. It seems very Unix-y to me: a simple tool that does one thing and does it well.
I've had gemini tell me "We are debugging this problem here in İstanbul" and talking about an istanbul evening, trying to give uplifting or familiar vibes while being creepy.
I think there was a setting about time and location which finally got rid of that behavior.
I got much better at this when my kids were born, because it was the only way I could get work done on some of my (computing) side projects. I went from having hours of uninterrupted "in the zone" time during evenings and weekends to having much less time overall, and what time I did have was broken into smaller chunks.
I got much more thoughtful about how I used my time and also got better at pre-planning what I had to do so as to make the best use of it. Mostly the key was to just try to tackle smaller tasks and accept that progress would be slow.
That's been exactly my experience as well. Sometimes doing a little research on a lunch break gives enough direction on how to spend available time later on my project.
Accepting that progress will be slow has been the most difficult adjustment, and applies to more than just side-projects. Choosing books or games also becomes a more strategic decision when what used to be a weekend sprint, turns into a several week marathon.
Pretty much all of these reliability reducers are manufacturers trying to eek a little more MPGs by throwing lots of complicated technology at the problem, which introduces a lot more failure points.
Headlights and taillights on my current vehicle are supposedly around $1500 each, mostly due to a bunch of sophisticated sensors being built in.
Back in the 80s headlights were standardized (in the US at least) - you either had rectangular or circular. They were available at every auto parts store. Now they're a special order item from the dealer.
New synthetic oils are very durable. They actually do last a long time.
There are oil tests that confirm this. Also, 10,000+ mile oil changes are not new, and there are tons of used vehicles on the market, running around with long oil change intervals, and high mileage.
> But the market has spoken! Users prefer Litestream. And honestly, we get it: Litestream is easier to run and to reason about. So we’ve shifted our focus back to it.
That makes sense to me. LiteFS used FUSE, which meant figuring out how to run and mount a custom filesystem. Litestream is a single compiled Go binary that you point at the SQLite database file (and accompanying WAL file).
Doesn't matter. Republican politicans and influencers (if separating the two still makes any sense) framed it as an attack by the "woke" and "radical left" on these fabled american values.
Not maybe so, it is what’s happening. Whether their stance reflects reality or not is not (is it ever with these people?) the point - they’re using it to stir the pot as usual.
Republican politicians and influencers frame everything as an "attack" by the "woke" and "radical left". It makes for a great preemptive distraction when they're actually responsible for most of those things. Bland gray/beige color schemes get decided in board rooms full of uninspiring executive-class types who can't think of anything but trying to cargo cult their way into making the Line go up.
According to Jeff Geerling's video, the main PCB in the 500+ is identical to the 500, same revision and all. Presumably they planned both the 500 and 500+ at the same time so they designed a single PCB that could accommodate both, and then only populated the m.2 parts when building a 500+.
So I don't think they "backed out" rather just didn't have the 500+ ready to launch yet.
Note that the mechanical keyboard is probably one of the major reasons the Pi 500+ took a lot longer to release than the regular 500.
According to an interview on the Pi blog[1], it was "years", with prototypes being built through 2023.
I know the design lifecycle for a product like this is in the 3-5 year range, and adding on a custom mechanical keyboard in a mass-market product like this is a tall order.
Honestly I'm not put off by the $200 price tag. If you use one in person (like at a Micro Center here in the US), you'll feel it's a decent midrange mechanical keyboard. It won't compete on the high end (IMO $200+), but to strap that onto a decent low-end PC in a fanless design isn't cheap, even at the scales Raspberry Pi operates.
They have some margin, for sure, but that's also how they turn profit, which is especially useful since then went public.
At least they're still putting out products like this, that don't really have any industrial/commercial appeal, compared to specialized compute modules for individual customers[2].
After college I moved from the far western edge of one timezone to the far eastern edge of another zone. I grew up with 5-5:30pm sunsets in winter, and now I live with 4-4:30pm sunsets. I moved here 25 years ago, and every single year when November/December come around and I get those early sunsets I hate it. It's one of the reasons I'd like to move away from here.
I know it's just one person's opinion, but to me those extremely early sunsets in the middle of winter are a huge quality of life reduction.
I believe part of the problem is that if you're in the middle or western edge of your zone, the winter sunsets aren't so bad. I suspect a lot of people who would prefer DST year round live on the eastern edge.