Live data from Hacker News

Ask HN: What are the best technologies you've worked with this year?

news.ycombinator.com

31–40 of 155 posts

Re: Ask HN: What are the best technologies you've worked with this year?

#31
post #11

2010 was, for me, the year of JS-related technologies. (I'm actually rather disappointed I haven't had more time to check out Clojure and to use Haskell and Scala more--I was doing quite a lot of front-end web stuff.) 1. Socket.IO ( http://socket.io/ ) It lets you use websockets and automatically fall back to flash sockets, long polling, or several other real-time communication methods if websockets aren't supported…

Thanks for #1, never heard of websockets before.

Re: Ask HN: What are the best technologies you've worked with this year?

#32
post #17
post #15

Twilio. Ringing phones is pure magic, and provides so many disruptive opportunities it is staggering.

Sure. You can disrupt someone on the toilet, at the dinner table, in bed, etc, etc. Very disruptive indeed.

or... while they're using their phone as a method of programmatic notification?

Re: Ask HN: What are the best technologies you've worked with this year?

#33
I continued to work with F#, deploying a couple of small apps.

The really cool part came when I realized that with F# I was programming at the language level -- that I could effectively and easily write my own languages. So I decided I would like rails-like entities, where the entity reads the structure of the table and then conforms itself to whatever is in the table.

Couple hundreds of lines of code later, and presto chango, I could simply say "give me a list of customers" and point it to the table and I had a list of customers. This totally disconnected the database data structure from the code. Add a new field in the database and there was nothing to change in code. Or add a new field in the type and have it percolate out to the database. Change database providers and it was only a few function changes. Very cool. The kind of simple fix Microsoft should have done with data access instead of writing ODBC/ADO/OleDb//EF/etc

Then I had a blast with mailboxes, er monads, agents, and threads. Ended up writing a small app that was purely functional and all ran in the background. It was so automatic, at first I couldn't figure out how to start the dang thing!

This led to a venture into MPI and other technologies which has just begun. I'm also trying to wrap up my language work with a full DSL sometime soon (if I have a project that needs it). Looking forward to parsing and setting up trees and walking them. I also broke out of windows and started working in a linux environment using Mono, Apache, and MySQL.

Incredibly fun stuff. Looking back, I really had a blast this past year. Next year should be even better.

Re: Ask HN: What are the best technologies you've worked with this year?

#36
The iPad has changed everything. It's an entirely new type of computer that turned out to be substantially better than anyone imagined. Watch a 5-year-old use an iPad for the first time and you will immediately see and understand why this is a major paradigm shift. It's the first "socially acceptable" computer -- at Christmas I can pull out my iPad, plop it down at the dinner table and share pictures with the family, and it's not at all considered rude.

Re: Ask HN: What are the best technologies you've worked with this year?

#40
post #11

2010 was, for me, the year of JS-related technologies. (I'm actually rather disappointed I haven't had more time to check out Clojure and to use Haskell and Scala more--I was doing quite a lot of front-end web stuff.) 1. Socket.IO ( http://socket.io/ ) It lets you use websockets and automatically fall back to flash sockets, long polling, or several other real-time communication methods if websockets aren't supported…

I'm looking forward to seeing someone combine Backbone.js with Websocket-based persistence. It's a bit out of scope for DocumentCloud to tackle, but the building blocks are there.

One client makes a change to a model -> changes are synced to the server -> other clients that currently reference that model have its attributes updated -> all the UI that displays the model is automatically re-rendered.

It's not critical for most applications, but is a really nice, nice-to-have for any JS app that displays the same editable data to more than one user at a time. Built-in conflict resolution mechanism for bonus points.

Post reply on HN