no_future | 11 years ago | on: I Love Julia
no_future's comments
no_future | 11 years ago | on: I Love Julia
no_future | 11 years ago | on: I Love Julia
Everytime I see this BS I think of this:
https://www.youtube.com/watch?v=lrp57IAlh84
It's fine to say something more reasonable like "I have high hopes for this very early stage language in the future", but this kind of fanfare is the reason why stuff like Java got so big.
no_future | 11 years ago | on: Mean People Fail
no_future | 11 years ago | on: I quit: Miseries of an Uber driver
no_future | 11 years ago | on: Mean People Fail
no_future | 11 years ago | on: Mean People Fail
no_future | 11 years ago | on: Mean People Fail
From this one:
"There is also a complementary force at work: if you want to build great things, it helps to be driven by a spirit of benevolence. The startup founders who end up richest are not the ones driven by money. The ones driven by money take the big acquisition offer that nearly every successful startup gets en route. [1] The ones who keep going are driven by something else. They may not say so explicitly, but they're usually trying to improve the world. Which means people with a desire to improve the world have a natural advantage. [2]"
From "Why there aren't more Googles":
"Umair Haque wrote recently that the reason there aren't more Googles is that most startups get bought before they can change the world.
Google, despite serious interest from Microsoft and Yahoo—what must have seemed like lucrative interest at the time—didn't sell out. Google might simply have been nothing but Yahoo's or MSN's search box.
Why isn't it? Because Google had a deeply felt sense of purpose: a conviction to change the world for the better. This has a nice sound to it, but it isn't true. Google's founders were willing to sell early on. They just wanted more than acquirers were willing to pay.
It was the same with Facebook. They would have sold, but Yahoo blew it by offering too little.
Tip for acquirers: when a startup turns you down, consider raising your offer, because there's a good chance the outrageous price they want will later seem a bargain. [1]"
Though, I guess when you're that rich you can't help but think that anything that comes out of your mouth is a golden gospel, even if it is at odds with your previous statements. It sure is easy to play the whole holier-than-thou "I don't care about money I care about changing the world" game when you're already loaded.
no_future | 11 years ago | on: A Eulogy for RadioShack
no_future | 11 years ago | on: Ask HN: What's the future of Google?
no_future | 11 years ago | on: Introducing Snapcash
The actual reason it got popular, which a lot of other people in this thread have mentioned as well, is because it was much faster than MMS because the photos were low quality(and at the time I don't think Apple had introduced iMessage), and the photos didn't stick around on your phone after they'd been sent, so it was perfect for sending silly/mundane things that don't need to be preserved.
no_future | 11 years ago | on: Twitter's debt assigned 'junk' status
no_future | 11 years ago | on: Why I Walked Away From a $12M Acquisition Offer 18 Months After Our Launch
no_future | 11 years ago | on: A Question
no_future | 11 years ago | on: How we built our app in 2 weeks using Ionic Framework
C and Java can run on any platform(far more than HTML and JS which were developed to run in browsers), what lock in?
no_future | 11 years ago | on: How we built our app in 2 weeks using Ionic Framework
no_future | 11 years ago | on: How we built our app in 2 weeks using Ionic Framework
Everybody always tries to make this comparison(WELL IF YOU WANT IT TO RUN SO GOOD JUST WRITE IT IN ASSEMBLY), and it really goes to show how little they know. Programmers don't write things in assembly because today's compilers can write much better assembly than pretty much anyone. No compiler can write C better than even a mediocre programmer, which is why if you want to write something that runs very smoothly or requires high performance stuff, you write it in a C-family or JVM language. That aside, specifically your comparison makes no sense to me. Everything is assembly underneath, so I don't think anyone would say that it is useless unless they had part of their brain stem missing. HTML and JS have no place on mobile(aside from fools trying to shove them on there, hence my rant), they could be completely removed from the equation and nothing would change, and people who actually want to build good products rather than SHIP AS FAST AS POSSIBLE AT THE LOWEST COST POSSIBLE ON EVERY PLATFORM SIMULTANEOUSLY SO WE CAN MAKE THE MOST PROFIT POSSIBLE FUCK IF IT RUNS LIKE SHIT could chug along making great products, with languages designed to make great products on that platform. The developers that feel they "aren't that bad" are probably ones who haven't used anything else and don't even care to try, which is why they are trying to make them work on mobile.
no_future | 11 years ago | on: How we built our app in 2 weeks using Ionic Framework
The rich web applications that have become standard today are not what HTML and JS were designed for, hence, as I said before, the deluge of frameworks and compile-to languages that try to put bandaids over Javascripts warts. Even huge players like Google push stuff like Dart because JS is so bad.
Few people have tried to develop a replacement for C(aside from fringe projects like Rust), mainly because it's good at what it does - anything you can do with a computer. Yes, Swift is meant as an ObjC replacement, but it seems more aimed at improving programmer productivity than fixing anything wrong with ObjC.
HTML AND JS WERE NOT DEVELOPED TO RUN NATIVELY ON DEVICES! WHY WOULD YOU WANT THEM TO RUN ON DEVICES?
no_future | 11 years ago | on: How we built our app in 2 weeks using Ionic Framework
That I call traditional frontend web tech ancient and out of place today isn't even really an opinion - the deluge of Javascript/CSS frameworks, compile-to languages,and lists of best practices would suggest that something is wrong there. Web stuff is just way easier to get into so there are a huge amount of developers available, especially the types who spend more time yapping on their blogs about the latest overhyped software trend than actually writing software.
I don't know about animations and whatnot, but for games and image processing i.e. 2 enormous chunks of all mobile software, Javascript isn't replacing anything anytime soon.
I don't understand why someone would want to spend hours trying to optimize languages which weren't designed to run native software on a platform to be as effective as the ones that were when you could just write the software in the native language, to me this just seems like an exercise in futility. Even moreso considering the fact that Javascript and HTML are horribly unproductive languages, though I suppose since so many people know them well they can be more productive in them than in a language they don't know.
no_future | 11 years ago | on: Why Facebook Has Entrusted Its Future to the CEO of PayPal