Hacker News .hnnew | past | comments | ask | show | jobs | submit | more cpplinuxdude's commentslogin

IFFT has a recipe to silence your phone when you're in focus time with rescue time.

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.


Meteor fan here (new convert). Why build something that already exists, just by curiosity?


In my view, following reasons:

1. There are few web based mind mapping tools that are really good.

2. Learning new technology by making things (Meteor in this case)

3. Putting what you make in public for feedback.

4. Improving it iteratively to match the best in the market. Desktop or web-based.

5. Test the boundaries of the platform (Web in this case)

6. Feel good about it as a dev. :)

Start again with a new product. Keep learning and feeling good eternally. :)


Not the author, but a couple of reasons that seem likely:

1.) To learn how to build a non-toy application in Meteor

2.) Freemind is a desktop Java application, so having this be web based means it's available to more platforms.


Very accurate, these and some more reasons stated above.


Would you like a foot-rub with that sir? :)


If that pleases the users ;)


This is a little worrying; after much research I'm starting a new project for a startup using the meteor stack.


Why worry? Does it solve your problem today? Don't fall into the same trap that so many people fall into who worry far too much about how popular the tools they use today will be 3 years from now. Focus on what makes you productive now. Your startup has a far greater chance of failing than Meteor.


and if it takes longer to get what you need to do done with meteor your startup might have a far greater chance of failing because of meteor.


Author here. Hopefully part 2 will answer your worries a little bit. In the meantime, check out Mantra [1] and the Meteor Guide [2].

1. https://kadirahq.github.io/mantra/ 2. http://guide.meteor.com/


Understandable-- but if you are productive on Meteor today, or you and your team have already committed to learning about it, I would suggest that you should see that through. This kind of uncertainty/doubt around open source frameworks is par for the course, unfortunately, and I think it would be a real shame to stop before you've at least built a prototype with the technology you've already invested time with (particularly since so much of a v1 is figuring out the interface/interaction design anyways, y'know?) Just my 2¢.


I work for a startup that has grown our team and product over the past two years, building a major application on Meteor. It's been great seeing the platform grow, and we've been able to benefit from many of Meteor's components from the very beginning. We can add new features very quickly because of the base Meteor provides.

If Meteor is a fit for your project, definitely use it. Real-time, isomorphism, and more can be of big benefits to rapid development.


Interesting. I think the posts contains a lot of useful information, however I believe this kind of response is detrimental toward user acquisition.

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.


The response is also abrasive bordering on condescending. The tone is very much along the lines of "what are you, stupid?" Even though they answer the question in quite some detail, that's really not the kind of thing that makes others be willing to open up about what they don't know and get better.

The Filesystem Hierarchy Standard is a very different approach to storing applications on the filesystem than to how MS-DOS/Windows does it. There's a learning curve for Windows users and they do get confused. They conceive of all files for an application residing in a single directory dedicated to that application, whereas the FHS thinks of distributing files for an application according to purpose.

I agree - I find locate to be very useful, and failing that grep/find.


A modest amount of time spent learning how to use the main features of find, with options like -o, prune, -exec, {}, along with xargs, grep, can repay itself many times over in a short period.

Of course, it presumes the user has the necessary technical bent.


In the same grain I find which and where is very useful. Additionally, find itself is a command that does its job pretty well.

For less serious searches: du -a | grep -in filename # usually works


Any code examples I can just load?


Not yet, but if there is demand I can definitely add some!



that'd be great :D


> Imagine a car where the passenger's side is fully set up to drive, and with the push of a single button, the driver can swap all control to the passenger. I'm having a hard time thinking of situations where this is better than just stopping the car.

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.


> a restaurant in in Zhangjiagang city recently started charging patrons for fresh air, after owners bought air filtration machines for the establishment and added a surcharge to people’s bills for the operation costs.

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.


Yup. And right now, people above a certain age raise an eyebrow when a domain is not a .com, or .co.uk, or .[something familiar].

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.


Doesn't holistic approach just make sense?

It's not like you learned to speak with your parents reading you the dictionary beginning with the letter A.


Its a good way to start and actually make things happen. But it's also important to get beyond that to become a strong developer.

Some do, some don't.

jQuery is a common way to learn to do front end programming. It saves a lot of time when used well. But it is important to extend the knowledge to core javascript and be able to write code when jQuery is not available (like when writing scripts to embed on different sites).


The approaches aren't exclusive either, you can start "holistic" and then learn more by going "analytic" afterwards, once you have the gist of things.


Agreed, this is my preferred way of learning.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: