skysight-inc/HackerNews huggingface dataset:
An investigation into whether NASA's public messaging jived with their internal communications seems like it could be a good idea, since we know previous disasters were in part caused by NASA feeling external pressure to perform even while their engineers were freaking out internally.
CachyOS August 2024 Release: Nvidia Open Module, Cosmic, Secure-Boot, and More
In that case, you can use "-t ext4" (or whatever filesystem type you use) to show only disks formatted with this filesystem type.

On my machine, none of the snap/tmpfs/efivars stuff shows up:

user@hostname:~$ df -ht ext4
Filesystem Size Used Avail Use% Mounted on
/dev/sdc 1007G 49G 908G 6% /
I agree that Kate is a good code editor. I have tried more than a year ago when I still use KDE Plasma (now switched to Gnome). Honestly, I am happy that there is at least one GUI Code Editor from a big community that actually on par with some popular code editor (VS Code, Sublime, etc). Because I see that most code editors made by the Linux community are always lacking in features when compared to other popular code editors.
However, there are some things that make me not use Kate as my daily editor. One of them is the file browser feature which I find more complicated than its alternatives in Sublime Text or VSCode for example. In addition, the small number of plugins for Kate is also one of the reasons I do not use it.
This is partly true, but there is a caveat: it's 10 lines of finished. In order to get there you would write and edit this piece of code many times over until it reaches the desired quality. And VIM is meant for "editing" code.
I was in Grand Teton national Park last week and was looking at the sky to view the Perseids meteor shower, and I just saw chains of these Starlink satellites constantly moving across the sky. They look like tiny little stars, moving smoothly in an equally spaced out line.
Thomas Stanley, 1st Earl of Derby, KG would approve.
Hmm... This might be where my process differs, I guess?

In my normal process (not exploratory work), I don't write a single character until I'm sure of how the thing I'm making will fit into the overall design (such as the API it will have, how it will interact with other components, its placement in the overall architecture, what its responsibilities are and how to structure it so as to minimize potential confusion and make what it is doing clear to a reader, mentally walking through code paths to make sure other components can use it as intended, etc). All of that happens in my head, not in an editor (although I might have a few notes jotted down if it's a big change or a whole new feature).

Then, once I know exactly what I intend to write, I just dump it all down into the source files. 80% of it is already "finished code" in that I won't be changing it again unless I've made a serious design error.
> Real estate is an unusual case, because the really isn't anyone with a monopoly on real estate. The supply constraint comes directly from the government through zoning rules. We effectively have a cartel whose board of directors is the zoning board.

It happens basically everywhere, even when the rules are different. If I understand correctly, the primary limit in the UK is there's not enough builders, which is not to say the government isn't in the way as that's despite it also having constant planning issues with regard to the "green belt"; likewise in modern Germany, my understanding is not enough builders (and again yes the government could be better because bureaucracy is very slow, but they're not the limiting factor); likewise DDR (not even trying to be a free market) where the government was organising the construction work and trying to do it cheap and fast but there still wasn't enough.
Affordable High-Throughput Protein Purification
Try Spek [0]

It's a popular tool for verifying the quality of music downloaded via P2P platforms. Re-encoding YouTube rips is popular - especially bootleg tracks - and this helps weed them out.

[0] http://help.spek.cc/
They decided to keep the code on the local machine, but the language server on the remote one. That seems like a recipe for inconsistency. You only get relevant results from your language server once your code has synced.
very much recommended practice by many with, of course, caveats and situations where perfect is the enemy of good, etc, etc

e.g. https://trunkbaseddevelopment.com/monorepos/
Right, sorry. My only defense is that I just woke up half-dead
But they're great at financially justifying and ordering hits on whistleblowers.
Blaming Agile for software stagnation puts the wrong villain in the wrong play
I think discussions like this mostly miss the point.

Obviously you want basic, stable and well documented functionality in your programming language.

But JavaScript does simply not have it. So how do you solve this dilemma?

1) the everything is an import way: use NPM and create a dependency hell from hell (requires Satan) made by Lucifer (same as Satan but different) using lava with fire (requires node v <= 9.42.0815) and heat (deprecated) requiring brimstone (only node v > 10.23) with a cyclic dependency on the Devil (incompatible with Satan).

2) the Golang way: copy paste ALL the things, only for your co worker to copy paste all the things again, only for your co worker to copy paste all the tings again, only for your...

Way 1 wastes your time when it breaks (sooner than later) but is necessary for non trivial functionality. Way 2 works only for trivial packages so choose your poison.

JavaScript (apart from not being a good programming language in general) is sorely missing a std lib.

One could argue that having a bad std lib is even even worse (PHP anyone?) but it is really hard to decide.

Sadly JavaScript is just unfit for the purpose it is being used for.
I built an open-source Cluster Headache Tracker from my hospital bed
As a cluster headache sufferer and developer, I found existing tracking tools inadequate. So I built a new one, coding between attacks while hospitalized. Here's what I learned about innovation, open source, and turning adversity into opportunity: https://paolino.me/cluster-headache-tracker/
At 44 years old and with 22.5 years of experience I will now go to the corner weeping that I have met maximum 3 people like you in my entire life.

You people apparently don't dwell in Eastern Europe or even most of Europe (I have been around). It's a meat grinder here.
Why? There are many innocent applications that consume lots of virtual memory with no intention of using it. Sometimes sparse algorithms call for that sort of thing. It can be a nice crutch when you're in a pinch for time. A good example of a tool that does this is TSAN. It gobbles up virtual address space, which is practically free, thanks to the magic of modern MMUs. That's too powerful and good a thing to need to give up completely.
This concept would possible be used to get around the stalking features that Apple et al has implemented.

Ex: Get N donor tags. Have it cycle through the N tags every 24/N hours. Therefore, to apple (/ device tracking), the "stalkee" is never being followed by a single tag for an extended period of time.
The accountants can’t be bothered because your comment isn’t even using basic terms correctly.

Your comment suggests that reinvested cash is being "hidden" as expenses, but in reality, these reinvestments are usually recorded as capital expenditures (CapEx) rather than operating expenses (OpEx), depending on the nature of the investment. While CapEx can be depreciated over time, it is not typically expensed immediately in the way operating costs are.

The implication that companies can completely avoid taxes by reinvesting is misleading. Even though reinvestments may reduce taxable income through depreciation or other deductions, this is a legal and common accounting practice, not necessarily an attempt to "hide" profits. There are also tax laws in many jurisdictions which limit the extent to which such deductions can offset income.

Your understanding also conflates profit with cash flow. Profit is an accounting concept that reflects the net income after all expenses (including taxes). Cash flow, on the other hand, reflects the actual cash generated by the business. Reinvesting profits does not "hide" cash flow but rather allocates it to future growth.

Companies don't simply choose between declaring profit and reinvesting to avoid taxes. The decision to reinvest is often driven by strategic goals, such as expanding operations, developing new products, or acquiring other businesses.

Reinvestment reduces the company's taxable income and thus the taxes owed, but it does not eliminate taxes or "hide" the profits. The company benefits from reinvesting by potentially generating more revenue in the future from the new product, which should generate more tax revenue down the road instead of restricting growth now.

Here is an approximation of your comment translated from accounting into software development, minus the part where you misunderstand essential terms:

> It’s ridiculous that software developers waste so much time writing tests for their code. If the code is written correctly in the first place, you wouldn’t need tests at all. Instead of wasting time on tests, developers should focus on just writing perfect code from the start. It’s clear that the whole idea of ‘unit testing’ is just a way for developers to justify their jobs and take longer to finish projects. Shouldn’t we just hire better developers who don’t need to write tests?
My only gripe with Sublime Text is that they've changed to a "semi subscription" license model, where licenses expire after 2-3 years, and you essentially need to buy it again after that time.

It's essentially the same model used by other editors like the Jetbrains suite, but unlike Jetbrains, updates to Sublime Text (and Merge) are few and usually don't contain much other than bugfixes.

I've faithfully purchased Sublime Text licenses since the initial versions (switched over from Textmate), but as my ST4 license recently expired, it has forced me to review just what i get for the money i pay.

ST was excellent when it first arrived, and it's still one of the fastest loading editors out there, but pretty much every other editor has more or less caught up, including free ones like Zed and VSCode, making a recurring cost harder to justify.
I literally don't know anybody else who would read this feature and also has Signal. ProPublica said they added a signal contact number just for this feature -- I couldn't seem to find that number in Signal. I was wondering if it my issue or theirs. I figured reporting it here on the site might be useful. Apparently I was wrong.
ha, Torp! Nice!

But yes, is a mix/jungle of options. But I find fascinating that paying with cards has a far more adoption than some places in western world.
There are really only a handful of approaches to preventing this kind of supply chain attack, and all come with tradeoffs (ranging from the infeasible to the merely impractical):

- Don't take any 3rd party dependencies. Build everything in house instead. Likely only possible in niche areas of government/defence where sky-high budgets intersect with intense scrutiny.

- Manually validate each new version of every dependency in your tree. Also very expensive, complex vulnerabilities will likely still slip through (i.e. things like SPECTRE aren't going to be caught in code review).

- Use firewalls/network security groups/VPC-equivalents to prevent any network traffic that isn't specifically related to the correct operation of your software. Increasingly hard to enforce, as our tech stacks rely on more and more SaaS offerings. Needs a properly staffed network admin to enforce and reduce the pain points on developers.

- Network isolated VMs/containers that can only talk to a dedicated container that handles all network traffic. Imposes odd constraints on software architecture, doesn't play well with SaaS dependencies.

In practice you run with whatever combination of the above you can afford, and hope for the best.
I think the "uncle that doesn't know anything but claims to be an expert and will tell you his opinion" is the best description of LLMs that I can think of. They will say anything confidently without knowing anything.
That's just for show.

A grid is visible in the background of the drawing. Such a grid is used to set up the initial outlines, by copying it from the reference photo with a grid drawn on top of it (typically done in Photoshop). Other artists use a projector to trace.

As another commenter mentioned, the depth of field removes any doubt that a photo is used as a reference.

Picking up and placing back the watch to see details would constantly change the lighting, especially in the details. It is impossible to get such a level of detail by "drawing from nature", even in studio conditions.

It's not a coincidence that paintings only became more realistic after the invention of photography.
> They don’t work from your local development env and also work in your CI env.

This is one of the biggest selling points of bazel-like build systems. Like to the extent that, for some changes, bazel can say "even though you changed this source file, I can be 100% certain that that change didn't affect any tests and so I will not run them"
Some time ago I read an article explaining that initially games used to sell upgrades which were making the player stronger in multi-player games. The net result was that the games were loosing players because that mechanic was seen as unfair (pay to win).
So they switched to aesthetics enhancements only and that resulted the correct strategy to have in game sales and not loosing players.
Unfortunately cannot remember further details to prove this memory, sorry.
By the time you need append-only job statuses it's better to move to a dedicated queue. Append-only statuses help but they also make the polling query a lot more expensive.

Deleting older rows is a nightmare at scale. It leaves holes in the earlier parts of the table and nerfs half the advantage of using append-only in the first place. You end up paying 8kb page IO costs for a single job.

Dedicated queues have constant time operations for enqueue and dequeue which don't blow up at random times.
There is experimental support for arbitrary executables:

https://worker.graphile.org/docs/tasks#loading-executable-fi...

But you can use a thin JS wrapper to make shell calls from Node. Slightly inconvenient, but works well for my use case.
> what about the site selection, and all the legal and administrative hurdles needed to actually get permission to build a new cell tower somewhere

It depends if they're building new towers or just upgrading existing ones. Doing a like-for-like swap can presumably be done entirely by the vendor, setting up new sites indeed needs a bit of work, so maybe whatever little technical staff they have handles that (or maybe even that is outsourced too).

> How about MVNOs and eSIMs?

When it comes to MVNOs it depends whether the MVNO runs (at least parts of) their own infrastructure or is just white-labelling the upstream carrier's one.

In the former case they can indeed do it, but the company culture challenges still apply. You need to hire and retain good engineers, something I'm not aware of any telecom company actually prioritizing. Meaning they too will eventually end up with a ball of mud in a few years.

In the latter case they're just reselling the upstream turd with a bit of polish. If the upstream ball of mud can't manage eSIMs, they can't either.

> I've only done the travel eSIM thing

I wouldn't recommend relying on these. You're getting bottom-of-the-barrel capacity that (even if it works) is so slow that you'd be lucky to even use up half your data cap. You are always roaming and your data is tunnelled through what feels like some dial-up modem in some shady warehouse. These are a scam.
Dead austronauts would hurt Biden/Harris 10000x more.
I'd suggest you revise your competitor analysis. Bazel definitely has a test command that with remote execution and caching absolutely allows you to run entire test suites in seconds* both locally and in CI eg. https://blog.aspect.build/typescript-with-rbe
The current outlined plan does not require an extra SpaceX launch, so that argument doesn't make sense.
It depends by which metric you mean "better". For a collection of executives that cost in the order of six figures an hour, it makes sense to put them on a plane and get them there as quickly as possible, even if it sometimes means chartering a jet. Is this stupidly polluting? Of course. Does this figure into the incentives? Not really. Could it figure into the incentives if clean fuel was available? Plausibly.
I have a friend a bit younger than you born in rural ireland; when she was a child her phone number was 8.
I like someone who is capable of making something out of "nothing".

If that was an executive I was working for, neither one of us might be tasked with starting with nothing at all any more, but if the proven capability is there then the amount of leverage when starting with truly abundant resources will be through the roof.

If I'm the one operationally leveraging the resources under nominal conditions, and who I'm working for doesn't have deep enough experience handling much more extreme leverage themself, they're never going to fully appreciate the upside I would like to bring to the shareholders.

It doesn't make sense for me to be working for someone that doesn't have some kind of core background like that, or they'll never be able to grasp but a fraction of the possibilities that can't be realized any other way.

Another key factor is integrity. It has got to be there in everything set out to be accomplished, and ideally you're adding true value more so than extracting it.

But what I really find interesting and makes me want to work for somebody, is when they are a sharp enough business operator to get it all done without any disadvantage to anyone else at all.

We all know how rare that is but also that it can be done, so why not?
Well, maybe people should not own guns. At all. Any gun, let alone "a collection".
More user-friendly option, can scan the whole library instead of having to load files one-by-one into Spek: https://fakinthefunk.net/en/index.html
Perfectly humanlike
The problem with overcommitting beyond the sum of RAM and swap is that userspace processes can't protect themselves against the kernel's lies. You allocate memory, handle the result, access the address space and someone dies. The Linux default behaviour is an insane over-optimisation, but without it forking large processes becomes painfully expensive. The proper solution is to spawn directly through suitable system calls instead of the traditional fork() + execve() way.

Imo a good compromise to this day is to overcommit RAM with swap as fallback for correctness even if performance falls of a cliff if you use it. All of that is on top of resource limits and usage monitoring.
> I swear someone in Google's exec team is going out of their way to make Google products suck.

This may be closer to the truth than many people think. In an analysis from 3 months ago [1,2] it was alleged that Google search sucks so badly not just because of AI and whatnot, but because control of the search division was finally handed to the revenue people in 2019, who promptly rolled back important spam filtering in an effort to drive up searches. Deliberate use of dark patterns to increase "user engagement" is nothing new, of course, but I was still surprised that Google would sink this low. Don't be evil, bwa-ha-ha-ha.

[1] https://www.wheresyoured.at/the-men-who-killed-google/
[2] HN discussion: https://news.ycombinator.com/item?id=40133976
Typically you have owner files or similar in the subprojects that are read by automation tooling and humans alike
https://github.com/zed-industries/zed/pull/16349
> Performance-wise e.g. VictoriaMetrics' prometheus-benchmark only covered instant queries without look back for example the last time I checked.

prometheus-benchmark ( https://github.com/VictoriaMetrics/prometheus-benchmark ) tests CPU usage, RAM usage and disk usage for typical alerting queries. It doesn't test the performance of queries used for building graphs in Grafana because the typical rate of alerting queries is multiple orders of magnitude bigger than the typical rate of queries for building graphs, e.g. alerting queries generate the most of load on CPU, RAM and disk IO in typical production workload.

Please file a feature request at https://github.com/VictoriaMetrics/prometheus-benchmark/issu... to add the ability to test resource usage for typical queries for building Grafana graphs if you think this will be a good feature.

> I am also not aware of VictoriaMetrics giving back anything to the Prometheus ecosystem (can you maybe link some examples if I am wrong?)

Sure:

- https://github.com/prometheus/prometheus/issues?q=author%3Av...

- https://github.com/prometheus/prometheus/issues?q=author%3Al...

- https://github.com/prometheus/prometheus/issues?q=author%3Ah...

> As per recent actual examples, here's a 2 submission of the same post bashing project in the ecosystem: https://news.ycombinator.com/item?id=40838531

This submission posts a link to the real-world experience of long-term user of Grafana Loki. This user points to various issues in applications he uses. For example:

- Issues with Loki restarts - https://utcc.utoronto.ca/~cks/space/blog/sysadmin/GrafanaLok...

- Issues with structured metadata in Loki 3.0 - https://utcc.utoronto.ca/~cks/space/blog/sysadmin/GrafanaLok...

- Issues with single-node Loki setup - https://utcc.utoronto.ca/~cks/space/blog/sysadmin/GrafanaLok...

- Issues with Loki logcli command - https://utcc.utoronto.ca/~cks/space/blog/sysadmin/GrafanaLok...

- Issues with Grafana Loki data compaction - https://utcc.utoronto.ca/~cks/space/blog/sysadmin/GrafanaLok...

- Comparison of Grafana Loki vs traditional syslog server - https://utcc.utoronto.ca/~cks/space/blog/sysadmin/GrafanaLok...

As you can see, this user shares his extensive experience with Grafana Loki, and continues using it despite the fact that there is much better solution exists, which is free from all the Loki issues - VictoriaLogs. This user isn't affiliated with VictoriaMetrics in any way.
> Won't be surprised to see that many would probably need a safari map or README documentation in every single folder to navigate a repository as large as stripes.

No different to having thousands of smaller repos instead.

I personally dislike monorepos, for very niche, in-the-weeds operational reasons (as an infra person), but their ergonomics for DX cannot be understated.
Has anyone made the transition from VS Code to NeoVim or Zed and succeeded / recommend it?

Years ago I saw a colleague operate as an absolute beast using VS Code with vim bindings and it was impressive to watch.

But I've never watched anyone code in vim/emacs etc and felt it's a more effective editor than vs code.
Also using a monospaced font for both the written text and command line output is certainly a choice. I get that it is often an aesthetic choice, but given that a blog post is written with the idea to be read, one I don't think is a particularly good one. Although the last time I made a remark about that on HN it became clear to me that a lot of people don't see the issue. Even if there are decades worth (at this point) of research that makes it clear that a sans serif font (or even a serif font on modern displays) works better for readability. ¯\_(ツ)_/¯

It is clear that the author is very explicitly going for the aesthetics of a terminal, given that all formatting of the text is ASCII based down to the line length being hard coded as if we are dealing with a hard limit of columns.

Personally, I'd prefer something more like this: https://www.creesch.com/dump/img/img_66c3127604542.png.
Public Key Infrastructure/Enabling (PKI/PKE)