jakejake

Providing an option to install with npm simply makes it more convenient for those devs who already use it - which surely is not an insignificant number. Nothing is requiring you to work that way or stopping you from downloading the files manually.

I just started to use npm (and indeed package managers in general) for my work recently and it's opened my eyes. It makes sense to me that this will be the preferred way of working for every dev/designer. Just as we mostly all use git now. It's hard to imagine that time when we just shared files via FTP and didnt use version control. I'd encourage anybody like me who was resistant, or working on a large code base that doesn't use those tools - give it a fair try on a side project.

You're right, typo in the title!

I personally find it odd to create every component as a jquery plugin. To me, it makes more sense to write a plugin only when you're extending jquery core functionality itself in some way.

As far as "extending" goes though, it's not always clear. Is a date picker extending jquery's core? I personally think not, but there has evolved an expectation that every web component must be initialized like so:

$('#container').doSomething();

So I suppose a lot of people do it that way just to have a familiar look to their API, or even just to show up in listing as a jquery plugin.

I agree about the quality of those few pitches I watched. But if you notice the red vs green monetary amount next to each video - all of them except one were rejected. So you can skip and watch only the green ones, I'd assume, to see the decent pitches.

I rather thought the videos were examples of what not to do, along with constructive criticism explaining why.

I think that most wars are are just based on the wealthy and powerful retaining or increasing their wealth and power. Average citizens generally don't have problems with each other. Excepting whatever propaganda we've been fed.

I found the videos really interesting to watch because we see lots of polished pitches here on HN, but here we're seeing everything. These are mostly just going to a VC with a hand out - asking for money. But, that's what pitching a company is. I think a lot of people who haven't done it imagine a slick deck presentation in a boardroom. The reality is that you have to be able to sit down in a coffee shop and sell your idea to someone who has more money than you.

As far as the terms - I didn't look it over closely to see if it's a fair or predatory deal. Anybody know if it's a fair deal?

The word "trained" does seem dubious as if the bees were taught to obey commands!

More likely the bees were "persuaded" to use cannabis by either proximity of the plants and/or treating the plants in some way to attract the bees.

Same here. Not having multiple projects open is a total deal breaker for us. We have a couple of shared libs that go with our projects and not being able to have them all open together is painful.

I can't seem to get into the game of fully automated deployments to production. It definitely interests me but a few things always hold me back.

The first issue is that I've probably set up 10 or 15 app development and deployment "systems" if you will. I've found that it's very beneficial to automate the simple stuff but it quickly reaches a point of diminishing returns. A super-custom system always works great for a while until some big change or library upgrade or refactor or whatever comes down the pipe. Then we spend a ton of time resetting up everything. We have to keep the build system components up to date so it doesn't turn into an ancient mystery box. Sometimes an upgrade breaks the whole thing and then we're on stack exchange all day debugging a parser library or some other thing that we don't care about. Basically spending hours and days and weeks on the build system so we can have that sweet one-click (or fully automated) deploy.

The other thing is that we release frequently but we tend to double check everything before it goes to production. Our staging server is auto-deployed except DB changes which we do manually. Right now it's about 2-3 clicks for us to deploy to production and it works fine. We still do DB changes manually though. It takes a minute or two to deploy. I feel like the process encourages that final check that everything is cool.

I guess I'm nervous to set up something that deploys to production simply by adding a tag to a slack message or the git commit message. Should I get over myself? If I change my thinking is it possible that deployment to prod could be a non-event?

That is true, and to make matters worse it's probably near impossible to figure the right amount out when you've just started the company. You don't always know how people will wind up using your app.

This is possibly the most interesting fumblebrag that I've read in a while. It has a few issues which have been hot on HN recently as well as some age-old problems.

The dependence on third-party services like maps, messaging, flight data, etc. is an interesting topic. Services that help you to get up and running in a couple of clicks are awesome at first. But they can become a burden when your usage goes up beyond a trivial amount. This is a great lesson about thinking ahead when choosing third-party providers - either by passing the expense along to your customers or having a roadmap to phase them out when you hit a certain volume.

Another point is the one-time pricing which, in my mind, is somewhat of a ponzi scheme for a business model. I always cringe a little when I see a cool new app with a "one time payment for life!" pricing. You just can't support customers forever with a single lifetime payment unless you are earning revenue in some other way (i.e. advertising). It's easy to think that you'll continue to gain more customers forever, but you're setting yourself up to be crushed by your own success. Unless you're planning on regularly releasing new apps and/or in-app purchases for your customers to purchase, it's not a long-term business model.

Sorry to see the Just Landed go - it looked like a cool app. I think there is a lot to learn from this post so thanks to the author for posting.

That's pretty much exactly what my perception is. Add to that, you're account gets shut down and/or frozen without warning and only a kafka-esque system to find out why you were shut down.

It makes sense that isn't true but I have to admit it is what comes to mind.

I's say it would be more like comparing a male who rapes a female with a male who watches that rape.

Regardless, though, the term "pedophile" by definition is someone who is sexually attracted to children. There is no distinction about whether or not they actually committed a sexual act with a child. A person who commits a sexual act with a child is by definition a pedophile and a rapist, since children cannot legally give sexual consent.

In other words... Art.

I feel that people who watch child porn and find it appealing rather than repulsive - qualifies you as a pedophile in my book. It's certainly a lesser crime than actual sexual assault of a child. But watching sexual assault for enjoyment and trading in these videos is still a crime. The term pedophile fits just fine as far as I'm concerned.

A plugin that allowed you to whitelist as you go would probably be pretty usable after a few days of training.

Don't forget the semi-colon on the end of line 10 to remove the line break and spread the message across the whole screen!

Perhaps these teen sites were a drop in the bucket and not worth the hassle of any association with diet pills? But to just throw away a loyal audience of millions of people who are proving to be profitable customers as well - seems careless.

From the sound of it these kids probably would have gotten into compliance immediately with a warning. You'd think it would be worth tumblr's time. Apparently not though.

Well like many people, this guy is pointing out a true and real problem. SF is a world class city but there are an unusually high number of drug addicts and homeless people walking the streets. But the author lacks any understanding of the root causes and, comically doesn't see his own role in the problem.

None of us like seeing homeless people but the problem is not that they are unsightly or annoying - the problem is why are they homeless to begin with and what is such a wealthy city doing to help? If you're only thinking of your own selfish needs then it makes sense to just "sweep up" people on the streets and send them somewhere out of site. Perhaps a good whack on the head with a night stick will dissuade them from returning. If you have no heart or compassion then it probably seems like a great idea. But if you have any sense at all then perhaps you can try to use some of your privilege to find real solutions to homelessness and perhaps lend a hand rather than try to swat them away.

I really don't know of any specific cases either, but it does seem to be a fear that is perpetuated regardless.

Regardless it's just seems like there's so many opportunities to create legal trouble by giving a reason, and almost no reason against saying nothing.

Ordinarily I'd agree with you. Except the tradeoff of having Google's other contributions to the main branch is probably worth it for a little bit of code that isn't harming anyone else.

It's perhaps not fair, but just a reality that a company like Google has a lot to offer so they can sometimes get special treatment.

I think the only way really to make it work is by having a private "beta" invites or the placeholder or something so that you can build some excitement and get people signed up. Because if your app requires a lot of data (i.e. people) before it becomes useful, then you can't really turn it on with like 5 users!

It is a very tough problem. I might look to other sites and try to see what they have done. Ello for example is one recent site. Perhaps there is a way to partner with an existing service. You will have to get creative to get past the chicken/egg problem. I wish you success!

He's one of the original creators of one of the first web browsers - arguably one of the early architects of the web. And since has parlayed his fortune to become one of the top investors in silicon Valley.

And now, apparently a self-righteous hypocrite who is arguing against net neutrality because it suits his financial interests in Facebook.

You can create a placeholder site that explains your idea and see if you can get people to sign up to be on your announcement and/or beta list.

That will also tell you if your idea is any good - if you can convince people to sign up.

Cool!

Did you ever release yours on the app store? I'm struggling with electron packaging for the Apple app store and hoping to find a kindred soul to help get through it!

Sometimes I really feel like I'm falling behind the times because I don't use a lot of third party services or platforms for my company's apps. I feel like I stick with simple tools at the expense of not getting any "good stuff" for free.

When something like this shutdown occurs though it makes me glad that I can just spin up a plain old server or two and put together whatever services that I need. I can't tell if I'm a dinosaur or a maverick!

That sums up my experience pretty well. I tried installing it for a couple of sites and seemed really cool at first. But just weird things started to happen with styles and such and it seemed like it was going to take a lot of research and debugging to get everything dialed in. Not really having time to do that, I disabled it and put it on the list for later. I wouldn't call it a "negative" experience necessarily, just not the easy win that I was hoping for.

I do think it would be awesome for some legacy code if it was critical to get the performance tuned up and you have a day or so to get everything configured.

The fact that the pricing plans were taken as-is from an HTML template (that had nothing to do with hosting) is a pretty good sign that the project is a bit rough around the edges.

A good lesson indeed, if you pretend to be serious and do a decent job, people are quite likely to take you seriously.