Hacker News new | past | comments | ask | show | jobs | submit | more ghenne's comments login

The term Hypertext was coined by Ted Nelson, probably 1965. Check out his book Computer Lib/Dream Machines. He envisioneers the internet quite well.


Coined '63, published '65 according to wikipedia http://en.wikipedia.org/wiki/Ted_Nelson

I'm old enough to have read Computer Lib ('74) when it came out, I have a first edition which I imported into the UK by sending some sort of international money order to a US bookshop. For some reason I also have a second edition.


Computer Lib/Dream Machines is amazing. It made me appreciate _why even more, actually...


blinking.


Do browsers still implement <marquee>?


No, but both <blink> and <marquee> are quite easy to do in javascript...


Here is the code in an App Studio project:

http://blog.nsbasic.com/?p=1060

Runs fine on an iPhone 5!


The one in the html should not be there.


Some things not to teach:

Don't do: Numerical analysis, Compiler design, OS programming, Real time coding


As much fun as Org/Arch is, I'm thinking we can leave most of that and ASM behind, as well.

Not totally behind, but committing a semester to them as a course is what hasn't been working.


Good idea! Some things to teach...

HTML JavaScript programming, Practical SQL/SQLite usage, Project Management, Visual Studio .NET


I think .NET seems a bit heavy for what I've got in mind. I also probably don't understand .NET as well as I should either.

Can I get some more clarification why .NET should (or shouldn't) be included in a modern, practical curriculum?


In our case (NS Basic/App Studio) we wrote a translator for VB style BASIC to JavaScript.

We wanted to create a cross platform development that could target iOS, Android and other mobile platforms. We started the project about 2 years ago, and saw a few key developments in the JavaScript space.

1. HTML5: the extensions did a lot to move it from a web scripting language to something that could be used for real applications. The Cache Manifest allowed the developer to specify a list of files to be stored on the device, so the app could run offline, with no access to a server.

2. Home Screen: The mobile platforms added the ability to pin web apps to the Home screen with their own icon, making it possible to start them much like native apps.

3. Performance: Work by the browser folks on the internals of the JavaScript engine resulted in huge boosts in performance. The results are in this table: http://www.nsbasic.com/speedtest.htm. You can see the transition from early BlackBerrys being able to run a few hundred JS loops per second to the Motorola Xoom at 718,000. The benchmark is simplistic, but the message is clear: JavaScript on mobile device is 1000 times faster than a few years ago.

It turned out that it was fairly straight forward to write the Translator. Yes, there were enough weird edge cases to question anyone's sanity to do this again, but the result works well. All the control structures translated one to one, so there was little or no drop in performance.

We then built a Visual Studio style IDE around it, with support for frameworks like jQuery Mobile, jqWidgets and Sencha to build a complete dev environment. It's been a lot of fun.

(and yes, you can use JavaScript instead of BASIC if you want!)


My dad taught me programming in 1964, on IBM equipment where you used patch cables to write code. I was 10 at the time. Been programming ever since. I'm teaching my kids now - they are both using Scratch, which makes them 3rd generation.


There are some interesting projects out there for you. One of them is NS Basic/App Studio, which provide a VB like environment, then generates the JavaScript, HTML and CSS. (You can also program in JavaScript.) I agree - dev environments have to become more user friendly to be really good. (disclosure - I'm one of the guys having fun working on the NSB project)


We've been aware of how slow CF is on Windows CE for a while. Here are some benchmarks we have run:

CuWin 3500, CE5, NS Basic/CE 8 NS Basic/CE: 26529 loops/second Microsoft .NET: 133 loops/second

Acer beTouch E101 Windows Mobile 6.5, 528 mhz, NS Basic/CE 8.0 NS Basic/CE: NS Basic/CE: 16669 loops/second Microsoft .NET: 3060 loops/second

CuWin 5500, CE6, NS Basic/CE 8 NS Basic/CE: 14394 loops/second Microsoft .NET: 764 loops/second

i-mate 400mhz, WM5, NS Basic/CE 8.0 NS Basic/CE: 12632 loops/second Microsoft .NET: 1290 loops/second

Running the same test under NS Basic/App Studio, an iPhone 4 scores 282,674, Nexus One is 403,000 and the Motorola Xoom is 718,484. Plainly, Windows CE.NET has a long way to go!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: