LL and LR parser generates different derivation, and as such it is deterministically non-deterministic, hence UB.

Not just like "what kind of gender people I like" this kind of oversimplification but it's more about your attitude towards gender stereotypes and roles, for that's what I saw in a more deep connotation.

I observed this through observation of the attacks to Rust due to the huge presence of LGBT people.

Now while I'm pretty much straight myself, I don't reject LGBT people and don't want to partake in identity politics.

I just want things that works no matter what background you have, yet there are some people attacking Rust because of its inclusiveness nature.

And just like Linux is being perceived as nerdy and geeky and "gaming socks ready", the tokenization of things, and there attaching political meanings to it, are quickly coming to everything, so perhaps I'm too general here as well.

Let's say it is not political, but definitely adding more meanings to its technical origin and nature

Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.

Maybe we should one day include Golang or Rust to it

https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule

I would still define first-order Futamura projection as the original definition that you have direct encoding and code-to-code expansion and transformation between so.

Insane amount of bureaucracy, paperworks, and how we are missing deadlines so we write shit code that the quick and dirty solutions were never replaced.

Algorithms and data structures therefore are more like helping you utilize the machine economy better, but it doesn't have any meaningful impact on the social aspect of it. That's a hard lesson I had to learn from my two previous job, though now I'm considering starting my own small business just to make a little bit of living enough to survive.

But now my ADHD kicked in and is still lazy and I had so many concerns whether the market validation is great, how to deal with situations if I broke customers stuff, how to gain (and hopefully not regain) trust if any bad things ever happen, what if I want to go vacation and suddenly the server broke and got code zero (the highest level of alert I termed internally, when you had alertmanager flashing everything red, network storage is down, corruption happened) during a trip to Bahamas.

I'm still in the watershed of thinking really to do this or not, but the job market is filled with ghost jobs that are not worth my time either, I'm basically "dead locked" right now and had to make a decision quick.

Either choice is fucked for me, as I started to notice after going to work, despite I got some really interesting ideas in tech, but I'm not a charismatic person so I can't really make those idea to fruition, because no one wants to listen to me and implement it together, so I'm pretty sure it is impossible for me to be a great leader (tech lead probably, but CEO level of leadership and coordinator and manipulate the grand scheme of thing, nah, I pretty much can't do).

Now the problem is, even if I'm pretty sure to get fucked, you should choose the one that inflicts minimum pain to you. So far having my own business seems like a less painful to die and bankrupt, and I'm preparing to sell off some of my stuff to get a last dip of my fortunes and have fun. Will see how it looks. Bankruptcy is nothingburger in this modern society perhaps.

Now you see how the bottlenecks can't even be the code anymore and even goes beyond code, despite having the same core template: I don't even have to code, to repeat the same "quick and dirty" kind of mindset in another domain, in another instance. That's something LLM, heck not even AGI can solve: decision-making based on situations with limited time and resources, and it can be personal or organizational or even structural.

This is very much not going to be solvable by a bunch of lines and statements and expressions, but it really need some time to dig in and compromise. Pick your kool-aid and drink it

But the biggest problem is, even human itself is subjectable to hallucination. That is called being delusional, or being drugged. So it is inevitable from the first principle.

To me it seems more like leveraged buyouts + debt restructuring all at once. I rather coin this term "debt offloading", which could also cover the cases with Enron for the tactics they used about 25 years ago

By using a long distance communication device this eliminates the proximity strike problem. This could easily be extended to say like distributing the voting rights to different generals at different regions, and given that the device is genuine and not modified, can be a hardware voting key to say like launch the nuke in secrecy or not.

Whether adversarials can use the radio signals that it emits to triangulate you and thus track you is another story, though.

What I (or LLM) vibed out is that I told it to observe how the APIs are called, and used Ghidra MCP server that I configured to load and decompile the C native libraries and do a deep research, analyzing how the native libraries worked, and then rewrite the code without using JNI but to for example, use LWJGL's OpenGL binding for the Jagex's implementation for OpenGL, and also some other native libraries like the "C library" which is basically some hardware information. Then Ghidra will puke out the decompiled pseudo C code, and let LLM to make sense of it.

The only native code left is the software rendering mode but it is obviously out of the scope as of now because we all know how worse it could be to implement software rendering in Java even with JIT. AOT might be another story, but software rendering in general is not a good idea anymore today. The code is intentionally snubbed out from being loaded in the class loader so it is a RuntimeClassError. To be fair if you want "software rendering", going through llvmpipe or Zink would fare much better.

As a result, the game client now can run over technically any platform given that LWJGL supports it, not having to care about it being 32-bit or 64-bit, without much limitations on the JVM platform besides from some deprecated APIs that I can just slop it out asking LLM to replace them with modern alternatives but I just don't really want to bother yet.

This is a direct consequences to my findings in https://github.com/stevefan1999-personal/demcstify to decompile and reconstruct Minecraft to source code, but this time I already have a partially working and launchable game only that the state of the source code was obfuscated. This is a direct thesis to the closing part of my demcstify project: you can't hide your code by layering down obfuscations and virtualizations as LLMs are kind of great at dealing with those semantic games.

Instead, now softwares can be cheaply manufactured and cloned to some port, I think it is serious time to think about how the future of software development and open source entangle with each other -- LLM can basically read the binary (binaries if it has multiple platform supports), spew out enough reasonings to know what the code and algo are doing, and even make a reasonable clean-room reimplementation of your software (I have one pending with Picovoice's Porcupine, but I just want it to run on ESP32, I have yet to release it until it really runs)

Comments URL: https://news.ycombinator.com/item?id=47973371

Points: 1

# Comments: 0

It is not like I don't know that Golang's interface could do that. It's just C# simply did better. I do enjoy using Golang for writing network application such as network protocols and IO intensive workload, which is where Golang really shine through Goroutines, but if you want a generalist that is famiilar and did all-rounds, I would still consider C#/Java/Kotlin for that purpose.