I also don't understand why anyone would ever want to get a PhD, which is just a manner of exchanging almost free labor for a nearly worthless piece of paper. It's like a participation trophy at this point for people that are not homo economici.
-21 karma · joined September 18, 2025
I also don't understand why anyone would ever want to get a PhD, which is just a manner of exchanging almost free labor for a nearly worthless piece of paper. It's like a participation trophy at this point for people that are not homo economici.
Most distributions install links2 as links.
> But I wonder: Whose ruffles did you panty in order for your comments to land this way?)
I don't know, but most people on voting based forums don't like what I have to say, even though I am almost always right. For example, when I say that Linux is an operating system using a software development methodology from the 1970s, that hurts some people's feelings. Similarly, when I say that I use Linux, because I am poor (read: not a decabillionaire), not because it's good (Mac/Windows are obviously even worse), that just rubs people the wrong way. So, ultimately, it's because most people are political and stupid in nature.
I think almost everything sucks relative to my standards, which is only natural, because I am engineer and I only exist to fix broken shit.
Speaking at a conference? Same story. You do it, because it's for "personal development", until it's pointless.
Conferences have n00bs and PMs, not the experts, because they don't need to learn anything anymore.
I don't think I ever had a colleague that even ever heard of the concept, let alone applied it. Of the "smart people", they typically only have heard of plain continuations, if you are lucky.
The debugger in Racket was useful when I used it years ago.
Unfortunately, it's kind of difficult to beat an entire planet cranking out libraries in other languages as many interesting programs are written for an ecosystem; if 90% of your project is building FFIs to make something work, perhaps you can better just choose the language of fools dun jour.
I don't think Scheme is the most academic language, today. Such honor would go to a language supporting a computable version of homotopy types, which I would guess only 1000 people in the world would be capable of using assuming production grade implementations (of which none exist).
Stupid people ruin everything.
Accounts are basically free. Not having accounts; that's expensive.
Any system designed picking such standards is basically betraying their client.
I think, if you want to annoy these people maximally, you should write an annotated version of the standard in a mathematical formal language.
I read the table constraints, which try to do something simple, but it's written in the most convoluted way possible.
I think I considered ASN.1 for a system once, but rejected it because of more modern technically superior system.
If the parser for something like ASN.1 doesn't fit in 80 lines of Haskell, perhaps you just shouldn't use it.
I don't know who these assholes are that say "Sure, let's make things slow and buggy, since we all hail Satan after all".
You said you were already using someone else's environment.
You can't later say that you don't.
Whether or not shell access makes sense depends on what you are doing, but a well written application server running in a cloud environment doesn't need any remote shell account.
It's just that approximately zero typical monolithic web applications meet that level of quality and given that 90% of "developers" are clueless, often they can convince management that being stupid is OK.
The right way this would work is via a systemd service and then it should be instant.
So, you created a square wheel, instead of a NASA wheel.
Please start a class action suit and ping me when it gets somewhere.
Things like Lambda do fit in this model, but they are too inefficient to model every workload.
Amazon lacks vision.
Your point is that users are too stupid/lazy to comprehend specifications. That is, they won't bother to read that the specification of their formally verified secure version of Google Maps really just copies their credit card data to a random server.
I just don't agree.
1. they are idiots
2. they do it on purpose and they think you are an idiot
For me, it just means that the moment you integrate with any API, you are basically their bitch (unless you implement one from every competitor in the market, at which point you can just as well do it yourself).The specification for a text editor would be much simpler than an implementation. For example, efficiently searching for a substring is non-trivial, but a specification is easy. So, all that I would be interested in, is a proof that "eval(optimized_substring_search needle haystack) = eval(easy_substring needle haystack)", for example. Obviously, there are many thousands of such theorems that would have to be done to clone Emacs, but at least a new release wouldn't contain bugs anymore (wrongly specifying something would happen, but it's much easier to write a specification of desired behavior than to find the exact bug in some mess from someone else, because it conflates implementation and specification in the first place).
I guess one could automate finding obvious exploits via LLMs and if the LLM finds something abort the update.
The right solution is to use Coq and just formally verify everything in your organization, which incidentally means throwing away 99.999% of software ever written.
I wish I could know the kinds of queries that could be answered when there are no economic constraints on existing infrastructure. That would suggest whether they have already hit a scientific wall (and that's the difference between it being a $10T+ industry or a 500B industry). On consumer LLMs, it's still easy to get the LLM to admit queries are beyond its abilities, although many of those questions are also beyond 99.9999% of humanity, to be fair (in that the things I ask don't exist yet anywhere and possibly will never due to their non-trivial engineering nature).
You are the nobody here.