I will treat this comment charitably and just say that it's yet another case of "definition of X sounds good, so X can't be bad".
I believe in reality it's less about "please don't kill us" and more about getting officials to set up the "pleas profit us" situation.
Yes, money don't change hands in an office, so it's TECHNICALLY not a bribery.
Well, unlike regulators, companies die without profit. So they do indeed need profit. Smaller companies might want a system currently tilted against them to be changed. Larger companies might spend a fortune on regulation-following that has harmful outcomes, e.g. raising prices, for no benefit. Both of those motivations sound reasonable, and both getting their way may result in more profit for them. There's nothing wrong with profit.
The only thing that can possibly be bad is the regulation-writer, or the regulation enforcer, behaving incompetently and/or corruptly, who decides or enforces bad rules.
This applies to a lot of scientific and practical (like construction) topics in general. Everyone relies on someone else (or something else) knowing what to do.
"every time I have to type "as" my inner Haskell programmer screams." - most of the times you don't have to. You choose to.
"If I could add one feature to Typescript it would be something like "as" that actually validates the result against the type system and can fail." - I don't think it's fair to expect that since most of the statically typed languages will not guarantee things in runtime unless you specifically run a validation code in runtime.
There's also type guards and good old self-written validation functions you can use.
"I don't think it's fair to expect that since most of the statically typed languages will not guarantee things in runtime unless you specifically run a validation code in runtime."
If I have a value of type X in a static language, then I know that it absolutely conforms to the layout of type X. It isn't even that we have to provide a "validation function", it is that it is quite literally physically impossible for my value to not conform to the definition of type X, in the languages like C or Go or Rust where the type layout is actually a specification of a layout of data in memory. If I have JSON '{"a": 1}', there is no way whatsoever to stick that in a "struct { A string }", because it physically doesn't fit. By "physically", I mean, in RAM, in the physical cells and voltages. There's no way to validate that a "struct { A int }" 'really contains an int' because there is no way for it to be anything else.
Typescript specifically has these issues because all of its objects boil down to a Javascript object with certain keys, and all of the values are ultimately of type "any" no matter what Typescript tries to lay on top of it. If I have this sort of data come in to a static language, I have to have a step where it very deliberately converts it down to the static representation. There isn't an equivalent of "as". Modulo unsafe, but we don't count unsafe in these sorts of discussions.
I am absolutely guaranteed in a static language that if my struct says field "A" is an int, it absolutely, positively is, always has been, and always will be.
The main problem I encounter with "as" is when I have external data coming in. For that I have zod and validation functions. What prompted my post is my experience yesterday where I corrected an AI using "as" (which it used because a lot of its training data does this) and had it call an actual validation function that I happened to already have before it cast it into the type. But the reason my Haskell programmer screams inside is that a validation function can still be wrong, because the compiler isn't helping me. In a static language, I can guarantee that if I have "I dunno, some JSON value" on one side and a struct comes out the other end with some value derived from it, I have absolutely had some bit of code check that and pack it into the static value in a way that the compiler has helped check. I can further reliably compose these promises quite reliably through further type specification in my static type.
A validation function can still have bugs in it that a static language compiler would have strictly, compile-time validated. It's better, but it's still the manifestation of the quite accurate criticism that dynamic languages end up trading away all their convenience with not specifying types with having to have vast swathes of validation, and testing of that validation, in the testing backend. In Typescript, I can mostly sorta kinda compose them together, but it takes a lot more features and grease and effort. I appreciate Typescript in its capacity as taming Javascript and prefer it substantially over Javascript alone, it's probably the best thing of its type that we could hope for, but if I consider it as a language that stands alone, I really really dislike it.
Ok, I checked what Go does.
It indeed can generate runtime validators from types. Neat, TIL.
I'd argue it's not by default a capability of statically typed languages, rather something that a language creator can choose to add via reflections or some other mechanisms. So in my mind it's not really static vs dynamic systems.
In Typescript you would need to use additional libraries like this: https://typia.io/
Clearly, it makes sense to have perfect pitch only in connection with a particular instrument for practical purposes.
Besides being a neat party trick, it gives more possibilities and makes things easier if a person wants to work with music professionally, especially with academical (aka "classical") music.
Is there anything about notes and instruments tuning that is not arbitrary? But hear me out: there's few hundred years tradition behind it, at least in the west, so why not follow it for a kid?
"I assume that if the learner drifts later in life by under a semitone, then things will seem like they're between keys." - problem that never occurred to anyone with a perfect or just good pitch.
> there's few hundred years tradition behind it, at least in the west
Not even close to being true!
- There's not been any real convention for most of the history of western music (and no tuning fork anyway) and pitch varied hugely between regions, people and time. Different musician groups in the same church would likely be on different pitches. 415Hz is often used for baroque music but that's just a modern convention, there was no such standard in baroque times.
- 432Hz was somewhat conventional at the end of the 1800s, start of 1900s
- 440Hz is the "official" standard since then
- Many orchestras are tuning to 442, 443, or even 445Hz nowadays
So there's not been any such thing as hundreds of years of tradition, and even now that we do have standards (and ways to measure frequency precisely), pitch inflation continues to be a thing.
>415Hz is often used for baroque music but that's just a modern convention, there was no such standard in baroque times
415Hz is one modern semitone below the standard 440Hz. Many (but not all) baroque instruments were tuned slightly lower than modern ones, and 415Hz is the most convenient slightly lower tuning that retains compatibility with modern instruments by transposing down a semitone.
Not opposed to defence in principle. But Switzerland's army has proven, repeatedly these last few years, that they are incompetent. From understanding a multi-billions contract before signing it to selecting relevant technology (drones that fundamentally cannot fly in a civilian airspace, etc).
Not only incompetent: the way the F35 was handled really looks like corruption from the outside. And for some reason the head of the defence ministry AND the head of the army left not so long after that...
I feel that too many people are confusing arguments they agree with with logical arguments. Most of people, when they claim that something is rational or logical, actually mean that it's a position that they agree with.
I have no reason to believe that back in the day when internet was only for nerds the situation was different.
> I have no reason to believe that back in the day when internet was only for nerds the situation was different.
Strong disagree. Having lived those times, it really really was different, and there are a bunch of reasons for it.
1. First, back then (90s, early 00s) there was very little financial incentive to participate in discussions. BBSs, IRC, forums etc. were mostly non commercial. People joined without any expectation of making a profit, just for "the fun" of it. And for something new, interesting, evolving. Way less perversion of topics for monetary gain.
2. People back then made a clear separation between being online and offline. We literally had the term IRL coined. So a lot of discussions were "in abstract" and much less prone to be taken literally or seriously. A lot less identity / ideology stuff as well. Having a clear separation made it easier to not confuse your real world self with your online persona. Having an idea debated wasn't about you / your identity.
3. Politics was much less divisive back then. There was political debate, but again a bit more "abstract" and theoretical. I'd say the moment when this changed was 2008s US presidential campaign. Until then the Internet was seen as "not important". It has changed a lot since then.
4. Entry barrier. This might sound elitist or disparaging, but it really was a thing back then. The people online were mostly tech inclined, or curious enough to learn. It was much more educational, and (linked to point 1 above) everyone wanted to learn the cool new thing, without any monetary incentives. Much more sharing of pure knowledge, helping out and so on. It of course changed over time, but the early days were really something beautiful. I have very fond memories.
> 3. Politics was much less divisive back then. There was political debate, but again a bit more "abstract" and theoretical. I'd say the moment when this changed was 2008s US presidential campaign.
At least as one of the "first ones" from the AOL days (too young for the Eternal September, old enough to have gotten online too early) - most of "us" were young and didn't care about News. We were more interested in Mr. Burns getting shot and whatever internal drama was happening in our online fan clubs. I remember 9/11 happening, but instead of switching websites I continued to read online webcomics and my "Learn VB in 24 Hours" book.
A lot of us were just younger then and our social groups were more focused on other things. I am in an indie game Discord right now that's clearly not my demographic anymore. I don't interact, I'm just there for game updates. But, those kids are making their own memories right now. I think as adults, we just sort of ~forgot~.
The internet was different, for sure. But the post you are responding to just stated that they don't really believe arguments were rational and logical back then. I don't think any of your points refutes that.
It was different in several ways, one was far fewer people enforcing norms or doing marketing in those forums, far less moderation and tone policing, and far more tolerance (even rejoicing) into getting into deep technical argumentation and "well, actually" debate. No "influencing" and mere marketable "content" creation either.
Not to mention for a good while, FOSS was a big nerd holy grail (informing many discussions and forums, away from corporate solutions shilling and careerism), and a big goal of every tech nerd (unlike after about 2010).
Also nerd culture was by nerds, for nerds, not dilluted and "championed" by every mainstream hipster.
Remember when even Comicon was something mostly nerds, the kind "normie" people used to point and laugh at, went, and sci-fi/superhero movies excited the same small demographic niche?
This feels like maybe even the majority of the problem.
In general corporate social media favors memetic content and disfavors "inconvenient" content. Inconvenient meaning things that cause non-trivial numbers of users to mash the thumbs down or "report content" button. The premise of that is supposed to be that people are reporting spam and trolling etc.
The problem naturally being that people will also use the platform's "make it go away" mechanism to penalize anyone who tells them things they don't want to hear. And then the sort of people who insist on telling the technical truth even when it's inconsistent with the political lie tend to get shadow banned into irrelevance, which leaves what in everyone's feed instead?
That’s a ZIRP problem. You didn’t have massive sprawl communities until the investment was there to build systems to keep Nazis and trolls away.
Slashdot really highlighted this for me - if you followed the site and the core forum of founders, dealing with moderation was horrible. The writing of CmdrTaco over the years really made it sound like it just made him miserable.
Your interpretation of behaviour is slightly off. Nerds use discussion to explore what they don't understand. There is no value in discussing something you already know everything about. What could you learn from that? If someone claims that something is rational or logical, they are seeking feedback to see if others can poke holes in where it is not rational/logical. Think something akin to Cunningham's Law.
> Most of people, when they claim that something is rational or logical, actually mean that it's a position that they agree with
I'd claim a relevant axis is argument as deduction (common in mathematics) vs argument as rhetoric/persuasion (common in politics).
It's not that the former type is necessarily rational. "All birds have wings, planes have wings, therefore planes are birds" is the former type of argument and fallacious, whereas "are you really comparing birds to planes?" is the latter type.
I feel the former can allow deeper exploration of some topic, but sometimes involves things like playing devil's advocate for stances outside of social norms - and requires others to engage at that level rather than taking the rhetoric path of shaming you for even considering it.
I remember Usenet in the 90s being 50% interesting conversations mostly about niche topics and 50% randomly devolving into flame wars in larger communities.
Even "Eternal September" as a concept was something from around 1993/1994 right?
Same for the 2000s era online-bulletin-board. I often go to thegearpage.net and am appalled at the amount of shilling, dismissals and disrespect, but then I remember that in the 2000s the main guitar forum was Harmony Central, which was mostly kids calling other kids moms names.
EDIT: But coldtea makes a good point about some (IMO) more recent changes: tone-policing, excessive marketing. There's IMO also a different attitude towards curiosity today.
One thing I do miss from the early internet was less anonymity being the norm on Usenet/forums/etc. Discussions tend to stay more civil when both parties know there's a "real" person on the other end.
Otherwise, my memory of early 90s internet supports exactly your conclusion. There may have been better opportunities for small discussions, but big ones devolved the same way they do today.
For a counterpoint, you only need to look at the cancer that is Facebook comments from people on their own name and face and a lot of bio attached. It's not the anonymity. At least not by itself.
I am remembering the same Internet. I got into lots of flame wars on comp.software-eng and before that on Compuserve and various FIDO boards.
It was never a very placid or friendly place. There was more tolerance for vigorous debate than there is now. The debate didn’t change many minds, I suppose.
I think there is a difference when you can assume that the other person probably isn't a complete idiot. Compare Reddit's technical subs and HN and there is a vast difference in general civility. Non-nerds look at this site's CSS and their mental parsing breaks entirely, so that filtering still exists.
Learning to code just so you understand better the AI output makes sense.
Learning to code and making it your profession - I think times are really hard for juniors now. The bar will be high, especially considering systems thinking and general intelligence. Coding for work is not as much fun. Herding a bunch of LLM tools and trying to force them to make something you need is arguably not fun.
For what it's worth, I don't think those good old times of high salaries and relaxed work for developers will ever come back.
So the value it is producing is for you as the service provider on the hype.
If the whole notion of "I set up a service because there was so much demand form friends" is even to be believed nowadays...
