We are so used to providing statistics and being empirical but we need some humanity as well.
420 karma · joined February 6, 2009
bbalban@b-labs.com
We are so used to providing statistics and being empirical but we need some humanity as well.
Also chrome has been getting slightly slower than its initial releases. I hope it won't slow down further.
Also what is your future value proposition? Is it only the ability to link emails to linked in?
You can create slides and directly upload to slideshare or get a link to embed on your site. Feel free to share your experiences with others.
Next, I gotta figure out how to create actual compelling videos.
Even facebook is one big application based on messy technology. They can cope with it only because they have lots of Ms.
You can't fix it by extending crippled java script whose name has a misconception to begin with.
Let me give you an example: In 70s operating systems were built as ad-hoc services on top of the hardware. Functionality was implemented in ad-hoc fashion, interfacing to each other in afterthought, clunky ways. Then came Unix, and eventually evolved the design by bundling the filesystem, disk IO and process memory management in one implementation. We need someone clever to do the same to web and relieve us from this mess.
"So, if you will indulge my claim that backwards compatibility is hard (even absent the private API issue) it is pretty easy to see why supporting other runtimes is ceding a lot of control to a 3rd party. Imagine if 10% of the apps on iPhone came from Flash. If that was the case, then ensuring Flash didn’t break release to release would be a big deal, much bigger than any other compatibility issues. Since Apple doesn’t have access to Flash CS5’s runtime library code or compiler frontend, they might be put in a position where they would need to coordinate with Adobe to resolve those issues. Shipping a new release where Apple breaks any specific application, even a top seller, is not an issue if the release is compelling, most apps work, and Apple has the option of working with the vendor to help them fix their app. Shipping a release where they break a large percentage of apps is not generally an option. Letting any of these secondary runtimes develop a significant base of applications in the store risks putting Apple in a position where the company that controls that runtime can cause delays in Apple’s release schedule, or worse, demand specific engineering decisions from Apple, under the threat of withholding the information necessary to keep their runtime working."
A small business/startup website solution that is compact, editable, live and clearly describes the product and company.
No, its not vague or different every time. It should:
1) Clearly describe the product
2) Clearly describe the company and what it does.
3) Does not look mediocre. (E.g. those static html sites based on those usual narrow rectangular templates with links at the side or top).
4) Easily changeable. (i.e. updates on parts of it without much html tweaking)
Extra:
5) An easy-to-update company blog, ability to upload multimedia content such as embed product videos. A startup is changing quick, and so should the website.
Do the first 4, I'll buy it. Then add 5.
Examples:
I have researched and both have spent considerable amount of time building theirs, and they have all 5. Why not do it off the shelf?
Tcl syntax is ugly, tk GUI's are ugly and look old.
Also, Python is the winner for me because it's syntax resembles C but is a lot easier to write.
Partly the problem is that linker people are unaware that the new generation of software engineers have no knowledge of linkers. I hope he goes one step further and makes a book out of it.