mseepgood

5 ms·

1.
by mseepgood 28d ago
"May well be added at some point" it said and added they were at some point.
2.
by mseepgood 2mo ago
It's not good Go code anyway. In Go you would use a for loop. Just because Go has generics nowadays doesn't mean you should abandon good taste and write ML/Haskell/Rust/C# in it.
3.
by mseepgood 2mo ago
Isn't that just how one falls asleep? I've been doing this every evening for decades.
4.
by mseepgood 3mo ago
Of all the messages they could have sent they chose the most boring.
5.
by mseepgood 4mo ago
He's probably dead by now.
6.
by mseepgood 5mo ago
> It seems to me that humans often fall into the trap of anthropomorphism. That's true, but they also often fall into the trap of exceptionalism.
7.
by mseepgood 6mo ago
This text lacks information about why it is being sunset.
8.
by mseepgood 6mo ago
A third that will never have a wife.
9.
by mseepgood 7mo ago
> We would immediately build better telescopes to track it precisely, refine its trajectory models, and begin developing propulsion systems capable of interception That's not what would happen. We wouldn't mobilize. We'd f
10.
by mseepgood 7mo ago
With a statically compiled language it is usually culled through dead-code elimination (DCE), and with static linking you don’t ship entire libraries.
11.
by mseepgood 7mo ago
The question is how many decades each user of your software would have to use it in order to offset, through the optimisation it provides, the energy consumption you burned through with LLMs.
12.
by mseepgood 7mo ago
Our railways don't need sabotage - trains fail to run anyway.
13.
by mseepgood 10mo ago
So why do people still design declarative languages?
14.
by mseepgood 10mo ago
> Octals must start with zero and then o/O literals. No, the o/O is optional (hence in square brackets), only the leading zero is required. All of these are valid octal literals in Go: 0600 (zero six zero zero) 0_600 (zero unde
15.
by mseepgood 10mo ago
You're looking at the wrong production. They are octal literals: octal_lit = "0" [ "o" | "O" ] [ "_" ] octal_digits .
16.
by mseepgood 1y ago
The values for x and y should't come from your brain, though (with the exception of 0). They should come from previous index operations like s.indexOf(...) or s.search(regex), etc.
17.
by mseepgood 1y ago
Delegation is key
18.
by mseepgood 1y ago
So he only did four hours of actual work per day.
19.
by mseepgood 1y ago
Is it some kind of CORBA?
20.
by mseepgood 1y ago
You don't even have to write proper sentences. "me get error X how fix here code:" usually works.
21.
by mseepgood 1y ago
Is asking good questions or making clear requests what people now refer to as 'prompt engineering'?
22.
by mseepgood 1y ago
The second most popular issue was adding generics. So it's probably not a resistance to change.
23.
by mseepgood 1y ago
> sometimes a decision is better than nothing Not in this case. The most popular Go proposal/issue of all times was 'leave "if err != nil" alone': https://github.com/golang/go/issues?q=i
24.
by mseepgood 1y ago
It's good to have languages with different approaches to design and and with different design philosophies.
25.
by mseepgood 1y ago
- It has poor visibility, it hides control flow branches in a single statement / expression. That's one of the reasons Go got rid of the ternary operator in favor of an if statement where each branch has to be on its own line. - I
26.
by mseepgood 1y ago
One reason I consider Rust's approach worse than Go's.
27.
by mseepgood 1y ago
How would you set a breakpoint on the error return case?
28.
by mseepgood 1y ago
Sometimes doing nothing is the right thing to do. (Quote from Until Dawn) Go chose not to change the error handling - Nature remained in balance.
29.
by mseepgood 1y ago
Or the 2006 London incident, where a Putin critic was irradiated by a radioactive source in his stomach.
30.
by mseepgood 1y ago
They were composed by Ennio Moricons.

More ›