News for hackers. Stuff that matters.

murdoze

Re:We’re closer to ‘engineering’ blood vessels on Saturday August 05, 2023 @11:24PM (#37018704)
Any chance it cures hypertension? High or low blood pressure?
Re:I Still Use Windows 95 (archived, 2008) on Wednesday May 17, 2023 @04:32PM (#35980895)
Windows NT 3.51 still the best
Re:What Wikipedia Did on Sunday May 14, 2023 @04:03AM (#35936249)
As if Eastern imperialists are any better, if at all
Re:qsort.h – Quicksort as a C macro (2019) on Sunday May 07, 2023 @05:11AM (#35849455)
Agree, but it's nowhere near TASM or even MASM macro processor ;0)
Re:Monoliths Are Not Dinosaurs on Saturday May 06, 2023 @04:09PM (#35844951)
Microservices reveal communication.

I believe we do not have the right tools yet.

Re:The Red Hat model only worked for Red Hat on Wednesday April 19, 2023 @06:38AM (#35626523)
Without this patch QNX was simply not usable, since it had a random race condition in the kernel, which just broke everything.

They have incorporated the patch into some QNX 6.5 version, but we had to deliver the product long before they did this.

Intel Joule?

Never again.

I love Google Docs and Sheets and hate Word and Excel.
I see no value in the Windows desktop. For my tasks.
Re:The Red Hat model only worked for Red Hat on Monday April 17, 2023 @02:49AM (#35597497)
We have discovered a critical bug in QNX 6 kernel in a networking scenario. There is no workaround, since the bug was in the core of their message passing infrastructure - a non-blocking by design kernel call, SendPulse(), sometimes blocks.

It took me 9 months talking to them about this problem until I managed to reproduce it on just two nodes and half a page of code, and record kernel logs that clearly showed a race condition.

We have received a patched kernel in a few days, and it worked like that for a while. This fix was merged into the official release after almost two years.

After that - only Linux, where we can see and fix stuff. No proprietary code and bureaucracy, no "fast, robust and reliable" operating systems.

Travis J Corcoran's Aristillus series. Exact match and more to come.

Roger Zelazny's Roadmarks, if you stretch it a bit.

Re:A CPU Is a Compiler on Sunday March 26, 2023 @02:43PM (#35317916)
The same about the difference between software and hardware
Re:An Apologia of Lazy Evaluation on Sunday March 26, 2023 @10:15AM (#35314676)
Real-time code has high requirements for correctness and execution deadlines.

Which means, w/o deterministic execution Haskell not suitable for a whole niche, where its safety properties are in a high demand. Which is a pity.

Re:Why Take a Compiler Course? on Sunday March 26, 2023 @09:47AM (#35314408)
Chomsky is fine with formal grammars, but completely wrong when it comes to natural languages.
Re:Why Take a Compiler Course? on Sunday March 26, 2023 @09:44AM (#35314373)
In the algebra course one of the assignments was actually to prove that 2 + 2 = 4.

In a ring with a unit.

Re:Why Take a Compiler Course? on Sunday March 26, 2023 @08:29AM (#35313745)
I also wrote a source-generating disassembler for a 8-bit i8080-based Soviet-designed computer, RADIO-86RK — because I wanted to improve software published in the magazine. And explore stuff.
Re:Why Take a Compiler Course? on Saturday March 25, 2023 @04:04PM (#35306690)
FORTH ;)
Re:Let's write a setjmp on Sunday February 12, 2023 @06:01AM (#34761892)
One of the largest C++ projects I worked on was compiled with exceptions disabled (-fno-exceptions).

Still in production, for 20 years now.

Re:Sussman Explains the End of SICP on Sunday February 05, 2023 @04:32AM (#34663356)
Like DOOM?
Re:What the hell is Forth? (2019) on Sunday January 22, 2023 @09:14AM (#34477575)
Indirect threaded code is quite a universal program representation.

We used to have our Forth-like system back in 1994, with a virtualized NEXT point, so we had execute, interpret, compile and two link stages behaviors for each word. This allowed produce making an optimizing linker, which produced very tiny .COM-files. I still have source code for it.

I think this idea can quite easily be taken to the extreme, and allow adding things like - type checking - debugging - SSA IR generation (say, for LLVM optimizer) - lots run-time checks (for tests)

So I believe a Forth system can be made quite safe.

Re:Video games made in the USSR (2020) on Tuesday December 13, 2022 @02:48PM (#33974693)
Dare to substitute Holocaust for Holodomor in this context?

If, of course, what you're telling is true.

Re:Video games made in the USSR (2020) on Monday December 12, 2022 @04:33PM (#33960700)
Collateral damage
Re:Video games made in the USSR (2020) on Monday December 12, 2022 @04:30PM (#33960643)
W/a the Polish? Warsaw used to be part of your empire.

Or the lucky bastards are in NATO already, out of your reach?

Re:Video games made in the USSR (2020) on Sunday December 11, 2022 @06:20PM (#33948737)
Have you heard of the Address Programming Language?

https://www.youtube.com/watch?v=ZsLlYY50zec (English subtitles)

https://www.youtube.com/watch?v=JxgFR_tK0iA