I originally posted last week as a paid product to get some feedback on the idea, but after some thinking decided opening it up as a free resource.
This collection is basically an expanded version of a bookmarks folder I have been collecting for around a decade of building side projects and businesses. I tried breaking it down into an easy to follow format (although I think the navigation is still a little wonky) so that it can be something you refer back – a personal knowledge-base of sorts.
These are just links. Nothing is downloadable, and I don't claim ownership of any of the content in the list.
I realize charging people for this seems a little unorthodox -- it's one of the reasons I posted this on HN before anything, to see what people think of it. Calling it a bookmark folder is a little underselling it; I've spent the better part of a decade collecting most of these links. When I built this, it felt like what I'm offering is the time and effort saved collecting this, instead of the actual content.
I’ve been putting off switching my native apps to cross-platform simply because I’m too busy to learn react, so it’s great to see that vue is finally an option.
Of course it’s probably a little too soon to completely switch live apps to this, at least until it stabilizes a little bit.
Edit: never realized this existed for the past two years and is simply a wrapper for react native.. any reason it’s being posted now?
Shoutout for Framework7. I built a test app in both Ionic and Framework7 and vastly enjoyed the experience of F7 over Ionic.
For Ionic Vue is still in beta, poorly documented and had some vague errors with obtuse solutions. It didn't have all the components you might want in an app either, so less boiler plate.
Framework7 has full Vue documentation, and the handful of components that aren't Vueified (Calendar, Toasts) are easily integrated using native JS and the this.$f7 helper.
Their creator is highly active and responds to almost all (non-idiot) questions on their forum.
Downsides of F7: no SCSS but CSS variables which clutters the inspector, a lot. You can always overwrite these with a scss file but the variables are always there.
Quasar and Ionic aren’t native though. They give you the JS app in a browser packaged into an app. React/Vue native give you a real native byte code app.
Ionic capacitor seamlessly integrate with native plugins and you can write your own.
Btw the react native js engine is much slower than the one on Ionic, at least on IOS.
Ionic screwed me like a deck screw with their update path being more of a secret way into Mordor. Perfectly good app that can’t be compiled anymore without a full rewrite in what is effectively a completely different framework.
I initially used it with version 1/Angular 1.x. Then when Angular 2 was basically a complete rewrite from scratch Ionic did the same. For a little bit I was still able to compile the code but quickly their tools became unavailable and unusable.
It's true. But also I consider Angular 2+ to be inferior to other similar frameworks. It was overengineered to no end had as much to do with Angular 1.x as a space shuttle has to do with a horse buggy. I remember looking at how they proposed to specify templates via `` template strings as part of the JS code, making their template language completely unreadable and thinking how that's such a step back in usability compared to how Angular 1.x did it, which was basically what Vue.js does.
And I do still have some scars that haven't fully healed from that transition. Look at Vue's evolution from 1.x to 2.x to 3.x. The new way to create components in Vue 3 is what Douglas Crockford proposed way back in like 2008. Except it's reasonably worse for code readability compared to Vue 2.x because it is completely unstructured. And at one point the Vue team was talking about taking out half the features that I routinely use in Vue 2.x such as $emit()/$on(), watchers, etc.
I don't have as much experience with React, but from what I understand they break compatibility much more frequently than Vue does. Plus, JSX is a very polarizing tech and I am firmly on the side that dislikes it.
Compare all of the above with a project like Django where backwards compatibility is maintained for years and developers consider it a big cost to break features. It's a much more carefully developed project and it makes running the code much easier. The template syntax has not changed in what, 10 years at least? In the meantime how many JS frameworks have we seen rise and fall? As far as I am concerned, every time a framework or library update breaks my application, the framework is imposing a cost on me. Adding new features and refining existing features? Fine. Breaking the world because someone didn't like how $emit()/$on() worked? That's like if the Linux kernel decided tomorrow to switch to using Windows syscalls because they got a Windows developer on the team.
NativeScript unfortunately just can't compare with React Native in my experience. I've been a Vue dev/consultant for several years, I wanted to love NativeScript, but every single time I try to build something with it (last attempt was about 2 weeks ago) I come across a missing feature and end up begrudgingly switching to React Native.
If your goal is to actually put out high-quality apps, do not switch away from doing them natively. No cross-platform kit can compete. You are making sacrifices, sometimes big ones, in order to get the cross-platformness.
I've thought a lot about this. My biggest problem is that I'm the only one maintaining the project, and using something like vue + cross-platform would make things a lot easier than maintaining 3 different code bases (ios, android, web).
My understanding is that cross-platform tools have matured enough to be used as replacements to native implementations. Is that not the case?
From the (limited) work I've done building React Native app's.. In most cases, the user is not going to be able to tell any difference from a native app.
Exactly, other than very minimal metrics you can't do much of anything without cookies. It's great that there are now many alternative analytics services available, but I feel like they all just do the exact same thing – stick a two-line script on your website, then get some very minimal data about your website. This is probably good enough for most people, but it becomes very hard to actually do anything with this data if you're running a more "serious" project.
But I'm always amazed at how much popularity these projects seem to gather. I myself made a very simple landing page [1] for a similar service (but one that caters more to the saas based applications), and it's managed to gather some interest even though I've barely done any promotion to it.
This was inspired by Sahil's twitter thread [1] the other day. I included the number of employees along with any relevant blog posts or interviews for each company to provide more context.
Interestingly enough, it turns out Basecamp's founders actually kinda sorta got some money from Jeff Bezos [2] when they were starting out, but apparently the money was never used to fund the company so technically they're still bootstrapped.
Maker Bites is an aggregator-based community site that helps surface the experiences, lessons, and thoughts of members of the maker community. Submissions generally include blog posts, interviews, stories, lessons, experiences, and tips.
Since submissions on Maker Bites are aimed at spreading knowledge and fostering discussions, most content is timeless in nature. In fact, outside of "Show MB" style posts, announcements and news submissions are discouraged.
In most contexts, a "maker" is someone who's involved in a technology-based project, generally as startup founders or bootstrapped developers building businesses.
For a second, that "raised 5 mil" line really made me doubt everything I've learned from you guys until I actually read through the post. Congratulations!
Re downvotes: the problem with that is sometimes book recommendations can be very personal or context-dependent. Sure 10 might not recommend, but what if the recommendations come from people whose background / experience / goals better align with yours? I included profiles for each founder under every book for exactly that reason — so you can learn more about them and about what might have driven these recommendations.
Yes. But what if the same can be said for those who don't recommend? I read a lot. Most of the time it's time well spent. But I don't recommend everything I read either.
