and I just straight up installed GNU Octave on the server and called out to it from python, using the exact code the mathematician had devised.
and I just straight up installed GNU Octave on the server and called out to it from python, using the exact code the mathematician had devised.
Just call it Agent-based programming or somesuch, otherwise it's really confusing!
Gazans still hold Israeli hostages, Hamas has publicly stated that more civilian deaths helps their cause [1], they're still fighting, the UN refused to distribute aid because they were getting attacked [2], and Israel unilaterally pulling out of Gaza and leaving them to govern themselves is literally what led to October 7th...
1 - https://www.cnn.com/2024/06/11/middleeast/sinwar-hamas-israe...
2 - https://www.wfp.org/news/un-food-agency-pauses-deliveries-no...
Edit - I love it. Down votes instead of responding to this comment's question. Again, what's your solution people?
Edit 2 - is this really a good use of the flagging tool? Is this what HN is about?
Not saying that can't happen with CGI, but since Tomcat is a shared environment, it's much more susceptible to it.
This is why shared, public Tomcat hosting never became popular compared to shared CGI hosting. A rogue CGI program can be managed by the host accounting subsystem (say, it runs too long, takes up too much memory, etc.), plus all of the other guards that can be put on processes.
The efficiency of CGI, specifically for compiled executables, is that the code segments are shared in virtual memory, so forking a new one can be quite cheap. While forking a new Perl or PHP process shares that, they still need to repeatedly go through the parsing phase.
The middle ground of "p-code" can work well, as those files are also shared in the buffer cache. The underlying runtime can map the p-code files into the process, and those are shared across instances also.
So, the fork startup time, while certainly not zero, can be quite efficient.
M$ (appropriate name for that time) of the day was doing its best to own everything and the did not let up on trying to hold back the open source internet technologies until the early 2010's I believe. Its my opinion that they were successful in killing Java Applets, which were never able to improve past the first versions and JavaScript and CSS in general was held back many years.
I still recall my corporate overloards trying to push me to support IE's latest 'technologies' but I resisted and instead started supporting Mozilla 3.0 as soon as they fixed some core JS bugs for our custom built enterprise JavaScript SPA tools in the early 2000's. It turned out to be a great decision as the fortune 500 company started using Mozilla / Firefox in other internal apps in later years long before it became common place.
I don't have a receipt printer, what helps me is an A4-sized whiteboard with marker when I feel like I'm falling behind my tasks. Also, to use todos sparingly, so they retain their effectiveness. It's actually quite underrated to forget and let go of tasks; what's important tends to stick around in your head and keep you up at night.
The snark was from my personal experience that serial procrastinators ride a particular high when they change their methods, especially if they spend money for something that hopefully solves their issues. It never lasts long, we return to baseline quite fast. This is why there is tons of posts about "here's how I solved my procrastination issue" when they've only used the supposed panacea for a couple of days. What's I find more interesting, is methods that have worked for someone for years. Then one can claim to have found a cure, albeit one that probably only works for them.
In any case, keep writing. It helps a lot if you too suffer from squirrel brain.
From 2020 I use a three column worksheet (Libreoffice in Debian): one row per day. One thin column for the date, the second for pending tasks, the third for the "done" ones. Theoretically I just copy-paste between the "pendings" to the "done", but I also add notes as the day progress, so it is also a kind of personal diary. At the end of the day tasks not achieved get moved to some rows below, and new ones are added as needed. The spreadsheet is configured to start automatically on session login, so I can't forget to see my daily assignment. Not perfect, but (mostly) works for me.
Biggest drawback though is that it's over-optimized for matrix math, that it forces you to think about everything as matrices, even if that's not how your data naturally lies. The first thing they teach about performant Matlab code is that simple for-loops will tank performance. And you feel it pretty quickly, I saw a case once of some image processing, with a 1000x speedup from Matlab-optimized syntax.
Other things issues I've run into are string handling (painful), and generally OOP is unnatural. Would love to see something with the convenient math syntax of Matlab, but with broader ease of use of something like JS.