Previously, I wrote a tutorial called Scaling React Native Apps for Tablets [0] more than a year ago & it got a lot of attention thanks to the user-friendly title which resulted in a lot of organic traffic from Google.
However, another library called https://github.com/marudy/react-native-responsive-screen came on the horizon at some later time. It is also easy to use. I thought about writing a tutorial on it for a long time & it's finally here.
When I submitted the earlier article, someone on Reddit said that a Tablet should fit in more content than a Phone which I completely did wrong in my previous tutorial because I never used a Tablet before. In this tutorial, I think I've rectified my mistake if you can see from the screenshot.
If you've ever wondered how to do responsive design in React Native, then be sure to check it out. Let me know if you have any questions :)
Posts that start with "Launch HN" get placed on the front page similarly to how job ads do. These are the two formal things that HN gives back to YC in exchange for funding it: https://hn.algolia.com/?sort=byDate&dateRange=all&type=comme.... The difference is that job ads can't be upvoted and decline in rank as a function of time, while Launch HNs can be upvoted and get ranked like regular stories after the initial placement.
Posts by YC startups after their initial launch don't get any special treatment. If a submission doesn't say "Launch HN", it's subject to the same rules as everything else.
Edit: HN also displays YC alumni names in orange to other YC alumni.
Well, the previous comment was describing the use of Redis as a cache, and in that use case, yeah, it's kind of between the application and the database.
That said, caching is just one of the possible uses for Redis. I think of it as an easy way to share arrays, dictionaries, queues, etc between different applications. Then it's easy to see how it can be used for almost anything.
When used as a cache, Redis is often used as a 'look aside cache' (vs 'look thru cache'). Generally speaking, Redis does not talk directly to your database. Instead, your code looks to Redis, and then if it doesn't find what it's looking for, your code looks to your SQL database
Ohh yeah like reading. But other than that I don't think there can be other indicators to know how much active you are on your Mac.
Can you provide any other examples which does not include mouse & keyboard?
I think mostly Developers, Designers & Gamers spend their time the most in front of the computer & need breaks.
For me, this app worked immensely well because I for the past couple of weeks I've been coding for 9+ hours without a lot of break (not more than 5 minutes) & it hurt my eyes & also there is a lot of headache too. Now I don't have to consciously remind myself to take breaks. AFK takes care of that for me :)
I am the maker of Away From Keyboard (AFK). Away From Keyboard is an app that reduces eye strain
with reminders to take a break.
AFK tracks movements on the mouse & keystrokes on the keyboard. After a certain interval, it notifies you to take a break & tells you to do some other activity to reduce eye strain. It takes care of your eyes for you without getting in the way.
I was inspired by Aware but I needed more features which is why I built Away From Keyboard (AFK). Also it was a great way to learn some Swift.
This app has helped me immensely & my eyes & head are more relaxed now thanks to AFK. Happy to answer any questions you have :)
I still don’t understand why Angular hasn’t died out. It’s very hard to understand and the tutorials can’t simplify that because it’s just inherently very complex. It feels highly over engineered like classical Java. Instead of allowing you to opt into more complex features as needed like a good framework should do, it forces you to learn its steel curve up front!
I really enjoyed Angular 1.x, was not happy with the 2.0 version (other then they fixed some critical performance issues with scaling websites). It was perfect for making simple single page applications for internal use at an an eCommerce company. POS, Order Processing, RMA processing, Research, competition and price controls, inventory & warehouse management, etc. I use ReactJS for large applications these days.
I think it's due to its enterprise users and customer bases, and never underestimate the power of legacy code base inertia that often keep these types of things going.
Previously, I wrote a tutorial called Scaling React Native Apps for Tablets [0] more than a year ago & it got a lot of attention thanks to the user-friendly title which resulted in a lot of organic traffic from Google.
In that tutorial, I used another library called https://github.com/nirsky/react-native-size-matters at that time. It works great.
However, another library called https://github.com/marudy/react-native-responsive-screen came on the horizon at some later time. It is also easy to use. I thought about writing a tutorial on it for a long time & it's finally here.
When I submitted the earlier article, someone on Reddit said that a Tablet should fit in more content than a Phone which I completely did wrong in my previous tutorial because I never used a Tablet before. In this tutorial, I think I've rectified my mistake if you can see from the screenshot.
If you've ever wondered how to do responsive design in React Native, then be sure to check it out. Let me know if you have any questions :)
[0]: https://medium.com/react-native-training/scaling-react-nativ...