HN user

wriq

212 karma
Posts2
Comments59
View on HN

By making that platform more accessible to millions of potential users. Their main source of revenue are Ad's so anything to increase a user count would seem like a good direction to go in.

"...Angular’s performance problems."

It's specific to Angular running in the browser opposed to Java running on a server. You'll certainly run into different performance bottlenecks especially in long running client side applications. What works on the JVM will be very different than what works on the browser especially across multiple vendor's JS runtimes and versions.

Not a problem that most people will have. If for some reason you do then hopefully you'll be able to monetize that popularity and hire someone who's actually really good it. ORM's are not optimal but they do let you make something quickly if you're not well versed in writing optimized queries, stored procedures, etc. For people like me dropping ORM's seem like a premature optimization.

Pencil 13 years ago

Has this happened? It does make sense to me and seems like a good opportunity for a competitor but I can't think of a case where a very popular iOS app lost out to an android alternative.

Pencil 13 years ago

It is that surprising? When you have limited dev resources it's smart to focus on the platform that would garner the most attention and profit.

There isn't a 'Best'. Getting a language & framework that will work for you is a personal thing. Just look at what's available (Rails/Play/Django/Node/etc) and implement a small but non trivial web app that has some similarities to what you're planning on building and see what you like the most. Ideally you will spend a bit of time researching on how to do something and you'll get an idea of what that language/framework's community is like.

Or just build it in PHP using Cake since if that's what you know the best you'll likely get it done faster. That way you can focus on the product instead of the stack, which in my opinion is more important.

Possibly, but like most technology there's is a set compromises you're willing to make. Rails and Django seem to be focused on getting something up and running ASAP and then dealing with whatever scaling issues you're going to have when you know exactly what they're going to be. Face it, a good amount of webapps out there won't need to be sharded. 37Signals just threw hardware at basecamp for a while (they still do?). Instagram made a few tweaks to django once they started growing rapidly, same with Disqus and i'm going to assume Pinterest did something similar as well. I would focus on the product rather than how to scale it in the early on. Once you hit the point of "How am I going to deliver this product to a group a users an order of magnitude high than I am right now" you'll hopefully have good test coverage and be able to make the right choice among sharding/read-slaves/better caching with the metrics you're able to collect.

"It’s just the slightly awkward first steps of a serious move by Nokia to differentiate itself."

This seems like the same old cell phone industry for me. Several years ago, camera megapixels were one of the most standout features on cell phones for consumers. It was simple enough to boost the number ever year and have a buyer go "Well 4 > 2, so this phone must be better" I'm not so sure if thats a valid strategy in this current market.

I understand certain pro users being skeptical on the whole 'Back to Mac' iOS-ification of OSX, me included but i'm already loving the Lion terminal. Nice implementation of full screen, 256 colors , no distractions and just one swipe away from all the 'consumer' things I want to do. There's a lot of fluff in this release, but the new Terminal alone made the $30 upgrade worth it for me. As for the Mac Pro disappearing, I couldn't care less. I would think this would impact high res image/video guys more since that seems like the Pro's target market. Developers seem fine on laptops with an external display.

I haven't heard of any stability or reliability issues regarding Apple's choice of storage in Air's, MacBook Pro's (w/ SSD), iPads, iPhones or any Flash-storage based product. A single blog post with it's extremely limited scoped is a weak reason to write off an entire group of storage tech.

You should adjust your belief to fit the available data, don't adjust the data to fit your belief.

I would normally agree, but in my opinion, surveys fall into the "Lies, damned lies, and statistics" category. They hold the same value as apache-bench numbers that are posted every time a new webstack appears.

Existing expertise

If the goal is to get to a minimum viable product quickly (like most startups) then existing knowledge is a pretty good reason to go with a certain stack. He even mentions having the main algorithm already implemented in C# so at that point it's pretty much no contest. He can always go the route similar to StackExchange in using Linux & Open Source on utility servers (Caching/Load Balancing) and keeping the MS-centric App/Database server.

It's a shame that it all seems to be up to one person and what he will allow considering how often the shootout is referenced in discussions. I wonder if Mike Pall's experience was similar when he posted the Lua/LuaJIT versions.

If a programmer tells you to use vim or emacs, tell them no. These editors are for when you are a better programmer. All you need right now is an editor that lets you put text into a file.

From Zed's LPTHW. While Vim/MacVIM is my editor of choice, if someone is just getting started and using RoR - TextMate or any easy to start with non-modal editor seems like the right choice. Trying to learn vim while learning a new language/framework at the same time could get frustrating. TextMate is still very popular, easy to start with, and last I checked (admittedly a very long time ago) the editor used in Railscasts.