wiennat

I wonder if we have a similar guide for JavaScript/TypeScript project.

I guess it is because Edge is using the one that comes with Chrome while OneNote has its own implementation.

What's happen to MS these days? I remember the documents during .NET 2.x days were very good, well-organized and useful.

The site is probably from 6 years ago

https://github.com/hunterbridges/yamanote-style

Cool story and congratulations on your work.

-------

I gave my 2010 macbook pro to my parents when I got a new one in 2015. They still use it to surf the internet and sometimes for netflix before bedtime. Its battery is so swollen that the lid cannot close anymore.

I also bought apple care but never had any chance to use it. Very impressive for a computer without any hardware failure for 12 years.

just static page. But you can use their worker service to run some server-side functions

I heard its name frequently around the time before nginx came to its fame. Maybe 15 years ago. However, I never heard any major players use it after that.

What surprising me the most is LiteSpeed is now somewhat unknown web server. Time flies.

I am doing this and it helps in mocking the interface in other classes tests.

Red Bull in Thailand and in the west come from the same origin, Chaleo Yoovidhya, the Red Bull founder.

The west Sriracha was developed by a Vietnam immigrant. You can see his recipe as one of many available Sriracha variants at that time.

I am also in the middle of moving off graphql to REST api. It is a 5 years old project and the graphql part was implemented with a very old spec. Since it has not been well maintained, it could not catch up with any features offered by graphql and users need to write their own queries by hand due to spec compatibility.

Rewriting it to REST allows us to "rebrand" these apis. At least, it does not scare our api users as the word "graphql" did.

thank you for sharing. I was thinking about building the same thing.

I use Ctrl + q

It can be introduced at many points.

in dev: You can setup dependencies without worrying about underlying os. So it is easier for building a new dev machine, adding a new team member, etc.

in integration test: you can setup multiple integration test environment as long as you have enough resource. Running multiple integration tests without interfering other team members is the major benefit here.

in prod: as you may know, for isolation and horizontal scaling. Easier roll back and update?

Not only sewage infrastructure in Thailand cannot handle toilet paper well, toilet papers sold in Thailand also does not dissolve well in water.

you can freeze in instant if you use that in cold winter.

(except you use Japanese washlet)

Shimokitazawa still have a lot of foreigners. It is surrounded by universities including Todai.

Japanese food has pretty high carb but they are mostly unprocessed.

I don't have any problem with their Go implementation. Instead, it is very impressive to me who has little knowledge in Go.

I just want to point out that Node runs with a single thread so it does not max out CPU utilization. It would be nice if the author does the benchmark again with multiple processes of node js.

This immediately comes into my mind when I see the charts.

It is also interesting to see that only one Node process can barely serve 10k connections.

---- After I check the source at [0]. They use a simple http module to serve the requests while they use `http.ListenAndServe` which spawns go routines, hence more CPU utilization.

[0] https://gitlab.com/stressgrid/dummies

Vue, Vuex, and Vue-router official document are good enough. Many concepts in Vue are similar or quite simple compared to what you have to know in React. However, I find that Vuex is a little bit more verbose than Redux. You might it troublesome at first but will be better after you are familiar with it.

Agree with other comments that Vue and its companion libraries have much larger API surfaces and have a lot of magic while React's advance techniques can be built upon few basic fundamentals so you need more time to remember those. But I feel that most of APIs are practical solutions to problems you need to fix by yourself in React.

This is a post from 2012.

They had some snacks with them when they went into the cave.

Basically, there is a warning sign for cave flooding during July and October. Monsoon season is not likely to start at the end of June so they might thought it is still be fine to go into the cave.

The food has been delivered after they found the group.

Medium also have horrible reading experience, at least for non-login users.

You still can do the same with the current version.

But it can improve those images taken in auto mode of point and shoot cameras.

Basically, the purpose of PCA is to reduce the dimensions of the dataset by finding components that most influence the data. I think your last sentence is quite accurate to describe what PCA is.