• 0

Easy Programming Language


Question

Recommended Posts

  • 0

Fre compiler? heh. good luck, i wasent able to find one, so i had to "aquier(spl?)" it from an online "store". And it was only the VB 5.0 Edition, they did not carry 6.0. As for a good tutorial? I had to "borrow" a book from the library. Good book to, its called "Step by Step". it even ahs pictures to lead you along.

  • 0

Best way to find out is to try for yourself; each person will have a different opinion on what's easy and what's hard. When you try a language you won't lose anything either; time is never wasted if you're learning something. Also what seems to be confusing to many is that once you start to use a language, you should always stick to it. This is completely untrue; programming languages are only tools used in writing programs, nothing more, nothing less. Whichever language is appropriate for the task, you should be able to choose it selectively based on your experience and the strengths of the language. For example if you're looking to extract data from a website, or do heavy string manipulation, C++ wouldn't be the smartest choice compared to Perl.

That is my opinion anyway.

bwx

  • 0

If you want to start with VB then get yourself a copy of VB 6.0 - may still be available under Microsoft's Student License (assuming you qualify). Other than that you'll have to acquire it elsewhere - I am sure there are plenty of people willing to sell licenses for VB 6.0 as they no longer need it since they have .NET

Parimal

  • 0
Thanx people, some how the topic changed as Schmoove started chatting about some other stuff didnt answer my question, but i think visual basic and pascal get a lot of votes

Can't agree with you...I think pascal is kinda old and that's why it is not so popular as vb...

  • 0

I'de say it depends what you want to do. If you want to move onto more advanced languages in the future I'de say Java (or C# if you're willing to shell out for VS.net) is a good start, they teach that at my uni to people who have no programming experience and while it's not easy it does allow for easy migration to C/C++ and even makes learning scripting languages like PHP easier as the syntax is the same (ASP on the other hand uses VB style syntax), plus the OO elements and automatic memory management make it a good choice for beginners with a will to learn. The fact that apps can be used on any platform also make it a good way to be sure your apps work for everyone, whether PC, Mac or Unix. VB is good if you just want to scratch the surface of programming, and aren't interested in taking it much further, as its syntax is very easy to understand, although learning anything more advanced is quite a step (although not impossible). Pascal is becomming less common, and in my experience isn't used much in commercial environments.

I'de recommend the Java and Netbeans combo (http://java.sun.com/j2se/1.4.2/download-netbeans.html) as this means you get a free IDE too.

  • 0

vb, seems to be a hell of a lot tutorials and knowledge base (vbcode.com) to teach you to do anything, i've made 4 or 5 programs with it, with no prior training. only other language i've used is c++ but i only installed that because it came free with a cd and i wondered what it was :\

  • 0

I concur with those who say BASIC is the easiest to learn, BUT...

It is true what they say about Basic being a spoiler for learning "stronger" languages later on. I speak from experience, having learned BASIC in grade school in the 80's, discovering Qbasic in the 90's and falling in love with it as a hobbyist programmer, and then getting so hooked on programming that I am now *trying* to master C++.

My "learning-curve" is now shaped like a 90-degree angle!

The thing I see clearly now, is that BASIC was never a real language, not like C++ is. In just scratching the surface of C++, I have already out-classed anything I ever wrote in QBasic, with about 3/4 of the language left to explore!

OK, I did acomplish a few cute little games in QB4.5 that I'm not quite ready to tackle in C++, but it's taken me this long just to get to where I'm confident that I'll eventually be able to "do it all". I can easily see where you could write a BASIC compiler in C++, no problem, but I could never imagine a C++ compiler written in BASIC! (Maybe Visual Basic....)

So, anyway, if you just want something to play with, Basic could work. But, take it from one who's been there, if you want to *really* program, it's much easier in the long run to learn the right language the first time!

JMHO...

Hosiah

  • 0

Basic or VB, if you give it a quick go, will show you all the general concepts of syntax and programming that later languages like C++ will use in insanely more depth, not saying that one will transfer smoothly to the other, but that it'd not be a lost cause to check out the much recommended VB.

  • 0

OK, just to add to my earlier Qbasic to C++ saga...

The one thing I miss the most about QBasic is, the graphics could be done:

screen 12

line(x1,y1)-(x2,y2),col

...just THAT easily! Instant raster graphics, and I used them so extansively that I even developed my own work-around for QB not using bitmaps...involving using an "etch-a-sketch"- type program I wrote which would save the pixels as numeric data in a text file, for later recall by other programs!

I really, REALLY miss raster graphics. The simple act of being able to turn the numeric data into pictures makes a programming language come alive for me, and it seems that this is the one thing that's going to be denied to me in C++...*sniff, whimper!* Though I have read ahead and compiled downloaded sample code enough to know that someday, I'll be able to do graphics in C++, too. From the looks of things, this appears to be the hardest thing to do in C++!

Yes, I know that old-style C has the "lineto" function, that's just the problem: old style, raster graphics seem to have become extinct in C (if I'm wrong about that, somebady, anybody tell me? Give a poor noob some hope?). Instead, I'm going to have to deal with graphics on a much more complex level with OpenGL or all that "device context class" stuff.

As <insert your favorite Diety> is my witness, if I do master C++ graphics, I'll write a function that translates all that complex stuff back into the simple "line" statement again, stuff it in a header file, and give it to the world!

Peace and Love and Granola,

Hosiah

  • 0

Logo, though it's not too useful, and some consider it not really a language

you can do a lot with scripting too, but it's not programming

as far as undebated programming languages the basic family

qbasic is the easiest but not too powerful

as far as serious easy programing i suggest vb .net 2003

as far as ones with free compilers I suggest python, a lot of people like java but java sucks

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
    • I'm reading the reports as EU rejecting Apple's proposal because Trusted System Agent would be an intermediary offered to third party AI's (this article is also worded as such) but Siri AI itself would not pass this intermediary. This would cause a situation where Siri AI would have more direct system access and offer it an unfair advantage. (speaking from EU regulator perspective here) Apple is citing security issues with doing what EU asked for, and I think this also supports this theory, because truly direct system access like Siri AI would make it impossible to control third party AI's running on the devices and e.g. reign them in via adjustments to Trusted System Agent. So, I _think_ this is the sticking point right now: EU saying they need to be on equal footing as Siri AI, Apple saying they can't be because Apple only trusts their own AI. Apple could of course be leaning a bit extra hard towards this because they're biased in terms of excluding competitors. One method to find an agreement would be to have Siri AI also run through Trusted System Agent and treat it as untrusted. This kind of defensive architecture design (especially when involving an AI) would honestly not be a very bad idea from a sheer engineering standpoint. But then Apple would need to swallow their pride and adapt worldwide due to EU, and make perhaps major updates delaying Siri AI once more.
    • I have not even heard of that game. will take a look
    • Chasys Photo 5.41.01 by Razvan Serea Chasys Photo is a suite of image editing applications including a layer-based image editor with adjustment layers, linked layers, timeline and frame-based animation, icon editing, image stacking and comprehensive plug-in support (Chasys Photo Editor), a fast image viewer (Chasys Photo Viewer) and a fast multi-threaded image file converter (Chasys Photo Converter) , with RAW image support in all components. It supports the native file formats of several competitors including Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr, and the whole suite is designed to make effective use of multi-core processors, touch-screens and pen-input devices. Designed under the mantra of “unique, flexible and powerful”, Chasys Photo takes a radically different approach to image editing with the aim of opening up new possibilities for those who dare to be different. Chasys Photo key features: Free-style layering with blending modes Adjustment layers with multiple adjustments per layer Linked layers (a.k.a Linked Smart Objects) Composite, Image List, Frame Animation and Object Animation image modes Animation, both frame-based and object-based (timeline animation) Animation Composer engine Image Stacking for noise reduction, super-resolution, etc. Tablet/Pen-input/Stylus support with pressure control Touch-screen support with gestures including pitch-to-zoom and multi-finger panning Support for the native formats of Adobe Photoshop, Affinity Photo, ArtWeaver, Corel PhotoPaint, FireAlpaca, GIMP, Krita, Paint.NET, PaintShop Pro and Pixlr Support for common formats such as JPEG, animated PNG, animated GIF, TIFF, PICT, WebP, HEIF, DDS, JPEG-2000, JPEG-XR, JPEG-XL, AVI video, etc. Support for the OpenRaster interchange file format and rare formats such as QOI, MNG/JNG and DPX Support for older formats such as PPM/PGM/PBM, PCX/DCX, PCD, TGA, COKE, etc. Comprehensive Camera RAW file support with live adjustment Extensive plug-in support with streamlined SDKs Support for Photoshop Filter Plug-ins (.8BF) Advanced printing and scanning engines PDF document generation Icon and cursor editing, import and export, including Vista-style and Mac-OS icons Screen Capture, including Video Screen Capture with multiple triggering modes Video capture from devices (e.g. TV/Video) Supports multi-core processors, High-DPI displays and Multiple Display setups Integrated File Browser, Bluetooth OBEX and in-built utilities (Calculator, Notepad) Shell integration with thumbnails and conflict detection Unlimited Undo/Redo and Asynchronous Auto-Save, with Just-in-time memory compression to save space Fully re-editable text with advanced styling and effects (TextArt) Full alpha channel through out the workflow with Alpha protection (a.k.a. transparency protection) Multiple language support with user-editable language files and translation assistant (Chasys Photo Language Studio) Anti-aliasing and super-sampling support in tools and paths* Smart-resizing (similar to seam-carving) Best-in-class post-edit heuristics anti-aliasing engine Physical measurement specification with display size detection via EDID Uses the latest CD5 specification with animation and multi-resolution Super-fast internal graphics engine (JpDRAW2) Full UNICODE support in all components Metadata save, restore and scale to imitate vector art Configurable Guides and Grids with Snap-to-Grid Smart-dither to custom palette Asynchronous preview rendering engine Pantone equivalent palettes for PMS 100 to 814-2x Automatic color naming ... and many more! Chasys Photo 5.41.01 changelog: New Features Layered images with multiple pages (Composite/Multi-page) Additional templates to support template-centric workflow New Layer Blend Mode: Inverse Luma Mask Horizon detection in Rotate Transform Cropping option when importing video Orientation options in QR Code Generator plug-in Solved angle ambiguities (CCW versus CW) Internal Improvements Improved graphics engine (JpDRAW2™ v26.05) Improved CD5 codec (v4.10, improved ACSC compression) Improved interpolation when downsizing images Improved motion detection in Video Capture Slightly lower memory usage (RAM is getting expensive!) File Support and Bug Fixes Improved PXZ file support (placeholders, blanks) [bug-fix] Memory leak in flt_JPEG.dll Download: Chasys Photo 5.41.01 | 46.1 MB (Freeware) View: Chasys Photo Home Page | Wikipedia Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!