> But they maintained a land, air, and sea blockade of the region, controlling water, food, power, trade, and immigration. And the region remained under continuous threat of the Israeli military returning. That's not self governing.
The key is that Gaza can be "self-governing" even with the above restrictions. What they lack is "sovereignty".
While it says that your personal data may be seen by human reviewers to troubleshoot, address abused or make improvement based on your feedback, it does not mention that your data will be used to generate ideas for blog posts.
It's harder to avoid bad quality videos that now you can't see downvotes.
As for the video being unnecessarily long - I have played with copying the transcript from the video into ChatGPT, but they tend to be too long for ChatGPT to handle.
> Too many properties are being used as investments and not as a primary residence.
When properties are being used as an investment, they are rented out. If that's true, it should show up as higher rental vacancy rate and low/stagnant rent. That's not the case in Vancouver, BC as we have low vacancy rate and rising rent.
Homes could be left as left empty as well, but we have multiple annual taxes, ranging from 0.5% to 3% of the total property value targeting these underutilized home, and that hasn't driven price down. In additions, these taxes essentially provide an one-time only increase in the number of homes available. They can be easily absorbed by population growth.
With the population increase in Canada, building more is the only way out.
I was surprised to hear that they got authors of RSS readers to get in touch and fix issues. Last time I looked for an RSS reader for Windows, it was a graveyard of abandoned software.
Steve Gibsons was always a bit of a laggard in adopting things through. He was writing pages about how assembly languages create small programs in the late 90s when that advantage was no longer relevant, running a newsgroup server and hooking up a web UI as a web forum, and so on.
Considering final application size as well as CPU and RAM usage will always be important, whether people believe them to be or not.
I won’t ever go so far as to recommend that others write stuff in Assembly, but I’d love to be able to do that.
CPU and RAM will matter so long as users are billed by those metrics. More RAM will always be more expensive than less RAM, and faster CPUs will always be more expensive than slower CPUs. If you write software that is used as scale, I would consider it a moral failing if you do not consider how many resources your application uses at scale and you do not make some effort to increase the efficiency of your application in some way.
Accordingly, I have almost zero respect for JavaScript developers, especially server-side JavaScript developers. Server-side JavaScript developers know that JS is inefficient and they choose to use it, anyway. How much coal has been burned exclusively to allow JavaScript developers to run Node on the server, instead of some other, more efficient language? A LOT, I guarantee it.
Performance and efficiency matter a lot at scale. At the small scale, no user has ever complained that their application was too fast or that it didn’t use enough RAM.
When you invoke a Lambda trillions of times per year, every last byte of RAM and every millisecond of CPU time matters. My employer has a few Lambdas which are invoked tens of trillions of times per year, and we saved a lot of money moving from Python to compiled languages. We’d save a lot more if we knew how to write assembly.
> especially server-side JavaScript developers. Server-side JavaScript developers know that JS is inefficient and they choose to use it
I'm in no way a JS fan, but this take is wrong. The main reason JS is on the server side is because it makes the transition between server side and client side trivial. Not everyone runs SAAS with billions of requests every seconds.
In terms of not only money and time, but also resources and energy spent, this increase in software productivity it is worth it in most cases.
The advantage of writing code in assembly was relevant then, and remains relevant now.
Given the vast regressions in usability and compatibility of software generally that we've seen in the past 10-15 years, someone maintaining and extending the functionality of superior older technology is doing something unequivocally useful.
It was a good era where when ICQ added too many ads and features to the 99a client, I was able to switch to an alternatives like Miranda IM and they didn't make any attempts to block the alternate clients.
>Is this the reason that my old mid/low end android devices become unusable even through they no longer get updates?
More recent versions of apps (like whatsapp, which requires to be updated regularly) are unnecessarily more demanding. Try disabling Play services, all Bloatware, all quasi-bloatware (calendar, contacts), all the way to the default keyboard. (pm disable-user --user 0)
Install FOS replacements with no internet connectivity, e.g. from f-droid and such (not affiliated)
It is easier to buy a new device, but I get attached to my pal ;)
Has Android gotten that bad? I last used it in 2018, and haven't exactly missed it since, but even back then I didn't think of Calendar or Contacts as quasi-bloatware.
Most of the memory in a phone is flash. All flash memory has limited write cycles and there's a speed/lifetime tradeoff, also. Flash devices normally actually have more memory than stated, writes go to empty pages that then replace the original, which is then wiped. Every cycle the cell grows slightly weaker until one day it's too weak.
In the best case when a page write fails the memory controller discards the page from the pool, when the pool becomes exactly equal to the official size the device goes into permanent read-only mode. (Which would brick any device it's built into. A PC you could pop in another drive, a phone you can't.) Many devices have failure modes worse than this.
The better the quality of the memory the more margin it has, and how much you write to a drive has little to do with how big it is--from a practical standpoint life expectancy is roughly linear with size.
>from a practical standpoint life expectancy is roughly linear with size.
For the flash itself (the giant mass of NAND or NOR gates making up the cells), in terms of TBW it's straight up linear with size. 2 TB flash storage has twice as many cells as a 1 TB (of the same make) therefore can eat twice as many write cycles (unless the manufacturer does something on the sly like change overprovision ratio based on capacity, change from TLC to QLC on higher capacity units and "forget" to mention it, etc., but those are factors beyond the basic logic gate arrays).
However I don't think size effects MTBF as that looks at factors unrelated to write cycles; things like catastrophic failure of a chip or a short that catches fire and burns down the server farm.
Realistically speaking, MTBF has little bearing when considering flash storage lifetime. TBW is where it's at. If the specs only give MTBF, I tend to assume the TBW is bad enough it's worth hiding and I'll avoid those . If not that, then it's either straight incompetence, recycled flash scam, or the manufacturer just doesn't give a shit (all of which are way worse than choosing to omit a low TBW rating).
It may seem like i'm nitpicking the word 'roughly' but i don't disagree with the sentiment. Depending on how you want to measure lifetime (jfc don't use MTBF), it isn't exactly linear, but it's not the flash's fault.
> This concerns the “macroeconomic slide,” introduced as part of the 2004 reform of the public pension system. The macroeconomic slide is an indexing mechanism that automatically limits total payouts of retirement benefits to keep them in balance with revenue from contributions (supplemented by fiscal subsidies), even while the contribution rate of working people is held to a legal ceiling.
In other words, the pension system was designed as pay as you go. Pay as you go system doesn't do very well with a decreasing working population because it relies on the current working generation paying for the previous generation.
Any kind of pension system does not work very well because a decreasing working population means decreasing supply of labor for the non working population, meaning increase in labor prices, which means someone has to take a reduction in the amount of labor they are able to purchase.
The key is that Gaza can be "self-governing" even with the above restrictions. What they lack is "sovereignty".