markmm

Rust is a terrible language. It has an identity crisis. Thinks it's a high level but also system level language. You cant be both. The unix philosophy always wins. Do one thing well. C is the perfect system lang and Java/C#/Lisp/Python etc are the cream of high level langs.

I found watching this at 1.5x speed was good as James ums a lot.

This is like Nokia sticking to keyboard in their phones. Worst decision ever made. Their interface will be out of date 5 mins after its made with no way of updating

Using a terminal on a mobile is a horrible experience. Smart phone UI's are the antithesis of CLI

Git written in Ruby, it's a no from me.

*nix pipes are part of POSIX and the OS/Shell implements them, if the app takes input and produces output it can be a component of a pipeline.

In short, the Curl developers couldn't remove pipes without crippling the app.

He wouldn't have released it, he will be spinning in his grave right now. They need to ditch Cook and get someone with a pair of balls.

I bet they wish he could come back, Maps/Siri/lack of innovation on new products.

Jobs was a good business man and decent presenter, to compare him to John Lennon is utterly inappropriate.

How about worrying about both equally, if you still don't get it see Diaspora, great idea and lots of buzz, but implementation was shit and it was DOA.

This is something newbies repeat to justify their choice of a piss poor implementation. Sure with 10 users hitting your Rails app it might perform the same as Nginx with a custom C handler talking to a database written in C, but increase the load and soon your handing Amazon thousands a month on ec2 nodes while I am still on a small Linode. The funny thing is because of code gen and experience I can probably write my app faster than you dicking around with framework after framework

I can turn around a project in a few months easily, and all my _running_ software will be C or C++. The secret is leverage and code generation (Where I will use a scripting language)

Wow!! your comment encapsulates the thinking of every wannabe startup loser that ends up smoking crack on some beach in San Francisco"

Will making it faster increase the chances of more people using it? Also this attitude of building shit products (Yes software is a product) because..well the chances are it will fail.. is precisely why so many startups fail. This is why you get one crapola startup after another........

"Show HN: Crap.ly -- we built this in 3 weeks using Ruby, it will scale up to 20 users before craping out, its a twitter scraper that connects to app.net and diaspora showing how much Money your Kick-starter project has made and includes quotes from Paul Graham about how to build a successful startup, because he has built so many"

Imagine Linus had built Linux using fucking node.js

Why are they moving from Ruby if it's just "string manipulation and database access"?

The problem is folks, as soon as you get a large number of users every compromise you made by using a toy language or database is magnified 1000 times. Google didn't implement in some scripting language to get to the market a few months early.

My experience is a software always takes much longer than expected, if your startup will fail if you run a few months over then you may as well go and place all your money on black at the casino. You need to get into a position were you can run 1 year over and still survive i.e. have other income while working on your startup.

1 server running Nginx with modules + Postgresql == 100 servers running Ruby/Node/Some scripting shit slow language talking to some NoSql crap.

I would spend a little extra time upfront and save many many expensive rewrites latter on. Use C from the start, you won't need to rewrite just scale with hardware.

This argument that using Ruby (or any language that makes programming easy but runs like treacle) to get something out the door a few months earlier is bullshit, I would rather release something a few months later that I didn't have to totally rewrite down the line 10 times.

$36 for a twitter clone with < 1% of the users, where do I sign up!!

Can somebody help me, I only have 1% of battery left, I was using IOS6 maps to get to my local mall but I am now in what looks like Antarctica? Im very cold and car hasn't got much gas left, I hope s

It annoys me that folks with a poverty of imagination are creating clones of existing apps that have already solved the problem. Another Twitter but open or Facebook with proper privacy..etc. Fail!.

One of the main reasons I hear people advocating MongoDB is it's ease of horizontal scaling, via replication and auto sharding. I wonder how many projects have such large data sets that they really require sharding of their data?

I understand having another node or two for fail over but I reckon with the spec of the largest offerings from AWS or Linode most people will never need to worry about this and can manage everything on one Postgres or MySQL db. Why complicate things before you have to.

/dev/null is the most scalable system though, just fire up a node and it's there.

"tortious interference." sounds like a disease a radio gets.... stolen from The Insider

How is this different from linked in, other than they have millions of users? Seems like another Facebook for XXXXX type idea.

Wait a few weeks, for his followup article entitled "Why I came back to Python....two words...mature libraries"

has the width changed? or just the height? If it's just eh height most apps will work as the view will just stretch.

Lucky she's married to you then eh?

Sorry couldn't resist

I am not asking it to have anything, the article is insulating that GO is the new go to language, it is not because it doesn't have mature and comprehensive libraries. When I make a decision to use a particular language I don't wan't to handicap myself, you need as much edge as possible. In 10 years maybe Go will have a vast array of mature libs but until then I shall be choosing Python and C.

It depends, if your app is just a dumb UI that calls out to services then all the logic etc should be in the server, the UI code should just be displaying and a bit of caching.

Once you have built it in one framework it will be much faster porting it to the others. I know it requires 3 updates when you add a new feature but it's not a major pain and you get native apps running very fast.

It might be nice for a quick script or standalone program, but most decent size software projects need plenty of mature libraries to be of much use. Python and C have decades head start here.