HN user

proyb2

116 karma

Programmer and musical

Posts11
Comments203
View on HN

One annoyed UX I dislike about Firefox is swipe back on iOS. Firefox team should fix their swipe back which go to previous page, it also lead to page refresh, and caused the scroll lose its position.

This deliver a poor experience when implementing History API compare to Safari and Google on iOS that work as expected.

I’m not sure how to feel about this warning notice?

“This product can expose you to chemicals including Nickel (Metallic), which is known to the State of California to cause cancer, and Bisphenol A (BPA), which is known to the State of California to cause birth defects or other reproductive harm. For more information go to www.P65Warnings.ca.gov“

I have experiment Meteor for a while in it early stage, I felt Meteor became complex to manage and didn’t like to stuck in a high technical debts.

Now I would rather wait for V language which seem to solve many limitations found in other languages.

Next.js 8 released 7 years ago

One concern on mobile where I find the scrolling is not respond for a second or longer whenever I swipe back to previous page in Safari, applicable in some of the showcases in Next.js too, is it the expected user experience?

Clients see Wordpress as a business platform/lack of dedicated supported in-house and developers on projects based could keep generate incomes from small businesses.

What are the amazing option do you suggests with batteries include in the language would be ideal.

Honestly, Go is great. Its simplicity is refreshing and its performance unmatched. I would still pick it if we need a small API or something that requires high throughput.

I wonder which part is performance unmatched?

My opinion would be Crystal language for its simplicity and higher throughput but unmatched performance is behind Rust and C.

"WARNING: This is a Google translated (originally Chinese) and reposted article that probably is mostly comfortably understandable for senior Golang developers."

The article is translated from Japanese, not from Chinese since Qiita is for the Japanese community.

I'm curious how well could Crystal language handles that huge amount of JSON since most of the Ruby code could be ported over to Crystal.

It has a JSON pull parser to minimize memory usage which is useful for memory constraint environment but at the expense of less performant. If that could be split up with fork Crystal processes, I believe it's feasible.

We don't get where "almost ready" message since I have been coding Crystal.

You knew each languages solve different problems in AI or space age.