• 0 Posts
  • 47 Comments
Joined 1 年前
cake
Cake day: 2024年6月29日

help-circle
  • I am interested in that battery research though, because charge-cycle wise, only lithium iron phosphate subsection of EV battery chemistry would last even near that long. Lithium ion only lasts 500 cycles before degrading to 70% and LiPo is only 1000. My ID4 could do 420 km on a charge, assuming a LiPo composition, that is 420k kilometers, which is a quarter of what you say

    Battery cells degrade very different depending on how they are used. The cycles you mention are the typical values for charging up to 100% and then emptying them completely. This isn’t how EVs are usually driven. Cells that are only charged to about 80% most of the time live longer. And with large arrays of cells as in an EV battery, the charging electronics also don’t just charge and discharge all cells evenly but can optimize for lifetime. Many EVs also don’t charge all cells to full when the car says it’s at 100% to increase the lifetime (that’s why you sometimes see a “net capacity” mentioned, it’s the amount of energy the battery management actually allows compared to what the cells could do).

    There are also studies that show that typical usage patterns with small charges all the time (from recuperating) and having long rest times (when the car is parked somewhere) results in a much longer lifetime than simulations with constant use had given, e.g. here: https://news.stanford.edu/stories/2024/12/existing-ev-batteries-may-last-up-to-40-longer-than-expected

    Battery chemistry is of course also something there is new developments in, for example CATL is starting production of sodium ion batteries, but AFAIK these are more about cost per capacity than lifetime.


  • I used fzf before atuin, and it works pretty similar, but atuin has a few additional features, as it tracks more information than the normal shell history. For example, you can also search only for commands that you executed in the current directory (great for stuff that is project specific). Or, if you use the history syncing feature, you can toggle search for commands you executed on either any or only the current machine.







  • I remember seeing a documentary about a village in Germany, where many houses were damaged by geothermal plants, caused by water entering layers where it usually didn’t reach and the material there taking in water and expanding. So it probably depends a lot on the local geology and also on the depth. I sadly don’t remember how deep the one in the documentary was.

    I know a few people that got geothermal heating installed for their homes (in Germany), which goes a lot less deep than something intended for whole cities or districts. The one at my friend’s home is 50m deep, and it looks like anything less than 400m is considered “near surface”


  • I don’t think it makes sense to compare those efficiencies, as one is for converting heat to electricity, while the other is for converting sunlight. If you use sunlight to heat water and then use that for a steam turbine, the efficiency is similar to a photovoltaic panel. The efficiency numbers are still useful, but only when they refer to the same starting point for the conversion (e.g. only comparing things that turn heat into electricity).


  • Die kaputten Tags waren im Hintergrundbild (Bilder scheinen allgemein in der Archivversion zu fehlen). Aber die ganzen /* ohne Gegenstück passen auch gut :) Der Satz mit den Nervenzusammenbrüchen ist bei der Seite zu Anwendungsentwickler:innen.

    Falls ich die Straßenbahn noch Mal sehe, mache ich ein Foto, da haben sie die kaputten Tags noch drauf


  • Die hatten bestimmt die gleiche Werbeagentur beauftragt wie die Rentenversicherungn für ihre “Echte IT” Kampagne, da war der Hintergrund auch voller (kaputter) HTML-Tags, bzw. zufällig im Text platzierter spitzer Klammern, weil schaut nach Code aus.

    Leider gibt’s echte-it.de nicht mehr (hatte auch andere Highlights, wie die Beschreibung der Entwicklerstelle mit “nach dem einen oder anderen Nervenzusammenbruch funktioniert’s”), aber bei uns fährt die Werbung noch auf einer Straßenbahn rum.



  • The only thing I still use Postman for at work is when running API performance benchmarks, as I wasn’t yet motivated enough to write a curl wrapper to do such tests and plot the results. Especially when doing things like ramp up etc. it becomes more than a simple for-loop.

    Can someone recommend an existing command line tool for that?








  • Do most packages usually have a manual entry ?

    Usually there are manual pages for commands, for libraries and drivers like libwacom it is less common, and they are not necessarily the same as the package name. Some packages also just have a Readme file or an HTML manual installed under /usr/share/doc or similar.

    When unsure, I often just check the list of files that belong to a package, most package managers can do it. E.g. on Debian-based (i.e. apt using) distros, dpkg -L $packagename will list it, in arch based distros it is pacman -Ql $packagename.