Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 0 Posts
  • 738 Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle
  • VBScript did catch on originally, though. When IE had over 90% market share, it was nearly as popular as JavaScript was. It only dropped in popularity when other browsers became more common. Back then, most scripting was just to enhance the page, and the page still had full functionality without it, so a lot of developers just didn’t care about making it fancy for the 5-10% of other browsers.

    “AJAX” (XMLHttpRequest) was originally an IE-only, VBScript-only feature. It was originally implemented using ActiveX, which only VBScript supported originally.


  • I’m hoping that more DOM and BOM APIs become accessible in WebAssembly without having to go through JavaScript. There’s a few frameworks that let you build web apps in other languages (like Blazor for C#) but they still need some JavaScript to interop with the browser, and going through a translation layer (WASM to JS to browser) adds some overhead.

    Even visual basic for the web would make sense

    This is exactly what I did for a few years before switching to JavaScript: VBScript. It was pretty common back in the early 2000s when Internet Explorer had 90%+ market share. The few remaining Netscape users would just get a page without scripts. There’s a lot of features missing in VBScript that exist in JavaScript though, even basic things like closures and first-class functions.







  • dan@upvote.autoProgrammer Humor@programming.devMy boss wants us to use AI
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    edit-2
    6 days ago

    My employer is trying to get people to use AI more, too.

    I’m skeptical of AI, but I’m finding it useful for menial tasks - things that you’d otherwise automate using an AST-based codemod tool (like jscodeshift, libcst codemod, etc), a hacky find/replace, or do by hand (boring, tedious work that I’d rather not do). Giving the AI system an example patch for something like migrating away from a legacy API, and saying “do this same thing across these 200 other files”, can have pretty good results.

    In general, it seems like a good tool for things where the entire process is well-defined - the prompt and context provide all the info it needs - and I include example code in the context.

    I don’t trust it for brand new code in a large existing codebase… Even the best AI models still get a lot of things wrong.