Can and want to or being efficient are different things. I "can" travel around in a city using public transport with 3 kids and all their sporting equipment, do I want to, no. Would any sane person want to? No.
see, this is the narrow minded view of so many europeans. Well just go to a closer sports club....is not an answer to the problem that thousands of people experience with small cars, and small roads.
Many more thousands have no issues with small cars or going to a closer sports club.
If the roads in cities are wide enough in cities for literal trucks, then they're wide enough for your car. Widening roads and making cars bigger makes pretty much everyone less safe.
Don't get me wrong, you're free to live in the boonies and drive 400km to your sports club, but don't call me narrow minded because I can load up 5 people in my VW passat and drive 500km for a 10 day vacation, or because I prefer not to get bulldozed by a car with a higher hood than me while walking to my local sports club.
That’s a bit of a strawman argument. Most journeys don’t consist of three children and all their sporting equipment.
As a practical example, in the UK, on average a young g child lives 1.7miles away from their school.
That is an easily walkable distance for most children, yet lots of parents choose to drive it because they feel the streets aren’t safe to walk on in rush hour.
If by redesigning streets to make active travel more appealing, you could reduce the number of cars on the school run by 10%; it would improve the traffic situation for the ones who still need to drive. Win-win
>This article gave an LLM a bunch of health metrics and then asked it to reduce it to a single score, didn't tell us any of the actual metric values, and then compared that to a doctor's opinion. Why anyone would expect these to align is beyond my understanding.
This gets to one of LLMs' core weaknesses, they blindly respond to your requests and rarely push back against the premise of it.
I read somewhere that LLM chat apps are optimized to return something useful, not correct or comprehensive (where useful is defined as the user accepts it). I found this explanation to be a useful (ha!) way to explain to friends and family why they need to be skeptical of LLM outputs.
I've come to the opinion that for the vast majority of apps I've built, it could all be built using HTML + CSS (all built server side). I can sprinkle in little bits of interactivity using something like HTMX. And I'll have a website that is very easy to optimise, has phenomenal backwards compatibility, and gets rid of a whole class of issues associated with SPAs.
I often regret in my career not pushing back more on "requirements" that ended up requiring a more complicated app, whereas the customer would have been happier with a simpler solution.
I guess you're right, but it's more of a curve, though. Once you get to any decent level of complexity, it actually helps to have a framework instead of just going all HTML+CSS. Also it helps having something standard as react (that every web developer should fundamentally understand) than doing your custom stuff if other people will be working on it in the future.
There's a lot to say about the side effects of frameworks but there's a reason why everything converges towards that.
I think it's the other way around, a framework will get you up and running quickly, but then it becomes technical dept, and if your app is complicated you will end up fighting the framework.
If you write something from scratch it will take a while to reach to the abstraction level where you can work fast. But then you have a fully custom abstraction layer that is not a "one size fits all" but custom tailored for your needs.
Good luck with hiring, onboarding, and maintenance of your bespoke solution. Also with your resume when seeking your next gig. For any serious project, ignore community and ecosystem health at your peril. To be clear, we're talking about framework selection, not leftpad vs DIY.
What you’re describing sounds like it was the customs check. Pre-brexit, if you were arriving from the EU, then there was no customs check since we were all part of the same customs union.
From a customs perspective, flying from one EU country to another EU is treated like a domestic flight.
If I (a British citizen) flew from London to New York, then on to Chicago; I'd expect to go through customs when I arrived at New York, but not when I arrived at Chicago.
I've come to the opinion that for the vast majority of apps I've built, it could all be built using HTML + CSS (all built server side). I can sprinkle in little bits of interactivity using something like HTMX. And I'll have a website that is very easy to optimise, has phenomenal backwards compatibility, and gets rid of a whole class of issues associated with SPAs.
I often regret in my career not pushing back more on "requirements" that ended up requiring a more complicated app, whereas the customer would have been happier with a simpler solution.
No need for HTMX, HTMZ can get you most of the way there if it is going from simple MPA to slightly more complicated. I used a variation of HTMZ to make a offline-first soccer app I use for myself. I thought I would need to use a front end for the match play page, but, nope, I used Morphdom with HTMZ and I was able to keep the simplicity of templating and a back end.
Follow the sun does not happen by itself. Very few if any engineering teams are equally split across thirds of the globe in such a way that (say) Asia can cover if both EMEA and the Americas are offline.
Having two sites cover the pager is common, but even then you only have 16 working hours at best and somebody has to take the pager early/late.
With self hosting email, if the digital sovreignty aspect is more important to you than the privacy aspect...
What I do is use gmail with a custom domain, self host an email server, and use mbysnc[1] to always be downloading my emails from gmail. Then I connect to that email server for reading my emails, but still use gmail for sending.
It also means that google can't lock me out of my emails, I still retain all my emails, and if I want move providers, I simply change the DNS records of my domain. But I don't have any issues around mail delivery.
I did all of those DNS shnigannas with spf, dmarc and others ones like 6 years ago.
I think I had problems with my emails like 2 twice , with one exchange server of some small recruitment company. I think it was misconfigured.
Ah there were also some problem with gmail at the beginning they banned my domain because I was sending test emails to my own account there. I had to register my domain on their BS email post master tools website and configure my DNS with some key.
In overall I had much more problem with automatic backups, services going down for no reason, IPs being dynamic and etc. Email server just works.
The custom domain is all you need for complete e-mail sovereignty. As long as you have it, you can select between hundreds (thousands?) of providers, and take your business elsewhere at any time.
Not OP, but yes. For personal use, you don't have enough traffic to establish reputation, so you get constantly blocked regardless of DKIM/DMARC/SPF/rDNS. Receiving mail is reliable though, so you can do that yourself and outsource just sending to things like Amazon SES or SMTP relays.
Depending on your mail flow, there's SendGrid and other options at a pretty reasonable cost to handle delivery concerns. I have one server set for sendgrid and another I've got setup for direct delivery... the only issue I've had sending from my own is to Outlook.com servers (not o365 or hotmail though). With DMARC/SPF, etc, gmail has been okay as well.
I never sign up for subscriptions anymore without using a virtual card. Once I've paid the yearly fee, I immediately cancel the card. When it comes to renew, they'll be very keen to let me know that my card needs updating.
I gave my old iPhone X to my father who's still using it, 9 years later, with software updates to iOS.
Compare that to the Google Pixel 2 (which came out in the same year), got it's last software update 3 years later.