All the more reason for them to go down sooner rather than later because they’re eventually gonna go down, so better now where they will have less impact outside the crypto world than they would a few months or years later.
Just live on rent. It will be far cheaper and flexible in India. The rent won't even pay the EMI for home loans for vast majority of these land lords in metros.
It doesn't work that well in practice. While real estate is overinflated for buying, rental yields reflect the market. They are under 2-4% of the property value in most places.
India is also expanding vertically in cities so new housing is often built in different area and older infrastructure is not maintained in the long run.
A significant portion of real estate is built on under the table money. You often pay 30-50% of the value in black money.
So, real estate is a very illiquid investment unless commercial in India.
There are also cultural reasons for artificially inflating real estate and Indian property developers are under huge loans similar to China. It won't be sustainable.
Cred recently added support for adding alias instead of real name. Many UPI apps also associate your phone number automatically to your UPI ID so you are handing out your phone number whenever you pay.
Unpopular opinion: so the majority has to suffer for the minority? Just give us the option to have both and the users can decide for themselves whether they need a special UI or not.
V8 only provides javascript execution. All the browser APIs need to be implemented by runtime such as fetch, filesystem, console, http, Intl, webgpu, serialization, any global objects, cloning, message passing, etc.
Any module system and dependency management is part of runtime (loading scripts, running them before executing code, etc).
Any other execution context such as workers or running wasm is also responsibility of runtime to implement and manage.
FFI or native extensions are also part of runtime. So one may use the built in networking APIs to build a server framework such as express or they may opt to bring their own networking layer through a native extension.
Frameworks such as express and next build on top of http node module.
Many of these APIs provided by runtime are also simply js scripts run in the global context before running your code.
Router is application specific, not part of any of the JS runtime but URL pattern can be used to build a router which is a standardized API implemented by both browsers and deno.
Runtime can choose to provide any API they want under their namespace so deno could provide a full blown router if they want to.
Yeah. Performance is rarely a concern. Although they are pushing it for serverless where micro benchmarks may matter if they are related to execution and startup time.
I think the benefit of deno or bun aren't as obvious when compared in the context of node on DX matter too.
Most of the tooling and standard library can be used without using the cli and switching runtime.
Tools like tsx simplifies running typescript code directly. It does pretty much what deno does internally using esbuild.
The modularity of runtime doesn't matter to consumers even if it's pretty cool.
FFI and security features are nice but I think the future is running sensitive code as a wasm module directly in separate isolated context.
The browser compatibility is an awesome boost but most bundler will polyfill that for you out of the box and you will use a bundler with either deno or node most of the time. I know polyfilling is not perfect but it's good enough for most.
I want to hear what strong reason people have for choosing to use either bun or deno in production.
I use deno for writing scripts because it's so easy to run them especially if they have any dependencies but outside of that, I haven't reached out for it.
So much interest and explosion.