Hacker Newsnew | past | comments | ask | show | jobs | submit | ralgozino's commentslogin

Argentina is a special case.

When inflation is absurdly high like in Argentina, Economy does not make sense any more.

Basic economic assumption are not true and you get things like that or that "spending" is actually "saving".

I don't think it relates.


At federal minimum wage, you make 15k a year. NASDAQ 100 is on average 14.6% per year. It only takes 100k to passively earn more than the vast majority of labor.

We have arrived to the point where capital is vastly more important and productive than labor. AI has only make that worse. Historically, there has been a balance because it was Capital and labor that were required to generate outsized returns. But once you strip out incremental cost with software, and tack on an AI "service" layer, where are the need for employees?

The one saving grace, is that this will also break the VC model. When one youtuber who has 100k subs can spin out 20 different apps a year, we fragment the app space, allowing alot of micro businesses to form around "brands". But "brands" will just be social media influencers.


Do you want to serve already existing files from a directory or just that the backend is a directory on your server?

If the answer is the latter, seaweedfs is an option:

https://github.com/seaweedfs/seaweedfs?tab=readme-ov-file#qu...


I went down this rabbit hole not so long ago too.

There was a discussion open on containerd's GitHub on removing the dependency on the pause image but it has been closed as won't fix: https://github.com/containerd/containerd/issues/10505

Also, if you are using kubeadm to create your cluster, beware that kubeadm may be pre-pulling a different pause image if it does not match your containerd configuration: https://github.com/kubernetes/kubeadm/issues/2020


You seem to be using tip. Switch to using a stable release (1.2 is the latest one) instead if you don't want to be exposed to potential issues.

FWIW I've using tip since the closed beta and never had major issues.


One of the maintainers said in another comment that it will download the formatter (ruff) and it is not embedded. So if you don't use that feature you won't even notice: https://news.ycombinator.com/item?id=44978660


Powerlevel10k is perfect for me: fast, configurable, looks really good. It is not maintained anymore though :( I guess I'll keep using it while it lasts



Thanks, this is a good find


that is not completely correct, see:

The United Provinces of the Río de la Plata (Spanish: Provincias Unidas del Río de la Plata), earlier known as the United Provinces of South America (Spanish: Provincias Unidas de Sudamérica), was a name adopted in 1816 by the Congress of Tucumán for the region of South America that declared independence in 1816, with the Sovereign Congress taking place in 1813, during the Argentine War of Independence (1810–1818) that began with the May Revolution in 1810. It originally comprised rebellious territories of the former Spanish Viceroyalty of the Río de la Plata dependencies and had Buenos Aires as its capital.

source: https://en.wikipedia.org/wiki/United_Provinces_of_the_R%C3%A...


That particular diagram seems to have been generated by https://plantuml.com according to the image's metadata


Yes! The EXIF data includes the full plantuml used to generate it, under the Plantuml tag.

https://www.plantuml.com/plantuml/uml/VPBFQXmn3CRlynGYzzdUXn...


Wow! That's pretty slick. I've only thought of EXIF data in the context of my digital camera.


I believe, though I can't find an unambiguous reference, that a tool or user is allowed to define and populate any XMP/Exif attribute it wants, within the technical limits of attribute/value definition of the relevant metadata. Whether or not anything else can read and make sense of that metadata is a different problem.


wow! didn't even think to look at that! ty!


I don't know if this is a recent addition, but I started recently to use it: `git worktree` is awesome. It let's you have more than one copy of the repository at different points without doing the stash dance.


This is, in some ways, reintroducing something that other source control systems forced on you (and you can see it in one of the videos that Scott linked, about using BitKeeper - Ep.4 Bits and Booze, https://www.youtube.com/watch?v=MPFgOnACULU). The previous tools I used (SourceGear Vault, MS Team Foundation Services) required you to have a separate working tree for each branch - the two were directly tied together. That's sometimes useful if you need to have the two versions running concurrently, but for short-lived topic branches or, as you say, working on multiple topics at the same time, it can be very inconvenient.

Initially it was jarring to not get a different working directory for each branch, but I soon got used to it. Working in the same directory for multiple branches means that untracked files stay around - can be helpful for things like IDE workspace configuration, which is specific to me and the project, but not the branch.

You can of course have multiple clones of the repository - even clones of clones - but pushing/pulling branches from one to another is a lot more work than just checking out a branch in a different worktree.

My general working practice now is to keep release versions in their own worktree, and using the default worktree (where the .git directory lives) for development on the main branch. That means I don't need to keep resyncing up my external dependencies (node_modules, for example) when switching between working on different releases. But I can see a good overview of my branches, and everything on the remote, from any worktree.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: