Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
goto11
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
121.
▲
by
goto11
4y ago
Smaller customers are often happy to hire a freelancer directly without the overhead of going through a middleman - as long as they trust the freelancer. Larger organizations tend to prefer hiring consultants through agencies since it is si
122.
▲
by
goto11
4y ago
XML contains a scheme/validation language, the DTD. The hard part is getting independent parties to agree on a common data exchange format. Processing the data in code is the easy part.
123.
▲
by
goto11
4y ago
I consider this a feature. XML specifies a data exchange format. How this is loaded into memory depends on your use case, language etc. You can use a DOM if this is appropriate or serialize into custom or native data structures. A browser r
124.
▲
by
goto11
4y ago
> thing called HTML which of course was a bit lacking in specification and uniformity at the time. HTML was actually pretty well specified except for one crucial omission: How a user agent should treat invalid HTML. XML simply declared t
125.
▲
by
goto11
4y ago
But the purpose of unit tests is to show that the code under test is correct , i.e. that min() return the smallest input, not just a random value of the same type. Static typing cannot do that, so it is in no way a substitute for unit test
126.
▲
by
goto11
4y ago
Accounting and banking does not allow epsilons. You always need to be able to account for every last cent on every account and every transaction. And the precision you need is fixed, so there is no purpose in using floating points. I guess
127.
▲
by
goto11
4y ago
If you want a version of typeof without this quirk it is trivially easy to write a typeof2023() function with the desired behavior. And it would be fully backwards compatible with existing code and existing browsers. No need to fork the lan
128.
▲
by
goto11
4y ago
So proving that `min(number, number)` returns a number is 99% as good as a unit test which shows that it returns the smallest number?
129.
▲
by
goto11
4y ago
> It tests at compile time that some function f takes A and returns B. That covers 99% of all possible input/output which you technically have to do in an untyped language. Sorry, I don't understand what you are saying here. By
130.
▲
by
goto11
4y ago
Type annotations are not comparable to unit tests at all. Unit tests verifies correctness of the behavior, not just the types. E.g. if you have a mathematical function like min(), unit tests can verify it return the smallest of the inputs.
131.
▲
by
goto11
4y ago
The web became successful because of the constrained formats of URL's, HTTP and HTML. This allowed linking between uncoordinated parties and it allowed indexing and searching. In contrast, powerful executable "black box" obj
132.
▲
by
goto11
4y ago
According to Wikipedia, HTML 4 was published in 1997, XML in 1998 and XHTML 1.0 in 2000, so it is unlikely there was any backporting from XHTML 1.0 to HTML 4. The issue around DTD's is confusing because browsers use the <!DOCTYPE>
133.
▲
by
goto11
4y ago
The three XHTML DTD's (Transitional, Strict, Frameset) were just copied from the HTML 4.0 spec, so they are independent of the HTML/XHTML divide. There are really three independent things in play: - DTD's define a set of vali
134.
▲
by
goto11
4y ago
XHTML 2.0 was not backwards compatible with HTML and was therefore doomed from the start. It would never have succeeded.
135.
▲
by
goto11
4y ago
Quirks mode is a backwards-compatible rendering mode which retains certain historical bugs in the CSS implementation. It is completely independent of the HTML/XHTML divide which is about the syntax of HTML.
136.
▲
by
goto11
4y ago
RDF is independent of (X)HTML and W3C kept control of RDF and related standards. It is true that RDF have failed to live up to its promise, but this have nothing to do with WHATWG.
137.
▲
by
goto11
4y ago
WHATWG did the right thing because W3C had basically abandoned HTML at the time. A fork of the spec was the only was forward for the web. But WHATWG is fully controlled by the browser vendors where W3C was more neutral.
138.
▲
by
goto11
4y ago
Editor-in-the-browser was re-introduced with `contentEditable` in IE6.
139.
▲
by
goto11
4y ago
Dan Harmon is a great storyteller, but this system, and indeed all these "universal story structure" systems all either: 1) Are so generic they doesn't say anything useful (like a horoscope which fit everybody). 2) Only match
140.
▲
by
goto11
4y ago
There is often a meta-hoax which vastly overstates how many people believed a hoax in the first place. For example the myth about the War of the Worlds radio show causing mass panic. The article mention "hundreds phoned in the followin
141.
▲
by
goto11
4y ago
What "marketing buzzwords" are you referring to?
142.
▲
by
goto11
4y ago
In any case, the TS spec is a superset of the JS spec, since it incorporates the JS spec. If you don't consider the JS spec as part of the TS spec then they are disjoint sets. But the TS spec cannot be a subset of the JS spec since t
143.
▲
by
goto11
4y ago
> All JS programs are also TS programs, but not vice versa. There's more JS programs in the world than TS programs. I think you are confusing terminology, because those two statements are contradictory.
144.
▲
by
goto11
4y ago
So you are saying the implementation of the Typescript language are a subset of all JavaScript implementations? I guess that is true in a certain sense. But this does not contradict the fact that TypeScript as a language is a superset of Ja
145.
▲
by
goto11
4y ago
TypeScript is a superset of JavaScript because any JavaScript program is also a Typescript program but not vice versa. There is no contradiction. > TS as a language is a superset of JS language. TS as a spec is a rough subset of JS spec.
146.
▲
by
goto11
4y ago
"Extends" does not mean it extends the type to contain more members, it means it extends instances to have more properties, thereby creating a subset or subtype. Perhaps it is confusing that TypeScript uses terms from both set-the
147.
▲
by
goto11
4y ago
A major source of tech debt is when you get a better understanding of the domain and realize some of the early design decision was not optimal.
148.
▲
by
goto11
4y ago
The only solution I have seen work: Paying back text debt should be an integrated part of regular development rather than a separate task. When you change or add a new feature in an area of the code, you clean up tech debt in the area, at l
149.
▲
by
goto11
4y ago
So the AST is transferred over the wire? How is it serialized?
150.
▲
by
goto11
4y ago
> I'm not an expert at JS internals, but I'm under the impression that if you call a function ten times, its code has to be interpreted ten times, so you get ten, temporary, abstract syntax trees. This is not the case even in a
More ›