Skip to main content

Small Basic for biginners












Microsoft recently introduced Small Basic, a programming language for beginners. It's a strip down version of BASIC with only 15 key words. It seems to be a fun programming environment & definitely worth while trying. You can write both console & graphical interface enabled programs & even develop your own version of Logo.
Some of the features include:
  • Its free
  • 15 key words that support basic programming concepts including conditions & iterations
  • Intellisense & context sensitive help
  • Define variables on the fly, no need to explicitly define them
  • Graphic programming
  • Subroutines
  • Third-party libraries can be plugged, API is given
It even comes with a simple but comprehensive user guide that introduce basic programming concepts & Small Basic.
Though it's intended for beginners, even advanced develops can use it to write scripts that perform simple day to day tasks.

Comments

hasala said…
Hi Dilum aiyya,

Nice to c u in the web, hope u r having fun and doing fine in Canada.

Y the microsoft Basic, they r trying 2 fools the world with their tricks, But v wont get caught, FOSS GAMBAS is much better i guess :) , but keep us posted on your news, for u taught us our first CS module so v r ever in debt to u. Wish u a very happy and succesful new year ;)
Dilum Bandara said…
Thanks for the comment. I think you miss the point...
Small basic is just a beginner’s interface to programming (can't even create an executable) whereas Gambas is suppose to be a fully fledged IDE. Windows support in Gambas is not the best, which is the platform most beginners use.
We started programming with DBase, FOXBase, Pascal, & C. No GUIs at all. We were happy even if we can write a simple sorting algorithm at that time. Whereas today’s programmers want to start with GUIs that make things much harder. So it's nice to have a beginners platform. It doesn't matter whether it's from FOSS community or Microsoft. The key thing is its availability.
simona said…
Hi Dilum, can you email me at simonamaloney@yahoo.com I have some questions for you. Thanks, Simona

Popular posts from this blog

Python Code to Calculate Gini index/coefficient, Robin Hood index, & Lorenz curve

Following Python code can be used to calculate Gini index, Gini coefficient, Robin Hood index, and points of Lorenz curve. Lorenz curve can be also plot if matplotlib is installed.
It's based on the steps given by Peter Rosenmai.

Download


Other online tools:
http://www.wessa.net/co.wasphttp://www.poorcity.richcity.org/calculator.htm

1. Building P2P Simulators with OverSim - Where to Begin

This could be a series of blog posts about extending or developing your own OverSim applications & overlay networks. OverSim has a minimal tutorial on writing your own application & overlay network; however, it doesn't show the big picture. So, I'm wasting lots of time playing with code & trying to understand the rest. Good thing is, I like it more & more as I understand. You need to change/develop only a few things, but finding out which ones is a hell of a task. I hope this will not only make my life easy but also will be useful to new comers. Here's what you need to do: You need some background on OMNeT++ OverSim extend OMNeT++. But sometime it has its own way of doing things (to make your task even simple) so understand the differences.Develop several OMNeT++ simulators. TicToc is a good one to start with. Extend it as you imagine.Read Towards a Common API for Structured Peer-to-Peer Overlays, which is the basis for OvseSim's API. Here'…

Describing Experimental/Simulation Setup

Sometimes the results of a performance analysis may depend on the computers used and/or specific features of software/libraries. In such cases it is extremely important to describe the experimental/simulation set up in details. It enables others to repeat those experiments as well as check whether the results are rigorous, statistically sound, and unbiased. Unfortunately, "Simulation Setup" is the shortest section in many research papers where authors try to save space by cutting down as much as details. Here are some tips on what to include (in addition to describing the experimental/simulation setup) based on my experiences:
Type of Simulation Are the results based on Experimentation, Emulation, or Simulation? If simulations also mention further details like whether it is Discrete Event, Montacarlo, Stochastic, or Deterministic simulation. Are the results for Steady, Dynamic, Starting/ramp-up, or Terminating state(s)?Number of Experiments/Simulations No of sampl…