Live data from Hacker News

How and why I built Japan Dev

japan-dev.com

171–172 of 172 posts

Re: How and why I built Japan Dev

#171
post #77

This was incredibly well-written and an enjoyable story. Congratulations on pushing through and getting traction. Something that resonated: > We had to put 5 million JPY (~$45k at the time) in our business bank account and leave it there. For... some reason. Living in Asia I've come across this bizarre government obsession with "money in the bank" when dealing with them: "You need $15k in a bank account to apply" "Ok…

IF you try to understand it from the regulators perspective, it totally makes sense. You see, the law is written for legibility, not for variation, and rightly so. $15k cash in the bank is easier to understand than $300k in ETFs. Your $300k ETF might be stable or it might fall below the value of $15k over 6 months (not likely but government officials are not in the business of investigating the stability of individua…

I understand why some governments do such things for businesses but my situation was for an entrepreneur visa application, the cash had to be there for six months to simply begin the process, what happened to it afterwards was irrelevant, I could invest in Dutch tulips for all they cared.

Amusingly I was not even required to incorporate there to get the visa unless going into certain industries, was clear with them that domiciling in Singapore makes far more sense for a saas startup and they had no problem with that.

Re: How and why I built Japan Dev

#172
post #161
post #160

Earlier quoted context omitted.

Can you explain more about these headaches? So far i'm still convinced of client side SPAs :D

To see your page content, crawlers need to load your JS and wait for it to hydrate the page. Google does this (but it's still not ideal). Most other crawlers don't. That means they won't see your rendered content. This becomes an issue with sharing on social media, because your meta tags won't be read properly. If you share a blog post on Twitter for example, it won't be able to fetch your og:image, title etc so it w…

Thanks for your input! server-side rendering should fix most of the first issue. You can get all the relevant data pre-rendered and it's pretty easy to do with the right framework. I've used quasar.dev for this in the past. It should also solve the initial load times (to an extent). The chaining can be fixed with lazy loading/code splitting.

The only thing i haven't fixed yet is hiding the cookie banner for bots :/

Post reply on HN