I assume it's because they would need to re-wire electrical and retrofit plumbing on a massive scale to accommodate kitchens and bathrooms for separate units. They end up needing to gut the entire building and cut through floors and ceilings without damaging any structural and load-bearing parts. It doesn't sound easy nor cheap.
I've heard stuff like this is much cheaper to come by used, auctioned by liquidated companies. Not necessarily the exact above mentioned models, but 'trendy' stuff like Herman Miller chairs, and similar. Let's say 500 bucks.
I found the velvet flag version on Amazon for $1150, which is still quite a bit.
It’s something to keep a look out for. They are iconic enough to pop up randomly in unusual places or furniture stores that you wouldn’t think would sell something like this.
This has nothing to do with NodeJS or NPM. The code is freely distributed, just like any open source repo or package manager may provide. The onus is on those who use it to audit what it actually does.
It absolutely does have to do with it. If we continued to ship software libraries like we still do on Linux, then you wouldn't be downloading its releases straight from the source repo, but rather have someone package and maintain them.
Except at the granularity of NodeJS packages, it would be nearly impossible to do.
Why are Linux packagers so trustworthy? In most distros, they're a group of volunteers. The group is smaller, but it's not impossible for someone with malicious intent to get the keys to the kingdom and upload packages with embedded malware.
The code is literally right there for you. It doesn't matter what ecosystem or package manager. Someone could distribute the same thing anywhere — it's up to those pulling it in to actually start auditing what they're accepting.
Heads up. The site you linked is just a wrapping of the original with adverts and tracking scripts. It isn't running the latest version either. Much better off using the creator's version.
SSR with CSR is a worst-of-both-worlds approach. It leads to brittle ”isomorphic” behaviors when the same code needs to handle both SSR and CSR, inevitable client-side ”hydration” mismatches and various other issues. The same code needs to fetch eagerly but minimally, but also use and update the server-provided data on the client-side.
Ultimately that so-called ”isomorphism” causes more numerous and difficult problems than it solves.
Especially cuz the vast majority of sites can either just be client rendered SPA's or server rendered multipage apps. There is no need for the complexity for most sites and yet this is the default for pretty much all js frameworks...
I gave up updating Nextcloud. It works for what I use it for and I don't feel like I'm missing anything. I'd rather not spend 4+ hours updating and fixing confusing issues without any tangible benefit.
reply