215 karma · joined February 28, 2009
[ my public key: https://keybase.io/angerman; my proof: https://keybase.io/angerman/sigs/7EDoTKOM0-EjREpBa5LSySUAbN4sM3Z1V6tglS-8G-Y ]
The underlying idea of generating your images "programmatically" is not a bad one to start but performance wise, if the image (View) is going to be static, rendering into a bitmap and using that subsequently is the more performant solution.
Maybe the tool we are looking for is not one that generates UIViews but let's us just get the images correctly name and at the right resolutions with a click? Like automatic slicing and exporting at predefined resolutions with predefined naming schemes. I just think this would better be done off the device.
For interactive views (drag, move, ...), where redrawing is necessary, this could be a valuable tool -- if it can do that.
I'm not saying you can't get the job done in a mainstream language; but I postulate that the mindset and attitude towards code of a good Haskell or Scala programmer is vastly different from your less expensive PHP or Java programmers. Some want to push the limits of what's technologically possible and others just want their paycheck by the end of the month; they are in both camps; are they evenly distributed?
My calculation went bottom up: say a low baseline salary of 25eur/h + 50% freelance cost = 37.5eur/h + ~20% tax = ~45eur/h.
I guess that the company would calculate 70eur/h to 90eur/h for projects (e.g. 560-720eur/manday).
If twitter has (some of) the best ruby developer (mentioned somewhere at the end of the video), why have they neglected JRuby? Why is it no option? For legacy code with native extensions this makes sense. But is jruby slower, more memory hungry on the JVM then scala or clojure? I always though that JRuby was one of the more performant languages on the JVM?
Apart from that it was an interesting talk.
Found the solution: This happens if you have "Macintosh HD" listed under the privacy tab of Spotlight's System Preferences.
If anyone has similar issues, or a fix, that would truly be great!
1.7GHz i5 -> 1.8GHz i7
No choice of flash no choice of ram :/ I love my current air. It's a really nice piece of engineering but even 4GB of ram are sometimes full. With an more powerful CPU more RAM would be a nice choice...
TB, Backlit KB and a faster CPU are very nice though.
--
[1]: http://corner.squareup.com/2011/07/ios-integration-testing.h...
What we did was this: - picked a somewhat hight price point ($2) This seemed to use like the sweetspot, with what we could live and what we would expect an honest buyer to pay. (who knows?!)
- we wrote to the canonical forum, where we expected most of the potential users. That resulted in an initial rush (two days after writing to the forum), but it wasn't much at all.
- the domain iebtapp.com was registered prior to publishing, but contained nothing more then a simple "Something's coming this december" string. Watching the server logs, there seemed to be some who were trying to figure out where the link from the app pointed.
- after some time, we wrote the current, very limited text on iebtapp.com. Not even with images. That seems to have resulted in a minor increase in sales.
- with some text on the website, we thought it was time to do some advertisement, and went with Google Ads. This too seems to have resulted in a minor increase in sales.
And here's what we plan to do: - add Appirater to the App. We have only a very few reviews, and they are not enough to get any star rating on the AppStore. Maybe this helps, who knows. I will closely watch this.
Personal conclusion: iOS development is really /a lot/ of fun. But I think we need to change two things: - More marketing. But not all at once; results should be measurable. - Niche markets, that are this tiny, can be a very high risk game. (Especially if someone else, writes to the forum that he's going to release another iPhone app and lets people sign up for the beta :-))
-- [1]: see iebtapp.com
These days, you find PHP almost everywhere. And how do you get to PHP? Let's assume we are in collage and want to write that next big website that's surely going to rule them all.
Now, we don't really know that much about all this "tech" stuff. But hey, I can hit "show source" in the browser. This must be easy. After a few baby steps with a WYSIWY(WishYoud)G tool, you decide to learn /some/ HTML for good. Once you figure that HTML alone can't do a lot, there's a somewhat native path to PHP.
You keep on reading tutorials written by others, who know as much as you or a little more. You are still on the cheap side, and need to keep tight on your money for that next big website you are going to write.
And the more you read the more enlightened you feel. Wow! I can actually do that and my dead cheap webhost offers PHP as well. Life is good.
Because you don't lack any minimal intelligence, you figure out how to write your next (big) website. You probably didn't succeed in writing the next FaceBook, but hey, you are now /one/ of the /web guys/. You probably think what you are doing is real fun.
There are then two paths you can take: - A: stick with PHP and feel enlightened all the way, when ever you learn some new trick, or - B: wonder if PHP is the only true real thing. You don't know C or some other "ancient" language, so you are still a little afraid. Perl seems to look a lot like PHP but it's syntax is confusing and no one of your friends on the forums you are frequenting is using it anyway. Then there is Python or Ruby. Wow those look strange. No curly braces for function bodies. Why do people here talk about templating? What's this about? Do I need that? PHP was so easy... Anyway, you are still curious and learn about this "other" way of writing webapps (that's what we are still primarily concerned with). Once you start to figure out that variables do /not/ have to start with $ to be valid, you wonder what else PHP might have hid from your novice learning? There is a lot more. Not necessarily PHP's fault. Just the lockin in that PHP mindset.
----
The basic problem with PHP (to me) is that I've seen it to be more a motel on the way to enlightenment. Some just find it too comforting to move on. Others, once they've passed it, rarely(ever?) come back unless someone else tells (forces) them to do so.
I would even say you could go as far as saying it one end of the spectrum. Where you have frontend web apps (html/js/css) on a variety of platforms[1] on the one end and the big corporate backed languages and frameworks on the other end.
[1]: This can be a real pita. Though it's being mitigated more and more by adding compatibility layers on top (jQuery et al).
$ which xetex
/usr/local/texlive/2009/bin/universal-darwin/xetex
$ xetex
This is XeTeX, Version 3.1415926-2.2-0.9995.2 (TeX Live 2009)
**