ntaso
Joined 12 years ago
Karma
221
Submissions
108
Member since
Feb 3
Recent submissions
Comment · 1 year ago
Well, it's totally likely. But there is VanJS, which calls itself a vanilla JS framework, which adds to the confusion: https://news.ycombinator.com/item?id=36067983
Comment · 1 year ago
The irony is: I wrote a bunch of small custom elements [0][1] that do one thing and I don't use Lit for that, because Lit is still overhead. The litte bit of boilerplate overhead of Web Components, I simply wrote by hand.
[0]: Table of contents element: https://github.com/cmaas/table-of-contents-element
[1]: SVG avatars (React-free fork of Boring Avatars): https://github.com/cmaas/playful-avatars
Comment · 2 years ago
Great idea, especially since many popular cycle tracking apps have a bad rep of sharing data eagerly with Facebook and other entities.
One thing though: I know it's popular in these apps to show the cycle as a "clock face", but if you think about it, this is a weird representation, because of the variations in cycle lengths (of natural cycles not changed by contraceptive hormones). So, if one cycle is 26 days long and the next cycle is going to be 30 days long, the clock face will show an average of 26 days for the next cycle and the handle looks stuck "5 minutes before 12" and every day, the handle doesn't tick one further, but the unit (day) becomes more compressed.
This makes comparing cycles unintuitive and suggests that natural cycles always have the same length. In reality, the majority of women have fluctuations of 8 days or more in their cycle's lengths per year.
Comment · 5 years ago
I dumped all note-taking tools and just use Sublime. I took the idea of timestamp-based ids from Zettelkasten and simplified it even more. My setup now is:
Create text file named `YYYY-MM-DD Title of the Note.txt`. Save to a folder. Write freeform.
I think it's important to understand one concept of note-taking:
You can either spend more time organizing to spend less time retrieving information later. Or you can spend less time organizing and (slightly) more time retrieving information.
If you're starting out or don't refer to older notes that often, it's a better idea to just dump everything with as little friction as possible and use a search tool to find information.
Comment · 9 years ago
I know. Same with textareas, especially if they're wrapped in some kind of scrollable container. It is a mess. I don't know why it's not being fixed.
The only reason I can think of is that Apple intentionally keeps the mobile experience slightly crappy so that people perceive native apps having higher quality.
Of all companies, Apple should be the one with the best usability in a browser, no? But hardly so.
Comment · 9 years ago
Wrong column. Transferred counts. Not the actual file size.
Comment · 9 years ago
Same here, except I had someone make native apps. They were bad and unmaintained for a long time (solo dev here as well, running a small business). But still, people used this Android app that didn't receive updates for 4 years(!) over a mobile website where I put a lot of effort into.
At some point, I gave up. If apps is what people want, I make apps. After a looong process of deciding between native and hybrid (build with Ionic), I finally settled on Ionic. The result is actually quite okay. People love it. I can maintain two platforms with a single code base and will probably rewrite parts of the web app with Node so that I can share core code between 3 platforms.
How all of this will turn out in the long run, I don't know. Maybe I'll outsource app development at some point again in the future, now that I have a working product that is exactly as I want it to be.
Seriously, consider releasing a Cordova-based app. Slap some functionality on top so that it won't be rejected by Apple (Website-only wrappers aren't allowed). Maybe an offline storage or whatnot. This shouldn't take too much effort and you might be surprised that new customers find their way to your business.
Comment · 9 years ago
I want PWAs to succeed, because I would love to publish close-to-native apps without an app store. I think PWAs are a great thing for the open web. However, hyping PWAs with unrealistic expectations doesn't do any good. The Ionic team talks in the same vein. I like Ionic, I don't like hype. Here are a few reasons why PWAs aren't there yet and probably won't replace most apps in the near future:
- No native APIs. Yeah sure, you can order a coffee at Starbucks, but the underyling hardware isn't exposed to JS. You won't be able to make a camera app with PWAs.
- Input controls suck. Same as with every mobile browser and every Cordova-based app: You cannot control how the keyboard behaves and I suspect that it's not even in Apple's interest to make Mobile Safari super-great. Sure, they're working on PWAs, but that doesn't mean anything. Just see how bad Mobile Safari's <select> looks like. Or bugs in multi-selects that have been there forever.
- They still run in a browser. It shows an address bar and whatever else your browser is always showing. Try Twitter's PWA right now: https://lite.twitter.com It's way too easy to accidentally swipe back. And then, Twitter being a shitty Single-Page-App, the browser loses its scroll position.
- PWAs suffer from the same problems like all SPAs [1]
And finally:
- A PWA is just a proxy to download and cache responses from a server. It enables offline support (kinda) for single-page apps. It's not a magical something. The problem is that most users go to the App or Play Store first (like djrogers pointed out here: https://news.ycombinator.com/item?id=15219682). They COULD be using PWAs – or at least good mobile webistes – right now, but they aren't.
I think PWAs will find their places and I'm betting on them, too, to a certain extend. But over-hyping PWAs without addressing these issues is just naive.
[1]: Great read on this topic: https://adamsilver.io/articles/the-disadvantages-of-single-p...
Comment · 9 years ago
I build an app with Ionic and didn't encounter a single problem you mentioned here.
- Router? What's wrong with it?
- Build process? `npm install` then `ionic serve`. I think that's it.
- Live reload and building my app became much faster during the last months. It takes probably 5-8 seconds today
Comment · 9 years ago
Why? App Store exposure, client-side demand for an app, offline-first – and quite frankly, because it's written for desktops in mind and the mobile experience just sucks. Wrapping it in Cordova at least gives some control over the experience, such as: You can't accidentally swipe back on the browser, full screen, no address bar etc.
Check out the Twitter PWA (https://mobile.twitter.com). Accidentally swiping back happens to me a couple times per day.
Comment · 9 years ago
Unless, of course, there's no backend and your app is a full-blown tool to run on the device only.
Comment · 9 years ago
Not your parent poster, but in a similar boat:
Because I've written the game in JavaScript and it renders to Canvas. It also works in the browser. To go native, I'd have to rewrite everything from scratch. And then I have to maintain 3 platforms.
Maybe Unity is the solution, but right now, it's not written with Unity.
Comment · 9 years ago
How is writing an entirely new view layer for every platform more maintainable than a few if-else trees? React Native doesn't come with good support for both platforms out of the box. Many components are unstyled. You still need to match the platforms' native behavior. TabBar is shit on iOS, you better go with TabBarIOS, and suddenly, you have exactly the same mess like in Cordova-based apps.
The benefit of Ionic 2 is that there's hardly anything you have to do yourself to target the OS / device. It's all handled by Ionic.