Typescript is also far slower both in terms of runtime and compilation time, uses much more memory, and is far more complicated which in turn has led to a ton more compiler bugs. It also inherits a ton of questionable features and API decisions from Javascript and has a tiny standard library which means most Typescript developers repeatedly end up turning to the NPM ecosystem which is an unmitigated disaster. Deployment also isn't even remotely as simple and reliable as Go even with Deno compile.
I like Typescript a lot but the reality of Typescript development is not great.
This isn't super clearcut. Typescript has lots of footguns and famously says that soundness is not one of their driving factors. There are lots of ways to devolve to accidental implicit any's (even with the no implicit any strict rule turned on).
Of course, Go makes zero attempt to enforce nullability (nilability?) in its type system... so... win some, lose some I guess.
The usual end result of Go is machine code, machine code is not safe to the degree you would consider Go to be safe. Yet you consider Go to be safe but not TS.
I don't see how they're competing, TypeScript can still share code between client and serverside, go "can't".
They're not exclusive to each other, routing "form submissions" though a ts verification layer and then down to Go makes sense to me if you need the Go performance but want to share things client and server side.
Also, application servers are cheap, persistent, fast and durable storage isn't, these won't be written in TS.
I don't think STD's are the primary deterrent, or even all that significant of a deterrent, to people having sex today. If sexual activity is taking a dip, then I would attribute it to:
(1) A progressive moral counterpart to the conservative moral prudishness behind the mid-20th century sexual revolution. It's strange. In some ways, sex positive feminism has prevailed. And yet, sex in general seems more loaded and viewed with suspicion than it was back in the 1990's when I entered my late teens and early 20's.
(2) Internet-driven pornography addiction, social anxiety, and an all-around trend toward increased isolation and atrophied social skills.
TL;DR - Sex is down because too many young women are patriarchy-triggered by sexual advances, and because too many incel dudes have no game and get their needs met through OnlyFans. I don't think it's because people fear the clap.
Is the inadequacy of existing mechanisms to protect against STDs your primary impediment for having sex at the moment?
I somehow doubt it given that the mechanisms to protect against STDs are much better than before, the treatments when you do get them are much better than before, and even with all of this Millennials and Gen Z are having much less sex than older generations.
But of course, if you just can't get off unless you are having unprotected sex with people you can't trust to not have STDs, then yes, I'm sure the mRNA revolution holds some promise. Hope it works out for you.
> Is the inadequacy of existing mechanisms to protect against STDs your primary impediment for having sex at the moment?
Consider scale. There are plenty of people who would love to take part in giant group orgies, at least once in a while, if there were no risk of communicable disease.
Everyone has their own idea of what a utopia might look like, I suppose.
Show me that at scale people are happier if they have lots of anonymous sex and giant group orgies.
But fair enough, if your primary impediment to having sex is that you want to engage in group orgies and just do not feel this is safe enough without better STD vaccines, then the mRNA vaccine revolution may be the silver bullet you have been looking for, hope it delivers for you.
I'm pre-millenial, and for me STDs are definitely a reason to hold slightly back, sexually. Also, not needing to be so careful with condoms is a pretty big plus for many of us that prefer it without for several reasons.
I also look forward to having the serious ones cured.
Chlamydia and gonorrhoea are easy to test for and not too bad if caught early. In Sweden we can just log in to a government health care web site, click a button and get a free test kit sent home.
Having herpes out of the way would be great. HIV/AIDS doesn't seem to be that big of a thing anymore, at least not in my awareness.
Not sure what is then left to be afraid of, except unwanted pregnancies and hurt feelings.
> Is the inadequacy of existing mechanisms to protect against STDs your primary impediment for having sex at the moment?
It doesn't need to be a primary impediment. Look at it in an economics sense: fear of and precautions over STDs impose an additional, unnecessary cost on sexual interaction. Like a tax, that imposes a deadweight loss where some sex doesn't happen that otherwise would occur.
Back in the real world, sex is certainly not a commodity, but someone who is particularly interested in sex with non-fully-vetted partners (particularly in casual or near-anonymous settings) would be more strongly affected by the STD deadweight loss.
Interesting that you mention it. I'm much more versed in TS than in go or java for sure, but after some knowledge sharing sessions with devs in those languages, as well as Scala devs, I can say they all _can_ learn a thing or two about types from TS, even if they themselves are superior on the backend.
For example I was surprised to realise how TS took go's value based interfaces and applied it to java concepts. And added almost Haskel level type manipulation on top of it.
These are rather recent developments - last couple of years stuff, but in TS you can write things closer to higher kinded types, conditional / dependent types and all sorts of wizardry that can explain to the compiler what _exactly_ you want to accomplish, much more so than in Java or go. And you have a very cheery and down to earth language underneath to do it with.
Once you do, you almost don't need unit tests - you get the "if it compiles, it'll work" kind of feeling. I've had sessions of days writing TS code without ever running it once, completing a complex feature, then compiling it and having it work exactly as specified on the first try, it's bizarre.
Now I'm not saying you can't do that with go or java, its just that I have a feeling people are dissing TS for what it was 5 years ago, and haven't realised they've been passed over already.
TS's biggest downside compared to langs like Scala is that you can't use typescript types at runtime, where apparently Scala gets its more advanced features (implicits etc). Oh oh and if it ever gets pattern matching and algebraic effects ...
And if deno's creators play their cards right and fix the standard library, give us go's channels, scala collections or swift's actors ... one can only dream.
You could probably codegen the .d.ts output of your types into different the body of API responses (or use it to generate a json schema), forking deno for it is probably overkill
I disagree with Paul when he weakened his argument from perfect to good taste. There are some artists who have more control over details than others. By perfect you would be able to perfectly recreate the reality of the subject/scene.
> The scripting languages of the future I see more in things like Unreal Blueprints.
A lot of people have an aversion for anything visual programming. Usually when someone mentions Blueprints (here or on r/gamedev on reddit) I see a whole slew of replies talking about how bad it is, how nobody makes any real things with it[1] and how visual programming is terrible. Of course, they're all programmers who forget that textual programming isn't for everyone and that visual languages are extremely successful in other fields (especially for artists and musicians).
I'm a programmer with ~20 years of textual language programming under my belt, but I spent a few months with Max/MSP and personally, I loved it. I'm a very visual thinker, I often think on paper or whiteboards with boxes and lines and I found that when using Max, I could skip this thinking step and go directly to code. Sure, its not for everyone, but for me, it was a very pleasant experience.
Yes, Max isn't a good replacement for a general purpose programming language and Blueprints apparently also has its warts, but they are extremely useful and successful and I do agree that we will see more like this in the future. I do feel that a good general purpose visual language could be created[2] Even Blender is moving that direction with its "nodes everywhere" thing.
[2] At the time, my big complaints with Max were lack of general purpose data structures (and reference types allowing you to build stuff like trees yourself -- although you could write C/C++ extensions and presumably create such things there), no tools for unit testing etc, afaik its added a bunch of data structures since so maybe its a lot closer now?
