AI cannot replace humans spiteful spirit
-
There used to be a UI library on the Amiga called MUI.
It used a bunch of C macros to let you define the window and all the controls. Was honestly pretty good considering it was like 30 years ago.
wrote on last edited by [email protected]There is another called ImGui which is also cool! Written in C++.
-
Raw film is objectively higher quality than raw digital. Are you saying that C is objectively higher quality than Rust?
Excerpt film isn’t objectively better…
-
Shoulda been something more like Java Web Start.
Maybe. But performance, availability, and security killed a number of viable options. Flash was always more ubiquitous than Java on the web but it eventually died too.
-
Not really, but I'd probably try to organize those into sub structures where it made sense. A data structure holding the UI state and FFT data all flat is kinda messy imo since it becomes unclear what is actually required where.
It is spite coding though.
He probably has a bunch of gotos too.
-
Vibe coding in assembly.
I tried vibe coding a simple assembly program and it couldn't do it
-
Excerpt film isn’t objectively better…
That's what your original comment was eluding to, so I was confirming with you that that's what you meant.
-
Maybe. But performance, availability, and security killed a number of viable options. Flash was always more ubiquitous than Java on the web but it eventually died too.
wrote on last edited by [email protected]Flash was also cancer that ruined web pages.
The reason Java Web Start wasn't, was specifically because once you clicked on the link, it downloaded the app and started it as a real desktop application, with its own window and taskbar entry and whatnot. It didn't rely on being embedded in HTML (I'm specifically not talking about Java applets, BTW -- they sucked too) or manipulating the DOM for its UI; it could use Swing and have the same look and feel as a native application.
-
This post did not contain any content.
laughs in Vaadin
-
Do React devs really hate React?
I think it’s great and I’ve been working with it for 6 years. Many issues were resolved over time. We didn’t even have hooks back when I started! Those were dark times. And the new compiler helps with memoization.
-
This post did not contain any content.
React Native
-
This post did not contain any content.
this is like when I built that web server in x86 assembly lol.
-
this is like when I built that web server in x86 assembly lol.
I bet that thing was fast!
-
This post did not contain any content.
I moved from Visual Basic (3 no less!) to C because I needed to optimize the performance of a software synthesis (like, sound synthesis) application I was developing at the time (mid-1990s). It boggles my mind to this day how much fucking work you had to do just to create a simple window in C. It instantly made clear why UIs at the time were so bad and I went back to Visual Basic for the UI with a compiled C DLL to do the heavy lifting.
There's no excuse for why UIs are still so bad today.
-
I have definitely gone into a rageful fugue state and woken up a week later after reworking an entire code base from being an inconsistent mess of slop...
...into actually having a common library of functions instead of just rewriting slightly different versions of them 8 times, having those functions only actually instantiated for necesarry classes...
...rewriting every variable name and function name to an actually consistent and intelligible naming scheme...
... and finally, moving a whole bunch of shit out of some kind of global 'think' type loop that doesn't actually need to be called or checked every goddamned micro second.
Done that more than once actually.
Never look inside 'baby's first video game mod' code, unless you have healthy blood pressure.
But uh yeah, spite, hatred, and anger are indeed powerful motivators for making good code, lol.
... so many idiots just jam everything into a global, called every tick loop, and then claim that it just can't be optimized, because "the game engine just can't handle it"...
I spent a good fraction of my career taking over and trying to fix code bases that my company refused to scrap and replace outright because they didn't want to admit their worthlessness. Complete rewrites would have taken maybe a tenth of the time I spent.
My favorite thing to encounter (which was nearly universal) was the phenomenon of a young programmer fresh out of college encountering SQL for the first time, deciding he hated it, and writing a huge mess of code to handle auto-generating the necessary SQL. I remember taking over one C# application that had classes named "AND.cs" and "OR.cs" which just took a String as a parameter and returned that String with " AND " and " OR " appended to it, respectively. In about an hour, I replaced three months of this guy's work that had bottlenecked the project with like five SQL statements.
It's insane to think what the civil engineering world would be like if it had the career structure of the software world.
-
This post did not contain any content.
I'm still waiting for the day we get a proper alternative to JavaScript.
If I had to make one, it would have a Bash-like syntax
-
Oh stop it. Are you saying you don't enjoy pressing the "Back" button in your browser, but staying on the same page. Therefore breaking the page so you refresh and lose whatever the fuck you were doing? /s
Yea let's go back to index.php and the 5 second load time for every clicked button
-
Oh man. You should see the source code for IOS (the Cisco one not Apple).
Spent 5 years working on it out of college. I think it's the most cursed code base you can imagine.
Not necessarily because of the massive struct defs everywhere. They are kinda needed when you're running an entire OS as basically a set of interacting Linux processes pretending to be an OS.
At some point Cisco realized they could not compete without putting a Linux kernel as their base. So they basically just copy and pasted the old code written in the early 90s for the IOS and put it into a set Linux processes.
To be clear. It's not just the front end. They didn't really change the code much from the old IOS. Its a cluster fuck of interprocess communication hacks that probably seemed like a good idea at the time.
It is a massive pain in the ass to code because you're basically doing everything on the Linux kernel and then frustratingly have to write the CLIs for IOS just so Cisco can continue to sell their proprietary OS with some of the most unnecessary hardware locks. Massive learning curve for any new engineer.
Literally, no one on the entire switching team knew how to send a message from a specific process to the IOS process. I had been assigned something that needed it. So I somehow figured it out and was "the guy" for that for the time I spent there.
Fuck. I'm gonna start ranting more if I go any further. But yeah, sometimes you need a massive struct because some idiot decided that forcing a closed source CLI on the market is a good idea for profits.
Definitely not a good idea for coding. But you learn quickly that no one actually cares about good code in this industry. There is no time for it. There is no reason for it. Just spit out garbage until it works and your manager won't care.
If you want clean code. Go write an open source project or a personal project.
I used to work for Cisco but I can't say what it's like internally. Not because of an NDA but because I literally have no idea. I worked for a much smaller competitor of theirs that they acquired, obviously just to remove a competitor from the marketplace. We were all allowed to work remotely but given nothing at all to do for six months and then everybody (except the executives, of course) was laid off.
-
This post did not contain any content.
can your React do that?? didn't fackin think so dabs mockingly
-
I moved from Visual Basic (3 no less!) to C because I needed to optimize the performance of a software synthesis (like, sound synthesis) application I was developing at the time (mid-1990s). It boggles my mind to this day how much fucking work you had to do just to create a simple window in C. It instantly made clear why UIs at the time were so bad and I went back to Visual Basic for the UI with a compiled C DLL to do the heavy lifting.
There's no excuse for why UIs are still so bad today.
The "excuse" is more or less the 20 or so replacements that have been made and died. I think Microsoft alone is responsible for 5 over the life of Windows.
We've more or less kinda settled on HTML only because it's already wide spread. But it's not perfect so more standards for the standards pile. Don't worry, react will end up buried by the next thing on the pile eventually.
-
I spent a good fraction of my career taking over and trying to fix code bases that my company refused to scrap and replace outright because they didn't want to admit their worthlessness. Complete rewrites would have taken maybe a tenth of the time I spent.
My favorite thing to encounter (which was nearly universal) was the phenomenon of a young programmer fresh out of college encountering SQL for the first time, deciding he hated it, and writing a huge mess of code to handle auto-generating the necessary SQL. I remember taking over one C# application that had classes named "AND.cs" and "OR.cs" which just took a String as a parameter and returned that String with " AND " and " OR " appended to it, respectively. In about an hour, I replaced three months of this guy's work that had bottlenecked the project with like five SQL statements.
It's insane to think what the civil engineering world would be like if it had the career structure of the software world.
First thing I tell my interns: "The guys that made that database are smarter than you, they got PhD's for the algorithms the database uses. You are going to use SQL properly, and query properly, because the database will always do it better than your python code."
