frenchman99

The Framework knowledge base says:

> To get notified when we open ordering in your region, you can navigate to the locales page and select your region from the dropdown box.

You may want to let them know you're interested, maybe that'll push them to open up: https://frame.work/fr/en/locale/edit?waitlist_country_code=E...

Although Framework are not available in all European countries, they are available in some of them. I live in France and just received mine a week ago. The current list is here: https://knowledgebase.frame.work/what-countries-and-regions-...

To me a live copy with delayed sync sounds like a backup. What defines a backup for you?

It is perfectly possible to do customer support on a specific schedule so that it doesn't become an interruption though.

> If developers had to do customer support for their products as a rule you bet they’d get grumpy.

Do you have data to support this?

I would love to do customer support from time to time to better understand the users of the product I work on as a developer. But that request has been denied to me many times, in multiple jobs.

To get people to communicate better, inspire them to do so and have faith in them.

> You're waiting for compilation, CI/CD, deploys, because of a bunch of irrelevant stuff.

You could setup your CI to only recompile what's changed, so you wouldn't be waiting for anything else than what you've changed. This usually requires a bit of work upfront, but once you've done it for 1 part of the codebase it is easy and low-maintenance to replicate to the entire codebase. With Gitlab CI (and others), you can import bits of yaml configuration here and there to avoid code duplication for such use cases.

> I'm personally against microservices

In some cases, you need microservices or at least being able to run only a single part of the monolith through configuration. For instance if you want to host parts of the codebase in a separate virtual machine for security or scalability.

I don't think the choice is a matter of opinion but a matter of technical/business requirements.

Debian being free of cost, I dont think you have a right to be mad about anything if you don't help with maintenance. Open source maintainers are not your employees.

Users can always switch back to Google if they so desire.

Yes I do find them unsound. Now you need ordinary people to understand the pros and cons of DMARC (SPF + DKIM). Not every one has this configured. In fact it's shocking how many companies don't have DMARC set up given the benefits.

If major providers such as Gmail/Microsoft/etc agreed to require DMARC for all incoming email senders, then maybe 5 years later we could speak about this again because then DMARC would be universally used.

Running a local k8s cluster doesn't guarantee that a remote cluster on some cloud provider will work the same either.

I've heard of and worked with multiple dev teams that develop with compose and deploy a totally different way (k8s, AWS auto scaling groups, heroku, etc), to great success.

Devs know about compose and understand it. As long as the containers behave as planned, the DevOps people can figure out how to deploy them on whatever production environment.

What do you mean with monitoring tools? You could deploy Prometheus/Grafana or an ELK stack on Compose so I'm not sure I understand what you mean

> not all npm packages are typescript

All Javascript is Typescript isn't it?

We French need to start thinking about sobriety. Setting progressive water and energy prices to encourage people to be more efficient in their use would also be helpful. Lots can be done. How about the government and parliament finally get it done instead of pointing fingers. I'm ready to restrain myself in lots of ways if it's in the general interest, even if it makes my life a bit worse on some aspects.

The cert is usually the public key. The private key is usually named key. So it doesn't promote secrets being saved within a container as far as I can see.

They could also have done speech recognition server side.

> Regrettably, this will have an intended impact

This reads weird to me (non-native English speaker). How can you regrettably reach your intended impact? Is that some kind of an idiom?

Even in France which lots of people call "socialist", the company can fire you at any time and has to pay only about 3/6 months of salary for "wrongful termination". That's low enough to not keep constantly underperforming people.

Given how much water is needed to extract metals from the ground to create new appliances, the total amount of wasted water is subject to debate. It may be better overall to just keep using the old thing till it breaks.

Sounds too me like you're saying "Let's take Hetzner so we don't have to be smart" and your CTO is telling you to be smart. In a way, he trusts you're smart enough to figure out a better way then just throwing hardware at the problem.

Also, while cloud pricing can be daunting, once you reach a point when Azure costs to much, you can look at optimizing things. There are a lot of techniques to keep cloud cost acceptable. Look up "FinOps" if you haven't already.

I think Fortrabbit allows you to scale easily to have a fault tolerant infrastructure without needing know-how. Kind of Like Heroku in some regards.

A dedicated server is nice but if it fails and you have no redundancy, your service goes offline.

There are also PaaS providers in Germany, such as Fortrabbit for PHP, which do a great job. Competes with some parts of AWS.

From a quick Google search, the linkin park logo looks quite different

Don't you worry, if we keep using the planet like we currently do, and like you do by saying you don't give a shit, then we'll all die soon enough because of our lack of respect for our environment — lack of access to clean water will hit loads of people in the coming decades.

Either that or we come up with laws that keep us competitive without destroying everything around us. I hope that's what Europe will do and I will support regulation that takes a tiny bit of comfort away if it makes us more resilient in the face of climate change and geopolitical difficulties.

Whether you give a shit or not isn't important. Regardless what you personally think, a law is accepted if it's acceptable. And most people will think "OK, I get that we can't continue to throw away phones and keep using some countries as slaves just because we want the latest iPhone now". Just like people in Europe accept to pay more taxes than in other places of the world because we get that solidarity is important.

If any third party repair shop can replace it, that'd already quite good. But manufacturers have been known to make it impossible even for 3rd party repair shops to do anything, or at least to make their lifes as hard as possible. That's a no-no.

Is 0.9mm really worth throwing away so many phones?

It's important to remind ourselves that the metals in these phones are mined in part by people with very difficult life conditions, often so bad that they die on the job. We ought to be able to repair what they contributed to build instead of asking them to mine yet another pound of metal just so we can save 0.9mm. This will also reduce need for mining, which creates all sorts of pollution.

> Use less and pay the same is an hypocritical and outrageous way to raise prices

That's what taxes are there for: encourage purchases that serve the general interest.

> So you actually ask to squeeze more money out of your own people?

No, we can use less gas and pay the same. People waste plenty of energy in lots of ways.

Being a Frenchman, I think government could push citizens to act, increasing price of Russian gas through massive taxes or something like that. We only import like 20% gas from Russia, from what I understand. Impact would be small for us and would prepare us for potentially more severe restrictions in the futures, helping us become more resilient. Am I missing something?

Sometimes, trying to be nice at first turns into deadly encounters. Sometimes, employing force early means not having to employ even more force later on. Difficult balance I guess.

You can have 2 Heroku apps, one for frontend with little resources since it's all static and one for API with more resources. Then create a custom Nginx config on the static app to redirect API requests and it should work fine.