> It's a what? Can someone ELI5 this for a lowly Python and JS dev - why would I want this?
Nah, but I can ELI a person with some programming experience.
Pattern matching is super useful for writing code that spends a lot of time building and deconstructing syntactic data structures.
Non-linear pattern matching is useful when de-constructing large-ish expressions that might contain multiple occurances of the same sub-term.
Nonfree datatypes allow you to encode some constraints about your datatypes; e.g., "lists that are equal modulo permutation".
Supporting type-checked non-linear matching over nonfree datatypes allows you to encode a lot of constraints in the type system and syntax that would otherwise be encoded with lots of nested if-statements and only checked by tests, not by static type checking.
This combination of features could be very useful when implementing a lot of mathematical code that operates over algebraic structures. Which is why the language's homepage mentions the implementation of (features for) computer algebra systems as a sort of killer app.
> this is not a business pain, this is an academic interest
Not all innovation is motivated by the business pains of today's engineering managers. And often the solutions to those pains are not recognizable; e.g., thousands engineering manager in 1950 could've beneifted from CAD software but I bet very feew were sitting around saying "I could really use a good piece of CAD software right now".
Scala is another good example of that, despite a marketing complaints about messaging. No one asked for FP+OO, but Scala took off because the combination of FP and OO solved a lot of the pain caused by Java.
Substantially improving the ease of implementing new types of computer algebra systems could easily create a lot of business opportunities e.g. in providing improved analysis/synthesis tools for all sorts of CAD tools.
that said, I don't think this language hits the target. See the hodge operator example...
> If behavioural economists are so good at predicting human behaviour, why aren’t they popular among consumer facing companies?
For the exact same reason that most software companies don't have a Computer Science Ph.D. on staff. Many companies don't need a high-caliber research department.
People who learn and understand how to apply ideas and theories from behavioral economics in biz and econ courses are well-represented in sales and marketing roles. Just like people who learn and understand how to apply ideas and theories from Computer Science in CS courses are well-represented in engineering roles.
> why none of the behaviourial Economists have ever tried starting up?
I'm sure many have lucrative consulting portfolios, but generally speaking: because they already have a pretty cushy and very well-paying job doing what they love.
You've seen pictures of the earth from orbit, right?
You probably mean that you haven't engaged in all of the crazy theories and arguments put forth by flat-earthers. But that's doesn't make your very simple observation-based opinion any less justified. Direct observation can and should eliminate the need for lots of hemming and hawing.
> Of course i believe in global warming, though ive never read a single paper / study on it.
There are many accessible descriptions of global warming and the evidence for it written for different levels (uneducated/child; HS-level; university-level).
> Of course i believe in evolution, i went to a school where they told me to believe it.
That sounds like a bad experience, and maybe that explains some flat earthing. When I was in school we were presented with a lot of concrete evidence for the evolution of the species, and Darwin's original was even required reading.
The deployment difficulty is also high, especially for what it offers. Deploying CSP on anything non-trivial involves a lot of coordination with basically anyone who runs code on your site.
Lots of sites have marketing departments which like to switch out their advertising, engagement, A/B testing, etc. code on a regular basis. Which in turn requires either changing the CSP frequently to accommodate, or else opening holes in the CSP to allow marketing to just copy/paste inline JS and other badness. At which point it's hard to justify CSP.
This has been my feature work for the past couple months (I work on an enterprise site builder, basically, with some users doing what you describe -- we need to support that but hopefully with a smaller/harder to misfire footgun). There's a lot of feature complexity even after you've simplified it down, and it's kind of maddening how much effort it is to just send an extra (correct for the context) string in the response headers.
The spec versions are interesting to read too, as well as browser compatibility. Differences in interpretation of the spec lead to github issues which lead to browsers fixing things in the past few months that have been part of the spec for much longer. (And if you have a big chunk of IE11 users, "what's the point" is valid.) An example of a spec issue is that I'm working on adding an endpoint for the report-uri directive so we can log some metrics but the first thing you see when reading about report-uri is that it's been deprecated in favor of report-to, but literally no stable browser release supports report-to yet.
It's also not really enough. https://github.com/tc39/proposal-frozen-realms is a useful extension, since it would allow frameworks to do what they need to set up everything but then lock down objects from further extension/abuse...
> as well as the sad decline (and preventable) of the American steel industry
I'm not sure where you get both "sad" and "preventable" from that documentary. The tragic decline of employment in the US steel industry was completely unavoidable.
The decline of American steel company's dominance between 1960 and 1980 might've been preventable, but the human carnage wrought by automation would've happened in any case.
Watching the documentary, you can see the coming storm. Every video of people working is a prelude to an industrial automation project. And it's no mistake that the documentary ends with an acknowledgment that today's steel workers operate a keyboard and mouse.
The most important lesson from steel is that competitive pressures + new ways of automating things = huge disruptions in the labor market (read: lots of poverty where once there was wealth).
Nucor still exists, Bethlehem does not. They sat on their market leadership, had a rudderless and massive management staff. I am talking about the companies, not the workers. Steel is so critical to civilization, it is crazy we lost it as core competency.
The title says "operators", not "operations", which I misread about three times :-(. I.e., there's still a sizable self-driving effort, but they've re-organized the humans doing the actual day-to-day driving of the cars:
> Uber confirmed it laid off about 100 autonomous vehicle operators in Pittsburgh and eliminated the position. The company plans to replace these jobs with about 55 “mission specialists”—specialists who are trained in both on-road and more advanced test-track operations, and who are expected to provide more technical feedback to self-driving car developers. Uber said affected operators could apply for these positions.
This is true for even very, very simple technology. My favorite example is gunpowder (the smokey kind we don't even use anymore), which requires potassium nitrate, which without modern (c. 19th century) processes you have to a) get lucky and find a cave you can mine/scrape from; or 2) collect manure, pour urine on it for a year, and then scrape off the top and process. It's actually freaking amazing anyone figured out how to do this, even though with hindsight we understand each reaction.
I actually prefer logs to interactive debugging -- grepping through 20 different execution traces is much more pleasant than stepping through them, and I can discover everything instead of stepping through N times to fill out my mental image as new information becomes salient from previous debugging sessions. Also, I have never learned how to interactively debug anything parallel or especially distributed :(
But I also try to write/architecture my code so that the big stuff always gets logged. In cases where the logging isn't as good as it should be, a few hundred lines of reflection/meta-programming can enable just enough aspect-oriented programming capabilities to enable this approach.
1. Green field+0 years: This particular portion of the system was designed in this way as a cargo cult.
2. Green field+2 years: Because that portion of the system was designed in that way, we had to modify this other portion of the system to achieve X.
3. Green field+3 years: Because of the change in 2, and this new constraint Y, we had to make this other change in a third portion of the system.
5. Green field+(3 to N) years: repeat steps 2 and 3.
6. Green field+N+M years: Wow 5 (or previous 6) has created a mess and exposed a serious architectural flaw from step 1 or previous 6. All of the logic in the various iterations of 2+3 are refactored as best as possible.
So, the "why" basically grounds out in "the refactoring we could afford to do in order to correct a mess that resulted from a cargo cult or previous refactoring of even older cargo cult".
Is that "why" functionally helpful? Usually not for me -- in either case, I can't really assume a lot and I have to proceed with laborious "just watch what the code does" debugging/logging that I would've done without the "why?".
> The current interpretation of the Establishment Clause requires schools to prohibit student-led prayers at school events
This issue is still in flux and is more complex than this.
Santa Fe ruled that the school's practice of running an election to select a person who then says a prayer on a PA system before a football game was unconstitutional.
But after Santa Fe was decided, the 5th circuit ruled in favor of Ward by finding that explicitly prohibiting student-led prayers is also unconstitutional! (At this point you've got to feel real bad for the school... damned from one side and damned again by the other.)
Also after Sante Fe, Texas passed RVAA which explicitly allows student-led prayers at school events. The constitutionality of those provisions have not been tested in SCOTUS.
So generally, the current state of affairs is quite subtle and messy.
Student-led prayers at voluntary student-organized events are certainly allowed.
Employee-led prayers in front of students are certainly not allowed in any circumstance.
Everything in-between is murky, and none of the case law is particularly revealing. E.g., what if Sante Fe had not used the PA system and didn't have any voting/guidelines about praying? Much of the legal reasoning in the majority opinion would not have been applicable.
Nah, but I can ELI a person with some programming experience.
Pattern matching is super useful for writing code that spends a lot of time building and deconstructing syntactic data structures.
Non-linear pattern matching is useful when de-constructing large-ish expressions that might contain multiple occurances of the same sub-term.
Nonfree datatypes allow you to encode some constraints about your datatypes; e.g., "lists that are equal modulo permutation".
Supporting type-checked non-linear matching over nonfree datatypes allows you to encode a lot of constraints in the type system and syntax that would otherwise be encoded with lots of nested if-statements and only checked by tests, not by static type checking.
This combination of features could be very useful when implementing a lot of mathematical code that operates over algebraic structures. Which is why the language's homepage mentions the implementation of (features for) computer algebra systems as a sort of killer app.
> this is not a business pain, this is an academic interest
Not all innovation is motivated by the business pains of today's engineering managers. And often the solutions to those pains are not recognizable; e.g., thousands engineering manager in 1950 could've beneifted from CAD software but I bet very feew were sitting around saying "I could really use a good piece of CAD software right now".
Scala is another good example of that, despite a marketing complaints about messaging. No one asked for FP+OO, but Scala took off because the combination of FP and OO solved a lot of the pain caused by Java.
Substantially improving the ease of implementing new types of computer algebra systems could easily create a lot of business opportunities e.g. in providing improved analysis/synthesis tools for all sorts of CAD tools.
that said, I don't think this language hits the target. See the hodge operator example...