-
-
Notifications
You must be signed in to change notification settings - Fork 3
/
index.html
336 lines (309 loc) · 15.8 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<title>You Might Not Need TypeScript</title>
<meta name="description" content="Examples of why you might not need TypeScript.">
<link rel="icon" href="https://static.hubspot.com/favicon.ico">
<link rel="stylesheet" href="css/style.css">
<script src="https://youmightnotneedjquery.com/js/index.js"></script>
<style>iframe { display: inline-block; width: 100%; height: 400px; border: 0; }</style>
</head>
<body>
<a href="https://github.com/jimmywarting/you-might-not-need-typescript" class="github-corner" aria-label="View source on GitHub"><svg width="80" height="80" viewBox="0 0 250 250" style="fill:#151513; color:#fff; position: absolute; top: 0; border: 0; right: 0;" aria-hidden="true"><path d="M0,0 L115,115 L130,115 L142,142 L250,250 L250,0 Z"></path><path d="M128.3,109.0 C113.8,99.7 119.0,89.6 119.0,89.6 C122.0,82.7 120.5,78.6 120.5,78.6 C119.2,72.0 123.4,76.3 123.4,76.3 C127.3,80.9 125.5,87.3 125.5,87.3 C122.9,97.6 130.6,101.9 134.4,103.2" fill="currentColor" style="transform-origin: 130px 106px;" class="octo-arm"></path><path d="M115.0,115.0 C114.9,115.1 118.7,116.5 119.8,115.4 L133.7,101.6 C136.9,99.2 139.9,98.4 142.2,98.6 C133.8,88.0 127.5,74.4 143.8,58.0 C148.5,53.4 154.0,51.2 159.7,51.0 C160.3,49.4 163.2,43.6 171.4,40.1 C171.4,40.1 176.1,42.5 178.8,56.2 C183.1,58.6 187.2,61.8 190.9,65.4 C194.5,69.0 197.7,73.2 200.1,77.6 C213.8,80.2 216.3,84.9 216.3,84.9 C212.7,93.1 206.9,96.0 205.4,96.6 C205.1,102.4 203.0,107.8 198.3,112.5 C181.9,128.9 168.3,122.5 157.7,114.1 C157.9,116.9 156.7,120.9 152.7,124.9 L141.0,136.5 C139.8,137.7 141.6,141.9 141.8,141.8 Z" fill="currentColor" class="octo-body"></path></svg></a><style>.github-corner:hover .octo-arm{animation:octocat-wave 560ms ease-in-out}@keyframes octocat-wave{0%,100%{transform:rotate(0)}20%,60%{transform:rotate(-25deg)}40%,80%{transform:rotate(10deg)}}@media (max-width:500px){.github-corner:hover .octo-arm{animation:none}.github-corner .octo-arm{animation:octocat-wave 560ms ease-in-out}}</style>
<div class="page">
<header class="page-header">
<div class="inner">
<h1>You might not need TypeScript... (syntax)</h1>
</div>
</header>
<div class="explanation">
<div class="inner">
<p>Everyone loves types, Everyone loves autocompletion, Everyone loves getting warnings before they arise.</p>
<p>But nobody likes wasting time compiling stuff. Hopefully this will help convince you or your company that you don't actually need the TypeScript flavor syntax. So i have embedded the same editor used in VS-code to show you that <b>you can have type safety with vanilla JavaScript</b> and have the best of both worlds and play around with it.</p>
</div>
</div>
<!-- <div class="share-buttons"><a href="https://github.com/HubSpot/YouMightNotNeedjQuery" class="share-button-github"><span>★ Star on Github</span><span class="github-stars"></span></a></div>
<script>
var handleChange, search, slider, stars, _this = this;
slider = document.querySelector('.version-slider');
stars = document.querySelector('.github-stars');
fetch('https://api.github.com/repos/hubspot/youmightnotneedjquery')
.then(r => r.json()).then(
data => { stars.innerText = data.stargazers_count },
() => { stars.textContent = '10k+'}
)
</script> -->
<br>
<br>
<br>
<br>
<br>
<div class="comparisons">
<section>
<div class="inner">
<div id="post" class="comparison">
<h3 style="font-size: 1.5em; margin: 0;">First thing first</h3>
<h3 style="margin-top: 0;"><a href="#public_private">Enabling type safety</a></h3>
<p>There are some hidden features available built right into VScode that not everyone knows about. They are so great that they are disabled by default as it almost seems like Microsoft wants you to use typescript instead and doesn't want you to use ESM or vanilla javascript.<br>Here are some features that should be enabled by default:</p>
<div style="columns: 2">
<div>
<iframe loading="lazy" src="config/json.html" style="height: 500px;"></iframe>
<ul>
<li>This can be added globally</li>
<li>Alternative it can be added to <root>.vscode/settings.json</li>
</ul>
</div>
<div>
<iframe loading="lazy" src="config/js.html" style="height: 500px;"></iframe>
<ul>
<li>Can be enabled per individual file (just to try it out)</li>
</ul>
</div>
</div>
<p>You could also add a <a href="https://code.visualstudio.com/docs/languages/jsconfig">jsconfig.json</a> to your project. jsconfig.json is a jsconfig.json is a descendant of tsconfig.json, which is a configuration file for TypeScript. jsconfig.json is tsconfig.json with "allowJs" attribute set to true basically.<br>Having it can help you generate d.ts files</p>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Type Guard</a></h3>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="type-guard/ts.html" style="height: 500px;"></iframe>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="type-guard/js.html" style="height: 500px;"></iframe>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Public / Private</a></h3>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="pub-pri/ts.html"></iframe>
<ul>
<li style="color: red">Not truly private (Only soft private)</li>
<li style="color: red">Unnecessary annotations</li>
<li>Should not be used anymore...</li>
<li>Unnecessary annotations</li>
</ul>
<br>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="pub-pri/js.html"></iframe>
<ul>
<li style="color: green">Truly private properties</li>
<li style="color: green">Clear at first glance what are private by looking at one method</li>
<li>Simple: Everything that that has # is private, the rest is public</li>
<li>You don't even need to annotate that the <code>'#name'</code> is of type=string or that it's private with jsdoc, VS code can figure out by the constructors argument that name was of type string (judging by the default argument value)</li>
</ul>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Generics in JSDoc</a></h3>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="generic/ts.html"></iframe>
<ul>
<li style="color: red">Too compact to read</li>
<li style="color: red">Doesn't Really make it more readable</li>
</ul>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="generic/js.html"></iframe>
<ul>
<li>Anyone with zero knowledge of jsdoc or typescript can understand whats going on by only looking at the JavaScript bits</li>
</ul>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Importing external / exported types directly in JSDoc</a></h3>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="import/ts.html"></iframe>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="import/js.html"></iframe>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Annotating destructured parameters</a></h3>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="annotate/ts.html"></iframe>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="annotate/js.html"></iframe>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Optional arguments</a></h3>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="opt-arg/ts.html"></iframe>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="opt-arg/js.html"></iframe>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Don't respect dynamic <code>import()</code> when compiling to commonjs</a></h3>
<p>CommonJS do support dynamic <code>import()</code> from commonjs since v12.17, TypeScript don't see it that way.`</p>
<p>TypeScript replace `import` with `require` and breaks esm-only imports</p>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="wrong-cjs/ts.html" style="height: 520px;"></iframe>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="wrong-cjs/js.html" style="height: 520px;"></iframe>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">TypeScript don't support ESM very well...</a></h3>
<p>Even doe you can transpile to es modules 1:1 with some target configuration, TypeScript is pretty bad at handling extensions and have totally ignored the <a href="https://github.com/microsoft/TypeScript/issues/16577">problem</a> ever since 2017 up until today and said: "We don't want to touch it, or automatically fix the extension problem, we rely on `require()` to do the job of resolving index and extension-less stuff" to summarize it shortly and marked it as "work as intended"</p>
<p>So developers did just simply add `.js` as recommended by the by some guides like the <a href="https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c">Pure ESM package</a>.</p>
<ul>
<li>Add {"type": "module"} to package.json</li>
<li>Add the `.js` extension at the end of imports</li>
</ul>
<p>For Deno users this is also a big problem. They don't treat remote http import any differently than browser and requires explicit path to the other file and wants you to write `'./ModalBackground.ts'` and `../index.ts` - never `../` or `../index.js` when you only got a `index.ts` file</p>
<p>So, the best thing to do is to not to publish Noncompiled TypeScript packages. TypeScript adds compile time overhead so it will take longer time to load</p>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="bad-esm-support/ts.html" style="height: 520px;"></iframe>
<ul>
<li>There isn't any file './ModalBackground.js' file, only a ./ModalBackground.ts</li>
<li>What if you actually have `allowJs=true` and want to import a .js file? ignore the extension</li>
<li>What should it do when there is a `ModalBackground.js` and a `ModalBackground.ts` file in same directory, what file should it load, it's impossible to do: `import('ModalBackground.ts')`</li>
</ul>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="bad-esm-support/js.html" style="height: 520px;"></iframe>
<br>
<br>
<br>
<br>
</div>
</div>
</div>
</div>
</section>
<section>
<div class="inner">
<div id="post" class="comparison">
<h3><a href="#public_private">Things TypeScript gets wrong</a></h3>
<div style="columns: 2">
<div>
<h4>TypeScript</h4>
<iframe loading="lazy" src="wrong/ts.html" style="height: 650px;"></iframe>
<ul>
<li>Something TypeScript really should be better at is Symbol.toPrimitive and how type casting really works in JavaScript.</li>
</ul>
</div>
<div>
<h4>JavaScript</h4>
<iframe loading="lazy" src="wrong/js.html" style="height: 650px;"></iframe>
</div>
</div>
</div>
</div>
</section>
<ul class="quote-slider">
<li id='quote0' style='right: 20%'>
"JavaScript is a relaxed language, and it's nothing that need to be fixed."
</li>
<li id='quote1'>
"JavaScript is not a language that is designed to be used in a strict way."
</li>
<li id='quote2'>
"If you want a strict language and get near native speed, don't settle for TypeScript or JavaScript. Use an actual typed language and compile to wasm instead."
</li>
<li id='quote3'>
"TypeScript could one day be totally obsolete/unnecessary when/if <a href="https://github.com/sirisian/ecmascript-types">Optional Static Typing</a> becomes a thing."
</li>
<li id='quote4'>
"TypeScript will always stand in the shadow of javascript and be one step behind"
</li>
<li id='quote5'>
"TypeScript is never going to be the language of the browser, Chrome tried implementing Dart and failed."
</li>
</ul>
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.3/jquery.min.js"></script>
<script>
jQuery($ => {
var i = 0
slideCount = document.querySelectorAll('.quote-slider li').length
setInterval(() => {
$("#quote" + i).animate({ right: "120%" }, 1500)
i++
if (i > (slideCount - 1)) { i = 0 }
$("#quote" + i).css("right", "-60%")
$("#quote" + i).animate({ right: "20%" }, 1500)
timeout()
}, 10000)
})
</script>
</div>
</div>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-R6C6PTKR9G"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-R6C6PTKR9G');
</script>
</body>