#toldya censorship still on social media, its bullshit lie if they never gave the people real numbers of invaders - go biuld that wall and seal in 100,000,000
Manchmal lohnt es sich über den Tellerrand hinauszuschauen denn Deutschland prescht nicht voran und sollte mal langsam machen, wie manche Kreise gerne behaupten. Wir hängen in vielen Bereichen hinterher und sollten besser mal die Füße in die Hand nehmen.
Zwei Beispiele:
Dank Power to the Grid" fährt man in #Frankreich 10.000 km im Jahr mit dem E-Auto umsonst.
Dänemark heizt mit Meerwasser und Flusswasser dank moderner Wärmepumpen unschlagbar effizient.
10.000 Kilometer umsonst mit dem E-Auto fahren. In Frankreich geht das seit diesem Jahr. Und die Dänen heizen ihre Häuser mit Meerwasser, unschlagbar günstig. Können wir das auch?
@Björn Schießle es gibt so viele gute Argumente, das weiter auszubauen, wie z.B. "Laut Fraunhofer Institut für Solare Energiesysteme könnte Europa dank dieser Technologie knapp 10 Milliarden Euro pro Jahr sparen."
und "Und tatsächlich ist bei Hamburg die erste Meerwasser-Wärmepumpe in Planung, auch in Neustadt in Holstein. Immerhin. Die Dänen sind uns hier einfach zehn Jahre voraus. "
Wir dürfen nicht auffhören diese Argumente immer wieder zu wiederholen, bis diese Fakten auch in die ängstlichsten Gehirne eindringt und den Weg in eine hoffnungsvolle Zukunft frei macht.
This guide walks you through tuning PCP’s pmlogger service to better fit your needs—whether you're debugging performance issues or running on constrained hardware.
NES mapper programming sounds like shitposts or elaborate pranks. For example, MMC1. Super common chip, used on Metroid, Legend of Zelda, Bionic Commando.
To program it, you simply write five bytes to the upper half of the memory space. The LSB of each byte is added to a shift register and then for the 5th byte the 13th and 14th bit of the address are used to determine which register to program.
this is the kind of thing you'd expect to happen as part of some kind of tricky DRM system but no, the NES's DRM is implemented completely differently (and outside of the view of the CPU).
also there has to be at least one cycle between writes, or it ignores them. This is intentional behavior because of a weirdness of the 6502 where any instruction that modifies memory does two writes, once with the original value and once with the modified value.
emulating this behavior correctly is required for at least two published games, because of course it is
one of the registers you program with this interface is used to select the PRG-RAM bank, which is the 4th bit on the CHR0/CHR1 registers... except for one game, A Ressha de Ikou, where it's the 5th.
it doesn't affect the MMC1, but the way some mappers are implemented on the NES also leads to a fun situation where your code needs to make sure the writes to ROM are only ever "writing" over the same value
this is caused by a bus conflict with the mapper and the CPU confusing the mapper. you try to write a 5 to $8000 to program the mapper, but the mapper has mapped 0 to $8000 and the 0 wins.
so even though the mapper is listening to writes in the entire top half of the address space, you gotta make sure the ROM has the correct values to write over, or it won't work.
every corner of the NES is like this. you look up any section of that machine and it's like "this came in 5 flavors, none of which are compatible, none of which is properly described in any commonly used ROM format. emulating or programming it correctly is difficult. three games depend on this working exactly this way, and another two games depend on it not working this way"
gaming consoles converging towards computers and tablets makes programming them easier (citation needed) but we're losing all the weirder (and bester) aspects of the art.
@lina @Ronflaix @pulkomandy on the one hand, it's cursed, on the other it probably saves a couple dozen gates, so who's to say whether it's bad or not.
@crzwdjk @Ronflaix @pulkomandy There's actually a legit reason for the LFSR (lower max delay path means it can run at a much higher frequency than a binary counter) but it's still cursed...
@lina @crzwdjk @Ronflaix @pulkomandy the details have fallen out of my recollection right now but I think I recently heard about a computer that used a LFSR for its instruction pointer register in order to save carrying. I think it might have been in an old HP calculator?
@lina @crzwdjk @Ronflaix @pulkomandy @foone@digipres.cluboh huh neat. I'm guessing that's extreme transistor saving rather than for speed since nothing it does is performance critical?
In addition to Intel preparing Bartlett Lake S EDAC driver support for Linux 6.17, several other recent and upcoming Intel processors are also set to see Error Detection and Correction (EDAC) driver coverage with this next version of the Linux kernel…
I’m sorry to report that this is unusable on my iPhone. Cannot scroll down to reveal the next button and when I do manage to get the url bar to quit covering it, nothing occurs on clicking. I’m going to have to try on the computer later, but thought you might want to know
Edit: oh shoot, I just realized it isn’t yours . Nevermind!
Vee: ดิจิทัล
in reply to Vee: ดิจิทัล • • •อีกอย่างที่คนมาคือ Fortran ใช้ HEAP ไม่ต้องใช้ผ่าน pointer เป็น array ก็ใช้เหมือน array ธรรมดา เพียงแต่ว่ามีคำสั่งมาช่วยจอง
โดยสรุปก็คือ สำหรับงานที่ Fortran สร้างมาทำ ประสิทธิภาพดีกว่า C และเขียนง่ายกว่า โอกาสพลาดน้อยกว่า
แต่ C ก็มีความเจ๋งหลาย ๆ อย่างที่คงไม่ต้องอธิบายในโพสต์นี้
fortran-lang.org/learn/best_pr…
Allocatable Arrays — Fortran Programming Language
fortran-lang.orgmavhod
in reply to Vee: ดิจิทัล • • •ส่วนตัวแล้วเลือก c เพราะมัน mass นั่นแหละครับ ถ้าอุปกรณ์อะไรที่มันจะรองรับก็ต้องมี c ก่อนภาษาอื่น
ส่วนเรื่องความเร็วเอาจริงถ้าไม่ใช่ส่วนที่ต้องเร็วมากก็โยนไปใช้ภาษา script ที่เน้นเขียนง่ายเอาล่ะครับ
Vee: ดิจิทัล
in reply to mavhod • • •@mavhod ผมก็เขียน C ครับ ถึงเดี๋ยวนี้จะเขียน Rust กับ Common Lisp ในงานเดียวกันมากขึ้นก็ตาม
ก็เลยสงสัยว่าทำไม Fortran ขึ้นอันดับ 8 ของ TIOBE ในค.ศ. 2024 เฉยเลย
mavhod
in reply to Vee: ดิจิทัล • • •Vee: ดิจิทัล
in reply to mavhod • • •