I think the point is that you can write your code using ES6 and ES7 and the TypeScript compiler allows you to output ES6 or ES5 compatible code if you want to make sure it runs in older browsers as well. You can do that with non-TypeScript ES code as well but you’re bound to use another transpiler. With TypeScript you get it „for free“ since you need to compile your code either way.
Ah yeah, kind of like how I get a drink for free if I get the hamburger menu, even if it costs more? Kind of weird perspective, but I can accept that it's something zealots tell themselves so "we're doing it differently" actually computes for them.
Don't be like this. Don't spit bile at people because they have different needs and preferences to you.
As I understand it, the TS compiler can translate newer JS features/syntax into backwards-compatible polyfills for you, automatically. I don't really use TS myself, but I'm not going to pretend like that isn't a useful feature.
I have used JS before TS entered the scene, and being able to transpile features/syntax like that is not a TS innovation, nor only available in TS. That's why flagging that as something "you get for free, since you added a compiler anyways" feels dishonest. Ultimately it's true, but if that's what you're out after, then adding TS to your project is going way above and beyond just "transpiling new syntax to old syntax".
> is not a TS innovation, nor only available in TS
> since I avoid TS, I cannot use ES6 and ES7, and my vanilla JavaScript doesn't run in all browsers
Where was that claim made? I don't see it in any Typescript docs, or in the book.
You seem to be saying that the TS docs say that these features are unique. They obviously aren't, the documentation is clearly not saying they are, and no reasonable person would say they were.
Transpiling to another platform is a multiplying benefit when combined with other benefits though.
For example: Clojure and Kotlin both target the JVM. The language design of each brings certain benefits. These benefits are clearly more useful if they have a wide deployment base in the form of the JVM.
> Where was that claim made? I don't see it in any Typescript docs, or in the book.
In the article, you know, linked in this submission, which my original comment quoted verbatim. Again:
> > Some of the benefits of TypeScript:
> > Access to ES6 and ES7 features
I'm saying that these are not "benefits of TypeScript" but benefits of doing transpiling in general with a tool that can "downcast" features like that, which is in no way exclusive to TypeScript nor even began with TypeScript, but AFAIK with Browserify.
When I talk about "benefits of language X" I try to keep it to things that are actually about the language, not particular implementation details also broadly available and used by others, because I feel like it'd be misleading.
Ok. I think you're misunderstanding that word as it was used. It's not the way I, and other responders, think the author intended it. They did not say 'exclusive benefit'.
A benefit of living in a house is that you don't get wet when it rains. If you didn't live in a house, you might get wet when it rained. But there are other things you could also do to not get wet, such as living in a tent.
It would not be reasonable to say "that's not a benefit of living in a house, because if I lived in a tent, or wore a rain-coat, I would not get wet".
The benefit of "staying dry" belongs to both "a house" and the superclass of "a sheltering structure".
If you defined benefits only on single dimensions, and only allowed them to belonging to level of abstraction at which they are exclusive, then you could argue that no language or technology has any benefit whatesover.
I think most people would think of "benefits of X" as an aggregation of individual specific benefits which may also belong to other aggregations.
> I have used JS before TS entered the scene, and being able to transpile features/syntax like that is not a TS innovation, nor only available in TS.
I used JS back in the 1990s. Transpiling to JS is a relatively new phenomenon.
No one said transpiling is a TS innovation, nor that it is unique to TS.
> That's why flagging that as something "you get for free, since you added a compiler anyways" feels dishonest. Ultimately it's true, but if that's what you're out after, then adding TS to your project is going way above and beyond just "transpiling new syntax to old syntax".
That's silly. Transpiling is something TS can do, so it's not dishonest to advertise it as something TS can do. If you think TS is too hefty, don't use it. But don't be toxic towards those that do.
You're moving the goalposts to try and defend a bad take. That's how you get brownie points on the Internet for extreme takes, but also how you prevent yourself from learning and growing in the long run. Learn to take an L. You'll be better for it.
The translation layer doesn’t really matter though, does it? If a user installs a game and it runs the same, the user doesn’t care about the translation layer inbetween. If installing and running a game on Linux is the same as running it on windows, there’s no reason to prefer one over the other for gaming.
It certainly does, because it allows game studios to keep ignoring GNU/Linux, even when they happen to have Android/Linux games written with the NDK, it is a Valve's problem.
The reasons stated against upscaling were that (re-)encoding video files should generally be done in a way that preserves as much of the original information and intent as possible. AI upscalers add information where there is none, thus modifying the video in a way that goes against that goal.
It is. And it’s also the fairest platform for musicians pay-wise. Though Epic apparently acquired Bandcamp[1] recently (presumably to stuff its IP catalogue for Fortnite Festival, so who knows how long that will be true for.
> Though Epic apparently acquired Bandcamp[1] recently
The article you linked is about Epic selling Bandcamp, which happened relatively quickly after they acquired it. I guess they didn't find any use for it in the end.
To add to this, when I went to school for design a long time ago, our typography teacher basically told us to never use underlines if we can use italics instead. It tends to mess with the readability of a paragraph and shifts the visual center of gravity downward, making text more difficult to parse.
I assume that’s also why italics and underline seem to be used interchangeably from time to time, since they generally achieve the same goal of emphasizing text in the same semantic manner.
Blink supports Windows, Android and Linux better than WebKit or Gecko does, to name at least one one reason. If it weren't for uBlock I'd probably be using a Chrome fork right now.
Google has already shown that they will slowly and methodically use every lever at their disposal to nerf ad blocking, regardless of what the user base thinks.
It's the exact same playbook Microsoft is using to block users from logging onto their own computer without using an online Microsoft account.
Given that Google has already started working to limit sideloading on Android, those days seem limited.
Blink is an open source project. If Google updates Chrome and Android to refuse sideloading at all, you can still fork both projects.
Your entire argument relies on a hypothetical you can't prove and doesn't scare anyone. To Android users you sound more like Chicken Little than the Boy who Cried Wolf.
Wipr and UserScripts on Safari prove to me that that's not a real issue...I understand compatibility problems are still issues, but ads/etc. are a fully solved one for Safari users.
For me it’s a lot of layout and rendering bugs that I run into with somewhat normal CSS transforms.
Anytime I build a site that has any kind of animation, there’s at least one weird rendering bug on iOS.
Also that stupid playsInline prop that if you forget it makes any video in the viewport hijack the browser and go fullscreen.
WebKit is not lacking in things your average dev needs and it’s not that big of a deal to work around, much like it’s not that big a deal to work around things in Gecko - or presumably Ladybird whenever it becomes usable enough.
Which is just laundered from real material that real humans put work in to create, only to be regurgitated by a krass homonculous of 1s and 0s for free without any mention of the real work that has been put into creating that information.
I’m not a big fan of the copyright system we have myself, but there’s a reason it exists. AI companies illegally training their AI on copyrighted content to reap the spoils of the hard work of other people that never get recognition for their work is the opposite of „giving back“.
Anecdotal evidence, but I’ve been driven into twice over the course of the last two weeks after driving every day for ten years and never having had a crash. Whether it’s touch screens mounted in the car or people being on their phone, something has to be done about people being distracted while driving.
I’m in Germany and using your phone while driving can lead to your license being revoked - the problem is that it’s not really enforced at all in my experience. Maybe it should be.
Rant over, I’m just honestly pissed about my car being wrecked TWICE and me being paranoid looking in the rear view mirror every time I’m stood still because people apparently can’t register a car standing at a signal.
I mean I doubt the problem went from 0 to 100 in the last few months, so I’m just not sure your anecdote says much about the amount of distracted driving, just bad luck.
reply