9

I just keep reinventing javascript

Comments
  • 2
    by accident
  • 2
    and it's also magnificently beautiful actually
  • 3
    I have acquired perfect 100% proxy usage without exploding RAM

    and it's done without any waiting queues. just automatically the code won't allocate resources until there's proxies there to deal with them

    even though the proxy management system is deep and integral but your outside code doesn't need to know about any of that

    it just works.

    this is what I always wanted and I thought I figured it out by accident when I started this rewrite like a week ago but I was wrong because I forgot all the internal edge cases

    then the dumbest epiphany entered my skull. could it be like how fetch works lol. in stages.
  • 5
    @jestdotty BeanScript, CoffeeScript, LoungeScript, SofaScript, BrightScript, MessyScript, TofuScript. I just made up these alternatives as well. lol.

    And they, well done on your fun journey. I've been wanting to reinvent JavaScript myself! Have you heard of Million.js that supposedly makes your React apps 90% faster? It sounds similar to your idea.

    Back a few jobs ago there was this JavaScript guru I saw who would debug JavaScript by looking into the hexadecimal address segments of RAM. lmao. Now that's when you can call yourself an expert.

    Fortunate discoveries. Like the movie Serendipity. lol. Like the movie Back to the future III. Discovered during hitting head in the bathroom! Flux capacitor! Great Scott!
  • 2
    @jestdotty I'm trying to understand your model. Hm, proxy.. so things are siphoning through a proxy system? No waiting queues.. that sounds wonderful, given JavaScript's single-threaded model.

    Now, I'm not an expert on JavaScript by far, but it is interesting. The JIT-handling of operations.. hmm.. hm.. sounds a bit different from Redux.. but wonderfully efficient, like generators.
  • 2
    @CaptainRant ok well not whole JavaScript

    people on this site dislike JavaScript

    but JavaScript got a lot right

    in regards to networking and "thread" behaviour I guess
  • 1
    @jestdotty Ahh, lower-level matter. Nice. Ultra-nerd medal. >:D lol Well done. I like it when I see interest and passion in the field.
  • 0
    @CaptainRant tbh I just want it to work lol, but sure
  • 0
    I never understood the programming language discussion thing. In modern programming, all you do is gluing APIs together, no matter if they're third party or built-in. My JS code is literally 95% fetch() followed by querySelector.

    All built-in APIs that do something useful are just linking C++ modules. If you're not doing stupid shit, Python is exactly as fast as C++ or Rust.

    The only scenario where speed matters is algos. Guess what? You should write your algos in C and link them to your Node/Python/Go/whatever code. And don't even get me started on reinventing algos. Do you really think you can write an algo in one evening that will be more efficient than what the guy whose PhD thesis it was a part of?

    Just because some engine parts require the precision only a million-dollar CNC machine can provide, doesn't matter you have to cut the whole car out of a solid block of high-performance engine block alloy.
  • 0
    Remember kids, sorting array in Python is always faster than sorting array in C, because Python's sort was written by someone else who's smarter than you, went through years of scrutiny and iteration, and doesn't have stupid novice algo complexity errors.

    Grow up.
  • 0
    seems like your brain damage is taking over.
  • 0
    @tosensei it's actually vastly improving 😋
Add Comment