Live data from Hacker News

Ask HN: What are you working on today?

news.ycombinator.com

141–150 of 314 posts

Re: Ask HN: What are you working on today?

#141
Today I am working on my strategic procrastination project - an Android game. I got bored with my regular project, a Data Deduplication file system, and decided to have some fun with learning Android development.

Re: Ask HN: What are you working on today?

#142
Trying to figure out how to get my mom out of these cash advance schemes and chronic overdrafts due to her lack of understanding of how banking works. Then reworking her finances into something manageable so she can manage to buy groceries.

Got some google maps integration going for one of my web app ideas this morning while on the train. Hoping to knock out the remaining stuff on the way home.

What am I not working on? Anything related to my day job, even though I'm at the office while I type this.

Re: Ask HN: What are you working on today?

#143
post #55

I am working on stuffing my face with burgers and chips prior to going back to the land of noodles and raw fish. Plus customer support emails, since birthdays and bridal showers don't stop just because I am on vacation.

I was figuring you'd hit the pizza up, first. :)

Re: Ask HN: What are you working on today?

#144
An Android app that turns the phone into a simple SMS gateway, allowing you to deploy SMS apps anywhere in the world the phone works (without having to install complex hardware/software, deal with service providers etc)

http://wiki.github.com/niryariv/txtgate/

Work environment: Java / Eclipse / Android (new to all of these, varying degrees of pain ;))

Re: Ask HN: What are you working on today?

#145
post #133
post #72

Earlier quoted context omitted.

There's not that much "wrong" with Silverlight. But I honestly can't find much "right" with it either. It just feels like Microsoft forked off and created this new platform that at the end of the day doesn't offer much benefit over HTML/JS/CSS. Granted, MS started Silverlight well before HTML5 started coming into form. Absolutely, C# is far more pleasant than JS and XAML is a nice alternative to HTML+CSS. All in all…

I like C# but XAML drives me nuts. Getting binding to work is like pulling teeth. I've taken to prototyping stuff in Flex because MXML binding is ridiculously simpler, although there's a bunch of C# stuff I'd love to get back...

I dislike what INotifyPropertyChanged imposes on my code. I also hate that faulty binding can't be found at compile time, but that might be expecting too much. I also dislike how binding is all or nothing, this isn't possible Text="{Binding PercentageOfFailure}%" But that also might be asking too much and even the idea that my view model should be formatting my data is a valid one.

Re: Ask HN: What are you working on today?

#149
post #85

Same project I've been working on for the better part of 3 months, unfortunately: a web based chat using GWT to replace a flash based one. The primary reasons are: we wanted to control the source code and remove dependecy on third-party products and becase we want the chat to work on iPad so flash is out. Running into tons of stumbling blocks primarily around keeping the app near realtime and stable. It's GWT on the…

I'm surprised that was your conclusion. Why do you blame HTTP if the point of failure in your case seems to be the database?

That's a good question. I suppose it's because even with Memcached taking the load off the database, we still have other issues. For example, because we're dealing with stateless connections here, it's hard to know if a client is still connected to the chat. We're polling from the client to the webservice every few seconds to 'pull' new messages and also tell the server, "Hey, I'm still alive". In order to determine if the client has left we have to monitor the polling to see if there are gaps in the poll times. Some gaps are allowed of course, because of slower connections or connection timeouts, so it gets a little tricky trying to determine if a client is still on the other end. I attribute that to HTTP, but maybe it isn't entirely to blame. If we were dealing with sockets directly, I would know the client is disconnected as soon as the connection was terminated.
Post reply on HN