searchableguy

They are also huge investors in crypto and any winding up will have an impact on a significant number of companies.

They control a significant portion of stablecoin, defi, and chain market too.

Their impact would be felt outside the crypto space if they ever go down.

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.

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.

Does that clear it up?

There is also overhead in passing structures and other communication required so that layer can change the number as well.

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.

Many legacy codebase don't have an easy way to add schema and make code changes so you end up maintaining a separate file to avoid making changes in the codebase.

It's a huge pain to maintain open API files and the generators are of varying quality supporting different specs. They also handle some parts differently in the output.

Which generator have you used for typescript? There are 4 of them and all of them have different issues.

I find the axios one the most stable but keen to know.

How do you also handle refreshing token, incepting request while passing the client through configuration in these?

I find interception and changing response breaks some of the client methods without a way to handle the failure.

Any example or resources you found useful would be appreciated.

I would like to use it with existing component library which is built using tailwind without making changes. Is that possible?

They don't take individual customers or startups without funding. They are focused on high ticket corporate customers.

For Indian market, razor pay and open money would be sort of equivalent focused on corporate banking.

In India, most neobank startups are bleeding money through rewards and incentives funded by VCs and they are all shutting down one by one.

There is no moat. Support is expensive. They are still tied up with a traditional bank because getting bank license is not an option for startups. This is the case almost everywhere, not confined to India. You would be working with a legacy bank and inherit all the limitations.

Banking is free for most people. UPI and rupay run by government agencies result in 0% charge for merchant and consumers. So you can forget about any transaction related fees.

This might not be common across the world but there is no lock in when investing in funds in India. You cannot lock in customers for mutual funds and related investment legally anymore as of last year, I believe. So not possible to make profit on investment management side.

It's really tough for a neobank.

Why not use playwright?

https://playwright.dev/

I always chuckle at this site does not need SSL post from n-gate.

PS: Use the URL directly in browser because the site doesn't like traffic from HN.

Spinning up a new VM from scratch itself will take around 10gb read and write.

If you are building containers or loading up a lot of data, can easily reach that.

I'm surprised your figures are low because I always see tens of gbs of write and read normally without doing much.

Reverse engineering is not illegal and if there is genuine demand for an alternative client, why would investors not fund it?

Eventually, you will become big enough to be next plaid and force everyone to open their APIs.

There is no ideological reason behind it.

I recently trained it on NFTs to generate variants of bored ape and punk style art.

The only problem right now is the variants are not consistent and it's hard to tell stable diffusion to make only slight variant changes with some mask and editing.

You can mask out the top head of the NFT punk and stablediffusion can generate different heads but that's fairly limited in the end result.

I think a cloud service which can automate the training and store textual inversion models would be a really cool startup. Ping me if you want to build this together.

I've been experimenting with it to spit out commercial style illustrations and stock photos. It's a lot of manual work with Google collab and frustrating to try.

And now the likely removal of graphql as wire protocol. What are the key reasons to remove the use of graphql query language?

https://column.com/

What you have proposed is technically infeasible to implement if you want to preserve properties of blockchain. It would be no different than a bank because KYC will add inherent centralization and fragmentation in the entire system.

So we need a compromise here because either way you cannot retroactively enforce KYC approved wallet to participate on-chain. If you do, it will be optional in that case the solution implemented by tornado is decent and does not require giving data to brokers who often sell it without permission.

Government can directly subpoena data from individuals when investigating them.

Any crypto to fiat ramp is already KYCed and businesses dealing with payments require KYC beyond a certain value transaction so in practice, the impact of KYC at on-boarding will be negligible. Not to mention, KYC can be easily faked by actors with significant stake in a globalised system.

Furthermore, the data does not support that money laundering is a bigger problem as percentage of transactions in crypto than traditional finance. The AML laws have been largely ineffective in practice in traditional finance with huge cost of compliance and degradation in experience for consumers & businesses.

So we need to think of a better solution to discourage money laundering than mass surveillance.