WhatsApp thrives because in many places, SMS costs are prohibitive (so TextSecure is not an option). In addition, it requires no registration and doesn't rely on external services (so ChatSecure is also out of the question).
1,548 karma · joined October 6, 2014
WhatsApp thrives because in many places, SMS costs are prohibitive (so TextSecure is not an option). In addition, it requires no registration and doesn't rely on external services (so ChatSecure is also out of the question).
It'd be amazing if there was an official and well supported Linux port of .NET. Just imagine having C#, F# and .NET libs available in a Linux environment and talking to Linux tools.
A second issue with "investing in your DE" is that we tend to update computers and installations a lot these days. Any extra step required to configure your environment becomes tedious over time. I used to have a rich dotfiles folder, but the pain of maintaining it became so high that I slimmed it down to the absolute minimum. I even forced myself to conform to some programs' defaults. The less time I spend hunting for this kind of highly specific documentation, the better.
I'd love to have a local HN to see what's going on in my country's scene.
I think HN clones like this should always be encouraged.
I've been a Linux user for roughly 14 years, and every time I try KDE, I can't seem to give it more than 5 minutes. The KDE UX is like kryptonite to me. I feel like a senile old lady when I use it, unable to grasp what the hell is going on.
I briefly tried KDE again when GNOME 2 was killed, and I uncomfortably went back to GNOME. I deeply disliked GNOME 3, but at least I found it usable. (I eventually switched to XFCE).
I know KDE is a mature, large, beautiful project, but ultimately a desktop environment is about user experience, and KDE's doesn't click with me. I'm aware my experience is entirely subjective, but I suspect there are others like me who just can't get used to the K. So we end up in GNOME, and by inertia resort to using and developing GTK applications.
I think it'd be very cool if there was something like XFCE for Qt. Maybe LXQt will play this role in the future.
Airbnb ultimately depends on how much renters, and indirectly seekers, are willing to pay. Its brand is not as well established as Facebook's (at least in my country). If a compelling alternative came up with lower fees, what would that mean to Airbnb? I'm not sold yet on its permanence.
I must be missing something.
There are places that simply don't give a shit about "smart creative" types, and there are places that claim to have a Google-like culture but in practice are just regular old boss-centric jobs. Every CEO wants to be like Google, but very few actually commit to it.
It usually starts like this: the CEO wants to have smart creatives and delegate decisions. But then he thinks about all that hard-won money he'll be throwing at an employee, so he hires someone middle level or fresh out of college "with huge potential". Then he systematically micromanages the guy, because he just can't make that jump. The poor soul either abides (not so smart creative after all) or quickly runs out of steam (this guy will quickly start looking at job posts). Eventually the new hire disappoints in some way and the CEO cynically complains about the failed promises of the cool tech company culture which he tried to implement.
Seeing a very successful company like Google follow these principles, and win, might influence decision makers in a positive way.
- This looks a bit like Rando, but Rando was more interesting. Even the icon of your app is plain.
- No Android support is a dealbreaker for a huge number of users, including me.
- Your only customer review is rather negative.
Work to make your app more appealing (read more about Rando, if you are not aware of it), port it to Android and try again. I'm sure you'll have better results next time.
Good luck!
I wonder about the resolution: was snorm() reimplemented correctly, or was an RNG with the 'wrong' interval supplied?
For longer texts, docs, etc: throw Wordpress (or some other CMS) in front of the damn thing. You can route whatever needs CMS functionality, say /docs, to WP, the rest to your app. If you want tight integration you can just pull the content from the WP database. If you want to get fancy, you can even install something like WP-API (https://github.com/WP-API/WP-API).
Some criticism: I think the website needs polish. It looks a little amateur, which might put off some users. And it took me a while to understand what it was about.
I wonder if there's a business opportunity in this area, especially for digital data. Something like a consultancy specialized in extracting legacy data and migrating it to modern databases where it could easily queried.
Obviously, but you shouldn't have to care about prototypical inheritance for simple databinding. The way view-models work in Angular leads to some complicated scenarios which, in my opinion, shouldn't exist in the first place (http://toddmotto.com/all-about-angulars-emit-broadcast-on-pu...).
> What?
See https://medium.com/@kentcdodds/counting-angularjs-watchers-1... for an explanation.
> To date I haven't seen a coherent argument against Angular; complaints seem focused around having to learn framework specific syntax (present in any large MVC framework) or the perceived "heaviness" of the framework (suggesting the apps you're building aren't complex enough to justify something like Angular)
I have no problem with learning framework specific syntax and Angular is actually lightweight, both from an architecture and from a code weight point of view. What I do find problematic in Angular are some design decisions which often lead to complicated, and non-beautiful, code. Angular is no doubt incredibly useful, even for smaller apps, and I'm grateful for its existence. It is a step in the right direction. But I do think it has room for improvement.
About Mithril, HTML generation with JavaScript is an odd design choice. Obviously it's much better from a technical point of view, but nested or complex HTML must get ugly fast, and I really don't want to deal with template code written by non-developers. Having said that, for a certain class of apps with high performance requirements and comprehensive browser support, Mithril is a very appealing option.
Stuff like ng-model-options="{ updateOn: 'blur' }" is far from straightforward. I guess you could do ng-model-options="model.modelOptions" and define the behavior in the controller, but then your controller would be handling far more than it should. By the way, wouldn't a separate directive be more appropriate for this? ng-update-on="blur" is more palatable.
And in my experience with Angular, it's never just "assign a value to a scope and done", except for the most trivial situations. When you leave these behind, you have to think about scope hierarchies. You have to watch your watchers. When you use something like angular-translate, you have to carefully consider synchronicity issues and the performance drawbacks of each way to bind your models. And so on. I love the power and flexibility that Angular gives you, but I wish there was a simpler way for it to do its magic.