A variation could be the rendering of a partial UI whilst you then fetch data client-side. Even in this case the web component has the advantage as no JS is needed to render the initial UI.
1,441 karma · joined September 14, 2023
A variation could be the rendering of a partial UI whilst you then fetch data client-side. Even in this case the web component has the advantage as no JS is needed to render the initial UI.
When market rent would be 1,200 yet you pay 800, somebody is paying for that 400. Typically the government, thus tax payers, and it will be subject to political turbulence. Ideally you want so much supply that the market value rent would be 800, as your idea illustrates.
The problem, at least over here, is that the naked price is still very high even without any profit motive. Land is expensive because cities are funded by that. And building that home really does cost 150-200K.
I'm sure you can find some 50K of wiggle room, but at the end of the day it's still going to cost 350K and rent/mortgage will reflect that.
How would you solve it? I'll run by a few ideas from the perspective of the Netherlands, as I'm most familiar with it.
"Address land lords by more heavily taxing them or applying caps to rent".
Tried. Has the exact opposite effect. They'll just sell the property. There will be fewer rental homes with even more price pressure.
"Intervene in investing. Control what gets build, introduce price caps, who gets to buy it (for example teachers), etc"
Tried. Projects will simply be canceled. We have a 70% decline in new supply. In fairness, also due to the high interest rates.
"Land should be cheaper"
Can't be done over here. It's the main income for municipalities. Take this away and local taxes skyrocket.
"Building the home should be cheaper"
Can't be done. Materials are more expensive, so is labor, and building standards are much more complicated.
All of the above applies regardless of zoning. So you're in the situation where building a new home costs about 400K at least. Your idea of an affordable home is 200K.
Do share how you plan to solve that?
It's obvious that there's no easy fix, otherwise somebody in the many countries that have this problem would have fixed it already.
Adults have free will.
The point is that the flavor "HTML Web Component" does not rely on JS to start rendering, unlike React.
It's not even culture that somehow organically came from the needs or habits of people. It's literally just a marketing scheme.
When my brother married, they went to the city council and signed a document. Later that night they threw a party in their own garden.
Probably didn't even spend 1K in costs, and everybody had a fantastic time and is still talking about it 20 years later. It really was a special day and they're a happy couple.
Just saying, you don't need all this garbage. It's about the people, not the stuff.
Such is the consequence of complex organizations and outsourcing, as well as employees increasing demands to have a say in their schedule.
When you really think about it, collaboration is the problem rather than the solution. The modern distributed nature of work means that you need a huge amount of collaboration to even figure out what to do, when, and to resolve all dependencies.
So it's pretty maddening that managers call for more collaboration. We need less of it. The perfect workflow is where you tell me with clarity what to do, and then let me do it without distractions or changing everything halfway-through.
Modern employees spent half their time in email, chat and meetings. Not producing anything. And that's generous, quite a few have to find actual productive time in the fragmented 10% of their schedule. It's as if we've all become managers.
It seems the true needs of survival need to be sufficiently expensive otherwise you can't boss people around.
Replacing a submit button with a dummy is wrong, it does not solve the accessibility issue where focus is lost or moves.
That sounds like a browser bug to me. It's absurd behavior. The focus change is as unhelpful as is humanly possible. It's not what the developer intended, it's not what anyone possibly would intend, so why is it the default behavior?
Same for "implementing an ARIA live region"
How about no? Developers are supposed to piece together hundreds of obscure articles to figure out the right way to build an accessible form. Most won't, but if they do, they're still not confident about its implementation.
How about after 30 years the web platform provides some elements that actually do something, with sane defaults instead of millions of developers being puzzled what to do for even the most basic of tasks?
Mozilla has defunded Firefox, allows for no way to directly donate to Firefox development, and now writes activist blogs.
So I tried to do it myself. Studying official materials, repair videos, the like. The important thing I learned is to get exactly the correct Wi-fi card because the laptop (the BIOS I guess) rejects any other type not on the "allow list".
So I ordered it and connected it, which was easy enough. Still rejects it.
Also, the laptop shipped with a wrong keyboard layout. Which my family member reported directly after purchase but Lenovo refused a return.
At work I also have a company issues Lenovo. It keeps prompting for firmware updates. The last time I applied it, it crashed the entire machine and it took me days to get it in working order again.
Your mileage may vary but to me these are Russian roulette machines. Fragile, full of arbitrary limitations, shit software, worse support.
At the same time, the reality check is that ads continue to be the way to monetize the masses as no other model works at this scale of users.
So do expect it to get worse. By means of IP, the Web Integrity API, whether you've opted-in to this new "Ad topics" thing in Chrome...the future direction is to discriminate clients. You will see the ad or not see the service.
The only resistance is to just watch less or not at all.
It doesn't mean that you shouldn't try, I'm just saying we need advise for the rest of us. If you're not in that 1% group that will make it big at a young age or can retire early, I propose the pseudo-retirement.
I'm middle-aged and slowly but surely optimizing my expenses. Paying down the mortgage. Optimizing the energy use of our home. Going from 2 cars down to 1. Buying extremely durable goods. Cutting useless daily expenses.
The idea is to bring expenses down to such a manageable level so that much less income is needed to keep everything going. Somewhere in the age range of 50-60, we pseudo-retire. We switch to a simple job nearby.
We're in our forties and could already make it on 2 minimum wage jobs right now. We still have a lot of room to cost optimize and if we really stretch it, 1.5 minimum wage jobs in 5 years is on the table, as well as 1 minimum wage job in 10 years. Quite likely we'll go for 2 x 3-4 days/week jobs, but even 2 x full-time would be fine.
The main motivation for this strategy is the very high retirement age (about 70-71) by the time we get there but also to get out of our demanding, stressful jobs. They're frying our brains and sanity.
The so-called "forced" update on the Bridge is to upgrade older Bridges that are as old as 2011 or 2015. The upgrade allows this ancient hardware to leverage features of the newer generations of bulbs.
So it's a compatibility update for old hardware. So that you can buy any generation of bulb and use it with any Bridge. If anything, it shows commitment to longevity, customer convenience and the prevention of waste.
But if you're not into that, the update is triggered by means of the official Hue app, which is the sole reliable touch point by which the company can enforce/communicate anything because they have no other way of reaching you. Use any of the 100+ other apps and they will not force you to update the Bridge. And if even that isn't solid enough for you, disconnect the Bridge from the internet. Everything you own works and keeps working.
As for the upcoming update triggering you to create an account: this is because too many people have shitty network setups, connect their Bridge to the internet and then complain that their lights are hacked. Whilst this account is created online, that interaction is one-time only. What it does is to create a username and cryptographic key on the Bridge after which that authentication is fully local. Which is the exact same mechanism in use by 3rd party Hue apps for over a decade now. Many people already are using an account because this is needed for some advanced use cases like syncing with Spotify or with your TV. Not to mention that it prevents "funny" house guests from messing with your lights.
The idea that your hardware is unsafe and might be rendered useless in the future is completely unwarranted and pure misinformation. Any Bridge, any bulb, no matter how old, will keep working until the hardware itself fails. This system is a shining example of longevity.
12 years of full compatibility, an open API, hundreds of 3rd party apps, ground level Zigbee compatibility, meaningful security updates, if this is a "collapse", what would you call other systems?
And no, I do not work for Philips or Signify. But I did build software on top of their system.
What is especially interesting is how a poorly researched article has an entire community nodding along. Immediate consensus on something blatantly false.
I suppose they can get away with all of this because the concept of competing for a customer doesn't really exist at Google. They can toy around without any consequences because they have a money printer.
Also, at Google's current size, anything producing less than 1B in revenue per month is frankly not that interesting. Small stuff.
Most teams do not have a dedicated designer. Most developers are quite bad at CSS. These teams, which are most teams, want to ship something that is not butt-ugly and do it fast.
That's what Bootstrap did and what Tailwind does. All the endless discussions about the technical merit of inlining utility classes versus hand-crafting CSS are pointless and cannot be resolved because they miss the point entirely.
The point is: ship something good-looking very fast by people that suck at UI or don't have proper time for it.
He was also in the Netherlands to talk about/with ASML and NXP. There's a few dozen critical European suppliers that Apple depends on.
He's also not hostile to legislation at all, he openly committed and confirmed to want to apply with legislation in any major market.
Contrary to popular belief, legislation is not always perceived as negative by businesses. Without legislation, you're somewhat forced to get as unethical as the law allows, because if you don't, somebody else will.
In more cynical cases, companies may even embrace legislation as a competitive advantage. An example would be pro-active copyright detection, the detection of misinformation on platforms like Youtube and Facebook. Very hard and expensive to implement, thus small companies don't stand a chance to compete.