Awesome Sauce Java with Hot Sauce OS

Being blind is difficult.  But it's not just being blind, it's the cyclical nature of my mental focus.  Getting hit in the head is like in the cartoons.  You get whacked, and there's a cross-eyed shock, then everything starts vibrating like cymbals.  What isn't visible is the lasting and debilitating damage to the neural trees.  A nice way to say whatever was learned and sitting on those neural trees is now gone.  My mind orbits like the zodiac, except only some of the signs are illuminated. What that means is? Today I'm productive.  Tomorrow I might not be.  I might not be productive again for days, weeks, or months.  I seem to be getting better in a way I haven't experienced in a long time. I can't remember being this focused in close to 30 years. Brain injuries are scary for the limitations they introduce. I'm going to do everything I can to try to make tomorrow as productive as today, if not more-so, but who knows.  So many stres...

It's kind of a weird thing to be saying, but Awesome Sauce Java is going to make it possible to evolve Java.  I've mentioned it before in a prior post.  But, by virtue of the design, ASJ will provide users with standard JDK Java calls, in a functional form, standard Lisp calls, new idioms, and modified/simplified/cleaned-up Java JDK & Lisp calls. I was just looking at both Java and Lisp code.  With regards to the Java code, I'm going to start with modifications by eliminating obvious redundancy.  Where a call contains the name of the argument, I'll eliminate it.  For example, the call to processWindowEvent( WindowEvent e ), could just as easily have been called process( WindowEvent e ). While it's going to take a little time, it just makes sense.  Because once the redundancy is removed from the calls, the language becomes easier to work with.  Calls become easier to remember and expressions become more expressive. I'll be doing the same with ...

I Only Sound Confused Until I'm Positive I didn't know I was going to be addressing this in Awesome Sauce Java.  But apparently, being on the inside of a Lisp invites exploration and all that exploration leads to wonder and now I'm standing inside a region of software I never wanted or planned to be, with a possible approach to possibly simplify some complicated things related to packages, with no confidence anybody is going to care. I'm tilting at windmills. Names are a vexing bane in software. Names are confounding in software. Just trying to get this article started has me confused. Maybe a little angry.  Packages are great, but they're not, but it's not nice to complain just to complain.  Best to point out the why they're great and why they're not, then show how to improve them. Packages are the best.  Maybe the best it can possibly be.  Whatever packages are?  They're a really, really, really, truly difficult hard problem. There may n...

I need a job. Meanwhile, I keep writing, because what's the point of saying you can write code if all you're doing is reading job descriptions, writing cover letters (barely), and sending resumes (barely, too)?  I spent years sending letters and applying for all kinds of jobs. Strangely with literally no response. Ever. I work. It's been a strange 7 years since getting assaulted by that guy who came close to tearing my head off. Today I'm working on and writing a few things:  Class definitions. With Awesome Sauce Java, you'll be able to create class definitions like Java defclass definitions like Lisp. One of the things I'm exploring is merging class definition into a new form that's like a combination of both the Java and Lisp methods. If this comes to fruition, it won't obviate class or defclass, just be another way to create classes. Concurrency Oh boy was I thinking about concurrency last night and this morning. Will write a separate ar...

I'm taking a break from JavaFX.  I almost have everything ready to build a first app.  I'm kind of excited, but I'm not sure what to think about JavaFX.  From what I've read, it looks nice, but I read about building a release app once and it seemed really complicated. Groovy and Kotlin and Clojure, Oh My I was looking at Groovy and Kotlin today.  I've been actively looking for sample code to use as comparison against Awesome Sauce Java.  This is going to be an ongoing project I'm going to do my best to keep going.  I think if I hadn't taken a detour into Android development, I would have done this a while ago, because it's important to present what Awesome Sauce Java looks like. I think getting macros working has helped me because that one feature was apparently occupying a lot of energy and mental focus.  Now that it's working and right in front of me?  My motivation is empowered and I want to get the next features done.  Bonus is that ...

I'm writing this to remind myself and because I'm hot on the trail of building UI code for desktop apps, server-side web apps, and Android apps, all in Awesome Sauce Java. I'm writing here a lot today. That's because I'm writing over there a lot, too, and doing some good things with Awesome Sauce Java today.  I had stalled out, but now I'm in a growth phase. I just started working on building Awesome Sauce Java stand-alone applications.  It'll take a few more minutes to get a test application built.  I might do a video to show how to create an ASJ application.  I'm still stuck on Swing apps, but while I was working on getting all the code organized, I also did some work to get JavaFX set up for ASJ.  After I get a test application built, I'll build a quick test application for JavaFX.  Finally. After the configuration and JavaFX tests, I'm going to do a little work on HTML generation.  Then, I'll do some research and work on rendering ...

Popularity is for People Who Something Witty The problem with code is it's all just a big giant <expletive> hack. There.  I said it. The problem with code is how we write code.  It's not what the code does.  In fact, the fact that we focus on what code does highlights that it's not just solvable, it's possible to approach. Figuring out how we write code and what's wrong with it?  It's like talking about diet.  We don't have a control, so we can't science things up about either diet or how we code.  We assume that how we code is the way it's intended to be, because we've mostly always done it that way. But it's a total frickin' hack.  I'd love to say I knew that yesterday or three years ago when I started writing Awesome Sauce Java, back when it was just a language for Calc Me Sum 2C.  But then it started to get to me and I didn't know what it was that was getting to me, but I knew it was the code.  Years ago, I had...