It is also being ripped apart by external actors - Iran, Israel, France, Palestine, Saudi Arabia, Syria, United States and I am probably missing others.
>Apple is the most environmentally responsible purveyor of mobile devices in the game
I would say that Apple devices are long lasting despite Apples best efforts to the contrary. In my country, India, at least, Apple charges absurd amounts for out of warranty repairs. 10 out of 10 cases i know, it would maker more economical sense to buy new rather than repair at authorized service centers. Sometimes the Apple service centers give the same advice.
Luckily the 3rd party networks provide good and affordable support for Apple phones at least. But Apple is fighting tooth and nail to shut these guys out. Pushing up the cost of repair with every new generation.
On laptops its worse. Apple is really pushing hard to shorten their useful life. Worst part is that they're setting the path for the rest of the industry to follow. Non-removable batteries, soldered RAM, CPU, SSDs, removing backward compatible ports, Use of adhesives, glass in place of screws - making repairs expensive and error-prone. List goes on and on..
Interesting. Do you include websites built using SSGs like Hugo, Gatsby in your statement? Also, any tips on how you handle security (with minimal maintainence) and page-load performance in Wordpress?
I haven't made CPUs before ( I am guessing you have?), so I am not sure of what you are implying. Are you saying that CPU technology is as easy or copy-able like a javascript framework? I can see that ISA would be copy-able. But what about a modern implementation?
The idea that the Facebook has a direct data pipeline into Jio's 370 million subscribers and vice versa and that Jio has a direct pipeline to the Indian govt. is a very frightening thought.
Anil Ambani's firm was chosen as an offset partner by Dassault, not by the Government.
"Chosen". As in forced to chose by the Indian govt. We know this because the French President literally said so in an interview.
“We did not have a say in this,” Mediapart quoted Mr Hollande saying. “It was the Indian government that proposed this service group, and Dassault negotiated with Ambani. We did not have a choice. We took the interlocutor that was given to us.”
>The reason cited was that it was not the government who was responsible to choose an Indian partner for the “offset clause” of the deal, it was Dassault who entered into a JV with Anil Ambani’s company.
Because the Indian govt. forced Dassault to deal with Ambani. We know this because the French President literally said so.
“We did not have a say in this,” Mediapart quoted Mr Hollande saying. “It was the Indian government that proposed this service group, and Dassault negotiated with Ambani. We did not have a choice. We took the interlocutor that was given to us.”
>if it is code that must be maintained, then at some point the hair may need to be shaved; it simply cannot grow forever as the world moves on around it. the doma of "never rewrite" is silly without further context.
"Shaving" seems more close to refactoring & partial rewrite than starting from scratch. Which is what we are talking about.
Still, You make good points. Maybe, we should think of "restarting from scratch" the same way we do premature optimization - (1. don't do it. 2. Don't do it too early. 3. if you must do, measure first)
I think every developer dreams of rewriting from scratch because they hate how hacky and ugly their code is probably due to rushed deadlines and because it was just supposed to be an mvp. And they think about throwing it away and starting clean and doing it the 'proper way'. This imo is the wrong reason to start from scratch.
But if your technical debt is genuinely preventing your product from going where it needs to go or do its job. That is the right reason. Again you have to make the calculation whether the technical debt is greater than the cost of rewriting from scratch, re-opening old bugs and introducing new ones, breaking your customers workflow - they also invested a lot into your old program. How many times have you liked a program until 'the damn devs went and ruined a good thing' by 'fixing what wasn't broken'. Again, customers don't see or care about the code or technical debt. They just need to get their work done.
Looking at it now, this video seems to have been particularly relevant, considering that the company went bankrupt because they trusted a bunch of silicon valley frauds i.e. Facebook..
>Mozilla has not been able to act aggressively as a commercial player. Just one example: KaiOSTech ...
I am just speculating here, but would this involve significant compromise on Mozilla's core values - specifically privacy? For example one of their investors and partners is Reliance Jio (the reason why KaiOS is the second most popular mobile OS in India) who brag about monetizing the data of their subscribers as a fundamental business model and strategy. The reason i was excited about FirefoxOS was that i was hoping that they would do the same for mobile operating systems as they did for the World Wide Web. Personally, i trust KaiOS devices even less than Android in that regard.
Either way my point stands. Firefox containers aren't profiles and imo shouldn't replace them. They should make profiles more user-accessible, but both solutions should exist simultaneously. If anything, effective use of containers requires more advanced knowledge & awareness making it more suitaed for advanced users.
You can judge for yourself by typing 'firefox -P -no-remote'. Right there, having to use the terminal , has already made it more clunkier than Chromium's solution. Admittedly, Firefox profiles are clunkier to launch & manage - like a hidden feature that has rebuffed all my attempts to streamline their management, as if by design. This can be remedied by use of desktop shortcuts (You can create separate shortcuts for different profiles) but then you have to also deal with the idiosyncrasies of your Desktop Environment (Gnome in my case :/) .
Once its launched its pretty much like running to separate firefox instances in your system with separate bookmarks, histories, settings, addons - like in Chrome. So it is a lot more heavier than containers as a result. Which is why i think the 2 functionalities shouldn't me unified like people in the comments seem to be asking. Similar to Threads vs processes. We need both.
Are you referring to Chrome's profiles? Because Firefox's counterpart to that is Firefox profiles, not containers. Firefox profiles are clunkier to launch & use though (like a hidden feature that has rebuffed all my attempts to streamline their management, as if by design). Type 'firefox -P -no-remote' to start with firefox profiles.
IMO containers and profile functionalities shouldn't be mixed. Containers are a lightweight version of Profiles. Running 2 profiles is essentially running 2 separate browsers running with separate histories, add-ons, bookmarks, settings. A bit like threads vs processes.
Far inferior IMO. Containers are incredibly lightweight compared to opening a separate profile. I would say Firefox profiles are more cumbersome to use than chromes..