- RN is a good place to start if you have React experience. The instant feedback via hot-reloading for UI is quite nice and makes learning fun. Maintenance can be an issue but it's gotten better over the years. Expo is a really great platform, and using Expo helps avoid many maintenance issues as well as helps you stay in JS land (including avoiding Xcode). RN will give you cross-platform out-of-the-box while also increasing exposure to platform-specific issues. In my experience, RN works well a lot of the time but then sometimes you need to deep dive on some tricky issue, which may require native code or a hack.
- Swift is a nice language that'll be most performant + provide the most-true-to-platform iOS UX and there's a lot of nice online resources for learning native iOS. It's a bit tricky right now because there are two native iOS UI frameworks (UIKit, SwiftUI). SwiftUI is the newer approach to iOS dev but you still need to use/interface with UIKit for some things. I'm finding SwiftUI pretty great these days, especially because it allows for Live Previews of UI (similar to RN's live reload); again, this live code<->preview link helps make learning fun. Xcode is a bit of a beast but it's not so bad imo especially for if you aren't on a huge dev team/project.
- I haven't used Flutter much so skipping discussion of that.
- RN vs native can be a divisive issue for a variety of reasons. Both have pros/cons and you can learn a lot from them.
- The best way to start likely depends on where you're at and looking to accomplish. If you really want cross-platform and/or enjoy React, then I'd look at RN. If you're excited about a particular platform, then I'd say go with that native platform's approach.
I'm always looking to better my flow for PDF reading so really appreciate this question.
I have settled with Notability due to its nice iPad app where I use my Apple Pencil to annotate - the annotated PDF syncs to iCloud so it's available on Apple products (don't think it supports Android/Linux so maybe not cross-platform but something I'd recommend checking out if you can live with that limitation). If it's a book I'm using to learn something (usually tech), I then transfer notes to Bear in outline format (using the Notability mac app to read notes) and sometimes Anki for flashcards. One downside is that Notability doesn't support ePub so I either convert those or read on Kindle.
I tried OneNote recently but the iPad app seems unable to handle larger PDFs like textbooks which is a major bummer and surprising to me.
For anyone in SF, I'd recommend checking out the Dolphin Club if you're into swimming in cold water – it's right on Aquatic Park in Fisherman's Wharf and has saunas that you can jump into right after your swim. It's probably my favorite place in the city and is open to the public every other day.
Are you sure that changing your implementation didn't fix a bug?
I've noticed that a lot of "dependency" problems on "complex systems" are usually programmer implementation problems. Changing the implementation forces you to review the original implementation (or throw it out) and fix the bug that caused you to change the implementation in the first place.
We’ve had exactly the opposite experience. RQ was an absolute nightmare in every aspect across two companies I’ve worked at. And when you need something that Celery supports that RQ does not, you are in a pickle.
I wish you the best, but I cannot help but think you will regret that decision.
Have never experienced this and we sold a huge number of our app using celery. Based on other replies one should pause, take a step back and consider if their code or design is to blame..
"Also, it isn't tobacco that is the big driver of juul sales. Weed is."
What do you mean by this? Juul doesn't sell weed products and is hugely successful because it has made nicotine addiction easier + more accessible (which is part of what the article argues).
Juul was spun-off from Pax (unclear to me if Pax still owns a portion of it). And Juul's nicotine is the "big driver" of Juul's sales, not weed (as the commenter above claims)
I have a friend who works at a competitor and according to him PAX still owned a majority after the spinout. Although, I tried looking it up and Philip Morris just bought a 35% stake, so this may no longer be true.
> Juul's nicotine is the "big driver" of Juul's sales, not weed
I agree, just trying to clarify that (at least at one point) the company that owns Juul also sold weed vapes.
I've never gotten a chance to try out CloudKit but it has always looked pretty cool to me, especially after previous experiences with Parse. However, it seems like it'd reallllly tie the app developer in to iOS -- e.g., let's say I launch on iOS, how do I handle Android and/or web? I understand a lot of apps go iOS-first/focused, but to tie your entire backend to Apple is a bit much (unless you have no plans to expand beyond the CloudKit offerings). From a quick Google search, it seems like there is a JS implementation but I don't see an easy way on Android. This might work great for iOS-specific apps but seems like a bit too much risk vs. other, cross-platform solutions. I do appreciate how the free tier scales with number of users -- think that's a cool approach.
Having said the above, I've always wondered why Apple doesn't have an iOS SDK for user-auth (or if they do, why isn't it more prevalent outside of the Game Center stuff). I'd much prefer to one-touch sign up for an app using FaceId (if needed/user-approved, the app could access user info, like email), then have to signup with an email/username or use another 3rd party like Google. This is especially perplexing to me after the addition of the iOS password manager (https://www.cnet.com/how-to/how-to-use-ios-11s-password-auto...) -- I think it'd be more compelling to offer password management behind the scenes in iOS (e.g, sign up with FaceId and have credentials generated/stored in password manager for off-device access; this could also encourage iOS generated passwords). There's a large chance I'm overlooking something here though, so who knows.
1) is so great -- thanks for making/sharing. I run into the clunky search process for 10k's once in a while and think your site does a great job improving that experience.
In case you're taking feature requests, these are some things I'd love to see in a 10k site (order in relevancy):
autocomplete in search
see recently released 10k's
browse functionality
10k specific discussions (e.g., annotating similar to RapGenius as well as longform analysis)
Some/all those may not be relevant for your site, just things I've always thought would be cool to see. And again, nice job with the site!
Thanks for linking to the slides from the feedback team! Have not seen that.
The problem however is that the stackoverflow discussion and the relevant JS library uses html2canvas and it generates unuseable screenshots containing more errors than probrably the original screen and therefore does not help on the problem the user has.
This is the same advice I was going to give and is how I've been working on my design skills.
One addition: you should look through Dribbble [0] or similar sites for inspiration, and you can use pre-existing resources for Sketch or Photoshop [1] to build mock-ups. I find it better to improve on design by iterating a bunch on mock-ups before working in HTML/CSS/iOS (since I'm much more familiar with going from design mockup -> front-end).
- RN is a good place to start if you have React experience. The instant feedback via hot-reloading for UI is quite nice and makes learning fun. Maintenance can be an issue but it's gotten better over the years. Expo is a really great platform, and using Expo helps avoid many maintenance issues as well as helps you stay in JS land (including avoiding Xcode). RN will give you cross-platform out-of-the-box while also increasing exposure to platform-specific issues. In my experience, RN works well a lot of the time but then sometimes you need to deep dive on some tricky issue, which may require native code or a hack.
- Swift is a nice language that'll be most performant + provide the most-true-to-platform iOS UX and there's a lot of nice online resources for learning native iOS. It's a bit tricky right now because there are two native iOS UI frameworks (UIKit, SwiftUI). SwiftUI is the newer approach to iOS dev but you still need to use/interface with UIKit for some things. I'm finding SwiftUI pretty great these days, especially because it allows for Live Previews of UI (similar to RN's live reload); again, this live code<->preview link helps make learning fun. Xcode is a bit of a beast but it's not so bad imo especially for if you aren't on a huge dev team/project.
- I haven't used Flutter much so skipping discussion of that.
- RN vs native can be a divisive issue for a variety of reasons. Both have pros/cons and you can learn a lot from them.
- The best way to start likely depends on where you're at and looking to accomplish. If you really want cross-platform and/or enjoy React, then I'd look at RN. If you're excited about a particular platform, then I'd say go with that native platform's approach.
- Recommended sites/tools: expo for RN (https://expo.dev/), 100 Days of SwiftUI (https://www.hackingwithswift.com/100/swiftui), Stanford's Developing Apps for iOS (https://cs193p.sites.stanford.edu/)