4,959 karma · joined October 31, 2013
This sounds weird to me... Why not assume that all jumps need to be long to start with (so that the code is valid), then relax them to short jumps during an N-pass optimization stage- so that you get the smallest possible code?
I would say that 2005 was peak car, except 2000 is slightly better because they had not yet gone nuts with serialized components.
(another reason is that direct inject fuel injection hadn't taken over yet, it's a disaster)
Always provide a DOI-style link, for example: https://doi.org/10.1088/0029-5515/30/2/001
These can be easily changed to actual working links with a simple browser substitution rule: replace the "doi.org" with "sci-hub.se" or whatever.
Would it be rude to print the link "https://doi.org/10.1016/0005-1098(83)90046-8" but actually link to https://sci-hub.se/10.1016/0005-1098(83)90046-8 when you click it? :-)
The DOI is key, then you can use a browser extension to do it, for example: https://github.com/natir/Redirector_doi_sci-hub
I'm pleased that the references to other ACM papers do work.
But try to click on this one:
Bainbridge, L. 1983. Ironies of automation. Automatica 19(6): 775-779;
https://pdfs.semanticscholar.org/0713/bb9d9b138e4e0a15406006...
Fail! No way to read the paper without paying or pirating by using scihub (and even if you do get the .pdf via scihub, its references are not hyperlinks). This does not help humanity, it makes us look like morons. FFS, even the music industry was able to figure this out.
https://www.idsa.org/profile/sassano/
Well there's a whole group, but Camillo is the guy I worked with when I was there.
The fast-paced startup is really the hack, combining the energy of youth with the ego-mania of their founders. Ask yourself, is it healthy?
Anyway, IBM's customers tend to be other fortune 100s and governments- basically other similar organizations, and my experience was that we took care of them pretty well. The products were not pretty (no Steve Jobs-like person to enforce beauty), and rather complex due to all the enterprise requirements. But they were quite high quality, particularly the hardware.
It reminds me of another IBM IT rule: they wanted your chat history (and email) older than two years to be all deleted for legal liability reasons. It was important to save your sametime chat history (an XML file) and export your email periodically if you wanted to keep this stuff.
This was actually better than Slack in one way- you could grep the files for things, and not have to rely on search within the tool.
Hint: by all means possible, make sure you are not the owner of (or manager of the person who owns) any assets beyond your personal laptop. If, for example, you end up being the owner of all the development and test servers of the original company, then it will become your responsibility to ensure that each OS (of each LPAR of each VM) is security compliant, is running the end-point asset manager, and has up to date OS patches, that the DASD is encrypted, and you must periodically show physical proof that the asset still exists and indicate where it's located- photos of assets tags or whatever. It will be your responsibility to dispose of the asset (with all associated paperwork) at the end of its life.
It helps if such machines are not actually on the 9. network, or are behind an internal firewall (then they don't care about the security compliance as much).
So how about: calories * digestion-efficiency - calories you personally need to expend to prepare or acquire it. The higher this number, the more processed is the food. So cane sugar is very bad, unless you personally harvested it.
Bad news for highly paid programmers.. basically all food should be considered ultra-processed since no physical labor was needed to acquire it.
>That's when I knew Arm would eventually eat x86: in 1989. It's finally happening now.
I had kind of the reverse feeling: when the 486 came out, I knew those expensive SPARC and MIPS workstations were all doomed.
https://www.ka9q.net/code/ka9qnos/
This worked in DOS, but was easily ported to Linux.
As far as DPMI: I used the CWSDPMI client fairly recently because it allows a 32-bit program to work in both DOS and Windows (it auto-disables its own DPMI functions when Windows detected).
; Fill memory with backward sequence
macro fill n
word n
if n != 0
fill n - 1
endif
endm
So "fill 3" expands to:
word 3
word 2
word 1
word 0
There is no way this was not known about when C was created. They must have been burned by recursive macro abuse and banned it (perhaps from m4 experience as others have said).The other assembly language feature that I missed is the ability to switch sections. This is useful for building tables in a distributed fashion. Luckily you can do it with gcc.
I've been meaning to update my toolbox to at least a pipelined processor of some sort (to up the IPC rate to at least 1), but so far just had no strong need. For applications that really need CPU power, I use SoC FPGAs like Zynq.
https://turbo51.com/download/Building-an-Optimizing-Compile-...
https://maxima.sourceforge.io/
I used it when it was called Macsyma running on TOPS-20 (and a PDP-10 / Decsystem-20).
Text interface will require a little learning, but not much.