kipple

> About 10 years ago we had a similar problem with jQuery. Often you would go to Stack Overflow to find the answer to a JavaScript problem you were having only to find the answer was given in jQuery.

I don't understand this argument. TypeScript is just JS + type annotations — you should be able to boil away any fluff and be left with functioning JS. Whereas jQuery has actual runtime logic that would need to be reworked if you wanted a $-free solution.

The author goes on to say:

> This was even worse when the question was along the lines of “How do you do (jQuery thing) in JavaScript?”.

When would anyone ask "How do you do (TypeScript thing) in JavaScript"?

> The 1960s broke authority, and it has never been repaired. It discredited adulthood, and adulthood has never recovered. The attributes of adulthood—responsibility, maturity, self-sacrifice, self-control—are no longer valued, and frequently no longer modeled. So children are stuck: they want to be adults, but they don’t know how. They want to be adults, but it’s easier to remain children. Like children, they can only play at being adults.

Is this true? Did adult-aged humans feel "grown up" pre-1960s?

Or, is a fundamental lack of certainty more intrinsic to our nature?

Has anyone seen this yet? I just ran across it, and it looks interesting...

Oo, this does watch face does look nice https://www.hodinkee.com/articles/the-eerie-beauty-of-the-ap...

Thank you, I'm glad you enjoyed it. I love the week skip too, interesting to see the shape change over the year.

Undocumented feature: if you hold down "w" or "shift+w" keys you can skip through weeks even faster.

It would be fun to see this with local daylight hours mapped to the squares, so I could get a feel for where my consumption is at within "daylight" vs the whole "day"

SunCalc is a good tool for this, if you're interested: https://github.com/mourner/suncalc

(I've used it on a personal project, and the API was a little awkward but the results are good: https://daylight.website/)

For web apps: TypeScript with Next.js & Vercel

Next.js takes care of your full-stack web app (client routing, server APIs, the fuzzy world of SSR/SSG/ISR) plus your whole dev/prod build (zero-config React & TypeScript, minimal config ESLint & Prettier)

And Vercel deploys it as easily as `npx vercel --prod`, or just hooking your GitHub repo up to the project through their web UI so it deploys on push. Their integration will even show the deployment status for each commit, from within GitHub.

It's a delightfully streamlined process, and a suite of tools that all have large communities and rich ecosystems.

Agreed. I particularly like the look of their `<Switch>/<Match>` component[1]:

  <Switch fallback={<div>Not Found</div>}>
    <Match when={state.route === "home"}>
      <Home />
    </Match>
    <Match when={state.route === "settings"}>
      <Settings />
    </Match>
  </Switch>

Which doesn't seem to have an analog in the React babel-plugin[2] or standalone lib[3]

[1] https://www.solidjs.com/docs/latest/api#%3Cswitch%3E%2F%3Cma...

[2] https://github.com/AlexGilleran/jsx-control-statements

[3] https://github.com/samuelneff/react-control-flow

Agreed, this "primary color based on language" is a cute idea, but awful to actually consume. JavaScript (my most visited) is a low-contrast orange (especially when wrapped with inline-code styling).

Overall the new design does feel more slick, I think it has potential. But I wish they had focused more on readability/usefulness over "cuteness".

This site doesn't need to be "fun" — they've successfully created a useful tool. They should be proud of that, and keep building in that direction.

> At the time, Tesla noted that they were not selling their stake in Bitcoin and that they planned to resume taking Bitcoin payments once the network shows a higher mix of renewable energy.

Is there a hope of this happening, with Bitcoin? I thought proof-of-work coins were fundamentally energy intensive, and proof-of-stake coins (like Ethereum 2.0) are the only way out of it.

Nice! That makes it more attractive.

Depth mapping would be great too, like I could pin virtual artifacts to my physical environment? Yes please.

Would you spend all day working in VR?

A few months ago, I would say no.

But I got myself a Quest 2 for Christmas, and now... maybe.

AR would make it better though, so I'm not just floating disconnected in digital space. I see in their homepage hero banner background[0] you get a floating window with video of your hands. It would be nice if the whole background is a passthrough to reality, and then you float your OS windows on top of that.

[0] https://simulavr.com/

Right now, here on the bleeding edge of VRPC, it would be something like $999. I'm seeing it as a Chromebook when they first came out — interesting concept, but not yet proven in an actual working environment.

Alternatively, some sort of money-back guarantee would be nice. "Try working in VR for 30 days, see how you like it."

Hah, agreed. There's one route in particular where Google consistently wants me to drive straight across a 5 lane road.

I switched to Apple Maps for the gentler routes, and the (IMO) more attractive UI when being displayed via CarPlay.

This would be a big (but exciting) departure from the current TS goal of "Impose no runtime overhead on emitted programs." [1]

Recently, I've been using Zod [2] and find it to be a satisfying equivalent: you define a schema, and then you get both a TS type AND a JS parser/validator (which works as a TS typeguard).

[1] https://github.com/microsoft/TypeScript/wiki/TypeScript-Desi... [2] https://github.com/colinhacks/zod

> No standing water means no ideal spots to lay their eggs. In the ’60s, Potter accomplished this by digging drainage ditches built into the park’s base layers, effectively draining the swamp in its entirety.

Seems like this is the real meat, I wish the article had gone into more detail here.

Looks like eslint is working on a new set of rules that would help with these currently-unprotected any cases: https://github.com/typescript-eslint/typescript-eslint/issue...

> Create a rule which uses type information to determine when you're inadvertently breaking type safety by using an any, potentially without knowing.

> Often libraries (or even the typescript defs themselves) can have weak(/lazy) types which return any. If you're not careful, you can inadvertently introduce anys within your codebase, leading to bugs that aren't caught by the compiler.

This particular example is close to my heart: the definition files for things like JSON.parse() were written before the "unknown" type was introduced as an alternative to "any"

And because this "any" is coming from an external definition file, it can't be caught by tsc's --noImplicitAny nor eslint's no-explicit-any

Those two rules allow us to protect us from our own code, but not external definitions/libraries. Relevant GitHub issue here — https://github.com/microsoft/TypeScript/issues/26188

Depending on your mortgage interest rate, have you considered continuing the 18 years and investing your extra cash in index funds? Market returns ~10% over 20 years, so if your mortgage is 6% or less it's in your best 'interest' to continue.

It's hard to search for, but it appears to mean "Developer Experience" — https://medium.com/@koba04/performance-and-dx-in-frontend-48...

At first I expected this to be some new version, but nope, it's the original. I love that this repo[0] hasn't been touched significantly in 6 years and it's still going strong.

[0] https://github.com/haxiomic/GPU-Fluid-Experiments

Nice! Glad to help

Another nit to pick: "Copying the message: the message is serialized, copied, sent over, and then de-serialized at the other end. The page and worker do not share the same instance, so the end result is that a duplicate is created on each pass. Most browsers implement this feature by automatically JSON encoding/decoding the value at either end."

This is untrue, modern workers use the structured clone algorithm[0][1], not JSON.stringify() & JSON.parse(). This algorithm has many advantages, such as preserving object references, supporting built-ins like Maps and Sets, and allowing cyclical/recursive structures.

[0] https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers... [1] https://www.w3.org/TR/2012/CR-html5-20121217/infrastructure....

I always love seeing anything following the philosophy of emergence[0], I think the "composition of simple rules leading to organic unpredictable complexity" is a powerful metaphor that can help understand nearly any natural phenomena.

It's exciting to see the increasing emergence of this idea (see what I did there) in modern science & industry, such as in MIT's Mediated Matter lab[1].

[0] https://en.wikipedia.org/wiki/Emergence [1] http://matter.media.mit.edu/tools

3 accounts created within the last 20 minutes leaving 5 positive comments between the lot of them.

That's not weird.

Wouldn't that be explained by the next paragraph?

> The distinction between the two astronauts makes sense only when you reintroduce the rest of the universe. In the classic interpretation of general relativity, then, inertia exists only because you can measure it against the entire cosmic gravitational field.

This seems like a case of a spherical cow[1], the thought experiment is simplified down to only these two astronauts. No fabric of space around them, and so no inertia.

Perhaps it would have been less confusing if the thought experiment had used two normal people floating in nothingness? The presence of spacesuits makes it seem like they exist within some sort of reasonable environment.

[1] https://en.wikipedia.org/wiki/Spherical_cow

All four users (including OP) commenting so far had their accounts created between 45 minutes and an hour ago.

That's not weird.

Be sure to check out the original article at the excellent Quanta Magazine: "CHAPTER 2: NETWORK TAPESTRY How Quantum Pairs Stitch Space-Time" https://www.quantamagazine.org/20150428-how-quantum-pairs-st...

As well as the prior article: "CHAPTER 1: ENTANGLED WORMHOLES Wormholes Untangle a Black Hole Paradox" https://www.quantamagazine.org/20150424-wormholes-entangleme...

So many JS libraries these days, I can barely smell which ones are real anymore

This is pretty clearly spam, right? These aren't examples from exemplary professionals, these are examples of one particular CV tool in action.

And they don't even look very good, they're all very "try hard" resumes. I'm assuming real top-paid professionals have conservative resumes clearly stating their accomplishments, without the unnecessary flash & pizzazz.

Not sure how this made it to the front page of HN....