Ask HN: What are you working on today?
141–150 of 314 posts
Re: Ask HN: What are you working on today?
#142Got 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?
#143I 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.
Re: Ask HN: What are you working on today?
#144http://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?
#145Earlier 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...
Re: Ask HN: What are you working on today?
#146Re: Ask HN: What are you working on today?
#147Re: Ask HN: What are you working on today?
#148Re: Ask HN: What are you working on today?
#149Same 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?