HNHacker News
TopNewBestAskShowJobs

nickelpro

2,445 karma · joined December 21, 2019

https://vito.nyc
submissionscomments
nickelpro··on Depending in Common Lisp – Using the CLOS dependent maintenance protocol (2022)
Yes, of course, that's why I brought up Fukamachi's work to point out that things can be better. It is possible to forego the mechanisms of interactive-development that intersect with image-based development, but that requires lispers to change how they've done things for generations. Neither the ecosystem or culture is aligned to it.

Ultralisp + Roswell + qlot produces something resembling a modern development workflow, but it is swimming upstream. ASDF is totally inadequate as a build system, it makes CMake appear terse and elegant by comparison (why on God's green earth is the present working directory not searched for the package I'm trying to build, like every other build system to ever exist?). Documentation and tutorials assume you're pulling things down with quicklisp and evaluating in the REPL. /r/Common_Lisp posters wonder why you would even want to use dependencies at all when you could just use [incomprehensible, brittle, unhygienic macro].

It has become possible, in the last two years or so, to produce sane common lisp workflows that operate somewhat like other modern environments. I very, very rarely encounter that usage in the wild. I would like nothing more than for the Common Lisp infrastructure to produce environments and workflows as obvious, intuitive, and correct as what every undergrad using Python in VSCode has today. I do not think the broader language ecosystem is there yet.

nickelpro··on Depending in Common Lisp – Using the CLOS dependent maintenance protocol (2022)
Image-based development is a dead end. Whatever one's feelings are about interactive development, any system that relies on information that was typed into a REPL three-months ago and is now only stored in the binary state of that REPL and nowhere else is totally insane as a production product.

And this is unfortunately how most Lisp tooling still works. Quicklisp and friends assume you're fulfilling external dependencies by evaluating things in the REPL. This is without mentioning that the entire ecosystem of external dependencies ships monthly as one monolithic group. Versions? Lockfiles? Nah dog, give me "October 2023".

The only person trying to fix this if Fukamachi with Roswell and qlot, and those are very recent projects (in the scale of Common Lisp), that have gotten irrational amounts of resistance from lispers. C now has project-local dependency management thanks to vcpkg/conan/Spack/etc, but lispers still insist that ~/common-lisp is good enough for every single project they will ever work on.

nickelpro··on Only bad poems go viral
There are certainly differences in medium. Lego sculptures and interpretive dance are different things. But within a medium? Genre? The composition of the expression? There are no real lines, only imagined ones. What is the difference between an interpretive dance and a walk? A shuffle? Falling down the stairs with elegance? You can try to come up with rules but there will be someone who stands completely still in a dark theater just because you said they couldn't, and calls it a dance. And it will be a dance, a kind of negative space of dance.

You've already accepted that you can't draw any definitive lines, that there is no specific criteria by which you can say a given work does or does not belong to a certain taxa of expression.

Now we're just bartering over how uncomfortable with the vibe you're willing to be. You can't say why Eminem isn't country because you can't really say what "country" is. For any single definitive criteria we could come up with a counter example, so none of it works. You just know it doesn't vibe.

I have no criteria, I recognize that such categories are totally arbitrary and useful only in a very limited scope of suggesting a general set of characteristics in communication between like-minded people, but ultimately hold no exclusionary or binding power.

And frankly, the bartering isn't an interesting discussion. If you want to say the Beastie Boys aren't jazz, more power to you, I probably agree. If you want to say meter is a requirement for poetry, again, whatever floats your boat, but recognize that's just your vibe, your personal ephemeral understanding. These things aren't useful or productive criticisms because they don't have any inherent value.

If someone else says that, in fact, Eraserhead is a RomCom nothing is gained by saying they're wrong other than your own smug satisfaction that you have a superior vibe-o-meter. We can't derive further facts from that rejection. We can't say, "Well we know definitively it is not a RomCom, and therefore it will definitively will or will not possess any of these characteristics".

The only purpose of genre is communication between people who are vibing on the same wavelength. It isn't an objective fact of the universe, it is itself a human expression, saying as much about the taxonomists as the subject of their taxonomy.

nickelpro··on There isn't much point to HTTP/2 past the load balancer
For Go, net/http is not something you should expose to the public internet, there's no secret sauce in there. It will just die to the first person to hit it with a slowloris or other DOS attack. Same with the common C++ options like boost.beast unless you're writing the logic yourself (but why bother? Just reverse proxy).

I'm unfamiliar with the common rust frameworks for http, but find it unlikely the situation is very different.

nickelpro··on There isn't much point to HTTP/2 past the load balancer
Most of them have a disclaimer in their deployment or tutorial docs, some with more strong language than others. Again, nothing bad happens if you don't, we don't write memory vulnerabilities into these servers. You are just far more vulnerable to DOS attacks.

* "We strongly recommend using Guincorn behind a proxy server" [1]

* "As a general rule, you probably want to: ... run behind Nginx for self-hosted deployments." [2]

* "A reverse proxy such as nginx or Apache httpd should be used in front of Waitress." [3]

For some, like uWSGI, they don't even want to talk HTTP (uWSGI supports its own protocol) and it's just assumed you're using a dedicated webserver to talk to public traffic. [4]

[1]: https://docs.gunicorn.org/en/latest/deploy.html

[2]: https://www.uvicorn.org/deployment/

[3]: https://flask.palletsprojects.com/en/stable/deploying/waitre...

[4]: https://uwsgi-docs.readthedocs.io/en/latest/tutorials/Django...

nickelpro··on Only bad poems go viral
I would accept that medium can be well defined. We can say an oil painting is not a macaroni sculpture with a high degree of certainty. Within the medium though, no I don't think you can make such defining lines in genre, in categories of artistic composition.

I would say "evokes feeling" is absolutely a characteristic of a poem. Slam poetry is often characterized by the performance, the visceral experience, more than anything about rhythm, rhyming, or meter.

Epics [1] are one of the oldest forms of poetry. A 70000 word narrative can not only be a poem, such works are some of the oldest artistic expressions in human history.

> Because to you deign it to be what?

A poem. And my friends understand what I mean when I say that. That you don't understand is hardly my concern, like I said I find this amusing, convincing you is not a goal of mine. The purpose of such categories, their only value, is to be understood by the communities which use them. Whether David Bowie's 1980 album Scary Monsters is art rock or post-punk has no real bearing on the album itself, no value beyond being understood by those discussing it.

We can take this one step further, and say that the community of milesrouts rejects such labels and has a different understanding of these words, a different set of values they choose to express, and this too is a valuable thing to recognize.

[1]: https://en.wikipedia.org/wiki/Epic_poetry

nickelpro··on Only bad poems go viral
If you want this post to be a haiku, and you publish it in your collection of haikus so labeled, I would be hard pressed to argue otherwise. Fountain [1] is a sculpture because Duchamp placed it a fine art exhibit and labeled it so ("by the artist's act of choice").

Surely, this post is an avante garde example, defying most of the characteristics associated with haikus in form. It can definitively be said to not have the 5-7-5 pattern of traditional Japanese haiku, but in fact all English language haiku deviates from traditional Japanese haiku (a 17 on haiku in Japanese is typically only 12 syllables (note the "typically")).

So you're doing something new and experimental with the form. We can debate the artistic merit, the value of such an experiment. We can argue about what you mean by labeling this a haiku, what message you are trying to convey in the experience of the post. We can even question the sincerity of your motives. But I don't think it's totally invalid, I don't think it can be rejected in the same sense we can reject 2+2=5.

[1]: https://en.wikipedia.org/wiki/Fountain_(Duchamp)

nickelpro··on Only bad poems go viral
These are elements of genre, any taxonomy of human expression naturally escapes the ability to be concretely defined. You can no more give a succinct, definitive differentiation between prose and poetry than you can between Rock&Roll and Pop music, or between Modernist and Expressionist painting.

To wit, you'll find there's a large amount of literature about "prose poetry", the most well known form being free verse. The idea being to capture or express some elements of poetry outside merely rhyme and meter. Which elements? How many are required to be considered "real" poetry? I can no more define that than Justice Stewart could define pornography [1].

This obsession with strict taxonomy is itself a shibboleth of the juvenile. What value does strict differentiation provide, if one exists at all? It is a poem because I deign it to be so, and my friends understand what I mean when say this thing I have made is a poem and that thing I have made is a short story. There are a set of characteristics these labels may imply (and such implications make them useful), but none are required, some may even be mutually exclusive.

[1]: https://en.wikipedia.org/wiki/I_know_it_when_I_see_it

nickelpro··on Only bad poems go viral
99.99% of people are exposed to math as multiplication tables, algebra, and geometry. I don't let that bother me when I need Fourier and Laplace, and I'm not interested in making others accept that there is more to these fields than what they learned in primary school.

It's just very funny. I couldn't imagine being an adult and stubbornly insisting that you don't like the spaghetti because it's not how your mom made it for you and that's the only way spaghetti is supposed to be made. This sort of self-centered and yet entirely unselfconscious world view where you never question why you think such definitions and boundaries are fundamental truths, eternal and unbending.

nickelpro··on There isn't much point to HTTP/2 past the load balancer
I write application servers for a living, mostly for Python but previously for other languages.

Nobody, nobody, writes application servers with the intent of having them exposed to the public internet. Even if they're completely memory safe, we don't do DOS protections like checking for reasonable header lengths, rewriting invalid header fields, dropping malicious requests, etc. Most application servers will still die to slowloris attacks. [1]

We don't do this because it's a performance hog and we assume you're already reverse proxying behind any responsible front-end server, which all implement these protections. We don't want to double up on that work. We implement the HTTP spec with as low overhead as possible, because we expect to have pipelined HTTP/1.1 connections from a load balancer or other reverse proxy.

Your application server, Gunicorn, Twisted, Uvicorn, whatever, does not want to be exposed to the public internet. Do not expose it to the public internet.

[1]: https://en.wikipedia.org/wiki/Slowloris_(cyber_attack)

nickelpro··on Only bad poems go viral
We've been searching for the bounds of art, poetry, and music, for millennia without any hope of definition or finality. Thankfully HN user milesrout figured it out. That's a load off my mind.
nickelpro··on Only bad poems go viral
lmao the author specifically calls you, yes you, out in the post:

> Talky free verse, prose poetry, or spoken word—while seemingly accessible—can also upset readers whose major exposure to poetry was through high school English. The absence of traditional markers they studied in class, like end-rhyme or meter, becomes instant evidence that something is “not real poetry” for this perpetually precocious crowd.

I thought this was half sarcasm when I read it, but no, here you are, in the comments.

nickelpro··on A year of uv: pros, cons, and should you migrate
> That's quite literally not the design, if by "dependencies" you mean including transitive dependencies.

I don't. Your transitive dependencies are not your problem, they are upstream's problem. Anything regarding version requirements of such packages belongs upstream.

> pyproject.toml isn't there to enable reproducible builds.

Agreed. The repository itself should not contain anything related to reproducible builds. Reproducible builds are a packaging concern not part of the source of the project itself. Ex, it would be appropriate to ship a lockfile alongside a wheel or a tarball that specifies it is the lockfile used to produce that particular build of the project; but both the wheel and the lockfile exist outside the context of the project itself.

> Some application developers would say that, as far as they are concerned, the code "cannot run" except in the context of a reproducible build.

Yes, they are wrong.

nickelpro··on A year of uv: pros, cons, and should you migrate
> Lockfiles are meant to describe the exact version of everything that should be in the environment to have exact reproducible behaviour (not just "working"), including transitive dependencies.

It is wrong to specify the versions for your transitive dependencies except to achieve reproducible builds, as in CI or other situations. If a dependency fails to correctly describe their requirements in their pyproject.toml it is a bug and should be fixed in the relevant upstream.

> There are others who'd like to replicate their builds: application developers who don't want to risk getting bug reports for problems that turn out to be caused by upstream updates.

If your application only works with specific versions of dependencies and has bugs in others, that should be described in pyproject.toml.

> In principle, if you need a lockfile, you aren't distributing a library package anyway.

It's irrelevant what kind of project you're describing, library, application, build-tooling, etc. Your pyproject.toml should contain the correct information for that project to run. If your project cannot run, contains bugs, or otherwise needs more specific information than is present in the pyproject.toml the answer is to fix the pyproject.toml.

Reproducible builds for the purpose of testing or producing hash-identical wheels, or similar situations where the goal is producing an exact snapshot of a build, is the only reason to be using lockfiles. None of those use cases aligns with, for example, tracking the lockfile in source control.

nickelpro··on A year of uv: pros, cons, and should you migrate
Then why even have the dependency file?

If the dependency file is wrong, and describes versions that are incompatible with the project, it should be fixed. Duplicating that information elsewhere is wrong.

Lockfiles have a very obvious use case: Replicable builds across machines in CI. You want to ensure that all the builds in the farm are testing the same thing across multiple runs, and that new behaviors aren't introduced because numpy got revved in the middle of the process. When that collective testing process is over, the lockfile is discarded.

You should not use lockfiles as a "backup" to pyproject.toml. The version constraints in pyproject.toml should be correct. If you need to restrict to a single specific version, do so, "== 2.2.9" works fine.

nickelpro··on A year of uv: pros, cons, and should you migrate
This is not packaging hell, this is you having a personal problem with how other developers work.

Python has come an immensely long way in the world of packaging, the modern era of PEP 517/518 and the tooling that has come along with it is a game changer. There are very few language communities as old as Python with packaging ecosystems this healthy.

I've had conversations with members of SG15, the C++ tooling subgroup, where Python's packaging ecosystem and interfaces are looked on enviously as systems to steal ideas from.

nickelpro··on Leaking the email of any YouTube user for $10k
There's no existing black market of criminals extorting politicians and celebrities over Youtube comments (also how you go from an email address to an identity is itself iffy).

You are imagining a potential market, the exploits are priced against markets that are real and pay out today. Security researchers aren't traveling salesmen going around to every shady character on the internet and pitching them on the potential of a new criminal enterprise.

nickelpro··on Fun with C++26 reflection: Keyword Arguments
Compile-time reflection is by far the most useful

It replaces the plethora of code generators that currently surround C++ like flies

nickelpro··on Working with Files Is Hard (2019)
And yet all of these systems basically work for day-to-day operations, and fail only under obscure error conditions.

It is totally acceptable for applications to say "I do not support X conditions". Swap out the file half way through a read? Sorry don't support that. Remove power to the storage devise in the middle of a sync operation? Sorry don't support that.

For vital applications, for example databases, this is a known problem and risks of the API are accounted for. Other applications don't have nearly that level of risk associated with them. My music tagging app doesn't need to be resistant to the SSD being struck by lightning.

It is perfectly acceptable to design APIs for 95% of use cases and leave extremely difficult leaks to be solved by the small number of practitioners that really need to solve those leaks.

nickelpro··on TikTok says it is restoring service for U.S. users
Legally, no, it doesn't
nickelpro··on TikTok says it is restoring service for U.S. users
That's not true, distributors of the app are fined. Meaning, very specifically, app stores.

From (2)(a)(1):

> (A) Providing services to distribute, maintain, or update such foreign adversary controlled application (including any source code of such application) by means of a marketplace (including an online mobile application store) through which users within the land or maritime borders of the United States may access, maintain, or update such application.

>

> (B) Providing internet hosting services to enable the distribution, maintenance, or updating of such foreign adversary controlled application for users within the land or maritime borders of the United States.

Possession of and providing non-distribution ( / maintenance / update) services to a "Foreign Adversary Controlled Application" are not in any way a part of the "Protecting Americans from Foreign Adversary Controlled Applications Act". Operative services are specifically and intentionally excluded from the list, to ease the burden of enforcement.

nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
Speech and immigration are completely different areas of the law, there's no useful legal point of comparison in this context.

The motivation is largely irrelevant to the analysis of this case. What matters is what effects the law has and what services it provides the government.

So for example, the law technically doesn't ban TikTok at all, but rather mandates divestiture. However, the timeline wasn't realistic to manage such a divestiture, so the court recognized that the law is effectively a ban. The effect is what matters.

Similarly, the law provides a mechanism for the President to designate any application meeting a set of criteria a "foreign adversary controlled application". The court recognizes that the government has a compelling interest in restricting foreign adversaries from unregulated access to the data of US citizens, and the law services that interest.

The law represents a restriction on freedom of expression, TikTok is banned, but the law also represents a compelling government interest. To determine the winner of these two motivations, the court has established various thresholds a law must overcome. The relevant threshold in this case was determined to be Intermediate Scrutiny, and a compelling government interest is sufficient to overcome intermediate scrutiny.

nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
https://en.wikipedia.org/wiki/Intermediate_scrutiny
nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
The law does not care about who financially owns the company, only about designations of control made by the president (along with a 30 day notice).

The law actually skips this step for ByteDance / TikTok and directly adds them to the list of "Foreign Adversary Controlled Applications" along with the enactment of the law.

nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
SCOTUS fully agreed that the law violates the First Amendment as written, it wasn't even a question at any level from the district court on up.

The decision was balanced on strict or intermediate scrutiny. At the distict court level it was observed that the case should probably be decided via intermediate scrutiny, but they upheld the ban under strict scrutiny due to "national security concerns".

The SCOTUS didn't bother with strict scrutiny or national security, and decided that the correct analysis was intermediate scrutiny and that the ban merely needed to serve a compelling government interest (which regulation of applications controlled by foreign adversaries meets).

It's entirely about speech, the only question in the entire case as decided at the district and SCOTUS level was speech. Whether the government should be allowed to violate the 1st Amendment due to compelling interest is everything the case turns on.

Personally, I think using intermediate scrutiny here is wild.

nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
That's not how the law works.

The law levies fines against distributors of the app, it doesn't ban possession or block the operation of the app itself.

Ie, Google and Apple are forced to delist TikTok or face heavy fines

nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
The case is entirely about speech, and the various levels of scrutiny that apply to laws that violate the First Amendment. You should read the decision before commenting on what was argued and decided in said decision.
nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
Facebook / Meta are not controlled by a foreign adversary as designated by the "Protecting Americans from Foreign Adversary Controlled Applications Act". Thus they cannot become subject to the distribution restrictions designated by that law.

The core factor in the law is control by a foreign adversary, it's not a law that outlaws data collection.

nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
The arguments presented to the SCOTUS and the opinion itself are totally contained within the context of the First Amendment. No one is even arguing about anything other than the First Amendment and the exceptions permitted to that amendment.
nickelpro··on Supreme Court upholds TikTok ban, but Trump might offer lifeline
The SCOTUS opinion does not rely on a national security interest to justify itself, merely that the ban is content neutral and thus is subject to intermediate scrutiny.
← PreviousPage 5 of 21Next →