cel1ne

"They are not needed anywhere." -> This should have been "They are not needed everywhere."

Types are important and necessary.

Can you skip them in a typed language? Yes, just use any, Object or whatever the equivalent.

Can you add them to an untyped language? No.

They are not needed anywhere. But I argue that especially JavaScript module-systems would have benefited greatly from them.

A million lost hours in fixing obscure "undefined is not a function"-errors from output of highly dynamic pluggable build/transpiler-systems like webpack, requirejs, babel, buck etc. could have been avoided.

JDBI.

1. Try a completely functional language like Haskell once to learn about side-effects.

2. If you do multi threading: Look into Immutability and communicating sequential processes

3. Use static analysis / linters / code checkers for every language you use. They provide a lot of tips. There are linters for bash and Dockerfiles as well.

I wrote an autohotkey script for windows to assign alt-* to most shortcuts which would require ctrl-*. Alt is physically where Macs Cmd is, so I had Alt-A for Cmd-A, Alt-F for Cmd-F, Cmd-W and so forth. This made a big difference.

Also I installed EasyWindowSwitcher and assigned it to a shortcut, which gave me window-cycling like in mac.

Have you tried a combination of quick-reading and taking notes.

If it's about train of thoughts: for each tab try formulating and writing down a question that came to your mind while reading it.

That is the creative takeaway and it might ease your mind enough to close the tab.

Use CDNs for delivering JavaScript libraries instead of including everything into custom bundles.

React could be transferred ONCE to the browser-cache instead of hundreds of times.

Copying the text gives: “ch a i r m a n ' s s tat em en t” Reconstructing the original text is a difficult problem to solve generally.

Why not looking for stretches characters with spaces between them, then concatenate, check against a dictionary and if a match is found, remove the spaces.

“On_April_7,_2013,_the_competent_authorities”

Same here.

"Where earlier reductions were largely negated by rising imports, the past decade has seen genuine cuts in the amount of CO2 for which the UK is responsible."

- https://www.carbonbrief.org/analysis-why-the-uks-co2-emissio...

Not really, since everybody who cloned a repo has a full copy of everything.

Reminds me of the saying that writing git was just a backup strategy for Linus Torvalds: FTP-mirrors were the first step to ensure that the kernel was never lost, git was needed to mirror the source-history as well.

Use REST for reading, but RPC-style calls for writing. Benefits:

1. Every write-call is a transaction

2. You can have complex filtering and sorting in the read/access side of your API without having to worrying about the update-side of things.

3. You can evolve the read-API, even change semantics and return different objects and again, not worry about transactions.

4. You are not limited to the HTTP-standard.

Here are also some good tips: https://www.vinaysahni.com/best-practices-for-a-pragmatic-re...

Very well put.

The argument is that GPT3 has no understanding of the world, just superficial understanding of words and their relationships.

We don't really know what "understanding of the world" means in humans. We just "see it when it's there".

We might be radically different from GPT-3, or we might not. Our way of learning is different in any way.

Something that came to my mind: Various GPT-3 answers resemble answers given by children: Mostly correct, but having misunderstood some crucial point.

In real human learning and conversation these points are easily corrected by feedback by explanation: "You see, the point is no one wears bathing suites to work".

Which would then be incorporated as new wisdom.

Maybe this feedback-mechanism is what GPT-3 is missing. Maybe we should talk to it.

sponge

Why not use > file?

mispipe

In bash there's PIPESTATUS for that.

You can call C with Java.

I did this 15 years ago, before I gave gentoo a spin. I compiled my kernel for many years (make menuconfig).

Bottom line: It's not worth it.

I use debian now.

You have to adapt while writing: If I want a "more important" sentence to be read, I put on it's own paragraph.

A drawing teacher put it like this: "Draw what's there, not set-pieces". (meaning the reusable furniture components in theaters)

AFAIK, you don't have to ship the source to be GPL-compliant, you just have to provide it upon request.

Unfortunately no HDR support.

The difference is that computer-on-your wrist are personal. They got cheaper and cheaper as everyone started to buy one.

I can't imagine everyone buying a spaceship, or even 1 in 10.000 people, if spacecraft costs were 10.000 times the super-computer costs of the past.

So no comparable revenue-stream to further drive down cost.

I use an AppleTV connected to a 43-inch 4k monitor [1]. No crappy TV-software and it's a proper screen, with proper response-time to use for the laptop as well.

[1] https://www.amazon.com/Philips-Monitor-Bdm4350uc-42-5in-3840...

I wonder if you could write a program that scans javascript-dependencies for function-usage that could be replaced by suites like lodash, to find and replace "leftpad-style dependencies".

https://en.wikipedia.org/wiki/X_Window_System

For example, warming itself has been highly nonuniform. It's not that every day, every location on earth is X degrees warmer.

What is happening is this:

For a location and a time somewhere on earth plot a curve depicting the probability of it's temperature. The highest point in the middle is the average, typical temperature for that day, but of course there are less probable outliers left and right, like in a normal distribution.

What climate change does is

a) it flattens that curve, meaning more varying temperatures, unusually hot or unusually cold days, become more likely and

b) it moves that entire curve to the right, so that the average overall temperature becomes hotter, even though there are more cold outlier-days than before.

I don't think so, i switched to Firefox about two years ago, after the major upgrades, and I think it's way snappier, faster and more usable than chrome.

You are right, you could say: "It's a problem, it doesn't matter if it's us or not, but we have to fix it".

Question is whether this helps the debate or not. It could help.

If you don't say "it's us", you generally mean that it's a natural occurring phenomenon / cycle. And with that generally comes the assumption "...therefore we don't need to fix it, because it will fix itself.".

I like the way the 350.org science page put's it:

   1.  It’s warming.
   2.  It’s us.
   3.  We’re sure.
   4.  It’s bad.
   5.  We can fix it.

Thanks for the tip. I actually memorized C4, not C1, mistake on my side.