168 karma · joined January 8, 2013
Most users probably have their browsing history switched on, and synced with their friendly browsing software provider anyway, totally reversing any privacy advantage a user might potentialy gain by using DuckDuckGo.
Expressive, concise code is always a good thing.
Meteor is excellent for MVPs and POCs; there are a lot of people out there with big ideas, but limited budgets to test out those ideas.
In Meteor, you can access your collections from the client and the server; and the vast number of packages on atmosphere makes writing a webapp in Meteor feel more like assembling lego than anything.
The speed at which we can write software is tightly correlated with our ability to innovate quickly; test things out, keep what works and throw away what doesn't.
I've developed things for clients in Meteor, in a matter of weeks what others have failed to deliver in year
90% or so startups fail, not because your front and backend were too tightly coupled, but because of a whole variety of other reasons. Given that most of that code will end up in the bin anyway, might as well focus on quantity, and switch to something more robust when need be.
I also put my laptop in a bag once in a while, padlock the bag, then put my phone and padlock key in my ksafe (http://www.thekitchensafe.com/). Offline heaven.
It's very much akin to the tech guy walking into a sale's person's office, to fix their immediate need. The tech guy is thinking all he has to do is teach the person to think for themselves, problem solved. All the sales guy is thinking is is "oh god, please don't teach me anything".
Personally I find locate and slocate very useful in linux to find the files I am after. Going over these might be more useful. That or whatever third party tools are available, with a UI and good UX, to achieve a similar goal.
I don't know about you, but when I'm a passenger in a car, I'm attentive to everything. I guess the fact I often have strong rapport with the driver (usually a family member) means we are in sync; I mean I'll literally do blind spot checks, and carry out many of the driver's visual rituals simultaneously.
I think this is an interesting scenario; machines assisting men in, for example, collision avoidance systems, or in this case all the way up to self driving; and men being required to help self-driving machines in unusual situations.
Having lived in Mumbai for 2 and a half years, this to me actually kind of makes sense.
Surcharging people will probably vanish once air filtration becomes more common, or ubiquitous (I've never been, so wouldn't know).
But in Mumbai, there's really nothing like stepping off the hot and polluted streets, into an air conditioned place with clear air.
Of course, the issue needs to be fixed at source, and this is so obvious it's hardly worth stating. But somehow, having lived in a polluted asian city, none of this surprises me, unfortunately.
But the more time goes on, the more we'll have users who just don't care if it's a .io, .xyz or .whatever.
It's not like you learned to speak with your parents reading you the dictionary beginning with the letter A.
What did you use it for, if I may ask? What how big a project are we talking about?
I would have thought hitting the docs wouldn't be a part of the annoyances list. Did you feel you had to hit the docs more than with any other language?
Initially it was used to extract tables from text documents, and its always had a strong focus on text manipulation and regular expressions.
Its implicit variables and syntax mean you can write very, very concise code. Yet by following stylistic guidelines of your choice, you can write code that looks sane and maintainable.
I really like the fact you can import os commands and call them as a part of the language. It makes writing scripts a breeze. In fact writing anything in perl is a breeze. Check rosetta code, you'll see Perl 6 is one of the most concise at every turn.
As much as I really like python, I find that calling system commands is a pain.. calling os.system is obviously far from great, and calling subprocess can get cumbersome.
I haven't played with perl in a while, but my past experiences with perl was always getting a lot done, with very little work.
What I tend to dislike with the concept of prior knowledge before being let to work on something, is that in the vast majority of cases, once you join a team that has such a requirement, you notice their knowledge acquisition rate is currently flat; they've become stagnant themselves and are generally insecure about what they know and don't know; it's usually people with a currently flat learning curve who assume others need to know a technology prior to working on it; they're just projecting their static mindset onto others.
Some people eat new programming languages for breakfast if they have to. Deal with it?
But some people don't care about their privacy any longer, because, well we probably have none at this point anyway.
So in for a penny, in for a pound.
Edit:
Consider putting something about privacy right at the top of the page, if such a feature exists. e.g all bookmarks are encrypted, and only the user has the key, or whatever.
returns to article
Other than that: fantastic work.
If these shares make money, that will be a bonus.
Also don't feel bad for forgetting an entire module. It means you watched it passively, rather than actively tried to solve problems using the knowledge you had acquired.
Can't consumers decide what their safety requirements are? If they prefer a different service, for safety reasons, can't they just use that service instead?