It compresses the indexes pretty well but don't forget to turn off postgres' own copy on write mechanism

I'm looking at the newest versal chips from Xilinx/AMD for a new design and buying a SoM & designing our carrier board could fit the bill nicely. We're still very early in the design process, we need to get prices for the chips too to see if it's an idea worth pursuing.

While the article that follows is well written, the original title feels very vague and clickbaity for me. Like "you won't guess what's wrong with this !!!".

I felt this give a much better idea of the content (technical problems that exposed people problems) and give chance to people that don't want to read about kernel politics / drama a chance to skip the article.

Comments URL: https://news.ycombinator.com/item?id=42202165

Points: 22

# Comments: 5

IIRC they mainly put power hungry compute nodes for the clusters in this new datacenter and I remember that servers full of GPUs had crazy power draw. The water then goes through an heat exchanger to help generate hot water to heat the campus and for the taps.

The mean could be a 5$ wrench, hacking into your devices or plain old surveillance

It's fair to assume Putin would try to influence the elections in trump's favor as he would have been beneficial for him.

The Ukraine invasion would have been much easier if trump had been relelected, finished pulling out of nato and kept the more isolationist policy that was in effect during trump.

IMO trump was also doing a lot of damage to the US and it's position on the world stage which is also beneficial for Putin.

You basically run the base load in your own data center and the surges go to the cloud. My university is evaluating this because sometimes you have multiple labs that need a lot of compute resources at the same time and local compute cluster has finite capacity.

For this we had to calculate forces to animate some kind of polygon with a lot of joints and we could not just call sycipy from the taichi code. I had to implement a very dirty polynomial equation solver in taichi for the demo

I just assumed that the latest bios was good and the server happily bricked itsefl

It can be voluntary or not but dismissing it like that seems strange to me. It's not because it doesn't leave physical scars that it can't cause trauma.

It guides you through making a Gameboy emulator step by step. When I did it I remember that something that was a bit frustrating is that you had to do things a certain way that only made sense much later when other pieces of the puzzle fell into place

You can probably find a solution with what you already now (as a junior programmer) as most problems programmers have to solve are not that hard but you may completely miss a better solution because you had no idea it was possible. I may be fine but you may also lose a lot of time later because it wasn't.

I agree that it's possible to self teach almost everything in CS but the point of university is to speed up the discovery of CS from scratch and have solid foundations. You certainly don't know everything graduating university but should now where to look when you have a problem imo.

Vcs integration and merge were also a big pain so most of the development was done on a single computer in the lab by many people.

The hardware that runs the LabVIEW code is solid tho and once you wrestle LabVIEW into doing what you want it works well

I used LabVIEW to code the control / data logging of a prototype racecar and the hardware only broke once when we probably zapped it with a nasty ESD or reverse polarity connection somewhere. We never figured it out and didn't ask when we sent the part to be repaired.

Programming in LabVIEW is something I wouldn't wish on my worst enemy though. It's extremely hard to debug and time consuming to refactor. I always felt that I was 10-50x slower than when I would code in a standard text-based programming language. Working collaboratively also put you in a world of pain because, at least when I used it and I think it's still the case, LabVIEW doesn't support git natively so you have to use an external tool. They have a tool to merge / diff their proprietary binary files but the UX is terrible and I think even if they really tried to do something good, diffing diagrams (which is what a LabVIEW program is IMO) is going to stay hard.

From my experience the people that code in LabVIEW are not software engineer and I had discussions where I was arguing that yes the channel feature is broken but that's not a reason to put all the variables used to communicate between components in a single global variable file for example.

But once you fought against the language long enough and have something that works you can be pretty sure it will keep working forever.