595 karma · joined November 18, 2014
Find me at http://shonfeder.net/
IMO, a language without proper modules, GADTs, or (now) an effect system, does not seem to me like it could plausibly be described as "essentially OCaml". Your point about having ad hoc polymorphism (outside of an object system) is another good point about why F# really is not OCaml on .NET.
Not to mention the difference of being trapped in (or having the luxury of, as you prefer) .NET vs. compiling to native binaries.
Glad you like F# tho!
People love to sulk in their parochial pits, I guess?
Thanks for clarifying :)
I think this is a part of the point: we are able to simply write direct style, and not worry at all about the effectual context.
> how do you find the code that will run when they do fail
AFAIU, this is also the point: you are able to abstract away from any particular implementation of how the effects are handled. The code that will when they fail is determined later, whenever you decide how you want to run it. Just as, in `f : g:(A -> B) -> t(A) -> B` there is no way to find "the" code that will run when `g` is executed, because we are abstracting over any particular implementation of `g`.
> if the system survives, the consequences will be inevitable: There is no way of reforming or modifying the system so as to prevent it from depriving people of dignity and autonomy.
But I also think that this claim is (1) practically impossible to prove and (2) a claim we morally ought to attempt to disprove.
I think we are in the third act of a very long play:
> If mechanical thinking and ingenious experiment produced the machine, regimentation gave it a soil to grow in: the social process worked hand in hand with the new ideology and the new technics. Long before the peoples of the Westenr nworld turned to the machine, mechanism as an element in social life had come into existence. Before inventors created engines to take the place of men, the leaders of men had drilled and regimented multitudes of human beings: they had discovered how to reduce men to machines. (https://en.wikipedia.org/wiki/Technics_and_Civilization)
I would include personal transformation. I think it should be clear that my point is not against "production-oriented pastimes" in any way.
> It's about doing for the sake of being.
Yea, this is totally aligned with my view too. I'd just note that being is not separable from becoming and changing.
I'm afraid you either didn't read me well, or I didn't write my intended sense well, or both. But I think we are pretty much in agreement in any case, assuming I understand what you've written here :D
The process of forming expressions just is the process of conceptual and rational articulation (as per Brandom). Those who misunderstand this -- believing that concepts are ready made, then encoded and decoded from permutations of tokens, or, worse, who have no room to think of reasoning or conceptualization at all -- they will be automated away.
I don't mean that their jobs will be automated: I mean that they will cede sapience and resign to becoming robotic. A robot is just a "person whose work or activities are entirely mechanical" (https://www.etymonline.com/search?q=robot).
I'm afraid far too many are captive to the ideology of productionism (which is just a corollary of consumerism). Creative activity is not about content production. The aim of our creation is communication and mutual-transformation. Generation of digital artifacts may be useful for these purposes, but most uses seem to assume content production is the point, and that is a dark, sad, dead end.
William Lawvere is also a post-hegelian.
I don't understand how you mean (3) to apply as a criticism at all. He is not making a claim about truth at some level, he's just reminding us what computation is and what its limits are.
afaiu, there are two ways to counter Penrose's claim:
a. Prove that consciousness is actually just computational.
b. Prove that merely stacking computations can somehow produce a super-computational system.
But this exact problem is why I am more interested in approaches that integrate specification and implementation into a single (dialectical) process (e.g., via type-theoretic methods).
Key features of note include
- Locality via modal types - Layout polymorphism for polymorphic unboxed types
See https://blog.janestreet.com/author/mslater/ for more.
Aspiring to rigorous reason and maximum reasonability is necessary for virtue. Maths is the way we reason rigorously about space and time.
(\* t.ml \*)
let () = print_endline "Hello, World!"
Then just doing a standard compilation and a strip: $ ocamlopt -o t t.ml && ls -l -h t | cut -d " " -f5
1.5M
$ strip t && ls -l -h t | cut -d " " -f5
356K
$ ./t
Hello, World!
I may be overlooking something, and would be interested to learn what if so, but I was surprised we got a result smaller than the rust binary in the first instance.I do. You may not quite be old enough to have seen/participated in this. Or maybe it wasn't happening where you live for some reason? (E.g., this was probably more common in the urbs than the sub-urbs, due to other alienating forces in the latter).
> people also downplay how much smartphones just replaced rampant TV consumption for people who like to be entertained constantly
It was (mostly) not possible to have a TV with you at all moments, on the bus, in line, in the toilet. This meant lots of times where people were with their thoughts or one another. Also, phones have not replaced TV but overlay it. Many (most) now watch their TV (even if streaming) while also layering distraction from their phone.
> Personally, I handle smartphone usage just fine as do most of the adults around me.
Good for you! I'm curious, what's your average phone usage in hrs/day?
IMO, the degrading effect of smart phones (and the distraction machines of the attention economy more generally) is something that should be discussed and problematized. If some are good at self-moderating, their contributions to the discussion may be especially helpful.
> I reject the idea that all techies need to reject technology and smartphones
Just to clarify, rejecting smart phones as they are currently designed and implemented as bad technology is not the same as rejecting all technology per se.
> projecting their own solution on to everyone else is about as appealing as the person who had a problem with drinking too much trying to insist that nobody else should drink any alcohol at all either
This is an interesting analogy b/c ["No level of alcohol consumption is safe for our health"](https://www.who.int/europe/news/item/04-01-2023-no-level-of-...). I doubt that smart phones are as unequivocally toxic as alcohol, but I do suspect that the current way they are used and developed may be, esp. thanks to gamification, nudge design, and surveillance. Research is coming out on this, but I think there is good reason to not assume it is systemically innocuous as you think it is.
However, b/c living in an inattentive society may actually be worse for everyone, it's possible that a better analogy may be smoking in public or drunk driving: if you smoke in public places or get behind a wheel, everyone is at greater risk.
> I also use my smartphone for important things like maps, taking photos, keeping lists, and even paying for groceries if I forget my wallet.
Imagine a utility that enabled these important functions but did not also constantly disrupt your attention with push notifications, harvest your data, or present the temptation of hours wasted in toxic digital fun-houses! :D It's possible!
A few things came to mind:
The view of programming as "summarizing what's on StackOverflow" is really alien to me. I suspect this is indicative of a particular approach to programming, and perhaps to working in general, which I don't share. The author's view seems to be that knowledge exists "out there" and the role of the "knowledge worker" is to accumulate, internalize, and reshape it into products derived by summarization. Compare this with another view on "knowledge work" taken from https://en.wikipedia.org/wiki/Knowledge_worker
> Nonaka described knowledge as the fuel for innovation, but was concerned that > many managers failed to understand how knowledge could be leveraged. Companies > are more like living organisms than machines, he argued, and most viewed > knowledge as a static input to the corporate machine. Nonaka advocated a view > of knowledge as renewable and changing, and that knowledge workers were the > agents for that change. Knowledge-creating companies, he believed, should be > focused primarily on the task of innovation.
High value knowledge work involves creating and transforming knowledge, not just compressing or reconfiguring it.
To expand on this in abstract terms: knowledge work is fundamentally cognitive and it gets its higher order purpose and potential from the application of reason; i.e., it is concerned with rational cognition. Rational cognition is mainly about synthesizing new, higher order concepts that direct and evolve given concepts into more general and potent structures. This work involves re-cognition as a necessary component, but if it were only recognitive -- as it would be if were only concerned with recollection and summarization -- it would not have the creative dynamic which it does.
To expand in more specific terms: programming work involves problem solving, but it is not mainly about reassembling existing solutions to solve known problems. The most valuable aspects of this work come from problem discovery, root cause analysis, and solution invention. (Programming work that consists in StackOverflow copy pasta is probably best viewed as the production of tech debt :) This is not to say resources like StackOverflow arent useful, they definitely are!)
I suspect it says more about the author's career aspirations and the reigning interests of the political-economic system that they envision a future where everyone is a manager. First, only if you have "manager brain" can you look at what's happening in tech and see a future where everyone is a manager as a positive development, when compared with a future where everyone is a researcher, artists, arisen, inventor, etc. Second, the managerialization of work is actually describing an idealized view of the present situation, and if it is looming in the future it is only as an intensification of the current dynamics. The rise of [the Professional Managerial Class was heralded in the 70s][1], and most tech workers are in the PMC:
> Who are these Americans working in the upper echelons of the knowledge > economy, exactly? ... the Professional Managerial Class. The PMC, as they are > now often called, came into existence in the late nineteenth and early > twentieth centuries. They were not the old petty bourgeoisie of small-business > proprietors and independent farmers, but a new class whose expertise was > required to make an industrial economy function: engineers, scientists, > teachers, doctors, social workers, functionaries, bureaucrats, and other > professionals and managers who had the know-how to create and control the > levers of the modern capitalist world [0].
The managerialization of everything does seem very likely, because that is basically what our current economic regime has been trying to achieve since the advent of the "digital revolution" (and maybe since Hobbes: a pyramid scheme of nested managers, where every managed worker is actually a manager automating its own autonomous subordinates).
Against the view that computers are a tool for rendering every "maker" into a "manager", I propose meditating on the view propounded by Conal Elliot that computers should be "telescopes for meaning".