My point is that Javascript + Node would make the basis for a nice bash replacement.
274 karma · joined October 3, 2008
My point is that Javascript + Node would make the basis for a nice bash replacement.
node.js is great for all those perl-y 1 to 10 liners. It should be the shell.
New browser feature - open this site in a temp VM.
Couple that with basic workflow and 'publish to site' and you have a product with very wide appeal and usefulness.
Wouldn't it be better to have the freedom to implement your own version of what the ultimate Reader is, especially in newer tech [ websockets, node.js, realtime updates, drag to rearrange widgets .. whatever ]
Id love someone to make a nice reader [and a nice mail groups] web app, Id enjoy working on these myself. It must be more efficient to build these things outside of Google, as a startup.
An RSS reader with nice UI, realtime update, location sensitivity, smart filters, and unobtrusive social features .. you had me at RSS :]
My intuition is that 'Layers/Layars' are a good abstraction for developers.. but I think maybe simple tag / search might be a better way to filter those things I want to be notified about as I walk around?
AR is cool, but I wonder if this coolness actually gets in the way.
Id like to set some interest filters and then walk around and get push notifications on my mobile home screen. Eg: set 'tell me about' = 'clothing discounts', 'art deco buildings', '2nd hand record shops' and 'friends with status Im-up-for-a-coffee'.
I think we need to take that step so that the technology kind of disappears into the background - location isn't there yet.
I dont think it needs a HUD VR helmet to work - just look at how crappy and successful the keyboard is.. so, yeah, simple short text notifications as you walk around would really make this meld into the daily routine.
great idea, thanks. its a bit of work, but doable.
By 'read-only' I mean its not easy for people to supply location information thats current. I put into Lokenote app an expiry date tumbler - eg. Street party for a few hours, blocked drain for a few days, building site for a few weeks.
Because of overhead at the moment, youd probably only enter location information that is going to be there for a long time.. but if it were easier to share that, wed see a more dynamic and relevant picture over smaller time scales.
Wikipedia, etc, have made an effort to standardise so that wiki articles can be tagged to a location, but I think theres a whole mass of less formal information thats really useful thats not being captured or used - ants would leave pheremones to signal other ants, we currently leave paper notes on lampposts, there should be a better way.
There are things local people know about, which still diffuse by word of mouth - and I still see paper notices posted on lamp-posts and at supermarket boards. This is why I did an experiment and built lokenote.com
I havent nailed it with lokenote, but it hints theres something there... Im aware this is a first, imperfect approximation of the kind of tool that will enable people to annotate locations. Sometimes you need to build these experiments to see what works or doesn't.
I dont think the storing/retrieving of geo-data is that hard a problem, you can roll your own nested squares approach, or reuse whats there now, eg. Mongo 2d indexes.
Rather, I think the problem is making a nice way to integrate the location dimension into our tools/web apps more seamlessly. eg. a dating chat app might just favour partners close to your location without being told what postcodes to look in. I see this as a 'too many knobs' type problem ( a bit like those search forms you see that have options for 10 different dimensions to filter on, which are better replaced by a single text search field, with hidden smarts. )
So how to bring location to the people, so its useful, effective, un-intrusive and read-write ? I dont think that question has been answered.
[edit readability]
I created Lokenote.com as I saw people posting adverts on lampposts, but I think that was too vague an idea, so maybe my first go at Lokenote was too generic [ pinning a note to the map ].
I did also build it for a guy who delivers packages all day and wants to share notes with other drivers on how to get to teh right entrance at a building or property - so I need to get that guy to use my site and make it useful for his realworld problem.
Reality has this way of being unpredictable... which makes it interesting, right?
Using mongo, node.js for real work, I find this a really practical environment, and I often write little 'perl' {java}scripts for text/data wrangling.
I wrote a little utility that has a jsonpath-like syntax to descend down into json docs in mongo from the command line, use that a lot.
I actually wrote my own KeyVal over Postgres in js. It worked fairly well, but got better perf with MongoDB which I found quite sane and easy to use.
This is a trade agreement!
I assume it has no provisions for 'extraordinary rendition' of mp3 downloaders ?
I use it to serve up several hosts on the same ip, or split sections of my url namespace into several node.js servers.
Maybe look at NodeJitsu blog as the articles seem readable, and those guys seem to use node heavily for running their hosting platform.
I played with Javascript sine animations as a way of introduce the idea of sine function in some intuitive way.
Eg Two Rotating Circles - http://quantblog.wordpress.com/2011/10/05/adding-circles-jav...
I think Javascript hacking in a web page is todays equivalent to hacking GW-Basic, Turbo Pascal or A86 assembler for my generation.
I like the idea of a framework.. but the Todo List app just seems overweight.
I personally dont want to see a Rails style or heavy iOS/Cocoa style framework for web.
What I like about Javascript is it has enough lisp that I can write surprisingly small amounts of code, and the code reads like the way I think about the problem. Also the async events are magic in terms of decoupling components [ reducing cross dependencies ].
I content that concise frameworks are possible in Javascript [and lisp], whereas they are not possible in C/Java/C++/ObjectiveC.
I use YUI mainly for table/grid widget - I preferred API design in YUI3 but found various table UI bugs when I 'mixed in' sortable and resize columns etc... This meant I had to go back to YUI2. I remember this experience as amorphic 'yui pain'.
Hopefully in current/3.4 the DataGrid is now fixed with official plugins working in unison?
Some thoughts :
YUI really needs one core person with an iron fist and a clear goal driving it forward. It feels like it has the guts of something incredibly useful, but is being pulled in too many directions.
In a large company its tempting to think ' we better keep that for Sandras or Simons team' .. dont do that... think like a startup and throw bad shit away :]
I can live with the verboseness if the Widgets are really nice - and thats a way to get HTML5/js/web-startup developers thinking about Yahoo again.
Some ideas -
Be ambitious upstarts, dont ask permission to kickass.
Give the team autonomy / ie. a virtual startup within Yahoo. Maybe split off a team or an Open Source startup ?
Demand all Yahoo use latest YUI by religious edict from on high [ Doug ? ]
Consider mobile?
Drop the legacy crud, get rid of any fallbacks, burn the bridges!
One Unified example, or a framework / app-designer as the canonical YUI demo
Google need to win the 'make patents irrelevant' battle not the 'my bullshit patent portfolio is larger than your bullshit patent portfolio' battle.
Mobile and Web are the same thing, its just we have a legacy crud that needs to be factored away.
Ideally my phone runs linux with a GPU accelerated HTML5 UI, and has a javascript programming model with open API to get to hardware features. We are nearly there.
I believe Objective-C and Java languages are ultimately unsuited to phone app development. [ because phone app development _is_ web app development ]
This would be a bold, unifying, visionary strategy. You already have this in place, it just needs to be amplified - doing so could be the perfect strategy to win the patent game by making the patent game largely irrelevant.
Hang in there.
It may help to think that a) these people are broken in some profound way, possibly from some early abuse b) this may not be directed at you personally, you did not deserve this, and this was not your fault
I do think the AirBnB business model needs to take into account some kind of insurance cover, or set aside some percentage of funds to apply to help in the edge cases like this - so that some of the practicalities are taken care of [ such as cleaning the apartment, temporary accommodation ] giving the victim some breathing space to heal from this.
For example, we could apply machine learning / data mining to categorise patents so that we can say patent N, M and L are 95% equivalent in some well defined sense.
ie. we could fight back with firm data which ridicules the Patent system into revamp or obsolescence.
I'm endlessly surprised to see how rare this is.
M$ involved in any way with Joyent and/or Node.js = really bad idea
This means I can reuse the same REST style data 'provider' from within a Javascript web UI and within an iOS or Android client app.
So theres quite a few reasons why using JSON simplifies things for me - particularly I notice that there is a whole layer or ORM style boilerplate code that I dont need now [ whether its SQLLite <-> Object or XML <--> Object ].
I actually like the SQL Lite implementation!
So I meant that instead of using SQLLite on mobile devices, pc based local fat clients or in the browser... I now use JSON now whereas I might have used SQLLite before [ I also use JSON where I might have used XML or windows config files etc ]
I did not intend to say JSON is replacing MySQL / PostgreSQL.