HNHacker News
TopNewBestAskShowJobs

johnnyjeans

606 karma · joined February 20, 2023

submissionscomments
johnnyjeans··on Propositions as Types (2014) [pdf]
My priorities are indeed different. Apologies for the inflammatory language. My remark WRT constructive proofs is more an observation I've made that most proofs which deal with non-finite values seem to be non-constructive. Not necessarily as a hard and fast rule, the two just don't seem to roll well together. Could be sampling bias, but poking and prodding with mathematician friends more or less confirmed it. Not well read enough to have more interesting things to say on it.
johnnyjeans··on An appeal to Apple from Anukari
My problems start long before the special APIs come into play. When we supported Mac, I just wrapped the APIs like you do for any other system. The problem is I don't use Mac, so building software for Macs is inherently troublesome. I can build and test for Windows just fine from Linux and OpenBSD. I can't for Mac.

Now you might say this is problematic, Apple doesn't want third-party developers locking their platform behind some conditionally compiled set of abstractions that ruin everything they've worked for. Putting aside how ridiculous that is given system APIs are often wrapped for normal abstraction reasons anyways, that's totally fine. But then, it's also not my problem because I'm not Apple. I don't mind supporting their platform, I'll even turn a blind eye to the audacity of charging a developer fee while offering abysmal documentation and support. But I'm not going to crawl and beg for the privilege.

> Do you want them to use cross platform frameworks that are not optimized for their system?

Just like everybody else, because it hardly matters. Outside of Apple-land, Intel, AMD and Nvidia all get along just fine with rewriting SPIR-V to their microarchitectures. CPUs get along just fine rewriting abstract instruction sets like AMD64 and the various ARMs to their microarchitectures. Code is by-default compiled for instruction compatibility. APIs like CUDA and ROCm explicitly exist for vendor lock-in reasons. There's absolutely no reason why the throughput of these APIs can't be generically applied to compute shaders. None at all. The hardware vendors just want to capture the market.

Apple isn't exactly working with exotic hardware. The M1 is yet another ARM chip, not some crazy graph-reduction machine. These standards are fine and used across a wide-derth of hardware to no real detriment. I would suggest you may over-estimate how much they actually care about this idea of "specially optimized APIs." Consider that Apple pushes Swift as the primary language you Should be Using to ship software on OSX, and yet garbage collection is still handled in software. That's not what vertical integration for engineering purposes looks like.

Again, it all hardly matters. I wouldn't mind just wrapping these APIs, they're not particularly special or exotic any more than their hardware is. But the fact of the matter is that as a non-mac user, they go through a lot of effort to ensure putting software on their platform is as unattractive as possible.

johnnyjeans··on An appeal to Apple from Anukari
Trillion dollar market caps don't come for free. The Apple Tree must be watered with the blood of third party developers so our gracious overlords can Do Computing Different.
johnnyjeans··on An appeal to Apple from Anukari
I'd argue you can see the hostility if you compare shipping to Windows vs shipping to Apple. Microsoft doesn't care if you copy over your MSVC suite into a Wine environment to build your software for their platform. Even SignTool just works. It's not necessarily trivial to do, but that's simply because the MSVC suite is a horrible mess like everything else Microsoft.

Apple explicitly disallows cross compilation in their Terms of Service. Even if you managed to get clang compiling for Mac on another Unix, even if you figure out how to get your app bundles signed outside of OSX, they'll revoke your developer license and invalidate your certs because you're in violation of their ToS. You're right they don't care about third party devs, but the amount of hoops you have to jump through for devops on Mac is almost certainly designed as a gluetrap.

johnnyjeans··on Propositions as Types (2014) [pdf]
Because they explain nothing and aren't useful for building new insights. It's not a direct verification of the existence or lack-of-existence of a thing with given properties. It relies on rules lawyering in a very specific logic to say something with basically no substance. Allowing it causes more problems for automated proofs than they solve, so long as your domain only deals with finites (which all real-world domains do exclusively.)

They're also generally much easier to create than constructive proofs, which makes them a convenient go-to for lazy academics.

johnnyjeans··on Propositions as Types (2014) [pdf]
Intuitionism in this context just means the proofs have to be constructive. (no proof-by-contradiction, or other half-assed academic hacks)
johnnyjeans··on An appeal to Apple from Anukari
> Same for macOS compared to Windows.

This hasn't ever been my experience. Maybe if you're in a really specific market niche where most of the userbase is on Mac. Only 5% of users on Windows paying for the software still absolutely dwarfs 100% of Mac users paying for it. We have more sales on Linux than we do Mac.

johnnyjeans··on An appeal to Apple from Anukari
> You go where the users are and the majority of the market (by revenue) are Mac users.

One of the worst things about Apple is how much time and effort they spend trying to lock you into their platform if you want to support it. There's no excuse for it. Even once they have you on their system, they're doing everything in their power to lock you in to their workflows and development environments. It's actually insane how shamelessly hostile OSX is.

johnnyjeans··on Linux Kernel Exploitation: Attack of the Vsock
> sel4 is very limited in scope and extending that to a semi-usable OS (that uses ""proven"" C) is expensive time and money wise.

Everything that has to meet a high criteria of safety is like this, yes. For the exact same reason unsafe exists in Rust and completely inescapable, because automatic correctness checking beyond the most trivial static analysis doesn't actually come for free, and it imposes intense design restrictions that make a lot of things very time consuming to do.

> Citation needed

https://groups.google.com/g/comp.os.minix/c/dlNtH7RRrGA/m/Sw...

You will never find a single point in the multiple archives of Linux's git history where a clean break point occurred and the kernel was greenfielded with the express intent of replacing its design abstractions with ones more appropriate and ergonomic for formal analysis. If you'd like to express further skepticism, feel free to try and find that moment which never happened.

Participation of large, well recognized corporations does not imply the kernel isn't a mess of technical debt. It actually implies worse.

johnnyjeans··on Closures in Tcl
absolutely, i don't even consider that a flaw. i dont like EOL comments stylistically.
johnnyjeans··on Closures in Tcl
it's a language that's trivial to implement because it's well designed and simple, it embeds very nicely, and it's fantastic for use as a debug shell and to implement guis. it's a great technician's language, if you work with technically-minded people who aren't necessarily programmers, it's a great way to hand them deep interactive power without the footguns of a forth.
johnnyjeans··on Linux Kernel Exploitation: Attack of the Vsock
I'm not sure what you're even trying to say. Do you think that formally verified C isn't a thing? Because it's not used in Linux?

Linux isn't designed to be formally verifiable. For all of the manpower and resources dedicated to it, it's still bidden to the technical debt of being a 30 year old hobbyist experiment at its core. If you want a formally verified, secure kernel that wasn't written by a college student to see if he could, seL4 exists.

johnnyjeans··on The Cannae Problem
In my view, it was won because the Elder Council underestimated the threat. Had they known how the defense of Sicily was going to go, they could have easily afforded to hire 50,000 more celts and turned them out onto the Italic peninsula to raise absolute hell. But hindsight is 20/20.

The Romans bet big and stretched their logistics to the absolute limit to march every conscript they could muster down to Sicily. The Italic peninsula was completely undefended. If word had reached the army (many of whom were gang-pressed enemies of the Latins) that their villages were burning, the overwhelming majority would have revolted and fled to try and make it back to their homes. There would have been no recourse for the Romans, they spent literally everything they had coercing their army together and getting them down south.

The Canaanites are a resilient kind of people, the Greeks created the Phoenix as a metaphor for their civilizational tenacity. They can bounce back from anything. But the Elder Council made a very grave mistake. After the first Punic war they did bounce back, but they never had a chance to stop the Roman barbarians ever again. Their imperialism of the other Italic tribes had become ingrained, and it allowed them to grow too strong for a non-martial culture to castrate. The grave danger of underestimation is the most important lesson to take away from the Punic wars, imo.

johnnyjeans··on Linux Kernel Exploitation: Attack of the Vsock
a subset of C is provable, and is the de-facto standard in the industry.

what is it with rust people and thinking robust, automatic correctness checking was invented in the last 20 years?

johnnyjeans··on Show HN: I built a hardware processor that runs Python
> I certainly understand the design of the language used to expose a PDP-11 in a portable way.

It depends on what you mean by that. The PDP-11's dialect of B's major changes were more ergonomic handling of strings to no longer required repacking cells, and pointers became byte-aligned rather than word-aligned. C adopted these changes from the PDP-11 dialect of B, but that's the extent of influence the PDP-11 ever had.[1] The compiler size restrictions imposed by the PDP-7 and the GE-635 are far more influential on the semanticalities of the family.

In this rhetoric, what I'll call the "Your computer is not a fast PDP-11" dialogue, I find that people will imply things like pointer arithmetic, granular availability of memory as a flat array, etc. were invented in 1973, as though these are special quirks of the PDP-11 that C thrusted upon the programmer. They're just a normal part of computing, really. All the same criticisms leveraged at C can be leveraged at Forth for example, which isn't even in this class of register machine.

> Intel failures tend to be more political than technical

In the case of Itanium and iAPX432? Absolutely not. Read through the manual of the latter for a lark[2], there was never any chance in hell this thing could have succeeded. You couldn't pay me to maintain code for such a machine, sufficiently smart compiler or not. Itanium was a repeat of the same blunder, only this time Intel didn't even try to base their design on any existing infrastructure.

[1] - https://web.archive.org/web/20150611114355/https://www.bell-...

[2] - http://www.bitsavers.org/components/intel/iAPX_432/171860-00...

johnnyjeans··on Show HN: I built a hardware processor that runs Python
I envision an inflected grammar. That sounds crazy I know, but x64 is an inflected language already. The pointer arithmetic you can attach to a register isn't an expression or a distinct group of words, it's a suffix. Part of the word, indistinguishable from it. Someone once did a great job of explaining to me how that mapped to microcode in a shockingly static way and it blew my mind. I see affixes for controlling the branch predictor. Operations should also be inflected in a contextual way, making their relationship to other operations explicit, giving you control over how things are pipelined. Maybe take some inspiration from afro-asiatic languages, use kind of consonantal root system.

The end result would look nothing like any other programming language and would die in obscurity, to be honest. But holy shit it would be really fucking cool.

johnnyjeans··on Show HN: I built a hardware processor that runs Python
Only if you don't understand the history of C. B was a LCD grouping of assembler macros for a typical register machine, C just added a type system and a couple extra bits of syntax. C isn't novel in the slightest, you're structuring and thinking about your code pretty similar to a certain style of assembly programming on a register machine. And yes, that type of register machine is still the most popular way to design an architecture because it has qualities that end up being fertile middle ground between electrical engineers and programmers.

Also there are no languages that reflect what modern CPUs are like, because modern CPUs obfuscate and hide much of how the way they work. Not even assembly is that close to the metal anymore, and it even has undefined behavior these days. There was an attempt to make a more explicit version of the hardware with Itanium, and it was explicitly a failure for much of the same reason than iAPX432 was a failure. So we kept the simpler scalar register machine around, because both compilers and programmers are mostly too stupid to work with that much complexity. C didn't do shit, human mental capacity just failed to evolve fast enough to keep up with our technology. Things like Rust are more the descendant of C than the modern design of a CPU.

johnnyjeans··on Curry: A functional logic programming language
a prolog wizard crossing the path is an exceedingly rare and brilliant event, im compelled to make a wish upon this shooting star :3

> I remember a guy telling me the simplest exercise in some or other of the classic functional programming books is implementing Prolog in (some kind of) Lisp and it's so simple!

it's really easy to underestimate just how well engineered prolog's grammar is, because it's so deceptively simple. the only way you're getting simpler is like, assembly. and it's a turing equivalent kind of machine, but because if you squint your eyes you can delude yourself into thinking it kind of looks procedural, people can fool themselves into satisfaction that they "get" it, without actually getting it.

but the moment NAF and resolution as a concept clicks, it's like you brushed up against the third rail of the universe. it's insane to me we let these paradigms rot in the stuffy archives of history. the results this language pulls with natural language processing should raise any sensible person's alarm bells to maximum volume: something is Very Different here. if lisp comes from another planet, prolog came from an alternate dimension. technological zenith will be reached when we push a prolog machine into an open time-like curve and make our first hypercomputation.

johnnyjeans··on Curry: A functional logic programming language
The comparisons they're making don't make sense to me. I don't think I've ever even seen a logic language without nested expressions. Also VERY weird they give non-determinism as a feature of logic programming. Prolog is the only one off the top of my head that allows for it. Even most Prolog derivatives drop the cut and negation operations. In the broader scope of logic languages, most aren't even turing complete, like Datalog or CLIPS.

I really feel like Prolog and its horn clause syntax are underappreciated. For as much as lispers will rant and rave about macros, how their code is data, it always struck me as naive cope. How can you say that code is data (outside of the obvious von neumann meaning), but still require a special atomic operation to distinguish the two? In Prolog, there is no such thing as a quote. It literally doesn't make sense as a concept. Code is just data. There is no distinguishing between the two, they're fully unified as concepts (pun intended). It's a special facet of Prolog that only makes sense in its exotic execution model that doesn't even have a concept of a "function".

For that reason, I tend to have a pessimistic outlook on things like Curry. Static types are nice, and they don't work well with horn clauses (without abusing atoms/terms as a kind of type-system), but it's really not relevant enough to the paradigm that replacing beautiful horn clauses with IYSWIM/ML syntax makes sense to me. Quite frankly, I have great disdain even for Elixir which trades the beautiful Prolog-derived syntax of Erlang for a psuedo-Ruby.

One thing I really would like to see is further development of the abstract architectures used for logic programming systems. The WAM is cool, but it's absolute ancient and theory has progressed lightyears since it was designed. The interaction calculus, or any graph reduction architecture, promises huge boons for a neo-prolog system. GHC has incidentally paved the way for a brand new generation of logic programming. Sometimes I feel crazy for being the only one who sees it.

johnnyjeans··on OpenVSX, which VSCode forks rely on for extensions, down for 24 hours
violating a corporation's terms of service isn't unlawful. outside of that corporation, at least.
johnnyjeans··on CVE program faces swift end after DHS fails to renew contract [fixed]
Grok becoming an artificial nepobaby running the entire CVE program with zero oversight sounds so fucking funny I don't even care, PLEASE god make this real holy shit I can't breathe at the thought
johnnyjeans··on CVE program faces swift end after DHS fails to renew contract [updated]
important to note: the US's food safety is already really bad. salmonella isn't a thing you have to worry about in first world countries. can't wait to see what plague demon spawns out of a food industry running amok after the FDA gets gutted.
johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
> it feels like once that kind of stuff isn't punished, it starts to snowball a change in the attitudes of the site as a whole.

Considering the site has been around for over 20 years and people still call out and flame racism, I think this is an uncharitable and unfounded cynicism. I'm not sure declarative claims of 3rd order effects in a system so chaotic are capable of being accurate.

johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
Nah I disagree. It's the best one. All of the extra shit other boards have just feels like needless bloat. Honestly the JS extension they added like 10 years ago is a bit much.
johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
Incredibly spot-on and well-put.
johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
What was bad about the interview? Can you share any details?
johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
There is no counter-culture anymore, not really. Society is virtually balkanized.
johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
Nah, the board culture really did change in the last 7 years. In a past that's not too distant nobody was obsessed with trans folk. That's not to say there weren't vulgarities and unpleasantries, but there was definitely a substantial IQ drop somewhere around 2018 and 2019. I haven't seen the "Install Gentoo" meme in a while, the old board culture was basically replaced with cringe fringe zoomerisms.
johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
/g/ genuinely was one of the worst boards on the website, but there were a handful of lurkers who made good posts in some of the general threads. the site as a whole was still was a diverse place up until yesterday, with only a few boards being unusably bad, and it was getting increasingly better.

it's a bit sad really. zero-barrier to entry, no login gates, no accounts, and traffic was so high that it moved really fast. it was like a dive bar covered in grime. will be sad to see it go. none of the other imageboards still kicking are quite the same, most are even worse tbh.

johnnyjeans··on 4chan Sharty Hack And Janitor Email Leak
It is not very niche at all. 4chan served a gigantic volume of traffic.
← PreviousPage 3 of 8Next →